Skip to content

'latest' tags should not push automatically #56

Description

@TimHess

The current image build process for 3/4 of the images in this repo:

  1. Download starter from start.spring.io
  2. Apply patches
  3. gradlew bootBuildImage
  4. if building in CI due to a merge to main:
    1. tag image based on metadata files, including latest
    2. push all tags

As a result, when we do things like #54 (which may not intend to change anything in any image), we've updated the latest tag of our images, potentially with unknown changes.

The process is nice enough for intended changes, but doesn't have enough controls in place for unintended changes. We need more control over whether/which tags should be pushed

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions