Uploaded image for project: 'MariaDB Foundation Development'
  1. MariaDB Foundation Development
  2. MDBF-336

Preserve several build images on quay

Details

    • Task
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • N/A
    • N/A
    • Buildbot
    • None

    Description

      Currently, the Docker images from our quay.io are overwritten if they for whatever reason are re-created. This may translate into failures in buildbot due to unknown issues even if the images are build successfully (see for example MDBF-330).

      We need a way to preserve the older, functioning image so that in case of failures, we can easily revert to use that until we find the proper solution.

      Attachments

        Issue Links

          is part of

          Task - A task that needs to be done. MDBF-41 Milestone 5: Desirable fixes

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            danblack Daniel Black added a comment -

            On https://quay.io/repository/mariadb-foundation/bb-worker?tab=history there is a revert to xxxx version on the right hand side.

            The current retention of untagged images is currently 1 month (https://quay.io/organization/mariadb-foundation?tab=settings)

            danblack Daniel Black added a comment - On https://quay.io/repository/mariadb-foundation/bb-worker?tab=history there is a revert to xxxx version on the right hand side. The current retention of untagged images is currently 1 month ( https://quay.io/organization/mariadb-foundation?tab=settings )
            faust Faustin Lammler added a comment - - edited

            Yep but this is only a temporary workaround.

            Suggested fix:

            • define a tagging scheme (os:tag?);
            • implement it in the CI;
            • test it (implement a rollback procedure at BB level).
            faust Faustin Lammler added a comment - - edited Yep but this is only a temporary workaround. Suggested fix: define a tagging scheme (os:tag?); implement it in the CI; test it (implement a rollback procedure at BB level).
            faust Faustin Lammler added a comment -

            The containers image workflow has been reworked by rvarzaru and we now have a much better workflow.

            faust Faustin Lammler added a comment - The containers image workflow has been reworked by rvarzaru and we now have a much better workflow.

            People

              faust Faustin Lammler
              vladbogo Vlad Bogolin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: