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

fix: pipeline and helm release #59

Conversation

mishraomp
Copy link
Collaborator

No description provided.

…process-as-we-have-pr-numbers-now-as-part-of-merge' into 57-fix-the-pipeline-and-release-process-as-we-have-pr-numbers-now-as-part-of-merge
@mishraomp
Copy link
Collaborator Author

need to find another way @DerekRoberts , cannot call .deploy.yaml, as secrets are redacted from outputs, and by default github does not allow sharing env vars between jobs.

outputs are not passed as seen below.
https://github.com/bcgov/nr-oracle-service/actions/runs/7775774985/job/21202161985#step:9:4

env var limitation:
https://github.com/orgs/community/discussions/26313
https://github.com/bcgov/nr-oracle-service/actions/runs/7775812852

@mishraomp mishraomp merged commit 69806e3 into main Feb 4, 2024
4 checks passed
@mishraomp mishraomp deleted the 57-fix-the-pipeline-and-release-process-as-we-have-pr-numbers-now-as-part-of-merge branch February 4, 2024 18:36
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.

fix the pipeline and release process as we have PR numbers now as part of merge
2 participants