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

Skip publish for v1 canary and latest #1641

Merged
merged 4 commits into from
Jun 15, 2021

Conversation

carolynvs
Copy link
Member

@carolynvs carolynvs commented Jun 15, 2021

What does this change

  • Move build-images and publish-images into mage so we can apply different publish logic based on if it's canary/latest or a build of the v1 branch
  • Change the naming convention for v1 builds to use canary-v1 and latest-v1 to prevent them from being picked up as tagged versions.
  • Only publish tagged versions for the v1 branch, not latest or canary for now to keep things simpler.
  • Fix .exe file extension for cross compiled windows binaries

What issue does it fix

broken build and other shenanigans

Notes for the reviewer

N/A

Checklist

  • Unit Tests
  • Documentation
  • Schema (porter.yaml)

I was running into conflict with how we detect versions with the other
tagging scheme (v1-latest would get flagged as a real release).
Switching the order so that it's latest-v1 will help avoid a bunch of
false positives and workarounds.

Signed-off-by: Carolyn Van Slyck <me@carolynvanslyck.com>
Do not publish latest-* or canary-* for simplicity

Signed-off-by: Carolyn Van Slyck <me@carolynvanslyck.com>
Signed-off-by: Carolyn Van Slyck <me@carolynvanslyck.com>
I accidentally used xplat.FileExt which isn't helpful because the builds
cross-compiled, so the windows binary was missing the .exe extension.

Signed-off-by: Carolyn Van Slyck <me@carolynvanslyck.com>
@carolynvs carolynvs marked this pull request as ready for review June 15, 2021 15:53
@carolynvs carolynvs changed the title Skip publish Skip publish for v1 canary and latest Jun 15, 2021
@carolynvs carolynvs merged commit fd32c79 into getporter:release/v1 Jun 15, 2021
@carolynvs carolynvs deleted the skip-publish branch June 15, 2021 16:36
carolynvs added a commit to carolynvs/porter that referenced this pull request Jun 15, 2021
* Change permalinks to prefix with canary/latest

I was running into conflict with how we detect versions with the other
tagging scheme (v1-latest would get flagged as a real release).
Switching the order so that it's latest-v1 will help avoid a bunch of
false positives and workarounds.

* Only publish v*, latest and canary

Do not publish latest-* or canary-* for simplicity

Signed-off-by: Carolyn Van Slyck <me@carolynvanslyck.com>
carolynvs added a commit to carolynvs/porter that referenced this pull request Jun 15, 2021
* Change permalinks to prefix with canary/latest

I was running into conflict with how we detect versions with the other
tagging scheme (v1-latest would get flagged as a real release).
Switching the order so that it's latest-v1 will help avoid a bunch of
false positives and workarounds.

* Only publish v*, latest and canary

Do not publish latest-* or canary-* for simplicity

Signed-off-by: Carolyn Van Slyck <me@carolynvanslyck.com>
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