Jesse Glick
Jesse Glick
> Rebuilding BTW **Re-run** from **Checks** should work.
> I think it should be good enough to mention that you may need to approve some signatures after the update in the release notes. Agreed
> If you don't want them, I'll go ahead and revert them. Yes please. It is not just about comfort when reviewing diffs; if we ever need to `git cherry-pick`...
> would the automatic PR test job deploy a timestamped snapshot Afraid not. > does it have to be deployed in some other way? IIRC you just need a jenkins.io...
> would the automatic PR test job deploy a timestamped snapshot BTW that has been superseded by JEP-305. [Docs](https://github.com/jenkinsci/incrementals-tools/blob/master/README.md#incrementals)
Jenkins [supports OIDC identities](https://plugins.jenkins.io/oidc-provider/) including customizable `aud`ience, but I am guessing this system only works from a SaaS for which you can register a specific permanent `iss`uer? The discussion of...
Right. To the extent I follow the discussion, this sounds related to https://github.com/sigstore/fulcio/issues/444. Sorry for any noise; I would suggest clarifying mentions of dual-mode systems like GitHub Actions or GitLab...
What is the use case that is not already covered by the `unstable` step?
> it would be sufficient if unstable step allowed to take a result other than UNSTABLE I think it would suffice to add an option to suppress https://github.com/jenkinsci/workflow-basic-steps-plugin/blob/9d389ecd7313b52b44395f954e43d4daf366112e/src/main/java/org/jenkinsci/plugins/workflow/steps/UnstableStep.java#L76 (Defaulting to...