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.

Sign up for GitHub

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

Jump to bottom

Make ACCESS-OM2 availible for Prerelease Environments #34

Closed
CodeGat opened this issue Feb 1, 2024 · 2 comments · Fixed by #35
Closed

Make ACCESS-OM2 availible for Prerelease Environments #34

CodeGat opened this issue Feb 1, 2024 · 2 comments · Fixed by #35
Assignees
@CodeGat
Labels
priority:high type:enhancement type:infra Related to CI/CD

Comments

@CodeGat
Copy link
Member

CodeGat commented Feb 1, 2024

Prereleases will be supported on access-nri/build-cd. We want this functionality for ACCESS-OM2, too.

References ACCESS-NRI/build-cd#32
Closes #33 as regular deployments are no longer deployed on git tag, but on merge after a successful prerelease deployment.
@CodeGat CodeGat self-assigned this Feb 1, 2024
@CodeGat CodeGat added the type:infra Related to CI/CD label Feb 1, 2024
@CodeGat CodeGat mentioned this issue Feb 1, 2024
Merged
@CodeGat
Copy link
Member Author

CodeGat commented Feb 1, 2024

Something to note: Should we tag prereleases? Upon deletion of the PR branch, these *-pre* tags will still be accessible.
We should still autotag the merges to main.

@CodeGat
Copy link
Member Author

CodeGat commented Feb 2, 2024

Note: No, no we shouldn't

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

@CodeGat CodeGat

Labels
priority:high type:enhancement type:infra Related to CI/CD
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Prerelease Functionaility ACCESS-NRI/ACCESS-OM2
1 participant
@CodeGat