[heroes] Chameleon dev branch at static.opensuse.org
Hi, We are changing the development model of Chameleon so it is more reliable. https://github.com/openSUSE/chameleon/issues/18 The master branch (https://static.opensuse.org/chameleon/) is the stable branch, well tested and won't be updated frequently. Used by all production sites. The dev branch, which we would like to deploy at https://static.opensuse.org/chameleon-dev/ , is the unstable version for testing and can break now and then. Used for testing sites and local development environment. Need your help to set up the cron job to pull dev branch. Thanks! -- Guo Yunhe / @guoyunhe / guoyunhe.me -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Hello, Am Mittwoch, 4. März 2020, 14:08:41 CET schrieb Guo Yunhe:
We are changing the development model of Chameleon so it is more reliable. https://github.com/openSUSE/chameleon/issues/18
The master branch (https://static.opensuse.org/chameleon/) is the stable branch, well tested and won't be updated frequently. Used by all production sites.
The dev branch, which we would like to deploy at https://static.opensuse.org/chameleon-dev/ , is the unstable version for testing and can break now and then. Used for testing sites and local development environment.
Need your help to set up the cron job to pull dev branch. Thanks!
In theory I can do this, and it "just" needs some additional lines in our salt code (pillar/role/static_master.sls). In practise the CI for our salt repo is currently broken, which prevents merging the needed changes in the usual way :-( If this is an urgent change, there's probably a way to bypass the CI and to merge it manually. So - how urgent is this? As a sidenote - please wait with merging the .gitmodules change. The deploy script/cronjob checks the sha256sum of all .gitmodules files, and refuses to deploy anything until someone reviews the changed .gitmodules and adjusts the expected checksum. (Background: git submodules are always bound to a specific revision, but for static.o.o we always want the latest - which means we do separate clones on static.o.o instead of using git submodules.) Regards, Christian Boltz --
My personal opinion is that bugzilla should be sent in a rocket to the oblivion and pick up something sane and usable, [...] Do you really mean the core Bugzilla software or perhaps some infrastructure software like this "Internet in CHAINs" thingy or whatever its actual name is? [> Cristian Rodríguez and Johannes Meixner in opensuse-factory]
-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Hi Christian, No, it is not urgent. I mean as long as it happens before 2021 :-P The plan changed a bit. We want to use /chameleon/ as unstable release and /chameleon-2.0/ as stable release. You can check the PR https://github.com/openSUSE/static.opensuse.org/pull/6 So let's do it in a safe/regular way. -- Guo Yunhe / @guoyunhe / guoyunhe.me 2020年3月4日 23:21 来自 opensuse@cboltz.de:
Hello,
Am Mittwoch, 4. März 2020, 14:08:41 CET schrieb Guo Yunhe:
We are changing the development model of Chameleon so it is more reliable. https://github.com/openSUSE/chameleon/issues/18
The master branch (https://static.opensuse.org/chameleon/) is the stable branch, well tested and won't be updated frequently. Used by all production sites.
The dev branch, which we would like to deploy at https://static.opensuse.org/chameleon-dev/ , is the unstable version for testing and can break now and then. Used for testing sites and local development environment.
Need your help to set up the cron job to pull dev branch. Thanks!
In theory I can do this, and it "just" needs some additional lines in our salt code (pillar/role/static_master.sls).
In practise the CI for our salt repo is currently broken, which prevents merging the needed changes in the usual way :-(
If this is an urgent change, there's probably a way to bypass the CI and to merge it manually.
So - how urgent is this?
As a sidenote - please wait with merging the .gitmodules change. The deploy script/cronjob checks the sha256sum of all .gitmodules files, and refuses to deploy anything until someone reviews the changed .gitmodules and adjusts the expected checksum. (Background: git submodules are always bound to a specific revision, but for static.o.o we always want the latest - which means we do separate clones on static.o.o instead of using git submodules.)
Regards,
Christian Boltz --
My personal opinion is that bugzilla should be sent in a rocket to the oblivion and pick up something sane and usable, [...]
Do you really mean the core Bugzilla software or perhaps some infrastructure software like this "Internet in CHAINs" thingy or whatever its actual name is? [> Cristian Rodríguez and Johannes Meixner in opensuse-factory]
-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
Hello, Am Mittwoch, 4. März 2020, 22:31:18 CEST schrieb Guo Yunhe:
No, it is not urgent. I mean as long as it happens before 2021 :-P
;-)
The plan changed a bit. We want to use /chameleon/ as unstable release and /chameleon-2.0/ as stable release. You can check the PR https://github.com/openSUSE/static.opensuse.org/pull/6
So let's do it in a safe/regular way.
It took a while, and I had to do some small changes in the salt setup (I originally didn't expect deploying two branches from the same repo), but - finally done ;-) Regards, Christian Boltz --
Maybe a change from Firefox to Iceweasel could be the solution. So, you are suggesting jumping from the mud right into the swamp...? [> Kim Leyendecker and Cristian Rodríguez in opensuse-factory]
-- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org
participants (2)
-
Christian Boltz -
Guo Yunhe