Skip to content

Conversation

@chatton
Copy link
Contributor

@chatton chatton commented May 30, 2021

This PR adds a GitHub Action which builds and pushes all of our images to Quay. The release process is as follows.

  • Manually trigger the Create Release PR action (master branch release.json should contain the desired versions, any that do not exist, will be built and released. no-op for already released images.)
  • Approve PR once all tasks have run. (triggers github release to be drafted, release text comes from docs/RELEASE_NOTES.md)
  • Publish draft (Release PR will be auto-merged and deleted)

This PR also includes a bump for the operator to version 0.6.1, so when the release task is called we can release this new operator version.

The evergreen release tasks have been removed.

@chatton chatton changed the base branch from add_github_action_to_create_release_pr to master June 5, 2021 23:17
@chatton chatton changed the base branch from master to add_github_action_to_create_release_pr June 5, 2021 23:20
Base automatically changed from add_github_action_to_create_release_pr to master June 8, 2021 14:40
@chatton chatton marked this pull request as ready for review June 8, 2021 15:48
raise ValueError("usage: determine_required_releases.py [image-name]")
image_name_map = _load_image_name_to_version_map()

if sys.argv[1] not in image_name_map:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we define a variable image_name = sys.argv[1] and use it in all 6 places?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, good idea 👍

args.image_name
)
)
return 0

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we want to exit here with code 0 or an error code?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right good catch, the reason for a 0 here rather than error, is that we run this task for every image we are going to release. This will update the release as a support version (for agent only currently), but we need this to be a no-op rather than failure for the other images.

This task will currently only fail if there is an error when interacting with the release database in Atlas.

Copy link
Contributor

@rodrigovalin rodrigovalin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@chatton chatton merged commit 948706d into master Jun 10, 2021
@chatton chatton deleted the github_actions_test branch June 10, 2021 13:59
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.

4 participants