Home/ Questions/Q 8816395
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T04:36:43+00:00

I am using Jenkins for Continous-Integration. I configured a job, which polls the scm

  • 0

I am using Jenkins for Continous-Integration.

I configured a job, which polls the scm for changes. I have one executor. When there is more than one scm-change, but the executor is already working, there is still only one job added to queue, where I want it to queue more than one job.

I already tried my job “parametrized” as a workaround, but as long as polling does not set any parameters¹ (even not the default ones²), this does not help, too.

Is there any way to get for each scm-change a new build in the job-queue?

[1] https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build

[2] I tried to combine this scenario with https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Dynamic+Parameter+Plug-in

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Described scenario is possible in Jenkins by using a workaround which requires two steps:

    • [JobA_trigger] One Job which triggers another job ‘externally’, via curl or jenkins-cli.jar¹.

    • [JobA] The actual job which has to be a parametrized one.

    In my setup, JobA_trigger polls SCM periodically. If there is a change, JobA is triggered via curl and the current dateTime is submitted². This ‘external’ triggering is necessary to submit parameters to JobA.

    # JobA_trigger "execute shell"
curl ${JENKINS_URL}job/JobA/buildWithParameters?SVN_REVISION=`date +"%Y-%m-%d"`%20`date +"%H:%M:%S"`
# SVN_REVISION, example (decoded): "2012-11-07 12:56:50" ("%20" is url-encoded space)

    JobA itself is parametrized and accepts a String-Param “SVN_REVISION”. Additionally I had to change the SVN-URL to 

    # Outer brackets for usage of SVN revision dates³ - must be avoided if working on a revision-number.
https://svn.someaddress.com/trunk@{${SVN_REVISION}}

    Using this workaround, for each scm-change there is new run of JobA queued which has the related svn-revision/dateTime attached as a parameter and is used as the software-state which is being tested by this job.

    ¹ https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI

    ² I decided to have dateTime-bases updates instead of revision-based ones, as I have svn-externals which would be updated to HEAD each, if I would be working revision-based.

    ³ http://svnbook.red-bean.com/en/1.7/svn.tour.revs.specifiers.html#svn.tour.revs.dates

    • 0