Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adapt docker images #49

Merged
merged 1 commit into from
Apr 25, 2023
Merged

Adapt docker images #49

merged 1 commit into from
Apr 25, 2023

Conversation

nichtsfrei
Copy link
Member

Pushes the version tags to docker hub on a tag release

  • greenbone/boreas:${major}
  • greenbone/boreas:${major.minor}
  • greenbone/boreas:${major.minor.patch}

This will allow container users to choose the newest 22 without having to adapt to each minor or patch version manually. If the latest 22 is buggy, they can jump back to either a patch or a minor version until there is a new 22 version that fixes it.

When the tag version is the highest major version and is not the first major release with minor and patch version is 0 than it also creates a latest and stable tag.

Just to give an overview, here are some examples:

Release 22.5.1 on greenbone/boreas would result in the following tags:

  • greenbone/boreas:22
  • greenbone/boreas:22.5
  • greenbone/boreas:22.5.1
  • greenbone/boreas:latest
  • greenbone/boreas:stable

Release 23.0.0 on greenbone/boreas would result in the following tags:

  • greenbone/boreas:23
  • greenbone/boreas:23.0
  • greenbone/boreas:23.0.0

Release 23.0.1 on greenbone/boreas would result in the following tags:

  • greenbone/boreas:23
  • greenbone/boreas:23.0
  • greenbone/boreas:23.0.1
  • greenbone/boreas:latest
  • greenbone/boreas:stable

Release 22.5.2 when there is already a 23.0.1 version available would result in the following tags:

  • greenbone/boreas:22
  • greenbone/boreas:22.5
  • greenbone/boreas:22.5.2

Pushes the version tags to docker hub on a tag release

- greenbone/boreas:${major}
- greenbone/boreas:${major.minor}
- greenbone/boreas:${major.minor.patch}

This will allow container users to choose the newest 22 without
having to adapt to each minor or patch version manually. If the
latest 22 is buggy, they can jump back to either a patch or a minor
version until there is a new 22 version that fixes it.

When the tag version is the highest major version and is not the first
major release with minor and patch version is 0 than it also creates a
latest and stable tag.

Just to give an overview, here are some examples:

Release 22.5.1 on greenbone/boreas would result in the
following tags:

- greenbone/boreas:22
- greenbone/boreas:22.5
- greenbone/boreas:22.5.1
- greenbone/boreas:latest
- greenbone/boreas:stable

Release 23.0.0 on greenbone/boreas would result in the
following tags:

- greenbone/boreas:23
- greenbone/boreas:23.0
- greenbone/boreas:23.0.0

Release 23.0.1 on greenbone/boreas would result in the
following tags:

- greenbone/boreas:23
- greenbone/boreas:23.0
- greenbone/boreas:23.0.1
- greenbone/boreas:latest
- greenbone/boreas:stable

Release 22.5.2 when there is already a 23.0.1 version available would
result in the following tags:

- greenbone/boreas:22
- greenbone/boreas:22.5
- greenbone/boreas:22.5.2
@nichtsfrei nichtsfrei requested review from a team as code owners April 21, 2023 09:30
@nichtsfrei nichtsfrei marked this pull request as draft April 21, 2023 09:31
@nichtsfrei nichtsfrei marked this pull request as ready for review April 21, 2023 09:38
@nichtsfrei nichtsfrei enabled auto-merge (rebase) April 21, 2023 10:58
@nichtsfrei nichtsfrei merged commit a1b0804 into greenbone:main Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant