-
Notifications
You must be signed in to change notification settings - Fork 81
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
Add tuf-on-ci workflows #1256
Add tuf-on-ci workflows #1256
Conversation
d5451b7
to
f2e4e49
Compare
This comment was marked as outdated.
This comment was marked as outdated.
f2e4e49
to
0bb632f
Compare
... and I had to rebase because the renamed workflow confused githubs merge resolution |
I've included the GCP details in the online-sign workflow:
|
Same name is used in tuf-on-ci workflows: I would rather rename this one since the tuf-on-ci workflow is used with workflow_call so referenced in other workflows Signed-off-by: Jussi Kukkonen <[email protected]>
These are direct copies from root-signing-staging: the required changes are done in separate commits to make them visible. Signed-off-by: Jussi Kukkonen <[email protected]>
Workflows were copied from staging. Modify them for production: * Tweak PR and issue templates * test workflows require URL changes (and some variable name changes) * test workflows also get a new step where initial root is defined (as python-tuf does not consider root < 5 to be valid) * deploy-to-gcs was modified so the gcloud details are internal to the workflow (since in prod it's a separate gcloud project/account, not the "tuf-on-ci online signing accout") Signed-off-by: Jussi Kukkonen <[email protected]>
* Disable all scheduled runs * Additionally remove publishing to GCS completely for now Signed-off-by: Jussi Kukkonen <[email protected]>
This test was just added in root-signing-staging so was not in the initial copy. Signed-off-by: Jussi Kukkonen <[email protected]>
Original design uses GitHub variables: This keeps the online-sign workflow unchanged from the upstream one and would be nice if the variables were managed with configuration-as-code. Unfortunately this is not possible in root-signing. Embed GCP details in the workflow. Signed-off-by: Jussi Kukkonen <[email protected]>
4ba1fbd
to
94a24d9
Compare
I had to rebase as GitHub uses a conflict resolution that failed in this case (the default one in git rebase just works). No changes. |
Add workflows for tuf-on-ci (see #1247 and for larger context #929).
These workflows should be complete and ready however: