https://github.com/JavatarPro/declarative-pipeline

jenkinsfile pipeline library
https://github.com/JavatarPro/declarative-pipeline

ci-cd jenkins-cd-pipeline jenkins-pipeline jenkinsfile

Last synced: 2 days ago
JSON representation

jenkinsfile pipeline library

• Host: GitHub
• URL: https://github.com/JavatarPro/declarative-pipeline
• Owner: JavatarPro
• License: mpl-2.0
• Created: 2018-05-20T11:36:32.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2023-09-02T12:32:54.000Z (about 1 year ago)
• Last Synced: 2024-11-06T23:41:09.479Z (7 days ago)
• Topics: ci-cd, jenkins-cd-pipeline, jenkins-pipeline, jenkinsfile
• Language: Groovy
• Homepage:
• Size: 720 KB
• Stars: 32
• Watchers: 8
• Forks: 14
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# javatar declarative pipeline

This is [jenkins shared library](https://jenkins.io/doc/book/pipeline/shared-libraries/) created by [Javatar](https://javatar.pro/)

### Documentation

Our [documentation is in confluence](https://javatar.atlassian.net/wiki/spaces/JDP/overview)

    

### What is this repository for? ###

* Setup CI/CD for micro-sevices with a help of jenkins & this library

  * java

  * golang

  * nodejs

* Setup CI/CD for UI repos based on docker or S3 artifacts

  * angular

  * react 

  * viewjs

### How do I get set up? ###

* You can use import @Library('declarative-pipeline') into Jenkinsfile

* All configuration should be in Jenkinsfile

* All code files must be groovy, Jenkinsfile's restriction

* All jobs (except development/experimental) should use tag version

* Jenkinsfile example [continuous-delivery repo](https://github.com/JavatarPro/declarative-pipeline)

### Contribution guidelines ###

* All experiments you can do in feature branch, import @Library('declarative-pipeline@branchName')

* After library works property merge into master and create tag version for it

### Who do I talk to? ###

* [borys-zora](mailto:[email protected]), [spetrychenko](mailto:[email protected])

### RELEASE NOTES ###

* 1.2

    - added yml configuration support

    - ui deployment to s3

    - sonar integration

    - marathon/mesos deployment on dev env with docker images included build number

    - multi docker project (multiple Dockerfiles in sub-folders)

* 1.1

    - added python support

    - added github support

* 1.0

    - tools supported: gitlab, docker, mesos

    - build tools: maven, npm

    - version control types: git, mercurial

    - version control providers: gitlab, bitbucket

    - sonar quality check