[JIRA] (JENKINS-58600) can't resolve libraries of form vX.X.0

14 views
Skip to first unread message

anthony.kerz@gmail.com (JIRA)

unread,
Jul 22, 2019, 8:21:03 AM7/22/19
to jenkinsc...@googlegroups.com
tony kerz created an issue
 
Jenkins / Bug JENKINS-58600
can't resolve libraries of form vX.X.0
Issue Type: Bug Bug
Assignee: Mark Waite
Components: git-plugin
Created: 2019-07-22 12:20
Environment: jenkins: 2.150.2
git plugin: 3.9.3
github plugin: 1.29.3
Priority: Major Major
Reporter: tony kerz

strangest thing, started experiencing issues with inability to resolve shared library with tag: v5.5.0, could find v5.5.1 and v5.6.0, but not v6.6.0.

 

this is against github enterprise 2.15.9

 

not 100 if this should be filed against the git plugin or the github plugin

Obtained Jenkinsfile from fb92a4e84a11fb775d1444fd59edcf9e82ecdca1
Running in Durability level: MAX_SURVIVABILITY
Loading library shared-...@v5.5.0
Examining digital-cloud/groovy-pipeline
Attempting to resolve v5.5.0 as a branch
Attempting to resolve v5.5.0 as a tag
ERROR: Could not resolve v5.5.0
ERROR: No version v5.5.0 found for library shared-pipeline

GitHub has been notified of this commit’s build result

org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: Loading libraries failed
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

mark.earl.waite@gmail.com (JIRA)

unread,
Jul 22, 2019, 11:56:02 AM7/22/19
to jenkinsc...@googlegroups.com
Mark Waite assigned an issue to Unassigned
Change By: Mark Waite
Assignee: Mark Waite

mark.earl.waite@gmail.com (JIRA)

unread,
Jul 22, 2019, 11:59:03 AM7/22/19
to jenkinsc...@googlegroups.com
Mark Waite commented on Bug JENKINS-58600
 
Re: can't resolve libraries of form vX.X.0

Are those tags of different types? Git supports two types of tags.

Is the pipeline shared library being loaded with legacy SCM or modern SCM?

Which form of pipeline shared library reference is being used, Git, GitHub, or something else?

Can you duplicate the same type of problem using a repository on github.com?

mark.earl.waite@gmail.com (JIRA)

unread,
Jul 23, 2019, 7:07:02 AM7/23/19
to jenkinsc...@googlegroups.com

I'm more suspicious that the issue may be a result of recent changes in scm-api and branch-api, but I'm not able to spend the necessary time currently to do that investigation myself. Which plugins have been updated on your installation since the last successful clone of a tagged pipeline shared library?

If you revert to the plugin versions before the last successful clone of a tagged pipeline shared library?

Has there been a commit to the affected pipeline shared library which has now caused the tagged commit to no longer be the tip of a branch? Refer to JENKINS-48061 as a possible source of additional information about using tagged references to pipeline shared libraries.

mark.earl.waite@gmail.com (JIRA)

unread,
Jul 23, 2019, 7:13:03 AM7/23/19
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-58600
I'm more suspicious that the issue may be a result of recent changes in scm-api and branch-api, but I'm not able to spend the necessary time currently to do that investigation myself.  Which plugins have been updated on your installation since the last successful clone of a tagged pipeline shared library?
If Does it return to correct function if you revert to the plugin versions before the last successful clone of a tagged pipeline shared library?


Has there been a commit to the affected pipeline shared library which has now caused the tagged commit to no longer be the tip of a branch?  Refer to JENKINS-48061 as a possible source of additional information about using tagged references to pipeline shared libraries.

mark.earl.waite@gmail.com (JIRA)

unread,
Jul 23, 2019, 7:15:02 AM7/23/19
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-58600
I'm more suspicious that the issue may be a result of recent changes in scm-api and branch-api, but I'm not able to spend the necessary time currently to do that investigation myself.  Which plugins have been updated on your installation since the last successful clone of a tagged pipeline shared library?

Does it return to correct function if you revert to the plugin versions before the last successful clone of a tagged pipeline shared library?

Has there been a commit to the affected pipeline shared library which has now caused the tagged commit to no longer be the tip of a branch?  Refer to JENKINS-48061 as a possible source of additional information about using tagged non-tip references to pipeline shared libraries.

mark.earl.waite@gmail.com (JIRA)

unread,
Aug 23, 2019, 9:19:02 AM8/23/19
to jenkinsc...@googlegroups.com
Change By: Mark Waite
Status: Fixed but Unreleased Closed

mark.earl.waite@gmail.com (JIRA)

unread,
Aug 23, 2019, 9:19:02 AM8/23/19
to jenkinsc...@googlegroups.com
 

Resolving this as "Cannot reproduce". I recently spent several hours performing various tag related checkouts of pipeline shared libraries as part of confirming that pipeline shared libraries can read a tag. Refer to JENKINS-56175 for the discussions.

Have you added the "Discover tags" trait to the definition of the pipeline shared library (either from the user interface or from inside the Pipeline job definition, depending on where you define your pipeline shared library)?
Change By: Mark Waite
Status: Open Fixed but Unreleased
Resolution: Cannot Reproduce
Reply all
Reply to author
Forward
0 new messages