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

[chore] add fixes for otelcol-contrib to release pipeline #760

Closed

Conversation

mowies
Copy link
Member

@mowies mowies commented Dec 4, 2024

This PR adds missing changes to the release pipeline that should have been part of #666

Signed-off-by: Moritz Wiesinger <[email protected]>
Signed-off-by: Moritz Wiesinger <[email protected]>
@mowies mowies marked this pull request as ready for review December 4, 2024 15:18
@mowies mowies requested a review from a team as a code owner December 4, 2024 15:18
@mowies mowies requested a review from fatsheep9146 December 4, 2024 15:18
distribution: goreleaser-pro
version: ${{ env.GORELEASER_PRO_VERSION }}
workdir: distributions/${{ inputs.distribution }}
args: release --clean --split --timeout 2h --config .goreleaser-build.yaml --release-header-tmpl=../../.github/release-template.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens when release --clean --split --timeout 2h --release-header-tmpl=../../.github/release-template.md is called again below?

Copy link
Member Author

@mowies mowies Dec 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the build for otelcol-contrib is split between 2 different goreleaser config files as of #666. so the first call gets a different config than the second one. (.goreleaser-build.yaml and .goreleaser.yaml)
the first call will just build the binaries, the second one continues business as is, while importing the prebuilt binaries and it should then continue as usual

Copy link
Member

@TylerHelmuth TylerHelmuth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking this for now in favor of #761. @mowies to move forward with the release in a guaranteed way we are gonna revert the original breaking PR. We'll get you a goreleaser-pro key so you can test everything in your fork before we merge it back into this repo

@mowies
Copy link
Member Author

mowies commented Dec 5, 2024

sounds good, I was gonna suggest the same thing

@mowies
Copy link
Member Author

mowies commented Dec 5, 2024

closing this in favor of #762

@mowies mowies closed this Dec 5, 2024
@mowies mowies deleted the fix-release-pipelines branch December 5, 2024 07:39
@mowies
Copy link
Member Author

mowies commented Dec 5, 2024

@TylerHelmuth @atoulme @mx-psi the new PR is ready for review. I was able to properly test it with a goreleaser-pro token:
#762

Test release on my fork was successful, i linked the workflow runs and the test release in the PR

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