The current official plugin workflow-cps does provide a way to retrieve a Jenkinsfile through a SCM, such as Git. The goal of this plugin is to provide another way to retrieve Jenkinsfiles via HTTP calls.
This is a way to separate to concerns : source code (SCM) and built artifacts (binaries). Built artifacts are immutable, tagged and often stored on a different kind of infrastructure. Since pipelines can be used to make production loads, it makes sense to host the libraries on a server with a production-level SLA for example. You can also make sure that your artefact repository is close to your pipelines and share the same SLA. Having your Jenkins and your artefact repository close limitsr latency and limits network issues.
The HTTP Pipeline Plugin was implemented to retrieve Jenkinsfiles through HTTP (or HTTPs) instead of a SCM.
- Create a pipeline job
- Select the
Pipeline script from HTTPoption in thePipelinesection
URL: https://api.github.com/repos/[your_org]/[your_repo]/contents/[path_in_repo]?ref=master Accept Header: application/vnd.github.VERSION.raw
To release simply call the following script:
mvn release:prepare release:perform
or
docker run --rm -it -v "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.8.1-openjdk-8 mvn release:prepare release:perform
You can contribute to this plugin by retrieving the source and following the official Jenkins plugin tutorial to install, run, test and package it.
This project is licensed under the terms of the MIT license.