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

Tweak staging invocation #131

Merged
merged 5 commits into from
Mar 14, 2024
Merged

Conversation

jku
Copy link
Member

@jku jku commented Mar 14, 2024

Main change here is the staging invocation: I'm proposing that a single action invocation only runs the testsuite once because

  • xfails becames painful if staging expected failures are not the same as prod (which seems like a normal thing at times).
  • The test results are much clearer ("Staging conformance failure" is not as critical as "production conformance failure")

Other changes in this PR (from testing and reviewing for a hopefully near future release):

  • run selftest daily (and on dispatch)
  • update linter config to silence warnings
  • update cli protocol doc and move --staging so it's not after the artifact filename

Fixes #130

I'll mark William a reviewer since we originally agreed to run test suite twice but I think we may have been wrong.


For release Notes:

  • The action now supports testing against Sigstore staging infrastructure: if your Sigstore client can be used with staging, please enable this by adding a second step to your workflow: see README

jku added 5 commits March 14, 2024 18:49
This was originally combined into a single invocation for convenience
but I believe this is more work than gain:
* xfails alone became painful if staging expected failures are not the
  same as prod (which seems like a normal thing at times).
* The test results are much clearer ("Staging conformance failure" is
  not as critical as "production conformance failure")

This means the caller does need to run the action twice to get both
tests

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
If we promise the order is static, let's make it something
sensible (don't have --staging after the artifact input).

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
We already have --trusted-root that also is not always present.

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
* Update config to current style
* use "ruff check" instead of "ruff"

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
Results should not change... except if infrastructure changes.

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
@jku jku requested a review from woodruffw March 14, 2024 18:01
@woodruffw
Copy link
Member

I'm proposing that a single action invocation only runs the testsuite once because

  • xfails becames painful if staging expected failures are not the same as prod (which seems like a normal thing at times).
  • The test results are much clearer ("Staging conformance failure" is not as critical as "production conformance failure")

Makes sense to me, thanks for documenting!

@woodruffw woodruffw merged commit 45d9f6d into sigstore:main Mar 14, 2024
3 checks passed
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.

how should we enable staging
2 participants