...
Make these changes on the release branch and on master of configuration.
Make a test tag
TODO: i'm trying ginkgo.rc1 with just test branches, not tags
Because real releases are made from tags, and very occasionally the difference between tags and branches is important, all builds should be done from tags. To make the vagrant boxes from a tag, but not yet mark the release, we'll make a test tag. The tag should use your personal prefix ("you/"), and be named for the release you are working on, but with an additional .n suffix:
...
| Code Block | ||
|---|---|---|
| ||
export OPENEDX_RELEASE=you/test/zebrawood.1rc1.1
git clone https://github.com/edx/configuration.git
cd configuration
git pull; git checkout $OPENEDX_RELEASE
python -m virtualenv -p python2.7 venv
. venv/bin/activate
make requirements
cd vagrant/base/fullstack # or devstack
vagrant up |
...