Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/codeasashu/jenkinfiles
Jenkinfiles for gitlab
https://github.com/codeasashu/jenkinfiles
Last synced: 9 days ago
JSON representation
Jenkinfiles for gitlab
- Host: GitHub
- URL: https://github.com/codeasashu/jenkinfiles
- Owner: codeasashu
- Created: 2019-10-13T20:53:43.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2019-10-13T21:07:18.000Z (about 5 years ago)
- Last Synced: 2024-10-05T00:40:59.248Z (3 months ago)
- Language: Groovy
- Size: 6.84 KB
- Stars: 1
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Jenkinfiles
**NOTE**- This project currently supports [gitlab.com](https://gitlab.com)
This is a collection of jenkinfile pipelines for several usage. This repo holds several jenkinfiles suited for different languages. For instance, `Jenkinfile-php` is best suited for `PHP` projects while `Jenkinfile-ansible` is best for ansible related operations.
## Quick Start
To get started quickly, navigate to your jenkins server and then do the following:1. Create new item, give any name. Select `Pipeline` from below item list
2. In job configuration, go to `pipeline` section
3. In definition section, select `Pipeline script from SCM`. In SCM, select `git` and enter this git repo in `Repository URL` section## How to use
The scripts are written so that it can be used individually. However, it can still work when your jobs are interlinked (dependent).
For instance, you may want to run ansible script after your `php` based job has been built, for deployment. For this to work, you can create two jobs:
- PHP
- AnsibleAnd in `php` job, you can set environment variable `NEXT_JOB` in the build configuration to run the next job after this
## Features
- Auto build on merge request event and push events
- Git diffs artifacts available as `diff.txt`
- Automerge source branch to target and push
- Ansible send slack notification