CI-users May 2017

ci-users@lists.centos.org

5 participants
3 discussions

Splitting a job and making dependencies
by Václav Pavlín 02 Jun '17

02 Jun '17

Hi all, I am very new to Jenkins, so please bear with me:) We have this JJB config: https://github.com/almighty/almighty-jobs/blob/master/devtools-ci-index.yaml Where there is this job-template: https://github.com/almighty/almighty-jobs/blob/master/devtools-ci-index.yam… The script basically copies content of git cloned directory and runs build script. If that run is successful it deploys the resulting docker image to OpenShift. We want to deploy images by tag - which corresponds to git commit hash, so it gets templated in by oc process. The problem is that there are templates which have more parameters and we have taken care of this with a small script in this repostory: https://github.com/openshiftio/saas/ So my goal is to use that saas tool to do the deploy instead of plain oc process > oc apply. As we have multiple templates which have different scripts, I'd like to avoid code duplication - I don't want to copy&paste the oc process/oc apply or the script calls around in the file. So my thinking to solve this was to create some kind of hierarchy - I found something about dependencies and something called multijob where a job would trigger a build phase (build a docker image) and a deploy phase (oc apply). The key part is that if any of the phases fail, whole job fails. Also, deploy phase must not be triggered when build phase fails. What would be the correct approach with JJB to solve this? Is this wrong thinking? Am I missing something from the Jenkins point of view? I know this would be ideally solved by pipelines, but I don't think that is an option at the moment. Looking forward to comments and suggestions, Vašek -- Red Hat Developer Tools team Brno, Czech Republic Phone: +420 739 666 824

2 2

Jenkins SafeRestart Tonight 19:59PM Eastern (23:59 UTC)
by Brian Stinson 26 May '17

26 May '17

Hi Folks, We'll be doing a saferestart tonight at 23:59 UTC in order to update a plugin. As usual, the quiet period will start 1 hour beforehand so running jobs can clear out. Any jobs that are triggered during the quiet period will be added to the queue and executed after Jenkins finishes. If there are any questions, please let us know here or in #centos-devel on Freenode. Cheers! -- Brian Stinson CentOS CI Infrastructure Team

1 1

unscheduled outage : empty inventory this morning, but now solved
by Fabian Arrotin 08 May '17

08 May '17

Hi, Just to let you know that this morning, some jobs used all the nodes that we still had already in "provisioned" state at the Duffy level, but that after that, no nodes were available to fulfil the other requests. This is due to a network issue we suffered during the week-end (and already contacted the IT team managing the switches to analyze the root cause), and because of that, the dispatcher process (in charge of deploying in advance the duffy nodes) put all provisioning steps into failed mode. I updated that back to normal, and dispatcher started to reinstall nodes and put those back into the "Ready" pool. Sorry for the inconveniences -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

CI-users May 2017