Skip to content

Commit

Permalink
Convert repo_token to uppercase
Browse files Browse the repository at this point in the history
  • Loading branch information
0x2b3bfa0 authored and casperdcl committed Oct 26, 2021
1 parent 5c5f2aa commit b3726d2
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 7 deletions.
10 changes: 5 additions & 5 deletions content/docs/self-hosted-runners.md
Original file line number Diff line number Diff line change
Expand Up @@ -238,12 +238,12 @@ Use either:
For instance, to use a personal access token:

1. Navigate to **User Settings** → **Access Tokens**
- in the "Name" field, type `repo_token`
- in the "Name" field, type `REPO_TOKEN`
- select `api`, `read_repository` and `write_repository`
- click "Create personal access token" and copy it
2. In your GitLab project, navigate to **Settings** → **CI/CD**
→ **Variables** → **Add Variable**
- in the "Key" field, type `repo_token`
- in the "Key" field, type `REPO_TOKEN`
- in the "Value" field, paste your Personal Access Token
- select "Mask variable"
- deselect "Protect variable"
Expand All @@ -255,7 +255,7 @@ credentials.
</tab>
<tab title="Bitbucket">

Bitbucket Cloud does not use access tokens. Instead, create a `repo_token`
Bitbucket Cloud does not use access tokens. Instead, create a `REPO_TOKEN`
variable with a Base64 encoded username and password.

Use either:
Expand All @@ -268,15 +268,15 @@ Use either:
intended use case: you limit the account to only access the repositories where
you plan to deploy runners to.

In either case, the steps to create a `repo_token` are:
In either case, the steps to create a `REPO_TOKEN` are:

1. Use a Base64 encoder of your choice to encode a Bitbucket username and
password:
- `echo $USERNAME:$PASSWORD | base64`
- copy the resulting Base64 token
2. In your repository, go to **Repository Settings** &rightarrow; **Repository
Variables**
- in the "Name" field, type `repo_token`
- in the "Name" field, type `REPO_TOKEN`
- in the "Value" field, paste the Base64 token
- select `Secured` to hide credentials in all Bitbucket logs

Expand Down
4 changes: 2 additions & 2 deletions content/docs/usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ create-CML-report:

⚠️ You _must_ provide a
[personal or project access token (PAT)](/doc/self-hosted-runners#personal-access-token)
via a `repo_token` variable.
via a `REPO_TOKEN` variable.

The example above generates visual reports in merge requests:
[![](/img/GitLab_CML_report.png '=400')](https://gitlab.com/iterative.ai/cml-base-case/-/merge_requests/3)
Expand Down Expand Up @@ -131,7 +131,7 @@ pipelines:

⚠️ You _must_ provide
[access credentials](/doc/self-hosted-runners#personal-access-token) via a
`repo_token` variable.
`REPO_TOKEN` variable.

The example above generates visual reports in pull requests:
[![](/img/bitbucket_cloud_pr.png '=600')](https://bitbucket.org/iterative-ai/cml-base-case/pull-requests/2)
Expand Down

0 comments on commit b3726d2

Please sign in to comment.