[Ci-users] Question about plugin installation: build-pipeline

Mon Oct 5 08:47:23 UTC 2015
Fabian Arrotin <arrfab at centos.org>

Hash: SHA1

On 02/10/15 18:23, David Moreau Simard wrote:
> 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=2&modificationDate=1340695983000
>  David Moreau Simard Senior Software Engineer | Openstack RDO
> dmsimard = [irc, github, twitter] 
> _______________________________________________


Let me add that Build Pipeline plugin to the list of plugins to be
installed during next maintenance window (as we have to restart
Jenkins for that too)
I guess no other project mind having that plugin installed.

- -- 
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
Version: GnuPG v2.0.22 (GNU/Linux)