Difference between revisions of "WSMEStackForgeTransition"

Revision as of 20:29, 22 July 2013

Importing WSME to StackForge

Based on http://ci.openstack.org/stackforge.html

Preparing the Repository

The existing DVCS repository is a Mercurial repo at https://bitbucket.org/cdevienne/wsme/

1. Convert to git with hg-git plugin
2. Add .gitreview file in anticipation of adding the repo to the openstack gerrit server
3. Add a CONTRIBUTING file to the repository to match the other StackForge projects
4. Push the resulting git repository somewhere so we can use it as a source for importing

Gerrit ACLs

Reviewers and contributors need LaunchPad IDs.

It is not necessary to sign the OpenStack CLA for this project.

Core Group Membership

A new wsme-core group will be created to have review permissions.

A new wsme-release group will be created to have release permissions.

Both groups will start with Christophe de Vienne, Doug Hellmann, and anyone else Christophe designates as members. The memberships can be changed over time as needed.

Jenkins Jobs

WSME uses Shining Panda right now: https://jenkins.shiningpanda.com/wsme/

The capabilities of StackForge and Shining Panda don't line up 100%.

1. SF has no Python 2.5 or 3.2 test servers
2. SF has no PyPy test servers
3. There are 67 different tox environments defined in the WSME tox.ini. We don't want to consume that many servers for every patch to WSME, so we will need to figure out how to batch them up.
   1. The run-tox.sh script used by infra assumes that the argument is the Python version. We should change that to be the tox env name, so we could have the WSME builders defined to run several sets of tests in a row.