Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
79148f04
Commit
79148f04
authored
Sep 15, 2020
by
Mike Jang
Committed by
Craig Norris
Sep 15, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Resolve "Move 1Password info from docs.gitlab.com to the Handbook"
parent
1a9c3e9c
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
13 additions
and
8 deletions
+13
-8
doc/development/documentation/site_architecture/index.md
doc/development/documentation/site_architecture/index.md
+5
-4
doc/development/pipelines.md
doc/development/pipelines.md
+3
-2
doc/development/testing_guide/review_apps.md
doc/development/testing_guide/review_apps.md
+5
-2
No files found.
doc/development/documentation/site_architecture/index.md
View file @
79148f04
...
...
@@ -227,11 +227,12 @@ for its search function. This is how it works:
there's a JavaScript snippet which initiates DocSearch by using an API key
and an index name (
`gitlab`
) that are needed for Algolia to show the results.
NOTE:
**For GitLab employees:**
The credentials to access the Algolia dashboard are stored in 1Password. If you
want to receive weekly reports of the search usage, search the Google doc with
NOTE:
**For GitLab Team Members:**
If you’re a GitLab Team Member, find credentials for the Algolia dashboard
in the shared
[
GitLab 1Password account
](
https://about.gitlab.com/handbook/security/#1password-for-teams
)
.
To receive weekly reports of the search usage, search the Google doc with
title
`Email, Slack, and GitLab Groups and Aliases`
, search for
`docsearch`
,
and add a comment with your email
to
be added to the alias that gets the weekly
and add a comment with your email
. You'll
be added to the alias that gets the weekly
reports.
## Monthly release process (versions)
...
...
doc/development/pipelines.md
View file @
79148f04
...
...
@@ -557,8 +557,9 @@ overwrites the Git configuration with the appropriate settings to fetch
from the GitLab repository.
`CI_REPO_CACHE_CREDENTIALS`
contains the Google Cloud service account
JSON for uploading to the
`gitlab-ci-git-repo-cache`
bucket. These
credentials are stored in the 1Password GitLab.com Production vault.
JSON for uploading to the
`gitlab-ci-git-repo-cache`
bucket. (If you’re a
GitLab Team Member, find credentials in the
[
GitLab shared 1Password account
](
https://about.gitlab.com/handbook/security/#1password-for-teams
)
.
Note that this bucket should be located in the same continent as the
runner, or
[
network egress charges will apply
](
https://cloud.google.com/storage/pricing
)
.
...
...
doc/development/testing_guide/review_apps.md
View file @
79148f04
...
...
@@ -165,8 +165,11 @@ This will grant you the following permissions for:
### Log into my Review App
The default username is
`root`
and its password can be found in the 1Password
secure note named
`gitlab-{ce,ee} Review App's root password`
.
For GitLab Team Members only. If you want to sign in to the review app, review
the GitLab handbook information for the
[
shared 1Password account
](
https://about.gitlab.com/handbook/security/#1password-for-teams
)
.
-
The default username is
`root`
.
-
The password can be found in the 1Password secure note named
`gitlab-{ce,ee} Review App's root password`
.
### Enable a feature flag for my Review App
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment