Skip to content
Snippets Groups Projects

point tag to string latest

Merged point tag to string latest
wip/ritesh/point-tag-to-latest into apertis/v2022dev2
1 unresolved thread
Merged Ritesh Raj Sarraf requested to merge wip/ritesh/point-tag-to-latest into apertis/v2022dev2
1 unresolved thread

Signed-off-by: Ritesh Raj Sarraf ritesh.sarraf@collabora.com

Merge request reports

Pipeline #213046 passed

Stage: base rootfs
    Stage: base image
      Stage: derived images
        Stage: image test
          Stage: publish images

            Pipeline passed for b26ad3fa on wip/ritesh/point-tag-to-latest

            Approval is optional

            Merged by Ritesh Raj SarrafRitesh Raj Sarraf 4 years ago (Mar 10, 2021 8:41am UTC)

            Merge details

            • Changes merged into with b26ad3fa.
            • Deleted the source branch.

            Pipeline #213047 passed

            Stage: base rootfs
              Stage: base image
                Stage: derived images
                  Stage: image test
                    Stage: publish images

                      Pipeline passed for b26ad3fa on apertis/v2022dev2

                      Activity

                      Filter activity
                      • Approvals
                      • Assignees & reviewers
                      • Comments (from bots)
                      • Comments (from users)
                      • Commits & branches
                      • Edits
                      • Labels
                      • Lock status
                      • Mentions
                      • Merge request status
                      • Tracking
                      .gitlab-ci.yml
                      29 29 RELEASE="${CI_COMMIT_BRANCH#*/}"
                      30 30 TAG=latest
                      31 31 else
                      32 TAG=$CI_COMMIT_REF_SLUG
                      32 TAG="latest"
                      • Emanuele Aina
                        Emanuele Aina @em ·
                        Owner

                        This is quite wrong to be honest, but it's definitely my fault for not having documented all the nuances here. :)

                        Once we have things running we can probably just clean the apertis/v2022dev2 history and pretend this never happened. ;)

                      • Ritesh Raj Sarraf
                        Ritesh Raj Sarraf @ritesh ·
                        Author Owner

                        Yes. I added it (and self merged it) knowing that apertis/v2022dev2 will have to be re-done once the initial pull from Bullseye is complete.

                        The current changes are just to get the bullseye-package-source-builder built and rolling.

                      • Please register or sign in to reply
                      Please register or sign in to reply
                      Apertis Website Terms of Use Privacy Policy