Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update web-ui.md #3398

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions user/web-ui.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,8 @@ Simple 'trigger build' control. Allow or prevent users with appropriate access t

In the case of a fork-to-base pull request:

* If this setting is ON, the encrypted environment variables will be available to the forked repository, which means that builds in the forked repository will have access to the encrypted environment variables from the base repository. This may be a less secure approach yet allows for a collaboration using forks and Pull Requests (PRs).
* If this setting is OFF and the build relies on any encrypted environment variable, the PR from fork to base repository will fail. This secures your base repository encrypted environmental variables by putting a constraint on accessing them from forks.
* If this setting is ON, the encrypted environment variables will be available to the forked repository, which means that builds in the forked repository will have access to the encrypted environment variables from the base repository. This may be a less secure approach, yet it allows for collaboration using forks and Pull Requests (PRs).
* If this setting is OFF and the build relies on any encrypted environment variable, the PR from the fork to the base repository will fail. This secures your base repository encrypted environmental variables by putting a constraint on accessing them from forks.

Read more: [Pull Requests and security restrictions](/user/pull-requests/#pull-requests-and-security-restrictions)

Expand All @@ -39,10 +39,19 @@ Read more: [Pull Requests and security restrictions](/user/pull-requests/#pull-r
In the case of a fork-to-base pull request:

* If this setting is ON, the custom SSH keys from the base repository will be available to the forked repository, which means that the build in the forked repository will be able to use the custom SSH keys from the base repository. Consider setting to ON if your collaboration model requires working with Pull Requests (PRs) from forked repositories or there are dependencies defined, which rely on SSH key from base repository.
* If this setting is OFF and the build is relying on custom SSH keys i.e. for fetching some additional dependencies, it will fail with a no access error.
* If this setting is OFF and the build is relying on custom SSH keys i.e., for fetching some additional dependencies, it will fail with a no access error.

Read more: [Pull Requests and security restrictions](/user/pull-requests/#pull-requests-and-security-restrictions)

## API Authentication

- **Token**: The field displays the encoded token.
- **Copy Token**: Click this button to copy the generated token.
- **View Token**: Click this button to reveal the encoded token.
- **Regenerate**: Click this button to regenerate the token.

For more information on using our API, head to the [Travis developer](developer.travis-ci.com) site.

## Enabling access to old build jobs

{{ site.data.snippets.enabling_access_jobs_logs }}
Expand Down