Stakater Pipeline Library
Problem
We often face situations where multiple projects were using the same CI/CD pipeline workflow(optionally with minor changes). This resulted in a lot of code duplication and redundant work when trying to update a functionality.
Solution
We decided to extract out the reusable components from different Jenkinsfile into a pipeline library making it the single source of truth and using it for CI/CD workflows of all our applications.
How to use Stakater Pipeline Library
Just add the following to the top of your Jenkinsfile
#!/usr/bin/env groovy
@Library('github.com/stakater/stakater-pipeline-library@v2.15.1') _
and you can directly use any methods available in the library.
Help
Documentation
You can find more documentation here
Have a question?
File a GitHub issue, or send us an email.
Talk to us on Slack
Join and talk to us on Slack for discussing Stakater Pipeline Library
Contributing
Bug Reports & Feature Requests
Please use the issue tracker to report any bugs or file feature requests.
Developing
PRs are welcome. In general, we follow the "fork-and-pull" Git workflow.
- Fork the repo on GitHub
- Clone the project to your own machine
- Commit changes to your own branch
- Push your work back up to your fork
- Submit a Pull request so that we can review your changes
NOTE: Be sure to merge the latest from "upstream" before making a pull request!
Changelog
View our closed Pull Requests.
License
Apache2 © Stakater
About
Stakater Pipeline Library
is maintained by Stakater. Like it? Please let us know at hello@stakater.com
See our other projects or contact us in case of professional services and queries on hello@stakater.com
Acknowledgements
- fabric8-pipeline-library; We got the motivation to write our own pipeline library from fabric8's pipeline library. Initially we started by improving the existing library but felt that it needed a major revamp to cater better to our needs so we decided to write our own version of pipeline library.