-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ISS-335 Start of bitbucket docs (#23)
ISS-335 added readme and image files
- Loading branch information
Showing
7 changed files
with
35 additions
and
0 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# Install the Bitbucket Pipeline | ||
|
||
## Create a “Repository Access Token” for Pixee | ||
|
||
1. Open your repo in Bitbucket and click on “Repository Settings” from the left navigation. | ||
|
||
<img src="../assets/bitbucket/settings.png" width=300/> | ||
|
||
2. Under “Security” click on “Access Tokens” | ||
|
||
<img src="../assets/bitbucket/access_tokens.png" width=300/> | ||
|
||
3. Click on the “Create Repository Access Token” | ||
4. Give the token a name (Pixee for example) and check the box for under “Pull request” for “write” access. This will add all the other necessary scopes automatically. | ||
|
||
<img src="../assets/bitbucket/scopes.png" width=400/> | ||
|
||
5. This will give you a key that you can copy for the next step. | ||
|
||
<img src="../assets/bitbucket/access_token_view.png" width=400/> | ||
|
||
## Add the “Repository variables” | ||
|
||
1. Click on “Repository variables” | ||
|
||
<img src="../assets/bitbucket/variables.png" width="200" /> | ||
|
||
2. Add a new one with the name “BITBUCKET_ACCESS_TOKEN_PIXEE” and the value from the step above. | ||
|
||
<img src="../assets/bitbucket/access_token_var.png" width="500" /> | ||
|
||
## Add the pipeline: | ||
|
||
1. Under “Pipelines” Click settings and make sure pipelines are enabled for the branch. | ||
2. Add the following bitbucket-pipelines.yml file to your project. |