Training new Browser Staff: Difference between revisions

From genomewiki
Jump to navigationJump to search
No edit summary
(Removed CVS references and added git and redmine references)
Line 5: Line 5:
* get a computer
* get a computer
* get a login
* get a login
* get a redmine account
* email for UCSC and SOE
* email for UCSC and SOE
* key card
* key card
Line 12: Line 13:
* set up ssh authentication among dev, beta and your linux box
* set up ssh authentication among dev, beta and your linux box
* check out a copy of the kent source tree
* check out a copy of the kent source tree
* get git commit access
* set up nightly cron to update kent source tree
* set up nightly cron to update kent source tree
* build your own sandbox
* build your own sandbox
Line 18: Line 20:
* vi (vimtutorial) -- or other editor
* vi (vimtutorial) -- or other editor
* mysql
* mysql
* CVS (or git, if we git it) tutorial: http://www.soe.ucsc.edu/research/compbio/cvsdoc/cvs-tutorial/cvs_tutorial_toc.html
* git -- see [[Working_with_Git]] and [[Getting_Started_With_Git]]


== Browser ==
== Browser ==
Line 30: Line 32:
# machine layout
# machine layout
# data flow
# data flow
# using cvs: day to day commands, and cvs reports/pair review process
# using git: day to day commands, and git reports/pair review process
# trackDb.ra and trackDb table
# trackDb.ra and trackDb table
# make docs
# make docs
# pushQ
# pushQ
# (for Q/A only) QAing a "normal" track (using the [[New_track_checklist]] perhaps)
# redmine
# (for Q/A only) QAing a "normal" track (using the [[New_track_checklist]])
##joinerCheck
##joinerCheck
# static docs
# static docs
# makefiles
# makefiles
# /usr/local/apache vs. the cvs tree
# /usr/local/apache vs. the git tree
# hgcentral
# hgcentral

Revision as of 18:51, 21 October 2010

(see also: Getting Started for Browser QA Engineers and Getting Started for Browser Dev Engineers)

Logistics

  • get a computer
  • get a login
  • get a redmine account
  • email for UCSC and SOE
  • key card
  • add your contact information to your .plan file
  • copy .tcshrc and .bashrc from one of us (both are needed to run scripts)
  • copy .hg.conf and .hg.conf.beta from someone, so you can run hgsql and scripts that use it.
  • set up ssh authentication among dev, beta and your linux box
  • check out a copy of the kent source tree
  • get git commit access
  • set up nightly cron to update kent source tree
  • build your own sandbox

Tools

Browser

  • Open Helix tutorials
  • ASHG hands-on tutorial

Data

Training person-to-person (in rough chronological order)

  1. machine layout
  2. data flow
  3. using git: day to day commands, and git reports/pair review process
  4. trackDb.ra and trackDb table
  5. make docs
  6. pushQ
  7. redmine
  8. (for Q/A only) QAing a "normal" track (using the New_track_checklist)
    1. joinerCheck
  9. static docs
  10. makefiles
  11. /usr/local/apache vs. the git tree
  12. hgcentral