[JIRA] (JENKINS-53201) Poll SCM not triggering on any externals: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.

119 views
Skip to first unread message

mdealer@gmail.com (JIRA)

unread,
Aug 23, 2018, 2:48:01 AM8/23/18
to jenkinsc...@googlegroups.com
Edgars Batna created an issue
 
Jenkins / Bug JENKINS-53201
Poll SCM not triggering on any externals: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.
Issue Type: Bug Bug
Assignee: Vincent Latombe
Components: pipeline, pollscm-plugin, subversion-plugin
Created: 2018-08-23 06:47
Environment: Windows Server
Jenkins 2.137
Subversion 2.11.1
Pipeline 2.5
Pipeline API 2.29
... (generally latest Pipeline to nearly latest other plugins)
Priority: Major Major
Reporter: Edgars Batna

None of the Multibranch Pipeline jobs seem to be able to cope with externals using Poll SCM.

Trigger on main repo change works fine, but externals do not. I'm not sure if it ever worked, but it's broken and totally not obvious unless you go into SCM Polling Log. Not only should this error not happen, but Poll SCM should be able to indicate errors without having to scrub through all logs.

This is a major problem as builds no longer get updated correctly without any feedback.

I added three components to the ticket as it's not obvious to me what causes it.

If builds are triggered manually, they build fine. Whenever SCM triggers a build it builds also fine. Similar bug was fixed this year when a build was failing with same error during checkout, so I guess same fix should be applied to the Poll SCM.

There is a similar issue like https://issues.jenkins-ci.org/browse/JENKINS-31869

But that is a completely different version and years older.

Polling log looks like this (multiply this a thousand times for large repos):

Started on Aug 23, 2018 1:34:29 AM
Received SCM poll call on master for trunk on Aug 23, 2018 1:34:29 AM
Using sole credentials <none> in realm ‘<https://repo:443> VisualSVN Server’
ERROR: Failed to check repository revision for https://repo/trunk
org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.
svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:66)
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:760)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352)
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:340)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:910)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:702)
	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:113)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1035)
	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:164)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:119)
	at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:178)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:43)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:47)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31)
	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239)
	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
	at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2535)
	at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1279)
	at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:79)
	at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:27)
	at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
	at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1476)
	at org.jenkinsci.plugins.workflow.job.WorkflowJob.poll(WorkflowJob.java:631)
	at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:603)
	at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:649)
	at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.
	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:694)
	... 30 more

 
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

mdealer@gmail.com (JIRA)

unread,
Aug 23, 2018, 2:49:02 AM8/23/18
to jenkinsc...@googlegroups.com
Edgars Batna updated an issue
Change By: Edgars Batna
None of the Multibranch Pipeline jobs seem to be able to cope with externals using Poll SCM.
Jobs are configured somewhat like this:
{code:java}
properties(
    [buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '2000', numToKeepStr: '400')),
    [$class: 'ScannerJobProperty', doNotScan: false],
    pipelineTriggers([pollSCM('H H(0-5) * * *')])
    ])
{code}
Trigger on main repo change works fine, but externals do not. I'm not sure if it ever worked, but it's broken and totally not obvious unless you go into SCM Polling Log. Not only should this error not happen, but Poll SCM should be able to indicate errors without having to scrub through all logs.

This is a major problem as builds no longer get updated correctly without any feedback.

I added three components to the ticket as it's not obvious to me what causes it.

If builds are triggered manually, they build fine. Whenever SCM triggers a build it builds also fine. Similar bug was fixed this year when a build was failing with same error during checkout, so I guess same fix should be applied to the Poll SCM.

There is a similar issue like https://issues.jenkins-ci.org/browse/JENKINS-31869

But that is a completely different version and years older.

Polling log looks like this (multiply this a thousand times for large repos):
{code:java}
{code}
 

mdealer@gmail.com (JIRA)

unread,
Aug 23, 2018, 2:52:02 AM8/23/18
to jenkinsc...@googlegroups.com
Edgars Batna updated an issue
None of the Multibranch Pipeline jobs seem to be able to cope with externals using Poll SCM.

Jobs are configured somewhat like this:
{code:java}
properties(
    [buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '2000', numToKeepStr: '400')),
    [$class: 'ScannerJobProperty', doNotScan: false],
    pipelineTriggers([pollSCM('H H(0-5) * * *')])
    ])
{code}
Multibranch job is configured to *not* trigger when scanning. Trigger on main repo change works fine, but externals do not. I'm not sure if it ever worked, but it's broken and totally not obvious unless you go into SCM Polling Log. Not only should this error not happen, but Poll SCM should be able to indicate errors without having to scrub through all logs.

mdealer@gmail.com (JIRA)

unread,
Aug 23, 2018, 2:53:02 AM8/23/18
to jenkinsc...@googlegroups.com
Edgars Batna updated an issue
None of the Multibranch Pipeline jobs seem to be able to cope with externals using Poll SCM.

Jobs are configured somewhat like this:
{code:java}
properties(
    [buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '2000', numToKeepStr: '400')),
    [$class: 'ScannerJobProperty', doNotScan: false],
    pipelineTriggers([pollSCM('H H(0-5) * * *')])
    ])
{code}
Multibranch job is configured to *not* trigger when scanning. Trigger SCM trigger on main repo change works fine , but externals do bot trigger on an external with this repo does not. I'm not sure if it ever worked, but it's broken and totally not obvious unless you go into SCM Subversion Polling Log. Not only should this error not happen, but Poll SCM should be able to indicate errors without having to scrub through all logs.

mdealer@gmail.com (JIRA)

unread,
Aug 23, 2018, 3:50:02 AM8/23/18
to jenkinsc...@googlegroups.com
Edgars Batna updated an issue
None of the Multibranch Pipeline jobs seem to be able to cope with externals using Poll SCM.

Jobs are configured somewhat like this:
{code:java}
properties(
    [buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '2000', numToKeepStr: '400')),
    [$class: 'ScannerJobProperty', doNotScan: false],
    pipelineTriggers([pollSCM('H H(0-5) * * *')])
    ])
{code}
Multibranch job is configured to *not* trigger when scanning. SCM trigger on main repo change works, bot trigger on an external with this repo does not. I'm not sure if it ever worked, but it's broken and totally not obvious unless you go into Subversion Polling Log. Not only should this error not happen, but Poll SCM should be able to indicate errors without having to scrub through all logs. The main repo and all external repos are on the same server, I can't see any problems with credential configuration either.

mdealer@gmail.com (JIRA)

unread,
Aug 23, 2018, 3:57:02 AM8/23/18
to jenkinsc...@googlegroups.com
Edgars Batna updated an issue
None of the Multibranch Pipeline jobs seem to be able to cope with externals using Poll SCM.

Jobs are configured somewhat like this:
{code:java}
properties(
    [buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '2000', numToKeepStr: '400')),
    [$class: 'ScannerJobProperty', doNotScan: false],
    pipelineTriggers([pollSCM('H H(0-5) * * *')])
    ])
...
checkout  changelog: false, scm: [$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: scm.locations as java.util.List<hudson.scm.SubversionSCM$ModuleLocation>, quietOperation: true, workspaceUpdater: [$class: 'UpdateWithCleanUpdater']]
...

mdealer@gmail.com (JIRA)

unread,
Aug 23, 2018, 4:26:02 AM8/23/18
to jenkinsc...@googlegroups.com
Edgars Batna updated an issue
None of the Multibranch Pipeline jobs seem to be able to cope with externals using Poll SCM.

Jobs are configured somewhat like this:
{code:java}
properties(
    [buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '2000', numToKeepStr: '400')),
    [$class: 'ScannerJobProperty', doNotScan: false],
    pipelineTriggers([pollSCM('H H(0-5) * * *')])
    ])
...
checkout  changelog: false, scm: [$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: scm.locations as java.util.List<hudson.scm.SubversionSCM$ModuleLocation>, quietOperation: true, workspaceUpdater: [$class: 'UpdateWithCleanUpdater']]
...
{code}
Multibranch job is configured to *not* trigger when scanning. SCM trigger on main repo change works, bot trigger on an external with this repo does not. I'm not sure if it ever worked, but it's broken and totally not obvious unless you go into Subversion Polling Log. Not only should this error not happen, but Poll SCM should be able to indicate errors without having to scrub through all logs. The main repo and all external repos are on the same server, I can't see any problems with credential configuration either.

This is a major problem as builds no longer get updated correctly without any feedback.

I added three components to the ticket as it's not obvious to me what causes it.

If builds are triggered manually, they build fine. Whenever SCM triggers a build it builds also fine. Similar bug was fixed this year when a build was failing with same error during checkout, so I guess same fix should be applied to the Poll SCM.

There is a are similar issue like https:// issues .jenkins-ci.org/browse/ like JENKINS-31869

But that is a completely and JENKINS-29079 but they, different version and , years older and are about checkouts not polling . I think some of the similar issues are long fixed.

mdealer@gmail.com (JIRA)

unread,
Aug 23, 2018, 4:27:01 AM8/23/18
to jenkinsc...@googlegroups.com
Edgars Batna updated an issue
None of the Multibranch Pipeline jobs seem to be able to cope with externals using Poll SCM.

Jobs are configured somewhat like this:
{code:java}
properties(
    [buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '2000', numToKeepStr: '400')),
    [$class: 'ScannerJobProperty', doNotScan: false],
    pipelineTriggers([pollSCM('H H(0-5) * * *')])
    ])
...
checkout  changelog: false, scm: [$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: scm.locations as java.util.List<hudson.scm.SubversionSCM$ModuleLocation>, quietOperation: true, workspaceUpdater: [$class: 'UpdateWithCleanUpdater']]
...
{code}
Multibranch job is configured to *not* trigger when scanning. SCM trigger on main repo change works, bot trigger on an external with this repo does not. I'm not sure if it ever worked, but it's broken and totally not obvious unless you go into Subversion Polling Log. Not only should this error not happen, but Poll SCM should be able to indicate errors without having to scrub through all logs. The main repo and all external repos are on the same server, I can't see any problems with credential configuration either.

This is a major problem as builds no longer get updated correctly without any feedback.

I added three components to the ticket as it's not obvious to me what causes it.

If builds are triggered manually, they build fine. Whenever SCM triggers a build it builds also fine. Similar bug was fixed this year when a build was failing with same error during checkout, so I guess same fix should be applied to the Poll SCM.

There are similar issues like JENKINS-31869 and JENKINS-29079 but they , are from a different version, years older and are about checkouts not polling. I think some of the similar issues are long fixed.

mdealer@gmail.com (JIRA)

unread,
Aug 23, 2018, 4:31:02 AM8/23/18
to jenkinsc...@googlegroups.com
Edgars Batna updated an issue
None of the Multibranch Pipeline jobs seem to be able to cope with externals using Poll SCM.

Jobs are configured somewhat like this:
{code:java}
properties(
    [buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '2000', numToKeepStr: '400')),
    [$class: 'ScannerJobProperty', doNotScan: false],
    pipelineTriggers([pollSCM('H H(0-5) * * *')])
    ])
...
checkout  changelog: false, scm: [$class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: scm.locations as java.util.List<hudson.scm.SubversionSCM$ModuleLocation>, quietOperation: true, workspaceUpdater: [$class: 'UpdateWithCleanUpdater']]
...
{code}
Multibranch job is configured to *not* trigger when scanning. SCM trigger on main repo change works, bot trigger on an external with this repo does not. I'm not sure if it ever worked, but it's broken and totally not obvious unless you go into Subversion Polling Log. Not only should this error not happen, but Poll SCM should be able to indicate errors without having to scrub through all logs. The main repo and all external repos are on the same server, I can't see any problems with credential configuration either.

This is a major problem as builds no longer get updated correctly without any feedback.

I added three components to the ticket as it's not obvious to me what causes it.

If builds are triggered manually, they build fine. Whenever SCM triggers a build it builds also fine. Similar bug was fixed this year when a build was failing with same error during checkout, so I guess same fix should be applied to the Poll SCM.

There are similar issues like JENKINS-31869 and JENKINS-29079 but they are from a different version, years older and are about checkouts not polling .

jsmith45@sogetthis.com (JIRA)

unread,
Sep 6, 2018, 5:02:05 PM9/6/18
to jenkinsc...@googlegroups.com
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

k0rbendallas@bk.ru (JIRA)

unread,
Oct 2, 2018, 4:53:09 AM10/2/18
to jenkinsc...@googlegroups.com

Subversion Plug-in 2.12.2, the problem is still relevant.

Jenkins 2.121.2

OS Linux

Started on Oct 2, 2018 7:40:00 AM
Received SCMpoll call on master for Build-Trunk on Oct 2, 2018 7:40:00 AM
Using sole credentials <none> in realm ‘<https://repo:443> svn’
ERROR: Failed to check repository revision for https://repo/libs/code-libs
org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.


svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)


Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:694)

... 30 more

 

 

 

 

 

 
Add Comment Add Comment
 

alb.morando@gmail.com (JIRA)

unread,
Oct 24, 2018, 9:40:02 AM10/24/18
to jenkinsc...@googlegroups.com

Hi

Same issue here

Any update on when the issue is solved?

 

Configuration:

Jenkins version 2.138.1 

Plugins lists
PLUGIN VERSION
------ -------
JavaScript GUI Lib: ACE Editor bundle plugin 1.1
Static Analysis Utilities 1.95
Ant Plugin 1.8
OWASP Markup Formatter Plugin 1.5
Jenkins Apache HttpComponents Client 4.x API Plugin 4.5.5-3.0
Authentication Tokens API Plugin 1.3
Autofavorite for Blue Ocean 1.2.2
Bitbucket Pipeline for Blue Ocean 1.8.4
Common API for Blue Ocean 1.8.4
Config API for Blue Ocean 1.8.4
Blue Ocean Core JS 1.8.4
Dashboard for Blue Ocean 1.8.4
Display URL for Blue Ocean 2.2.0
Events API for Blue Ocean 1.8.4
Git Pipeline for Blue Ocean 1.8.4
GitHub Pipeline for Blue Ocean 1.8.4
i18n for Blue Ocean 1.8.4
JIRA Integration for Blue Ocean 1.8.4
JWT for Blue Ocean 1.8.4
Personalization for Blue Ocean 1.8.4
Pipeline implementation for Blue Ocean 1.8.4
Blue Ocean Pipeline Editor 1.8.4
Pipeline SCM API for Blue Ocean 1.8.4
REST Implementation for Blue Ocean 1.8.4
REST API for Blue Ocean 1.8.4
Web for Blue Ocean 1.8.4
Blue Ocean 1.8.4
bouncycastle API Plugin 2.17
Branch API Plugin 2.0.20
Build Monitor View 1.12+build.201809061734
Build Timeout 1.19
Bitbucket Branch Source Plugin 2.2.12
Folders Plugin 6.6
Jenkins Cobertura Plugin 1.13
Code Coverage API Plugin 1.0.5
Command Agent Launcher Plugin 1.2
Credentials Binding Plugin 1.16
Credentials Plugin 2.1.18
Display URL API 2.2.0
Docker Commons Plugin 1.13
Docker Pipeline 1.17
Durable Task Plugin 1.26
Email Extension Plugin 2.63
External Monitor Job Type Plugin 1.7
Favorite 2.3.2
Jenkins Git client plugin 2.7.3
Jenkins GIT server Plugin 1.7
Jenkins Git plugin 3.9.1
GitHub API Plugin 1.92
GitHub Branch Source Plugin 2.3.6
GitHub plugin 1.29.2
Gradle Plugin 1.29
Green Balls 1.15
JavaScript GUI Lib: Handlebars bundle plugin 1.1.1
Handy Uri Templates 2.x API Plugin 2.1.6-1.0
HTML Publisher plugin 1.16
Jackson 2 API Plugin 2.8.11.3
Javadoc Plugin 1.4
JDK Tool Plugin 1.1
Jenkins Design Language 1.8.4
Jenkins JIRA plugin 3.0.2
JavaScript GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin 1.2.1
Jenkins JSch dependency plugin 0.1.54.2
JUnit Plugin 1.26.1
LDAP Plugin 1.20
Locale plugin 1.3
Lockable Resources plugin 2.3
Jenkins Mailer Plugin 1.21
MapDB API Plugin 1.0.9.0
Matrix Authorization Strategy Plugin 2.3
Matrix Project Plugin 1.13
Maven Integration plugin 3.1.2
Jenkins Mercurial plugin 2.4
JavaScript GUI Lib: Moment.js bundle plugin 1.1.1
Monitoring 1.74.0
PAM Authentication plugin 1.4
Pipeline: Build Step 2.7
Pipeline: GitHub Groovy Libraries 1.0
Pipeline Graph Analysis Plugin 1.7
Pipeline: Input Step 2.8
Pipeline: Milestone Step 1.3.1
Pipeline: Model API 1.3.2
Pipeline: Declarative Agent API 1.1.1
Pipeline: Declarative 1.3.2
Pipeline: Declarative Extension Points API 1.3.2
Pipeline: REST API Plugin 2.10
Pipeline: Stage Step 2.3
Pipeline: Stage Tags Metadata 1.3.2
Pipeline: Stage View Plugin 2.10
Plain Credentials Plugin 1.4
Jenkins Pub-Sub "light" Bus 1.12
Resource Disposer Plugin 0.12
Role-based Authorization Strategy 2.9.0
SCM API Plugin 2.2.8
Script Security Plugin 1.46
Simple Theme Plugin 0.5.1
Server Sent Events (SSE) Gateway Plugin 1.16
SSH Credentials Plugin 1.14
Jenkins SSH Slaves plugin 1.28.1
Structs Plugin 1.15
Jenkins Subversion Plug-in 2.12.1
ThinBackup 1.9
Timestamper 1.8.10
Token Macro Plugin 2.5
Variant Plugin 1.1
Warnings Plug-in 4.68
Windows Slaves Plugin 1.3.1

Pipeline 2.5
Pipeline: API 2.29

Pipeline: Basic Steps 2.11
Pipeline: Shared Groovy Libraries 2.11
Pipeline: Groovy 2.56
Pipeline: Nodes and Processes 2.22
Pipeline: Job 2.25
Pipeline: Multibranch 2.20
Pipeline: SCM Step 2.7
Pipeline: Step API 2.16
Pipeline: Supporting APIs 2.20
Jenkins Workspace Cleanup Plugin 0.34
xUnit plugin 2.2.5

alb.morando@gmail.com (JIRA)

unread,
Oct 24, 2018, 9:43:03 AM10/24/18
to jenkinsc...@googlegroups.com
Alberto Morando edited a comment on Bug JENKINS-53201
Hi

Same issue here

Any update on when the issue is solved?

 

Configuration:

Jenkins version 2.138.1   on Windows 10

ulrich.koehler@burkert.com (JIRA)

unread,
Nov 12, 2018, 7:57:03 AM11/12/18
to jenkinsc...@googlegroups.com

Same here with none-pipeline projects.
A workaround which helped me: select the same credentials a second time on 'Add Additional Credentials'

mdealer@gmail.com (JIRA)

unread,
Nov 15, 2018, 10:18:02 AM11/15/18
to jenkinsc...@googlegroups.com

I tried the workaround regarding additional credentials above and it helped:

checkout  changelog: false, scm: [$class: 'SubversionSCM', additionalCredentials: [[credentialsId: 'uuid', realm: '<https://subversion.server.com:443> VisualSVN Server']], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: scm.locations as java.util.List<hudson.scm.SubversionSCM$ModuleLocation>, quietOperation: true, workspaceUpdater: [$class: 'UpdateWithCleanUpdater']]

What I don't really know is what credentials these are, as I've been adding credentials all over the place to make it work recently. I might update my comment once I find out. I also think I've tried this before, so possible some recent Jenkins update helped too? Was it perhaps the realm that was missing? The credentials realm thing in Jenkins is a thing I've never used before.

 

eugene.pliskin@gmail.com (JIRA)

unread,
Oct 23, 2019, 7:05:02 AM10/23/19
to jenkinsc...@googlegroups.com

Having had the same problem polling for SVN externals, in my Scripted Pipeline job, with Jenkins version 2.200.

Then in my Groovy code for the pipeline I just added the "additionalCredentials" clause like this:

checkout([$class: 'SubversionSCM',
  workspaceUpdater: [$class: 'UpdateWithCleanUpdater'], // remove unversioned files
  locations: [[
  credentialsId: my_credentials_id, // login and password for SVN
  local: target_folder,     // target folder in workspace
  remote: revision_url]], // SVN repository and revision URL

  additionalCredentials: [[
     credentialsId: my_credentials_id, // same as above
     realm: '<https://my.svn.server.url:443> Restricted Area']], // learned this from error messages in polling log

  quietOperation : true // minimize output
])

And rebuilt the job. And waited for several polling-build cycles to occur.
After which at last the polling problem has gone! No errors more in polling logs.
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages