520571 - enable parallel releases without local symlink changes

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[[e-mail] (:bhearsum)]

Currently, we can do a different release on production-master and production-master02 by locally changing the release_config.py symlink to point to the right branch. We should be able to get rid of this locale change by doing the same thing we do with master1/master2.cfg:
* get rid of release_config.py in the repository
* create release_config1.py and release_config2.py in the repository
* symlink release_config.py -> ../configs/mozilla2/release_config1.py on pm01
* symlink release_config.py -> ../configs/mozilla2/release_config2.py on pm02

Comment 1

[[e-mail] (:bhearsum)]

Attachment: symlink craziness

I tried having master1/master2 import the release config in an attempt to avoid adding these symlinks but I don't think there's any way to get that to work. This is the simplest solution I could find. When deployed, we'll have to symlink the masters to release_config1/2, but since those files are just symlinks to real configs we never have to change the symlinks on the master itself; simply update them in the repository.

The only sucky part about this patch is that it makes running checkconfig locally more annoying, because you have to cp or ls a release_config first.

Comment 2

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 404651 [details] [diff] [review]
symlink craziness

Looks fine to me.

Comment 3

[[e-mail] (:bhearsum)]

Comment on attachment 404651 [details] [diff] [review]
symlink craziness

changeset:   1581:8dcd5fffdebf

Comment 4

[[e-mail] (:bhearsum)]

Updated the masters:
[cltbld@production-master moz2-master]$ rm release_config.py
[cltbld@production-master moz2-master]$ ln -sv ../configs/mozilla2/release_config1.py release_config.py
create symbolic link `release_config.py' to `../configs/mozilla2/release_config1.py'

[cltbld@production-master02 moz2-master]$ rm release_config.py
[cltbld@production-master02 moz2-master]$ ln -sv ../configs/mozilla2/release_config2.py release_config.py
create symbolic link `release_config.py' to `../configs/mozilla2/release_config2.py'

Comment 5

[[e-mail] (:bhearsum)]

Updated the documentation, too:
https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Documentation#Starting_the_automation