-
Notifications
You must be signed in to change notification settings - Fork 29
Common Questions
This page is for commonly asked questions about the plugin. The questions presented here are geared towards troubleshooting help rather than questions about what what features can or can't be implemented. If you have a feature suggestion, please open an issue or ask in the Gitter chatroom.
Q: I have a job setup to trigger on PUSH and PRMERGED events. When a pull request is merged, two trigger happen! Why is this?
A: PUSH events trigger whenever a branch is updated. This could be from pushing new commits, creating a commit directly in Bitbucket, or when new commits are added to a branch from a pull request. Removing commits from a branch or rebasing the branch will also trigger the PUSH event.
Typically, you should only use one of PUSH or PRMERGED event triggers. If pull request information is required for your job (such as $PRID or $PRAUTHOR), use the PRMERGED event. Otherwise, use the PUSH event with a ref filter.
A: Let's say your folder is named "MyFolder" and your job is named "MyJob". When setting up the repository hook, use "MyFolder/job/MyJob" as the job name. If you have any nested folders, make sure to include "/job/" in between each folder and the final folder and job.
Q: My Jenkins server uses self-signed certificates for https. When setting up the Jenkins settings, http connections work but not https. Is there any way to get https working?
A: If you are using self-signed SSL certs, you will need to manually add the cert to Bitbucket's cacerts. The following steps provided in issue #125 should help you mange this:
- Go to your bitbucket jre installation folder and see which certs files you have (cd /opt/atlassian/bitbucket/4.14.4/jre/lib/security/) There should be file called cacerts and there may also be jssecacerts If you have jssecacerts use it bellow, otherwise use cacerts
- Copy your jenkinns cert to a path locally accessible to your Bitbucket Server (same box, shared mount, etc).
- Go to your bitbucket jre installation folder (cd /opt/atlassian/bitbucket/4.14.4/jre/)
- Run keytool utility (bin/keytool -import -file /path/to/jenkins.cer -alias -keystore /opt/atlassian/bitbucket/4.14.0/jre/lib/security/jssecacerts) It should ask you for the password which is often just "changeit". Accept certificate.
- Restart BitBucket server