I'm also confused about the 'build key', as mentioned in the Repository Link popup window (Settings -> Integrations -> Links, click the Jenkins button).
The documentation Brian that links to above refers to setting up a hook not a link, and it seems in the Links section there is a way to 'Map an unlimited number of JIRA, Bamboo, Jenkins and Crucible servers'. Is there any documentation on this? Google is drawing a blank....
Sorry for the lack of reply. It sounds like "Build key" is actually what is referred to in Jenkins as the "Job name". I'm not personally familiar with Jenkins, but if someone can confirm this we can get the Links UI updated in Bitbucket to use more accurate terminology.
In Jenkins job configuration, under build triggers, trigger builds remotely, Authentication Token.
"Use the following URL to trigger build remotely: JENKINS_URL/view/All/job/myjob/build?token=TOKEN_NAME or /buildWithParameters?token=TOKEN_NAME
Optionally append &cause=Cause+Text to provide text that will be included in the recorded build cause. "
Seriously, how is there no documentation on this? I've spent half a day just trying to setup my Jenkins server to work with my BitBucket repo and no where on the Internet is there any reference to "build key", not in Jenkins' documentation and not in JIRA or BitBucket's documentation. What is the build key? What is the Jenkins URL supposed to be formatted as?
Can someone help me? This is a broken feature and I'm heavily considering just going back to GitHub and using some other tool for PM like BaseCamp or Teamwork.