Tim Jacomb

see also: https://github.com/jenkinsci/docker/issues/1228

Keep this in mind: https://github.com/jenkinsci/docker/issues/1228#issuecomment-961783533 you would need to get a SAN on the certificate on docker hub and then continue to provide that whenever the certificate is updated.

Ah ok, that's much easier than before.

You don't happen to have the merge strategy enabled? https://github.com/jenkinsci/configuration-as-code-plugin/blob/8b9efc1b9026942064d5248c92bf89cb00f83ea0/docs/features/mergeStrategy.md

We don't assign issues to users, just open a pull request instead and it will be reviewed

also see https://community.jenkins.io/t/using-gitpod-io-for-faster-docs-development-office-hours-jan-19-2022/1282/4 and https://community.jenkins.io/t/gitpodify-jenkins-projects/2362/7

> Given [JENKINS-75616](https://issues.jenkins.io/browse/JENKINS-75616) it might make sense to not implement that now but wait until we have a new tooltip implementation. @janfaracik @NotMyFault Agreed, @janfaracik and I have discussed this...

Make sure you test my line comment as I didn't test it

@jglick mind re-reviewing?

Oops got a bit keen there, I'll add the label and if anyone objects we'll revert. --- /label ready-for-merge ---- This PR is now ready for merge, after ~24 hours,...