Make common's update_analyzers job create branches with predictable names
Problem to solve
Currently, the branches created in the analyzer projects by the update_analyzers job have names that differ from project to another. It makes it difficult to loop over these branches to repeat the same action, like fetching the branch, updating the changelog, and pushing the update.
Currently, the name of the source branch is set in the update_common job, and includes the job id of this job.
Intended users
groupstatic analysis and groupcomposition analysis teams.
Proposal
Change the update_analyzers job so that it generates the name of the source branch, and pass it to the update_common job, and remove the SOURCE_BRANCH variable. The branches created in the same "batch" will share the same name.
Permissions and Security
Same.
Documentation
The update_analyzers and update_common jobs are not documented.
Availability & Testing
Can be tested by forcing PROJECT_IDS to one particular analyzer project, and creating a new tag for the common project. The tag should not be the one of an official release.
What does success look like, and how can we measure that?
All the source branches created in the same batch (from the same update_analyzers job) all share the same name.
Is this a cross-stage feature?
yes. both groupcomposition analysis and groupstatic analysis will benefit from this.