Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
Jenkins 1.609.1
Workflow 1.9-beta-1
git 2.4.0
git-client 1.18.0
-
-
Pipeline - October, Pipeline - April 2018
Description
if you have a workflow which uses multiple git repositories the actions and data contributed to the build by the git plugin produce almost unusable visual spam.
The tag action does not let you know which repository you are tagging, nor does the build data tell you which repository it is that has the specified hash.
Coupled with this you end up with 2 * the number of repos used (plus another 2 if you use workflow from SCM) actions - which simply does not scale. The actions should be refactored so there is one action that can display the data from multiple repositories / invocations and it should be clear which revision comes from which repo.
node {
git url: 'git@github.com:jenkinsci/git-client-plugin.git'
git url: 'git@github.com:jenkinsci/git-plugin.git'
git url: 'git@github.com:jenkinsci/github-plugin.git'
// just add more random repos to get the picture...
}
Attachments
Issue Links
- depends on
-
-
- Reopened
-
- is related to
-
-
- Resolved
-
-
JENKINS-54868 Display Organization/Project and Repository name(s) on the job details page
-
- Open
-
- links to
Activity
It would consider it a bug if I did not see the version/changes of the shared library, after all a shared library can change how your build happens and I would not like to see a build failure due to a new library with no changes, at the end time ss a lib owner I would want to be able to check that all projects had built correctly using the latest lib
teilo I think you meant to comment on JENKINS-41497. Last I looked at it, the proposal was to make this configurable, whether that be on the library or in the job.
jglick no, I was responding to abayer's comment. JENKINS-41497 is about triggering a build when a shared library is updated as I understand the original problem report.
teilo - So JENKINS-41497 covers both triggering and listing the shared library's changes. It's the same mechanisms behind the scenes, as it turns out. So the shared libraries aspect of this is dealt with.
jamesdumay - I believe this needs some thought and triage to see what other tickets are related to this - JENKINS-29326 may have popped up again, e.g.
Not really. I think we probably need an epic for reworking the backend for a bunch of APIs around reporting checkouts - there's this, there's dupes, there's shared libraries always showing up, etc...