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

Remove workflow_dispatch from test-porter-release action #3094

Merged

Conversation

kichristensen
Copy link
Contributor

@kichristensen kichristensen commented May 4, 2024

What does this change

Parameters cannot be used when triggered by anything other than workflow_dispatch. As this action is also triggered on PRs targeting the main branch, it cannot use parameters. An example of a failing action can be found here https://github.com/getporter/porter/actions/runs/8909019136.
Instead the parameters are no longer dynamic and the default values have been hardcoded.

UPDATE:
As the content of this workflow is already covered by the porter/porter-canary workflow, test-porter-release is deleted instead.

Checklist

  • Did you write tests?
  • Did you write documentation?
  • Did you change porter.yaml or a storage document record? Update the corresponding schema file.
  • If this is your first pull request, please add your name to the bottom of our Contributors list. Thank you for making Porter better! 🙇‍♀️

Parameters cannot be used when triggered by anything other than
workflow_dispatch. As this action is also triggered on PRs targeting
the main branch, it cannot use parameters.

Signed-off-by: Kim Christensen <kimworking@gmail.com>
@kichristensen kichristensen self-assigned this May 4, 2024
@kichristensen kichristensen removed their assignment May 4, 2024
@schristoff
Copy link
Member

Now this is showing "test-porter-release" job on PRs, and I think we only want it on nightly or when there is a merge into main :/

@kichristensen
Copy link
Contributor Author

@schristoff Good point, actually we might not want it at all, as the flow is also "tested" when producing the canary build on merge to main. That could be an argument for deleting the workflow all together. What to you think?

@schristoff
Copy link
Member

I'm cool with deleting it :)

kichristensen and others added 2 commits May 5, 2024 22:27
The functionality is already covered by the canary release deployment

Signed-off-by: Kim Christensen <kimworking@gmail.com>
@kichristensen
Copy link
Contributor Author

@schristoff it is deleted instead

@kichristensen kichristensen merged commit 1872d3e into getporter:main May 5, 2024
15 checks passed
@kichristensen kichristensen deleted the fixTestPorterReleasePipeline branch May 5, 2024 20:55
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.

2 participants