Not sure if this is a duplicate.
Background
Despite all the automation, there are still a few manual steps in order to run the full pipeline of Prerelease build -> Open a bunch of configs PRs -> Validate repro.
Find a way to automate the Prerelease build -> Configs PRs stuff.
Implementation details
Create a new comment command !configs for MDRs. It reads from a MDRs configs/auto-configs-pr.json configuration file.
That at minimum can do the following:
!configs # To open PRs that are defined in the default profile
!configs profile=PROFILE # To open PRs that are defined in the PROFILE profile
In future, consider the ability to specify configs irrespective (or maybe including) a profile:
!configs CONFIG... # For example, !configs dev-01deg_jra55_iaf dev-1deg_jra55_ryf
!configs profile=PROFILE CONFIG... # Use configuration from PROFILE, plus CONFIGs
Not sure if this is a duplicate.
Background
Despite all the automation, there are still a few manual steps in order to run the full pipeline of Prerelease build -> Open a bunch of configs PRs -> Validate repro.
Find a way to automate the Prerelease build -> Configs PRs stuff.
Implementation details
Create a new comment command
!configsfor MDRs. It reads from a MDRsconfigs/auto-configs-pr.jsonconfiguration file.That at minimum can do the following:
In future, consider the ability to specify configs irrespective (or maybe including) a profile: