-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 1.618
Subversion 2.5
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.
[JENKINS-29293] Repositories set as external are not triggered if they are in the list of jobs after the main repository
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. |
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. |
Assignee | New: Manuel Recena Soto [ recena ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Attachment | New: JENKINS-29293.png [ 30161 ] |
Attachment | New: JENKINS-29293.png [ 30162 ] |
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. |
balteanu_marius, What subversion workspace version are you using?