Notes, SCM Migration Project: GK tools meeting
10/22/07, 2pm PDT
Attendees:
Bonnie Corwin
Danek Duvall
Ken Erickson
Mike Kupfer
Rich Lowe
Dave Marker
Mike Sullivan
* Assumptions
- Consolidation movement will be in multiple phases. The exact number
and nature will depend on how the consolidation works, what tools it
uses, choices it makes, etc. We will move source repositories
outside before full open development is possible (i.e., we will not
wait until everything is perfect).
- Transition gate to Mercurial
- Move the consolidation gate source repository outside to
opensolaris.org
- Enable full open development with equal access to all tools,
process, etc.
- Moving the gate outside = moving the consolidation source repository
outside. It does not necessarily mean the machine that does gate
builds moves outside at the same time.
Will need automation to post archives, packages, etc. to
opensolaris.org. Will also want an internal clone so can do things
like browse using NFS.
* GK tools list on genunix
- List sections
- Tools that run automatically (currently labeled "Task")
- Tools that are run manually by gatekeepers (currently
labeled "gatekeeper tools and scripts")
- Could include gate hooks with tools that run automatically.
- Tool specifics
- pbcheck: all its checks should run before the putback, at least
ideally. Doesn't have all the checks we eventually want.
- add-gateling: still want some way to notify gatelings. Probably
an alias that people sign up for manually.
- clone_update: needed for SFW. Need to clarify for Ken whether we
keep a separate repo or just use tags. Most important thing for
SFW. Can't use just tags, to handle case where master repo is
external and build workspace is internal.
- rtcgen: mostly just need to change to parse putback log (looking
for new packages). Or at least that's what the SFW version needs.
SFW and ON each have their own version.
- Advantage to making things look the same: easier for gk's who have
to deal with both TW and hg gates.
* SFW information
- Plan: Transitioning to Mercurial is the big step. Will
collapse the first two phases (transitioning to Mercurial and
moving the gate outside). Will start new gate from scratch
(i.e., will not preserve history).
- Developer Tools needed
- nightly
- Cadmium
- webrev
- wx
- ws
- GK Tools needed
- clone_update (believe this will become 'hg pull')
- rtcgen
- pbconfirm would be nice; can live without for a while
* Dummy gate
- Need dummy gate set up for testing.
- Space available on two SPARC build machines (steam and train).
- Ken will choose one.
* Miscellaneous
- Do we need a formal test suite? Nice to have. Not mandatory.
- Don't believe SFW uses SCCS keywords so don't expect surprises
there.
- Project gate for SCM Migration Project is on opensolaris.org.
Gate contains all the tool work done so far.
* Next steps
- Ken: set up SFW hg repository and let everyone know where it is.
- Ken: choose machine for dummy gate
- Ken: set up dummy gate
- MikeS/Ken: set up email on dummy gate; work on rtcgen and
clone_update
- MikeK: set up email hooks and accounts on opensolaris.org machines
- Bonnie: check on status of webrev
- Bonnie: check on status of test framework setup
- MikeK: send out information about hooks.
- MikeK: make sure there is an sfwnv-notify alias.
