Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-29293

Repositories set as external are not triggered if they are in the list of jobs after the main repository

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • Jenkins 1.618
      Subversion 2.5

      Subversion schema:

      1. We've a main repo named for example "appcore"
      2. This repository has a total of 9 repositories set as externals
      3. 8 from 9 repository are from the same root repository named "appcore-tools" which have the following structure:
        1. appcore-tools/library/main/trunk
        2. appcore-tools/library/local/trunk
        3. appcore-tools/library/book/trunk
        4. ...
      4. The last external point to a different repository
      5. All these repos are on the same svn server and the user used to checkout the sources has RW access to all.

      Jenkins jobs schema:

      1. I have a job called "Appcore-BuildStable" which is responsible the build the main repository "appcore/trunk".
      2. For each external from point 2, we've separate jobs to build them. The name convention is Appcore-Main-BuildStable, Appcore-Local-BuildStable, Appcore-Book-BuildStable, etc..
      3. The last external from the different repository doesn't have a job (the code is not changed there).

      All jobs have the Pool SCM option enabled and SVN trigger has the post commit hook enabled.

      Behaviour:
      After I've updated Jenkins and Subversion plugin to the latest versions, the pooling is not working anymore for all the jobs that are after "Appcore-BuildStable" in the list of jobs (which are alphabetically ordered).

      If I commit something on appcore-tools/library/book/trunk, the job Appcore-Book-BuildStable starts.
      If I commit something on appcore-tools/library/main/trunk, the job Appcore-Main-BuildStable doesn't start because is after the Appcore-BuildStable.
      If I change the job name from "Appcore-Main-BuildStable" to "Appcore-BA-Main-BuildStable" and I commit something on the repo, the job starts.

      The workaround for me was to rename the job "Appcore-BuildStable" to "Appcore-X-BuildStable". In this way, all the other jobs are before this job.

          [JENKINS-29293] Repositories set as external are not triggered if they are in the list of jobs after the main repository

            recena Manuel Recena Soto
            marius_balteanu Marius Balteanu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: