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

Replace existing deb/fpm workflows with goreleaser #28830

Closed
codeboten opened this issue Oct 31, 2023 · 4 comments
Closed

Replace existing deb/fpm workflows with goreleaser #28830

codeboten opened this issue Oct 31, 2023 · 4 comments
Assignees
Labels
ci-cd CI, CD, testing, build issues closed as inactive Stale

Comments

@codeboten
Copy link
Contributor

Component(s)

No response

Describe the issue you're reporting

Currently we build the fpm/deb packages differently than we do in the releases repo, this should be consistent. It will also resolve the issue of updating to the latest version of ubuntu.

@codeboten codeboten added the ci-cd CI, CD, testing, build issues label Oct 31, 2023
@codeboten codeboten self-assigned this Oct 31, 2023
Copy link
Contributor

github-actions bot commented Jan 1, 2024

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Jan 1, 2024
@cwegener
Copy link
Contributor

cwegener commented Jan 1, 2024

It will also resolve the issue of updating to the latest version of ubuntu.

That issue is actually unrelated to the package building. It's an issue with the package installation testing that happens after the packages are built, see open-telemetry/opentelemetry-collector-releases#623 and #30202

Consistently building the binaries the same way during development and release will be good to have for some peace of mind though.

I'm happy to have a look at how big that migration task is and make a plan for the migration.

@github-actions github-actions bot removed the Stale label Jan 2, 2024
Copy link
Contributor

github-actions bot commented Mar 4, 2024

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Mar 4, 2024
Copy link
Contributor

github-actions bot commented May 3, 2024

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-cd CI, CD, testing, build issues closed as inactive Stale
Projects
None yet
Development

No branches or pull requests

2 participants