Scheduled Pipelines should be able to be run against the project's default branch.
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
Scheduled pipelines much have a specific branch specified. If that branch ever gets deleted, the scheduled pipeline will fail. It is not possible to have a scheduled pipeline that always runs against, say, the default branch of the project.
Further details
My company uses build branches, that always are created from master, and merged to master. Every version we make, we set the default branch to be, say, v2.3.4. However, we would like to have scheduled deployments of these build branches to our test environment at noon (for example). We currently have to manually update every project with a scheduled job to the new version, which can get very tedious and error prone.
Proposal
I propose we allow jobs (or scheduled jobs at any rate) have the ability to specify $default_branch (or some other name) as the branch target. This will always be set to the project's default branch, if it exists. This will allow the scheduled job to always run against the right branch, without any manual interference.
This could, later, be expanded to support more variables, or a RegEx pattern to run against multiple branches, etc.
What does success look like, and how can we measure that?
Success is if it becomes possible to schedule a pipeline for the default branch, change the default branch, and have the schedule run against the new default.