bbc / mobileci-jenkins-support

Mobile ci support plugin forked from Jenkins rebuild plugin

TODO:

DONE remove config options from job config screen

DONE enable "auto rebuilding"

change icon

DONE create pipeline DSL to use with plugin

create the other side of promote, a global promote object

• should contain things like the commit hash to build
• the last promoted hash or build number
• the last promoted version number
• maybe version number should be a real object with properties like major, minor, patch etc

can we get changelogs?

Read Me

About

Project for building PromoteRebuilder jenkins plugin.

Plugin provides variables global mobileCiSupport and stagePromotion.

Setup

Checkout project

Run 'mvn clean verify' to run all the tests.

After that you should be able to run tests from IDE such as IntelliJ as well.

Building project

To create a new build artifact update pom.xml with version name, then run hpi:create.

Output will be {project}/target/promoterebuild.hpi

Plugin dependancies

Probably makes sense to try and keep plugin dependencies up to date with the jenkins environment that plugin will be installed on. Tests don't mean much unless they are reflective of where the plugin will actually run.

// TODO what jenkins stuff should match what dependancies in pom.xml.

mobileci-jenkins-support's Issues

Migrate existing stored values from global domain to bespoke domain

Given a custom domain can be used to store values (Issue #1) it would be beneficial to migrate values stored in the global domain.

Given a credential is stored in the Global domain called: job/JOB_NAME/KEY_NAME
When the pipeline script for the JOB_NAME job is going to attempt to retrieve the value for the key KEY_NAME
Then the value stored in the Global domain should be moved to the custom domain and the value retrieved

Values stored via mobileCiSupport.store(..., ...) pollute the global credential store

The following pipeline will create a job/JOB_NAME/test credential in the global credential store:

stage("store") {
    mobileCiSupport.store("test", "value")
}

We could use a bespoke credential domain to prevent polluting the global store.