CI-users June 2016

ci-users@lists.centos.org

11 participants
6 discussions

CI Maintenance Window 27-May-2016 01h00 - 02h00 UTC (26-May-2016 21h00 - 22h00 EDT)
by Brian Stinson 24 Oct '16

24 Oct '16

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

5 10

pip install python-cicoclient fails
by Marek Skalický 27 Jun '16

27 Jun '16

Hi, I am using ci.centos.org in sclo-sig group. I am using slave01.ci.centos.org and some tests are failing when installing cicoclient (log attached). Even with new virtual environment 'pip install python-cicoclient' is failing. After 'pip install --upgrade pip' it is working fine. Does anyone know where is a problem? Is it somehow possible to fix this on system-level? (not to have to upgrade pip in every workspace) Thanks, Marek

1 0

Adding CBS Client Integration to ci.centos.org
by Brian Stinson 23 Jun '16

23 Jun '16

Hi Folks, In the buildsys meeting this week we discussed adding CBS client integration for jobs in ci.centos.org I think the easiest way to get this going would be to generate credentials for each project that would like to perform CBS operations (build, tag-build, untag-build etc.), and place the certificates in the workspace on the slaves. If this scenario is acceptable, we'd like to pilot this by Friday of this week. In that case you could add a separate build step to call /usr/bin/cbs with any koji operations you might need to do. In the future we can probably consider the Jenkins koji plugin, but that looks to need some work on storing credentials for multiple users. Are there others interested in integration with CBS? If so I'd like to get an idea of how you'd like to integrate and what operations you'd perform during your jobs. Cheers! -- Brian Stinson

3 4

Embeddable Build Status Plugin for CentOS CI
by Hardy Ferentschik 22 Jun '16

22 Jun '16

Hi all, just wanted to let you know that I requested to install the Embeddable Build Status Plugin on CentOS CI. See https://bugs.centos.org/view.php?id=10983 I would like to display a build status icon in the GitHub README for the projects which I configured on CentOS CI. Does anyone have any thoughts around it? --Hardy

6 6

Workflow to integrate a Github project with ci.centos.org?
by Ratnadeep Debnath 10 Jun '16

10 Jun '16

Hi all, [1] explains on the workflow to integrate a Github project with ci.centos.org to trigger builds on every commit or on a pull request. However, it misses to mention that we need a "secret key" to setup Webhook access to [2]. And, then users are left puzzled as to why the integration is not working. AFAIK, this secret key has to be created for a project by the admin of ci.centos.org and handed out to the project owner manually. This is not a great workflow for a new project to start using ci.centos.org as an alternative for Travis CI. Please feel free to correct me if I am wrong. [1]: https://wiki.centos.org/QaWiki/CI/GithubIntegration [2]: https://ci.centos.org/ghbrphook Thanks, rtnpro -- Ratnadeep Debnath, https://www.waartaa.com GPG Fingerprint: 033C 8041 A0E9 CDBA 2E02 B785 2119 5486 F245 DFD6

5 8

centos-ci as collaborator on repository
by Hardy Ferentschik 08 Jun '16

08 Jun '16

Hi there, I have been following this guide in order to setup GitHub integration for a build job I created on ci.centos.org - https://ci.centos.org/job/vagrant-service-manager/ The integration works in the way that if I push to master or create a pull request, the build starts and does it thing. However, it seems the plugin can now write back the status of a build. I keep seeing exceptions like this in the build (which otherwise complete fine): GitHub pull request #259 of commit f511fb644e90ce050f49efbee14d3c57b9ed8380, no merge conflicts. Setting status of f511fb644e90ce050f49efbee14d3c57b9ed8380 to PENDING with url https://ci.centos.org/job/vagrant-service-manager/51/ and message: 'Build started sha1 is merged.' FileNotFoundException means that the credentials Jenkins is using is probably wrong. Or the user account does not have write access to the repo. I added centos-ci as collaborator to the vagrant-service-manager plugin, however, it says now "awaiting centos-ci response". I think centos-ci needs to accept the collaboration invite. How does this happen? Is there anything I need to do or is there someone manually reviewing invites? If this is really the problem, it would be nice to add a sentence or two about this part of the process. Thanks, Hardy

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

CI-users June 2016