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
+ ci-users, not sure TripleO CI folks are subscribed to centos-devel.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Sep 7, 2016 11:56 AM, "Karanbir Singh" <mail-lists(a)karan.org> wrote:
> hi guys,
>
> I am trying to track down exactly how the tripleo jobs - specially the
> large image builds are being run. Were trying to track down network
> bottlenecks and the tripleo jobs are consistently coming up as the
> biggest pain points.
>
> Is there an overview available to look at for the work flow and data
> flow within the ci infra itself ?
>
> 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(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Folks,
We will be rebooting some of the CI infrastructure on Wednesday
September 7th starting at 06h00 UTC to apply updates. We will have the
usual quiet period starting 1 hour beforehand to let other job finish.
Below are the machines/services affected:
- - ci.centos.org Jenkins Interface
- - slave01.ci.centos.org (your Jenkins slaves will be reconnected for
you)
- - Duffy node provisioner
- - artifacts.ci.centos.org
- - Network services through the CI gateway (short outage)
We will keep the list up to date as we progress through this window. If
there are any questions or concerns please let us know.
Cheers!
- --
Brian Stinson
CentOS CI Infrastructure Team
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJXyaB6AAoJEIMGvNKzCweMZC0P/0wWQkU5ZWhmPyzSUKUzRAGw
uSau9ZV0BRAc9dM4djKraz9eNp+LoNjCiscEdrd5us8hVgNWtPMfhUqsg3AwJ3ym
6OXH7ja3ABideiP0X3Ycg2KmzBi14ti9NuNgY+WqPlYyly0r9nT0hv0qSomHDTU/
e7ot3Z56WYXk4ZQXb6/aOqgT5PajLJlnhT1N6LC8G+WU7Gx0qlzWRtIoxDGiOnAM
vjJv7i9tyJ8YLJWMUhoEL35b/UZGfMK5gGR/DFKdAxdzmE4CZD60oTFcQ1xn9qqD
JHSoiKy+5kY7dKETZspKltTaOgc+zFjxMeNVGcw8zP/uiZ4FVIVkgDuRlMzibMFm
7c3FqiPhAkg/QfTxIcFI27PQ6xxD7HpYtu0dvUxpqElRaXSYxHxP7deU6ENCiFkE
XQr764FW0K8+47b20cgJ4J0wBFeMLBXJnHBHzaEWmuJtHh26fYq0ncFOlA3rD/KO
0eJakH8uSHEUaco67EVc2b+SuL/mUEaA7T0Msh7LQllPPdV+Yx6otUkJmZCcK35/
WFvnANcrXzRoT7gkVr/jSiVlYELgPzFl71bKLDInpbmUCskbZlEIH5riqOVqsH9X
+cx1x/eR4YLug6XGATCjCs3Q80Aqae8LExmjSfaN3zazXXWx4esDV2CXv6aBc281
ZcrFRmeyKr0mxT+S3YvY
=l2+a
-----END PGP SIGNATURE-----
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