-
Notifications
You must be signed in to change notification settings - Fork 1
/
bitbucket.txt
46 lines (24 loc) · 1.27 KB
/
bitbucket.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Bitbucket integration
=====================
It's possible to connect bitbucket to deploy-commander and automate some deployment tasks.
We use the git flow by default for automated builds.
See `a successful git branching model <http://nvie.com/posts/a-successful-git-branching-model>`_
How it works
------------
Bitbucket has a post pull request hook that will post information when pull and merge requests are executed. We have exposed a rest endpoint that can catch this post request.
Setup and start the webserver (:doc:`See the usage <usage>`, and :doc:`config <config>`)
::
$ deploy-commander runserver
By default it will listen to the merge action from bitbucket. So when somebody merges code in the develop branch it will execute :
::
$ deploy-commander go:<project>,testing run:deploy-app
When somebody merges code into the release branch it will execute:
::
$ deploy-commander go:<project>,staging run:deploy-app
.. note:: Still in beta now.. we'll update as much as possible.
Setup Bitbucket hook
--------------------
Go to your webadmin https://bitbucket.org repo. Under settings -> webhooks you'll find
add webhook.
Select a trigger (pull request->merged) and enter your deploy-commander rest endpoint:
- http://<yourip/domain>:8086/api/v1/bitbucket/webhook