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

Consider moving official build signing out of the main build pipeline #13

Open
dagood opened this issue Mar 12, 2021 · 0 comments
Open

Comments

@dagood
Copy link
Member

dagood commented Mar 12, 2021

We can move signing out of the main build pipeline into an independent pipeline.

  • The main build pipeline could complete whether or not signing has finished yet, for more throughput regardless of signing infra speed/state.
  • If the signing infrastructure needs to change, it can be updated in one infra branch that applies to all Go branches.
    • A "floating" dependency like this is a red flag. It can cause unanticipated build breaks, and makes it hard to resurrect an old branch if the floating branch has had breaking changes since the last successful build.
    • This might be ok to float, because the set of artifacts seems like it will be relatively simple and stable over time.
    • If we need to update the version of signing tooling, it could be tedious to cherry-pick the change to each branch. updating just one branch is a way to avoid that. Another way would be to figure out how to set up auto-updates for these versions.
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

No branches or pull requests

1 participant