BitBucket

BitBucket connector

If configured, the plug-in exposes a hook for BitBucket events in a project in order to trigger pipeline events based on SCM events.

Seed configuration

The Seed used to generate a project must have its Type of trigger authorised parameter set to bitbucket.

BitBucket configuration

On your project BitBucket page, go to the Settings and to the Webhooks section.

In the Webhooks panel, click on the Add webhook button.

Enter any title, like Seed.

In the URL, enter http://<jenkins>:<port>/seed-bitbucket-api/ where jenkins is the host name of your Jenkins instance, and port its port it runs on. Note also the trailing slash.

You can also disable the SSL verification when needed (not recommended but can be needed while testing on a test Jenkins instance).

Leave Repository push as the default trigger.

When done, click on the Save button.

Now, whenever an event happens in your repository, the Seed hook will be called in your Jenkins instance.

Limitations

• the push events do not contain any information about the paths being updated. This does not allow the Seed plug-in to detect a seed event based on the paths of the files being impacted by a commit. Instead, the BitBucket connector will rely on a seed token (case insensitive) being present in the commit message(s).
• the BitBucket WebHook mechanism does not allow to specify any security token