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/log 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 at centos.org > http://lists.centos.org/mailman/listinfo/centos-devel -- Daniel Veillard | Open Source and Standards, Red Hat veillard at redhat.com | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | virtualization library http://libvirt.org/