We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Related: #2998
Related workflow run: https://github.com/infinyon/fluvio/actions/runs/4265630810/jobs/7425189192
The use this check for idempotence for publish/release. The intent is to prevent unnecessary re-building and re-publishing fluvio CLI.
fluvio
fluvio/.github/workflows/release.yml
Lines 205 to 211 in 2ca78f0
However, this condition is used for individual packages as well. We skip if only the fluvio binary is found.
Consequently, based on the current order of publish (fluvio CLI is first), runs that fail during package publish will always get skipped on re-runs.
We need a few things to make testing this easier to do in the future:
If we had package-level checks for publish/release, that would be equally as impactful.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Related: #2998
Related workflow run: https://github.com/infinyon/fluvio/actions/runs/4265630810/jobs/7425189192
The use this check for idempotence for publish/release. The intent is to prevent unnecessary re-building and re-publishing
fluvio
CLI.fluvio/.github/workflows/release.yml
Lines 205 to 211 in 2ca78f0
However, this condition is used for individual packages as well. We skip if only the
fluvio
binary is found.Consequently, based on the current order of publish (
fluvio
CLI is first), runs that fail during package publish will always get skipped on re-runs.We need a few things to make testing this easier to do in the future:
fluvio
CLI lastAlternate approach
If we had package-level checks for publish/release, that would be equally as impactful.
The text was updated successfully, but these errors were encountered: