Arnaud Jeansen

To explain further, the zbctl workaround that is mentioned above consists in doing the following: ``` # port forward to localhost 26500 kubectl port-forward -n zeebe-caseflow service/zeebe-gateway 26500 # retrieve...

@barmac I can't get this to work unfortunately. ## Prerequisites First, I expose my zeebe gateway with a port-forward. `kubectl port-forward -n zeebe-caseflow service/zeebe-gateway 26500` Then I retrieve the certificate...

Thanks @christian-konrad , yes I assumed @barmac was on vacation (I was back this week myself, hence the delay in testing the build). Looking at the comment, this talks a...

Hello @barmac I'm back from vacation too :) > Based on my experience, connecting to an IP with a custom SSL cert never works with zeebe-node which we use. This...

At least I now understand why the hostname I use is different from the CN in the certificate :+1: ``` $ openssl x509 -in bin/dev.crt -text -noout | grep zeebe-gateway...

Specifically, I was thinking of adding a configuration knob such as "forcePreTagCommit" that would default to false. I could then add this knob to the "if" condition in preTagCommit. ```...

Hello, Yes you understood correctly. The Jenkins Release Plugin lets Jenkins users define only one Jenkins job with all the build definitions, and some extra configuration / triggers before and...

Not sure I follow, what did you do in the preBuildStep?

Thanks for the example. So this job did the actual release into the preBuild step with the standard "gradle release ...", and then built the next snapshot version. I am...

No the gradle release plugin does the release during the postStep (once the build with the release version has concluded) with the "preTagCommit createReleaseTag updateVersion commitNewVersion" tasks. Or did I...