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

DO NOT MERGE: Enable tuf-on-ci #1313

Closed
wants to merge 2 commits into from
Closed

Conversation

jku
Copy link
Member

@jku jku commented Aug 12, 2024

Do not merge, this is informative only at this point.

These are the workflow changes I propose we include in the initial signing event PR, I'm making this a draft PR already so these can be reviewed separately and in advance of the actual signing event (#929).

Contents

  • Remove legacy workflows
  • Enable tuf-on-ci workflows (except publishing to production: let's do that after manual testing)
  • Add a note in README: Let's fixup the README after the event

@jku
Copy link
Member Author

jku commented Aug 12, 2024

I'm filing an issue to remove some of the expected checks and will fix this PR so it does not remove the workflow linting

@jku
Copy link
Member Author

jku commented Aug 12, 2024

@kommendorkapten please have a look at some point

@jku jku mentioned this pull request Aug 12, 2024
17 tasks
Copy link
Member

@kommendorkapten kommendorkapten left a comment

Choose a reason for hiding this comment

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

LGTM

Note that deployment to GCS is still commented out in publish workflow.

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
Delete legacy (meaning non- tuf-on-ci)
 * timestamp and snapshot workflows
 * GCS uploading workflows
 * signing event management workflows (dealing with "ceremony/" dirs)
 * various verification workflows: now handled by the
   tuf-on-ci tests and custom-test.yml

Remove these outright to prevent accidental changes to metadata from two
different maintenance systems.

If it turns out the migration will not be successful in the timeframe it
has, the PR that contains this commit needs to be reverted so the legacy
system can continue operation.

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
@jku
Copy link
Member Author

jku commented Aug 21, 2024

rebased on main to keep this up-to-date.

@jku
Copy link
Member Author

jku commented Aug 30, 2024

closing as I've merged to PR 1323

@jku jku closed this Aug 30, 2024
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