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

automatically create experimental-binaries package on release #1781

Closed
spoonincode opened this issue Oct 16, 2023 · 0 comments · Fixed by AntelopeIO/asset-artifact-download-action#4 or #1809
Assignees
Labels
CICD Anything dealing with the CI workflow behavior 👍 lgtm

Comments

@spoonincode
Copy link
Member

spoonincode commented Oct 16, 2023

User Story:
The AntelopeIO/leap development team wants an automated process to create the "experimental-binaries" docker image on each release so that we can streamline the management of semi-supported binary packages.

Considerations:

  • We should not make these packages highly visible to avoid implying a higher level of support than actually exists

Acceptance Criteria:

  • The automated process should trigger when a release is created.
  • It should search for the necessary packages as workflow artifacts.
  • The "experimental-binaries" docker image should be created using these packages.
  • The manual steps involving Docker build and push commands for the image creation should be eliminated.

Definition of Done:

  • The automated process has been implemented and successfully tested.
  • The "experimental-binaries" docker image is created automatically on release.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment