hi,
The Atomic devel builds are now running from cron again, after a 2 week lag, they now run every 12 hours, midnight and midday UTC. These builds now also run with a complete toolchain update taking place before the build gets run.
The build script is now in git itself : https://github.com/CentOS/sig-atomic-buildscripts/blob/master/build_ostree_c... and the cron worker will git pull, before running this, so updates are consumed immediately. That does make line 10 to 12 of this script completely redundant, but I've left it in as an indicator.
Build runs are logged at : http://buildlogs.centos.org/centos/7/atomic/x86_64/Builds/
And the ostree repo remains at : http://buildlogs.centos.org/centos/7/atomic/x86_64/repo/
Once the installer image starts building, we can push that to http://buildlogs.centos.org/centos/7/atomic/x86_64/ which would in turn allow the vagrant and image builds to also run.
Regards,
On 16/04/15 18:42, Karanbir Singh wrote:
hi,
The Atomic devel builds are now running from cron again, after a 2 week lag, they now run every 12 hours, midnight and midday UTC. These builds now also run with a complete toolchain update taking place before the build gets run.
http://buildlogs.centos.org/centos/7/atomic/x86_64/Builds/ has content, and we can verify that we have 12 hrly builds.
As the next step, I'd like to now expand this to run a build for every git branch in the upstream sig-atomic-buildscripts repo. What / how should we handle naming those ?
one option might be to leave http://buildlogs.centos.org/centos/7/atomic/x86_64/ as the place to deliver the master branch, and then create http://buildlogs.centos.org/centos/7/atomic-BranchName/x86_64/ for each branch, would that work ? We would also need new centos-release-atomic-<branchname> in each of those, otherwise the ostree upstream repo url will point into the default master's repo.
regards,
On Sat, Apr 18, 2015, at 03:48 AM, Karanbir Singh wrote:
On 16/04/15 18:42, Karanbir Singh wrote:
hi,
The Atomic devel builds are now running from cron again, after a 2 week lag, they now run every 12 hours, midnight and midday UTC. These builds now also run with a complete toolchain update taking place before the build gets run.
http://buildlogs.centos.org/centos/7/atomic/x86_64/Builds/ has content, and we can verify that we have 12 hrly builds.
Awesome, thanks! Having this script public and well known with logs is a big step forwards.
As the next step, I'd like to now expand this to run a build for every git branch in the upstream sig-atomic-buildscripts repo. What / how should we handle naming those ?
One thing that Ari and I have been exploring is using Jenkins for these sort of "post-Koji" tasks as it has a wealth of plugins (messaging, irc notification etc.), and supports "parameterization" of jobs which is is exactly what you mentioned above.
I'll see if we can get the prototype published soon, it's using jenkins-job-builder (which btw is now packaged for Fedora https://bugzilla.redhat.com/show_bug.cgi?id=1208904 and should be easily built on C7)
hi
On 18/04/15 14:58, Colin Walters wrote:
As the next step, I'd like to now expand this to run a build for every git branch in the upstream sig-atomic-buildscripts repo. What / how should we handle naming those ?
One thing that Ari and I have been exploring is using Jenkins for these sort of "post-Koji" tasks as it has a wealth of plugins (messaging, irc notification etc.), and supports "parameterization" of jobs which is is exactly what you mentioned above.
We might take the short route and add something to the mash runs for the time being, longer term getting a plugin that can mark a build as fail, when a test fails would be good.
I'll see if we can get the prototype published soon, it's using jenkins-job-builder (which btw is now packaged for Fedora https://bugzilla.redhat.com/show_bug.cgi?id=1208904 and should be easily built on C7)
This is sort of where I started from initially, having the work just get done and triggered from a jenkins job, Lets see how it works for the that model, we can always just go to this anytime. When we looked at JJB, it seemed limited in what plugins and what things it might be able to do, but its worth a revisit if it helps solve these issues.
On Sat, Apr 18, 2015 at 08:48:25AM +0100, Karanbir Singh wrote:
On 16/04/15 18:42, Karanbir Singh wrote:
hi,
The Atomic devel builds are now running from cron again, after a 2 week lag, they now run every 12 hours, midnight and midday UTC. These builds now also run with a complete toolchain update taking place before the build gets run.
http://buildlogs.centos.org/centos/7/atomic/x86_64/Builds/ has content, and we can verify that we have 12 hrly builds.
Out of curiosity, I followed http://buildlogs.centos.org/centos/7/atomic/x86_64/Builds/20150420_120001/lo...
and see errors:
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ---------- installer No config file: /srv/sig-atomic-buildscripts//installer.ini ---------- Vagrant usage: rpmostreecompose-main [-h] -c CONFIG [--ostreerepo OSTREEREPO] [-i IMAGES] [--name NAME] [--tdl TDL] [--virtnetwork VIRTNETWORK] -o OUTPUTDIR [--overwrite] [-k KICKSTART] [--vkickstart VKICKSTART] [-p PROFILE] [-v] rpmostreecompose-main: error: argument -c/--config is required ---------- liveimage usage: rpmostreecompose-main [-h] -c CONFIG [--ostreerepo OSTREEREPO] [--overwrite] -o OUTPUTDIR [-p PROFILE] [-k KICKSTART] [--tdl TDL] [--name NAME] [--diskimage DISKIMAGE] [--skip-subtask SKIP_SUBTASK] [-b YUM_BASEURL] rpmostreecompose-main: error: argument -c/--config is required ----------
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
and
sending incremental file list 20150420_120001/
seems to only cary the new directory
right ?
Daniel
As the next step, I'd like to now expand this to run a build for every git branch in the upstream sig-atomic-buildscripts repo. What / how should we handle naming those ?
one option might be to leave http://buildlogs.centos.org/centos/7/atomic/x86_64/ as the place to deliver the master branch, and then create http://buildlogs.centos.org/centos/7/atomic-BranchName/x86_64/ for each branch, would that work ? We would also need new centos-release-atomic-<branchname> in each of those, otherwise the ostree upstream repo url will point into the default master's repo.
regards,
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 20/04/15 14:58, Daniel Veillard wrote:
Out of curiosity, I followed http://buildlogs.centos.org/centos/7/atomic/x86_64/Builds/20150420_120001/lo...
and see errors:
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ---------- installer No config file: /srv/sig-atomic-buildscripts//installer.ini
yeah, adding the content into the git repos should resolve this.
and
sending incremental file list 20150420_120001/
seems to only cary the new directory
right ?
yes,
-
Colin Walters -
Daniel Veillard -
Karanbir Singh