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

deduplicate builds / publishing pipelines #509

Open
ccwienk opened this issue Jan 20, 2025 · 1 comment
Open

deduplicate builds / publishing pipelines #509

ccwienk opened this issue Jan 20, 2025 · 1 comment
Labels
component/cicd Continuous integration/delivery (tooling and processes) component/gardenctl Gardener CLI kind/enhancement Enhancement, improvement, extension kind/technical-debt Something that is only solved on the surface, but requires more (re)work to be done properly

Comments

@ccwienk
Copy link
Member

ccwienk commented Jan 20, 2025

Context / Motivation

Buildresults from this repository are built and published twice:

  • using concourse-pipeline / publishing as OCM-Component + github-release-assets ref
  • using GitHub-Actions/workflows to publish to brew / chocolatery ref

Having duplicate pipelines (which both build the same build-results) has the disadvantage of publishing different binaries (even for same sources, builds will typically yield slightly different binaries, as e.g. timestamps will affect output).

Considering there is an ongoing activity to migrate from Concourse -> GitHub-Actions, an obvious choice might be to extend existing GHA-Workflow to also create/publish GitHub-Releases and OCM-Component-Descriptors (there are some reusable github-actions / workflows at cc-utils - currently still WIP).

@ccwienk ccwienk added component/gardenctl Gardener CLI kind/enhancement Enhancement, improvement, extension kind/technical-debt Something that is only solved on the surface, but requires more (re)work to be done properly component/cicd Continuous integration/delivery (tooling and processes) labels Jan 20, 2025
@petersutter
Copy link
Member

As first measurement we have disabled the binary upload from the concurse pipeline ref

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/cicd Continuous integration/delivery (tooling and processes) component/gardenctl Gardener CLI kind/enhancement Enhancement, improvement, extension kind/technical-debt Something that is only solved on the surface, but requires more (re)work to be done properly
Projects
None yet
Development

No branches or pull requests

2 participants