Skip to content
Snippets Groups Projects

Update auto-build-image to v1.5.0

All threads resolved!

What does this MR do and why?

This was a feature-flagged change, see rollout issue #337990 (closed)

We delete the feature flag here to prevent confusion in production if the latest template falls behind stable.

The latest template must, however, remain, as removing it is a breaking change.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Hordur Freyr Yngvason

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • A deleted user added backend label

    added backend label

  • 2 Warnings
    :warning:

    featureaddition and featureenhancement merge requests normally have a documentation change. Consider adding a documentation update or confirming the documentation plan with the Technical Writer counterpart.

    For more information, see:

    :warning: You've made some app changes, but didn't add any tests.
    That's OK as long as you're refactoring existing code,
    but please consider adding any of the ~"type::tooling", ~"tooling::pipelines", ~"tooling::workflow", documentation, QA labels.
    1 Message
    :book: This merge request adds or changes files that require a review from the CI/CD Templates maintainers.

    This merge request requires a CI/CD Template review. To make sure these changes are reviewed, take the following steps:

    1. Ensure the merge request has the citemplates label. If the merge request modifies CI/CD Template files, Danger will do this for you.
    2. Prepare your MR for a CI/CD Template review according to the template development guide.
    3. Assign and @ mention the CI/CD Template reviewer suggested by Reviewer Roulette.

    The following files require a review from the CI/CD Templates maintainers:

    • lib/gitlab/ci/templates/Jobs/Build.gitlab-ci.yml
    • lib/gitlab/ci/templates/Jobs/Build.latest.gitlab-ci.yml

    Reviewer roulette

    Changes that require review have been detected!

    Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

    Category Reviewer Maintainer
    backend Shreyas Agarwal (@shreyasagarwal) (UTC+1, 6 hours ahead of @hfyngvason) Douglas Barbosa Alexandre (@dbalexandre) (UTC-3, 2 hours ahead of @hfyngvason)
    citemplates Lucas Charles (@theoretick) (UTC-8, 3 hours behind @hfyngvason) Marcel Amirault (@marcel.amirault) (UTC+9, 14 hours ahead of @hfyngvason)

    To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

    To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

    Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

    If needed, you can retry the danger-review job that generated this comment.

    Generated by :no_entry_sign: Danger

  • Setting label(s) ~"group::configure" based on ~"devops::configure".

  • added 1175 commits

    Compare with previous version

  • requested review from @tigerwnz

  • Hordur Freyr Yngvason marked this merge request as ready

    marked this merge request as ready

  • Hordur Freyr Yngvason marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed

    marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed

  • added 1 commit

    Compare with previous version

  • Tiger Watson resolved all threads

    resolved all threads

  • Tiger Watson approved this merge request

    approved this merge request

  • Tiger Watson requested review from @marcel.amirault and @dbalexandre and removed review request for @tigerwnz

    requested review from @marcel.amirault and @dbalexandre and removed review request for @tigerwnz

  • :wave: @tigerwnz, thanks for approving this merge request.

    This is the first time the merge request is approved. To ensure full test coverage, a new pipeline has been started.

    For more info, please refer to the following links:

  • Marcel Amirault approved this merge request

    approved this merge request

  • Marcel Amirault removed review request for @marcel.amirault

    removed review request for @marcel.amirault

  • Douglas Barbosa Alexandre approved this merge request

    approved this merge request

  • resolved all threads

  • Douglas Barbosa Alexandre enabled an automatic merge when the pipeline for 412f525a succeeds

    enabled an automatic merge when the pipeline for 412f525a succeeds

  • mentioned in commit 075476b8

  • added workflowcanary label and removed workflowstaging label

  • Please register or sign in to reply
    Loading