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

          Marius Balteanu created issue -
          Marius Balteanu made changes -
          Description Original: 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:
          appcore-tools/library/main/trunk
          appcore-tools/library/local/trunk
          appcore-tools/library/book/trunk
          ...
          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.

          After I've updated Jenkins and Subversion plugin to the latest version, 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.
          New: *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:
          appcore-tools/library/main/trunk
          appcore-tools/library/local/trunk
          appcore-tools/library/book/trunk
          ...
          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.

          After I've updated Jenkins and Subversion plugin to the latest version, 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.
          Marius Balteanu made changes -
          Description Original: *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:
          appcore-tools/library/main/trunk
          appcore-tools/library/local/trunk
          appcore-tools/library/book/trunk
          ...
          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.

          After I've updated Jenkins and Subversion plugin to the latest version, 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.
          New: *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:
          appcore-tools/library/main/trunk
          appcore-tools/library/local/trunk
          appcore-tools/library/book/trunk
          ...
          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.
          Manuel Recena Soto made changes -
          Assignee New: Manuel Recena Soto [ recena ]
          Manuel Recena Soto made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Manuel Recena Soto added a comment - - edited

          balteanu_marius, What subversion workspace version are you using?

          Manuel Recena Soto added a comment - - edited balteanu_marius , What subversion workspace version are you using?
          Manuel Recena Soto made changes -
          Attachment New: JENKINS-29293.png [ 30161 ]
          Manuel Recena Soto made changes -
          Attachment New: JENKINS-29293.png [ 30162 ]
          Manuel Recena Soto made changes -
          Description Original: *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:
          appcore-tools/library/main/trunk
          appcore-tools/library/local/trunk
          appcore-tools/library/book/trunk
          ...
          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.
          New: *Subversion schema:*

          # We've a main repo named for example "appcore"
          # This repository has a total of 9 repositories set as externals
          # 8 from 9 repository are from the same root repository named "appcore-tools" which have the following structure:
          ## appcore-tools/library/main/trunk
          ## appcore-tools/library/local/trunk
          ## appcore-tools/library/book/trunk
          ## ...
          # The last external point to a different repository
          # 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:*

          # I have a job called "Appcore-BuildStable" which is responsible the build the main repository "appcore/trunk".
          # 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..
          # 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.

          Subversion workspace 1.8.

          I've updated the Subversion plugin to version 2.5.1 and the issue isn't fixed.

          From the logs:
          Jul 14, 2015 8:03:15 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify
          Received post-commit hook from 22d56074-6c82-4296-bb9a-ef11210f5bf8 for revision -1 on paths [library/appcore-tools/trunk/README.txt]
          Jul 14, 2015 8:03:15 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify
          No subversion consumers for UUID 22d56074-6c82-4296-bb9a-ef11210f5bf8

          Marius Balteanu added a comment - Subversion workspace 1.8. I've updated the Subversion plugin to version 2.5.1 and the issue isn't fixed. From the logs: Jul 14, 2015 8:03:15 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify Received post-commit hook from 22d56074-6c82-4296-bb9a-ef11210f5bf8 for revision -1 on paths [library/appcore-tools/trunk/README.txt] Jul 14, 2015 8:03:15 AM INFO jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify No subversion consumers for UUID 22d56074-6c82-4296-bb9a-ef11210f5bf8

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

              Created:
              Updated: