when workflow uses multiple git repos the "git build data" and "tags" become next to useless.

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...
}