parameterizing the branch name for build job & its effect in SCM Polling process
8 views
Skip to first unread message
niristotle okram
unread,
Jun 8, 2015, 5:39:53 PM6/8/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to jenkins...@googlegroups.com
Some version info:
Git Client Plugin : 1.10.1
Git Plugin : 2.2.5
jenkins : 1.589
I have a simple jenkins job to perform the maven deploy Or maven release plugins from *a branch like (master or release branch) . Now, i changed it, the branch name is parameterized. Either the master or the release branch is specified before the job is manually triggered. Some screenshots of the job's conf page.
You will see from the screenshots that there is no default branch specified for the job. As of now, i see that the SCM polling is triggering the build from the master branch. i know that the dev are pushing on the master. I haven't had a chance to verify if the SCM polling triggers a build job/process when there is push to release branch.