-
Bug
-
Resolution: Unresolved
-
Minor
-
None
If a build parameter with default value is used in a SVN URL and the build should be started by changes in the SVN repository, a wrong URL is used for polling. The parameter used for the polling URL seems to be the parameter used in the last build and not the default parameter.
This is my URL in the Job config:
https://xxx/svn/repos/zzz/source/${BRANCH}
BRANCH is a job parameter and its default value is trunk
Expected result:
The URL used for polling the SVN repository should be constructed by using the default value of the parameter
https://xxx/svn/repos/zzz/source/trunk
Actual result:
The URL used for polling the SVN repository uses the parameter used in the last build.
https://xxx/svn/repos/zzz/source/tags/yyy
Then the poll does not see any changes (confirmed by https://xxx/job/zzz/scmPollLog/) and no build is started.
[JENKINS-34236] SVN polls wrong URL if it includes a build parameter
Description |
Original:
If a build parameter with default value is used in a SVN URL and the build should be started by changes in the SVN repository, wrong URL is used for polling. The parameter used for polling seems to be the parameter used in the last build and not the default parameter. This is my URL in the Job config: https://xxx/svn/repos/athlet/source/${BRANCH} BRANCH is a job parameter and its default value is trunk Expected result: The URL used for polling the SVN repository should be constructed by using the default value of the parameter https://xxx/svn/repos/athlet/source/trunk Actual result: The URL used for polling the SVN repository uses the parameter used in the last build. https://xxx/svn/repos/athlet/source/tags/yyy Then the poll does not see any changes (confirmed by https://xxx/job/zzz/scmPollLog/) and no build is started. |
New:
If a build parameter with default value is used in a SVN URL and the build should be started by changes in the SVN repository, a wrong URL is used for polling. The parameter used for the polling URL seems to be the parameter used in the last build and not the default parameter. This is my URL in the Job config: https://xxx/svn/repos/zzz/source/${BRANCH} BRANCH is a job parameter and its default value is trunk Expected result: The URL used for polling the SVN repository should be constructed by using the default value of the parameter https://xxx/svn/repos/athlet/source/trunk Actual result: The URL used for polling the SVN repository uses the parameter used in the last build. https://xxx/svn/repos/athlet/source/tags/yyy Then the poll does not see any changes (confirmed by https://xxx/job/zzz/scmPollLog/) and no build is started. |
Description |
Original:
If a build parameter with default value is used in a SVN URL and the build should be started by changes in the SVN repository, a wrong URL is used for polling. The parameter used for the polling URL seems to be the parameter used in the last build and not the default parameter. This is my URL in the Job config: https://xxx/svn/repos/zzz/source/${BRANCH} BRANCH is a job parameter and its default value is trunk Expected result: The URL used for polling the SVN repository should be constructed by using the default value of the parameter https://xxx/svn/repos/athlet/source/trunk Actual result: The URL used for polling the SVN repository uses the parameter used in the last build. https://xxx/svn/repos/athlet/source/tags/yyy Then the poll does not see any changes (confirmed by https://xxx/job/zzz/scmPollLog/) and no build is started. |
New:
If a build parameter with default value is used in a SVN URL and the build should be started by changes in the SVN repository, a wrong URL is used for polling. The parameter used for the polling URL seems to be the parameter used in the last build and not the default parameter. This is my URL in the Job config: https://xxx/svn/repos/zzz/source/${BRANCH} BRANCH is a job parameter and its default value is trunk Expected result: The URL used for polling the SVN repository should be constructed by using the default value of the parameter https://xxx/svn/repos/zzz/source/trunk Actual result: The URL used for polling the SVN repository uses the parameter used in the last build. https://xxx/svn/repos/zzz/source/tags/yyy Then the poll does not see any changes (confirmed by https://xxx/job/zzz/scmPollLog/) and no build is started. |
Description |
Original:
If a build parameter with default value is used in a SVN URL and the build should be started by changes in the SVN repository, a wrong URL is used for polling. The parameter used for the polling URL seems to be the parameter used in the last build and not the default parameter. This is my URL in the Job config: https://xxx/svn/repos/zzz/source/${BRANCH} BRANCH is a job parameter and its default value is trunk Expected result: The URL used for polling the SVN repository should be constructed by using the default value of the parameter https://xxx/svn/repos/zzz/source/trunk Actual result: The URL used for polling the SVN repository uses the parameter used in the last build. https://xxx/svn/repos/zzz/source/tags/yyy Then the poll does not see any changes (confirmed by https://xxx/job/zzz/scmPollLog/) and no build is started. |
New:
If a build parameter with default value is used in a SVN URL and the build should be started by changes in the SVN repository, a wrong URL is used for polling. The parameter used for the polling URL seems to be the parameter used in the last build and not the default parameter. This is my URL in the Job config: {{https://xxx/svn/repos/zzz/source/${BRANCH}}} BRANCH is a job parameter and its default value is trunk Expected result: The URL used for polling the SVN repository should be constructed by using the default value of the parameter https://xxx/svn/repos/zzz/source/trunk Actual result: The URL used for polling the SVN repository uses the parameter used in the last build. https://xxx/svn/repos/zzz/source/tags/yyy Then the poll does not see any changes (confirmed by https://xxx/job/zzz/scmPollLog/) and no build is started. |
Description |
Original:
If a build parameter with default value is used in a SVN URL and the build should be started by changes in the SVN repository, a wrong URL is used for polling. The parameter used for the polling URL seems to be the parameter used in the last build and not the default parameter. This is my URL in the Job config: {{https://xxx/svn/repos/zzz/source/${BRANCH}}} BRANCH is a job parameter and its default value is trunk Expected result: The URL used for polling the SVN repository should be constructed by using the default value of the parameter https://xxx/svn/repos/zzz/source/trunk Actual result: The URL used for polling the SVN repository uses the parameter used in the last build. https://xxx/svn/repos/zzz/source/tags/yyy Then the poll does not see any changes (confirmed by https://xxx/job/zzz/scmPollLog/) and no build is started. |
New:
If a build parameter with default value is used in a SVN URL and the build should be started by changes in the SVN repository, a wrong URL is used for polling. The parameter used for the polling URL seems to be the parameter used in the last build and not the default parameter. This is my URL in the Job config: {code:java} https://xxx/svn/repos/zzz/source/${BRANCH} {code} BRANCH is a job parameter and its default value is trunk Expected result: The URL used for polling the SVN repository should be constructed by using the default value of the parameter https://xxx/svn/repos/zzz/source/trunk Actual result: The URL used for polling the SVN repository uses the parameter used in the last build. https://xxx/svn/repos/zzz/source/tags/yyy Then the poll does not see any changes (confirmed by https://xxx/job/zzz/scmPollLog/) and no build is started. |
Workflow | Original: JNJira [ 170296 ] | New: JNJira + In-Review [ 183845 ] |