Monitor LAVA jobs when forcing their submission (!455) · Merge requests · infrastructure / apertis-image-recipes · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.

Emanuele Aina requested to merge wip/em/monitor-jobs-when-forcing-submittions into apertis/v2023dev1 Nov 29, 2021

When setting SUBMIT_LAVA_JOBS = 1 externally we were still not monitoring the LAVA jobs on secondary branches.

Fix that so that forcing SUBMIT_LAVA_JOBS = 1 causes the pipeline to both submit and monitor the LAVA jobs.

Apertis Website Terms of Use Privacy Policy