Hi Folks,
We will be having a maintenance window starting at 1AM UTC on Friday,
May 27th to do the following work:
- Upgrade to the latest Jenkins LTS
- Upgrade all plugins (including the Github Plugin) to their latest
versions
- Install the Pipeline Plugin (bug: 10825)
- Update the ansible version on slave01.ci.centos.org 1.9.2 -> 1.9.6
- Reboot the storage node
The following services will be affected:
- ci.centos.org: Jenkins Frontend
- artifacts.ci.centos.org: File availability
As usual we will have a quiet period starting 1 hour before in order to
let pending jobs clear out.
If there are any questions please let us know.
Cheers!
--
Brian Stinson
CentOS CI Infrastructure Team
hi
We are going to change the way the backend inventory works to
accommodate different architectures, different type of deployments and
different ways to return/teardown CI hosts.
As a result, users will no longer be able to call the /Inventory API
call for a complete state, you will need to supply your apikey for it to
return anything worthwhile.
For existing calls that already supply the apikey ( I believe the cico
client does ), there should be no change. But for anyone doing a generic
blanket call to get entire stock report, they will get an empty result set.
Is this going to impact anything anyone has in production right now ?
Regards,
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
Hey, to recap there are two things I really like about CentOS CI:
1) The idea that we can more easily share code/ideas/maintenance with
other users in the ecosystem, from RDO to libguestfs, etc.
2) The bare metal provisioning
Relating to #1 though, what I miss right now is a process/model for
actually sharing more with other users. For example, I find myself
wanting better code to manipulate artifacts beyond base rsync,
and I'm curious what others are doing. But how to find their code?
(Reading through the jenkins job UI configuration is too awful to consider,
I'd hope people are using JJB)
So, how about we start a wiki page with links/descriptions to projects
which are using CentOS CI? Can someone with the perms start that?
My entry is:
https://github.com/CentOS/sig-atomic-buildscripts/tree/master/centos-ci
Hello,
could you please set "Commit Status Context" in Jenkins configuration
in "GitHub Pull Request Builder" section to for example "ci.centos.org"
or something different. Or is this a problem?
We would like to run another Jenkins CI for the same github repo, so
this change is required to see all CI results for commit.
For more information see 'context' in https://developer.github.com/v3/r
epos/statuses/#statuses.
Thanks,
Marek
Hi Folks,
A couple of updates on the packages installed on the slaves:
We are now providing version 0.3.10 of python-cicoclient[0] system-wide.
If you are using your own copy in a virtualenv or otherwise, you may
continue to do so. We will be tracking all upstream releases for the
system-wide package.
For those of you working on the cloud setup in ci.c.o, we have the
openstack clients available to you.
If there are any questions please let us know here.
Cheers!
[0]: https://github.com/CentOS/python-cicoclient
--
Brian Stinson
CentOS CI Infrastructure Team
Hi all,
It appears as though the PostBuildScript plugin will be needed for the
matrix and multijob things I'm doing. Could you please add that to the
jenkins instance on ci.centos.org?
Cheers,
herlo
hi,
in the next few days we will deploy an update to the reaper service that
will reclaim hosts 6 hrs after they were deployed; having done some
analytics, it looks as if this will have no impact on anyone since all
the existing successful tests complete in under 6 hrs - however this
helps us reclaim orphaned hosts much sooner.
At the moment, the reaper process reclaims after 24 to 48 hrs of
deployment.
Regards
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
Hi Folks,
We're looking into upgrading ci.centos.org to the latest LTS release (In
the 2.x series). So far this appears to be completely
backwards-compatible with the set of plugins we have enabled, though we
will continue testing over the next few days.
*JJB USERS READ HERE*
If you use Jenkins Job Builder in your projects, can you please test
setting 'query_plugins_info=False' in your jjb.ini file and check for
adverse effects? We are still waiting on a fix in Jenkins to allow
regular users to access the plugin list, but in the meantime it appears
that there are only a few circumstances where this makes a difference.
If all goes well, we will schedule a time and inform the list on our
plans for the upgrade itself. As always if you have any questions,
please let us know here.
Cheers!
--
Brian Stinson
CentOS CI Infrastructure Team
hi guys,
with an increase in the number of slaves, we've noticed that the rdo
jobs are deploying machines at a much higher velocity than before - as a
result the ready pool is consistently hitting the low water mark.
Rather than do an overall quota limit, I'm looking at limiting the
number of duffy deploy's per 10 min cycle, but rather than propose
something I'd like to see what folks think is a reasonable number to
start from ?
regards,
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc