Page MenuHomePhabricator

Evaluate deployment-pipeline-jenkins plugin
Closed, ResolvedPublic

Description

The pearson bitesize group has created a jenkins plugin (https://github.com/pearsontechnology/deployment-pipeline-jenkins-plugin) that accomplishes much of what we need to accomplish for the Release Pipeline project. We should evaluate whether the pearson plugin meets requirements as laid out in T158812: Gather requirements for build manifest specification

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 7 2017, 6:18 PM
thcipriani closed this task as Resolved.May 10 2017, 5:20 PM
thcipriani claimed this task.

This was installed on the ci-staging cluster and we reviewed the plugin in the pipeline meeting: https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/Deployment_pipeline/2017-03-14#Pearson_Deployment_Pipeline_Jenkins_Plugin

Mostly we found:

  • This approach has some interesting tricks:
    • Interesting use of seed jobs plugin
    • init.groovy.d to build base jobs that in-turn build real jobs based on environment variables
  • This creates a Jenkins master per repository
  • This relies heavily on a Pearson base image that has 64 layers
  • This approach is highly-specific to the way Pearson runs things, we will not be using this plugin.