Hi Folks,
We'll be pausing jobs starting at 2300UTC in preparation for our
Maintenance period.
Stay tuned here, and to #centos-devel for updates.
Cheers!
Brian
Hi Folks,
Just a reminder that we'll be having a 1-hour maintenance period at
23:59UTC (7:59PM US Eastern) to install Jenkins updates and new plugins.
We will be pausing jobs 1 hour beforehand.
Feel free to join us in #centos-devel on freenode for any questions
during that time.
Cheers!
Brian
Hi,
I'd like to register a new vm/slave for the libguestfs hypervisor:
- fedora-22-i686 (libguestfs-ci-f22-i686slave or
libguestfs-ci-f22slave-i686, I guess)
could you please provide credentials for it?
Thanks,
--
Pino Toscano
You have been invited to the following event.
Title: ci.centos.org Maintenance Period 27-Oct-2015
We will have a maintenance period from 8:00PM to 9:00PM US-Eastern time to
install a batch of plugins and update to the latest version of Jenkins. We
will be pausing execution of new jobs 1 hour before this period.
We will be monitoring #centos-devel on Freenode for questions during this
time.
--
Brian Stinson
CentOS Infrastructure Team
When: Tue Oct 27, 2015 7pm - 8pm Central Time
Where: #centos-devel on Freenode
Calendar: ci.centos.org
Who:
(Guest list has been hidden at organizer's request)
Event details:
https://www.google.com/calendar/event?action=VIEW&eid=OHNzZHNvaXZvYmszNGdlM…
Invitation from Google Calendar: https://www.google.com/calendar/
You are receiving this courtesy email at the account ci-users(a)centos.org
because you are an attendee of this event.
To stop receiving future updates for this event, decline this event.
Alternatively you can sign up for a Google account at
https://www.google.com/calendar/ and control your notification settings for
your entire calendar.
Forwarding this invitation could allow any recipient to modify your RSVP
response. Learn more at
https://support.google.com/calendar/answer/37135#forwarding
CI/infra team requests installation on ci.centos.org jenkins of these plugins:
Build Pipeline Plugin
Multijob Plugin
BuildResultTrigger Plugin
Thanks in advance,
Steve Linabery
Hi All,
Looks like we have a few hosts assigned to the Openstack-Puppet project
that have been hanging around for a while. I'd like to add this project
to our automatic reaper script.
Any objections? Any hosts that need to stick around while you get data
off?
Cheers!
Brian
hi guys,
we have some machines allocated to atomicapp that have been around for a
few weeks, I setup a couple, but the others look like either orphaned
machines or someone else's static hosts.
Since we are adding in the machine reaper scripts, just want to make
sure that noone has a machine there they want data extracted from first ?
this is specific to the machines allocated to the atomicapp project.
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
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi
does anyone have notes on howto setup the jobs in jenkins in a way
that they get run on repo changes in cbs.centos.org/repos/ ? I know we
are doing this for a couple of jobs already, but unsure how it was setup
.
cheers,
- --
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJWGY7CAAoJEI3Oi2Mx7xbtCOwIAI0zd11pcdMvCiGrL5pUukEz
vDrQ8YdPb7wza00SVL6g4de3HJNYvx19TifNJOgF+D55zvBe3l9ySl179Dx8FGEV
mFruqRRBOCLXB7i/YYdH/KKQc6S3JKfspGDSnpZ5lfv/5HmDRb0ZQrKTbk927Kk0
EjX5lCzpyVCqMsMvCMSlmGxhek0WuOrT/FBg6E0YiOp/THT/2YafQwVQc7D4yJtB
jagB3838eHBMFWV3PplOMlYjucsew1du4YObPDgjTtqNaJDbTR4o/H7hSvdDdkVn
mCw/G0ZT8+kXZx2yr6+SzatO5IyLwEHiwcYhd9vReolvKKVh91oZwVj4HfU5GMA=
=L2t0
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Just to let you know that we've migrated today to a new node the
following roles :
- CI artifacts storage server (see
https://wiki.centos.org/QaWiki/CI/GettingStarted#head-a46ee49e8818ef9b50225…)
- Internal backup server
- Internal http mirror (aka mirror.ci.centos.org)
Should you encounter an issue, feel free to either report it on
https://bugs.centos.org, on this list, or in #centos-devel on
irc.freenode.net.
Kind Regards,
- --
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlYUwBMACgkQnVkHo1a+xU4G0ACbBGs7j5QC35khgiZk2rxnVC0e
hRQAn1ZMP88vW8KGjrHTUUWDrTj3I60i
=Z/dR
-----END PGP SIGNATURE-----
Hi there,
We're currently working on improving the RDO and RDO Manager CI.
As part of those efforts, I'd like to use the build-pipeline plugin
[1] to build a clear dependency flow of jobs to stay in the logic of
"fail fast" and avoid needless jobs where possible.
At a bird's eye view, it would look like this:
"Install RDO on a single node and do very minimal testing" ->
"Install RDO on multiple nodes with decent/exhaustive testing" ->
"Promote the tested set of packages in the 'passed-ci' repository"
This means we wouldn't bother doing exhaustive testing if the basic
installation or the minimal testing fails and we would only promote
the tested set of packages if the exhaustive testing passes.
What's great with the pipelines plugin is that the dependencies are
very clear and the dashboard it provides is very insightful to see
what is passing or what is failing [2].
We will eventually be moving the RDO and RDO Manager CI jobs to the
ci.centos infrastructure so knowing whether or not we can use this
plugin is important. There are other ways around doing this (with
another plugin, multi jobs) but it's not as straightforward, IMO.
Please let me know what you think,
Thanks !
[1]: https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin
[2]: https://wiki.jenkins-ci.org/download/attachments/54723106/bpp1.png?version=…
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]