Hi there,
My proposed fix for Jenkins causing memory leaks in all major browsers
has now been accepted upstream. [1] Is there any chance of patching
ci.centos.org to include it?
Regards,
Laurențiu
[1] https://github.com/jenkinsci/jenkins/pull/2539
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
As pre-announced earlier this year
(https://lists.centos.org/pipermail/centos-devel/2016-May/014792.html)
we'll have to move a part of our existing hardware to a new DC.
That means that the following public services will be powered off and
unreachable :
- https://cbs.centos.org (Koji build farm front end and also
builders/storage nodes behind)
- https://accounts.centos.org (auth backend)
- https://ci.centos.org (jenkins-driven CI environment and all nodes in
that dedicated/isolated environment)
What does that mean ?
- Nobody from the SIGs (https://wiki.centos.org/SpecialInterestGroup)
will be able to submit build jobs/tasks (so no update at all during that
migration)
- No CI job will be able to track CBS nor external repositories (and so
that means also that http://artifacts.ci.centos.org will be unreachable)
- Not possible for existing users to update their details on
accounts.centos.org, and not possible to create new accounts either
We're working on a plan to minimize the downtime/reconfiguration part,
but at first sight, due to the hardware move of the racks/cabling
parts/etc, the announced downtime will be probably ~48h.
Migration is scheduled for """"Monday October 10th, 1:00 pm UTC time"""".
You can convert to local time with $(date -d '2016-10-10 13:00 UTC')
We'll start to restore services as soon as possible, while working in
coordination with the DC people closely (and after validation about
network ports, connection)
During this period you can come talk to us in #centos-devel and we will
be posting updates there.
on behalf of the Infra team,
--
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
Hi,
It seems that slave "atomicapp-ci-slave01" CI machine is offline in
https://ci.centos.org which handle the CI for vagrant-service-manager
project [1].
Could we make it online? What could the reason for its being offline?
Attached few screenshots for the same.
[1] https://github.com/projectatomic/vagrant-service-manager
Regards,
Budh Ram Gurung
Hi Folks,
We had a report earlier today that presentation of some Multi Jobs was
causing stack traces in the Jenkins interface.
We've tracked this down to an interaction between the presentation layer
and jobs that parameterize downstream jobs with custom attributes. The
best fix for now was to downgrade to Multi Job Plugin version 1.21 which
should now be active.
We'll track the appropriate bugs[0] upstream and make sure this is resolved
for our upcoming move to Jenkins 2.
[0]: https://issues.jenkins-ci.org/browse/JENKINS-38053
Cheers!
--
Brian Stinson
CentOS CI Infrastructure Team
Hello,
With David's help, I've built a better pattern to consume python-cicoclient
alongside JJB. A major goal of this work was to avoid using curl calls to
Github.
In summary, it uses a builder to get nodes and a publisher to release nodes
without leaking. I've created a Github repo[1] with a real-world job (actually
a copy of one of our jobs).
Please let me know if you find this useful and if you have suggestions for
improvements. As I convert more jobs to JJB, it will be more flexible for
requesting more than one node and more than one OS version.
[1]: https://github.com/nigelbabu/centos-ci-sample
--
nigelb
Hi,
As discussed with Attila this morning, there were quite some issues on
the rdo-jenkins.ci.centos.org VM in the last days (leading to jenkins
slave not running and all jobs not running either).
Lot of xfs issues on the /home partition, and no xfs_repair didn't seem
to have helped.
As agreed with Attila, I deployed a rdo-jenkins-2.ci.centos.org VM (on
the same hypervisor) with a reduced vcpu/memory so that he can then
configure it (through the RDO ansible playbooks) and migrate what would
need to be migrated (like probably the jenkins workspace on that node)
After we'll have confirmation that it seems to work fine, we'll shutdown
the previous VM, and we'll change the vcpu/memory settings on the newly
configured VM.
--
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
Hi folks
Retriggering a job or trying to trigger it from gerrit is not working
I'm getting a NullPointerException on
Caused by: java.lang.NullPointerException
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerParameters.setOrCreateParameters(GerritTriggerParameters.java:447)
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener.createParameters(EventListener.java:263)
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener.schedule(EventListener.java:188)
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.retriggerThisBuild(GerritTrigger.java:849)
at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.actions.RetriggerAction.doIndex(RetriggerAction.java:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.IndexDispatcher.dispatch(IndexDispatcher.java:26)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
It looks related to the gerrit plugin. and arrfab found this bug
https://issues.jenkins-ci.org/browse/JENKINS-31198 but I'm not sure on
what to do.
Right now gating is broken because of this
Cheers,
Adriano