• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: mercurial-plugin
• Labels:

  None
• Environment:

  Pipeline: Shared Groovy Libraries 2.8 / Jenkins 2.60.3

1. 

   2017-10-25_17-40-05.png

   34 kB

   2017-10-25 14:42

2. 

   2017-10-25_17-40-27.png

   19 kB

   2017-10-25 14:42

3. 

   shared_pipeline_conf.jpg

   167 kB

   2017-10-19 17:37

4. 

   shared_pipeline_result.jpg

   62 kB

   2017-10-19 17:37

[JENKINS-46851] Mercurial doesn't use credentials in Modern SCM for Shared Library

Collapse comment: Jesse Glick added a comment - 2017-10-12 15:05

Jesse Glick added a comment - 2017-10-12 15:05

Please provide complete, self-contained steps to reproduce from scratch. JENKINS-45806 was fixed with a regression test demonstrating its effectiveness.

Expand comment: Jesse Glick added a comment - 2017-10-12 15:05

Jesse Glick added a comment - 2017-10-12 15:05 Please provide complete, self-contained steps to reproduce from scratch.  JENKINS-45806 was fixed with a regression test demonstrating its effectiveness.

Collapse comment: Dmytro Kozlovskyi added a comment - 2017-10-19 17:37

Dmytro Kozlovskyi added a comment - 2017-10-19 17:37

1. Add new shared library with ' Load implicitly' enabled.
2. Set 'Retrieval method' to 'Modern SCM'
3. Source Code Management - Mercurial

Added also screenshots

Expand comment: Dmytro Kozlovskyi added a comment - 2017-10-19 17:37

Dmytro Kozlovskyi added a comment - 2017-10-19 17:37 Add new shared library with ' Load implicitly' enabled. Set 'Retrieval method' to 'Modern SCM' Source Code Management - Mercurial Added also screenshots

Collapse comment: vladislav piskunov added a comment - 2017-10-25 14:38

vladislav piskunov added a comment - 2017-10-25 14:38

 I have same problem if use username/password credentials for shared libraries.

Expand comment: vladislav piskunov added a comment - 2017-10-25 14:38

vladislav piskunov added a comment - 2017-10-25 14:38  I have same problem if use username/password credentials for shared libraries.

Collapse comment: Nickolas Fox added a comment - 2017-10-25 14:46

Nickolas Fox added a comment - 2017-10-25 14:46

Don't know if problem has gone, checked with the latest release (and attached settings) and got the following output in jobs:

$ /usr/bin/hg clone --noupdate https://xxxxxxxxxxxxxxx.xxx/uxpractice/ci-lib /var/jenkins_home/hgcache/4FD2C121064AB2C970CE3642ADAF72421A0D78D0-ci-lib
abort: http authorization required for https://xxxxxxxxxxxxxxx.xxx/uxpractice/ci-lib
ERROR: Failed to clone https://xxxxxxxxxxxxxxx.xxx/uxpractice/ci-lib
Master cache lock released.
ERROR: Could not use caches, not fetching branch heads
ERROR: No version feature/RT462020-docker-compose-research found for library ci
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: Loading libraries failed

Worked fine to me on 1.61 version of mercurial plugin.

Expand comment: Nickolas Fox added a comment - 2017-10-25 14:46

Nickolas Fox added a comment - 2017-10-25 14:46 Don't know if problem has gone, checked with the latest release (and attached settings) and got the following output in jobs: $ /usr/bin/hg clone --noupdate https: //xxxxxxxxxxxxxxx.xxx/uxpractice/ci-lib / var /jenkins_home/hgcache/4FD2C121064AB2C970CE3642ADAF72421A0D78D0-ci-lib abort: http authorization required for https: //xxxxxxxxxxxxxxx.xxx/uxpractice/ci-lib ERROR: Failed to clone https: //xxxxxxxxxxxxxxx.xxx/uxpractice/ci-lib Master cache lock released. ERROR: Could not use caches, not fetching branch heads ERROR: No version feature/RT462020-docker-compose-research found for library ci org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: Loading libraries failed Worked fine to me on 1.61 version of mercurial plugin.

Collapse comment: Manuel Ryan added a comment - 2018-04-11 12:54

Manuel Ryan added a comment - 2018-04-11 12:54

Same issue here, using "Legacy SCM" instead of "Modern SCM" solved my issue.

Expand comment: Manuel Ryan added a comment - 2018-04-11 12:54

Manuel Ryan added a comment - 2018-04-11 12:54 Same issue here, using "Legacy SCM" instead of "Modern SCM" solved my issue.

Collapse comment: Victor Verbitsky added a comment - 2018-09-10 15:15, Edited by Victor Verbitsky - 2018-09-10 15:15

Victor Verbitsky added a comment - 2018-09-10 15:15 - edited

I have the same issue. And I think, that found the root of problem. See PR #119 in source repo

Expand comment: Victor Verbitsky added a comment - 2018-09-10 15:15, Edited by Victor Verbitsky - 2018-09-10 15:15

Victor Verbitsky added a comment - 2018-09-10 15:15 - edited I have the same issue. And I think, that found the root of problem. See PR #119 in source repo