It is a FreeStyle job, we have a embedded chip platform in which we need to cross compile a board support package inside a docker container. To do this we clone a fork of a community repo along with a few private repos containing some of our proprietary tooling.
Since this step is one of many, I would like to create an artifact listing each commit of each repo that was used in the build with the idea that this artifact will contain a full manifest of all resources (repos/commits, upstream artifacts along with the repos/commits used to build them) used in each build along the entire pipeline.
Currently we have get all this info from the log files and I have been tasked with finding a way to automate the process. One solution would be to recursively go through the entire folder structure of each build via a bash script, however using environment vars from Jenkins would make it a whole lot easier.
Can you clarify the context where you're envisioning using multiple repositories?
For example, if you're using multiple repositories in a FreeStyle job, then this enhancement is needed.
If you're using multiple repositories in a scripted pipeline job, this enhancement is not likely to be needed, since
JENKINS-26100provides the value of the SHA1 checkout for each call to the checkout command (along with many other values related to the checkout).