Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jenkins trigger not recognizing new certificate and CERTIFICATE option used with WAIT

Yolande Cates
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 12, 2025

We have been using the atlassian/jenkins-job-trigger:0.10.0 pipe to trigger jenkins jobs as shown in the image:

image.png

Our certificate expired and we now have a new one. It is no longer recognized by Bitbucket leaning our pipeline now gets a cert error (ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1007)) See below:

image.png

Is there some way I can upgrade the certifi package for the image? Should I be using a different image? (ie not gcc:15.1? I have tried pip install --upgrade certi but pip isn't installed which has led me down a path of attempting various installations without success.

 

The alternate path I have attempted is to use the CERTIFICATE option of the atlassian/jenkins-job-trigger:0.10.0 pipe which works for triggering the job but does not work for the subsequent connection from the WAIT option. If there is a way to use the CERTIFICATE option with the WAIT option, I am happy to go down that path.

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events