| //jenkins get last successful build parameters | |
| node("master"){ | |
| //get `branch` parameter of jenkins build | |
| String sh_curl_result = sh(script: "curl -u your_jenkins_user:your_secret_API_key 'http://jenkinsInstance:8080/job/Project/job/job_name_deploy_all/lastSuccessfulBuild/api/xml?tree=actions\\[parameters\\[name,value\\]\\]&xpath=/workflowRun/action/parameter\\[name=%22Branch%22\\]/value'", returnStdout: true).trim() | |
| println sh_curl_result | |
| //string() is not supported by jenkins xpath XML api, so need to cut `value` tags it via regex: | |
| result = (sh_curl_result =~ /(?<=>).*(?=<)/)[0] | |
| println result | |
| } |
I just had to set up Jenkins to use GitHub. My notes (to myself, mostly):
For setting up Jenkins to build GitHub projects. This assumes some ability to manage Jenkins, use the command line, set up a utility LDAP account, etc. Please share or improve this Gist as needed.
| import com.cloudbees.hudson.plugins.folder.Folder | |
| import hudson.FilePath | |
| import jenkins.model.Jenkins | |
| def boolean isFolder(String name) { | |
| def item = Jenkins.instance.getItemByFullName(name) | |
| return item instanceof Folder | |
| } | |
| def deleteUnusedWorkspace(FilePath root, String path) { |
| import hudson.model.*; | |
| import hudson.util.*; | |
| import jenkins.model.*; | |
| import hudson.FilePath.FileCallable; | |
| import hudson.slaves.OfflineCause; | |
| import hudson.node_monitors.*; | |
| hosts = getProperty('HostsForCleanup') | |
| hosts = hosts.split("\n") | |
| EmailToReport = getProperty('EmailToReport') |
There are many Git workflows out there, I heavily suggest also reading the atlassian.com [Git Workflow][article] article as there is more detail then presented here.
The two prevailing workflows are [Gitflow][gitflow] and [feature branches][feature]. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited.
When using Bash in the command line, it leaves a bit to be desired when it comes to awareness of state. I would suggest following these instructions on [setting up GIT Bash autocompletion][git-auto].
When working with a centralized workflow the concepts are simple, master represented the official history and is always deployable. With each now scope of work, aka feature, the developer is to create a new branch. For clarity, make sure to use descriptive names like transaction-fail-message or github-oauth for your branches.
| To avoid `Scripts not permitted to use method` %groovy.lang.GroovyObject getProperty java.lang.String% for example during pipeline script execution, | |
| need to approve the following signatures: | |
| to approve: | |
| method groovy.lang.GroovyObject getProperty java.lang.String | |
| method hudson.model.ItemGroup getItem java.lang.String | |
| method hudson.model.Job getAllProperties | |
| method hudson.model.Job getProperties | |
| method hudson.model.Job getProperty java.lang.String | |
| method hudson.model.User getProperty java.lang.Class |
