CI-users

ci-users@lists.centos.org

1 participants
418 discussions

Start a nNew thread

networking down?
by Colin Walters 21 Oct '16

21 Oct '16

A lot of the https://ci.centos.org/view/Atomic/ jobs are failing to DNS resolve github.com.

2 1

Introducing Linch-Pin, Hybrid cloud provisioning using ansible
by Clint Savage 20 Oct '16

20 Oct '16

Hi all, Recently, as part of the CentOS PaaS SIG and Continuous Infra, We've been working on some basic tooling for CI. One of the tools that came out of this work, is Linch-Pin. It's a fairly simple tool for multi-cloud provisioning that's starting to get some traction. Currently, it's being used to provision Duffy instances inside for one Jenkins job in CentOS CI[1], but can do so much more. If you're interested in learning more about it, or trying it out, I'd love to hear your take. It's all open source and ready for you to try it out. I've written a blog post about Linch-Pin, and plan to do a series over the coming months. Check out the first installment in the series. http://sexysexypenguins.com/posts/introducing-linch-pin/ A link to the project is in the blog post, but also included below[2]. Additionally, there is some documentation[3], which is in the process of being improved. I'd love feedback on the blog post. And we're obviously interested in feedback on the project as well. Cheers, herlo 1- https://ci.centos.org/job/origin-from-source-0-test-matrix/ 2- https://github.com/CentOS-PaaS-SIG/linch-pin 3- http://linch-pin.readthedocs.io

1 0

Jenkins Job Builder is now available on the CI Agents
by Brian Stinson 19 Oct '16

19 Oct '16

Hi Folks, We finished up the packaging and have installed Jenkins Job Builder 1.6.1 on slave01.ci.c.o Cheers! -- Brian Stinson CentOS CI Infrastructure Team

3 2

Jenkins Gerrit comment trigger broken again
by Attila Darazs 18 Oct '16

18 Oct '16

Hi folks, I think the Gerrit Trigger plug-in got updated again (to 2.22.0) and broke the retriggering of jobs by Gerrit comments. If it got updated please downgrade to 2.21.1. If it's this version, something is still broken, but then I don't know what. :) This is our conversation in #centos about it last time this happened (on the 6th of September): (01:43:13 PM) adarazs: https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger -> Version 2.22.0 (released Aug 17 2016) -> JENKINS-30821 - Add comment-added comment as job parameter (pull #295) -> https://issues.jenkins-ci.org/browse/JENKINS-30821 (01:43:13 PM) adarazs: -> looks to me like they were messing with this exact part of the plug-in and this is a contender for having this specific error appear while trying to fetch the comment that triggered the job. (01:43:25 PM) arrfab: adarazs: version is 2.22.0 so it seems the last one (01:44:35 PM) adarazs: it might help to downgrade to Version 2.21.1 (released Jun 07 2016) -Attila

2 2

Setting up JJB service jobs in CICO
by Ratnadeep Debnath 14 Oct '16

14 Oct '16

Hi, I want to create a job in ci.centos.org, which creates other Jenkins jobs, using Jenkins Job Builder. However, JJB is not installed on the Jenkins slaves or master node. I'd like to know what would be the best way to create such service jobs in CICO. Thanks, rtnpro

4 3

Refactoring the CI test for Vagrant images
by Laurentiu Pancescu 14 Oct '16

14 Oct '16

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

3 2

Infinite loop with multiple repos?
by Laurentiu Pancescu 13 Oct '16

13 Oct '16

Hello, while adapting the cloudinstance-vagrant-manual-build job on ci.c.o, I thought to skip the manual cloning of a second repo via shell scripts and add a second repo via the Jenkins UI (I expected it would be cloned into a sibling directory to the directory hosting the clone for the first repo, but it seems to have just overwritten it). When I ran the job, it not only failed, but retried the job immediately, causing some sort of infinite loop. Cancelling the current job was useless, since a new one started immediately, and I ended with more than 250 failed jobs in just 1-2 minutes; I had to disable the project to stop it. I only had a trigger to start cloudinstance-vagrant-test on success - no idea why it retried again and again... Is that expected behavior? I switched to manual git cloning, this works without issues. Laurentiu

1 0

ci.centos.org is now running the latest Jenkins LTS (Jenkins 2)
by Brian Stinson 13 Oct '16

13 Oct '16

Hi Folks, During the migration this week we went ahead and migrated our Jenkins instance to the latest LTS (which means Jenkins 2!). The core functionality is completely backwards compatible with Jenkins 1, and we kept all of our plugins pinned to the versions we had running before. Just a reminder for the only known effect: - If you're using JJB to configure some of your jobs you _may_ need to set 'query_plugins_info = False' in the [jenkins] section of your config file. If you notice any trouble, please let us know here. Cheers! -- Brian Stinson CentOS CI Infrastructure Team

2 1

[infra] : Hardware migration status (full/correct version)
by Fabian Arrotin 11 Oct '16

11 Oct '16

As announced some time ago ( https://lists.centos.org/pipermail/centos-announce/2016-September/022065.ht… ) , there was a big hardware migration/DC relocation happening yesterday that impacted several of our public services. Here is a small report of that migration, that finally took less time that previously announced. * 2016-10-10 - 1pm UTC : we started to preconfigure all changes, and powered down all the services in correct order * 2016-10-10 - 2pm => 6pm UTC : hardware was moved/migrated * 2016-10-10 - 6pm => 8pm UTC : hardware was (in serial order) plugged back in and ipmi/oob interfaces reconfigured, and network started to be validated * 2016-10-10 - 8:30pm UTC : https://accounts.centos.org was back online and operational * 2016-10-10 - 9pm UTC : https://cbs.centos.org was back online but builders were still disabled for validation * 2016-10-10 - 9:45pm UTC : https://cbs.centos.org : builders were enabled and working again * 2016-10-11 - 3:30am UTC : https://ci.centos.org now fully operational (after some network reconfiguration needed post-migration, and validations Thanks a lot to Brian Stinson (on-site) and DC people who helped for that migration (Matt, Jon, Nathan, Nina, Phil) Should you encounter an issue , feel free to discuss with us in #centos-devel on irc.freenode.net PS : sorry for the previous and incomplete mail : sent by accident before finished and probably due to lack of coffee and short night ... -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

3 2

[infra] : Hardware migration status
by Fabian Arrotin 11 Oct '16

11 Oct '16

1 0

← Newer
1
...
28
29
30
31
32
33
34
...
42
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

CI-users