Hi there,
I heard that the Atomic team would be potentially interested in reusing the cico test for our Vagrant images centos/6 and centos/7, but their images are not built in CBS.
I refactored cloudinstance-vagrant-test to accept a single parameter, BUILD_INFO, containing a JSON string (an array of hashes containing build information). This should allow other projects to use it if desired, since it doesn't parse the CBS logs anymore. This part was now moved to cloudinstance-vagrant-build and cloudinstance-vagrant-manual-build, which generate a JSON string like the following pretty-printed equivalent:
[ { "major_release": "6", "provider": "virtualbox", "url": "https://cbs.centos.org/kojifiles/work/tasks/4846/114846/centos-6-1-1.x86_64...." }, { "major_release": "6", "provider": "libvirt", "url": "https://cbs.centos.org/kojifiles/work/tasks/4846/114846/centos-6-1-1.x86_64...." }, { "major_release": "7", "provider": "libvirt", "url": "https://cbs.centos.org/kojifiles/work/tasks/4848/114848/centos-7-1-1.x86_64...." }, { "major_release": "7", "provider": "virtualbox", "url": "https://cbs.centos.org/kojifiles/work/tasks/4848/114848/centos-7-1-1.x86_64...." } ]
The scripts are in https://github.com/lpancescu/cloudinstance-vagrant-cico-util.
Hope this helps, Laurențiu
On 13/10/16 10:59, Laurentiu Pancescu wrote:
I heard that the Atomic team would be potentially interested in reusing the cico test for our Vagrant images centos/6 and centos/7, but their images are not built in CBS.
Jason, could we use these for the atomic vagrant box's ? we would need to publish the box to ci artifacts and then trigger the job.
Lala, could we maybe use this as an additional level of tests for the adb box as well ?
Regards,
On Thu, Oct 13, 2016 at 4:02 PM, Karanbir Singh kbsingh@centos.org wrote:
On 13/10/16 10:59, Laurentiu Pancescu wrote:
I heard that the Atomic team would be potentially interested in reusing the cico test for our Vagrant images centos/6 and centos/7, but their images are not built in CBS.
Jason, could we use these for the atomic vagrant box's ? we would need to publish the box to ci artifacts and then trigger the job.
we have the first part -- this is where downstream, continuous and alpha vagrant images are published on each run:
https://ci.centos.org/artifacts/sig-atomic/downstream/images/ https://ci.centos.org/artifacts/sig-atomic/centos-continuous/images/cloud/la... https://ci.centos.org/artifacts/sig-atomic/centos-continuous/images-alpha/cl...
I'll look at the triggering part
Lala, could we maybe use this as an additional level of tests for the adb box as well ?
Regards,
-- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
-
Jason Brooks -
Karanbir Singh -
Laurentiu Pancescu