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
4d95acc6
Commit
4d95acc6
authored
Oct 12, 2021
by
Rémy Coutable
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document the 'as-if-jh' jobs
Signed-off-by:
Rémy Coutable
<
remy@rymai.me
>
parent
22b4b31d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
2 deletions
+17
-2
doc/development/pipelines.md
doc/development/pipelines.md
+17
-2
No files found.
doc/development/pipelines.md
View file @
4d95acc6
...
...
@@ -127,7 +127,7 @@ Consult the [Review Apps](testing_guide/review_apps.md) dedicated page for more
## As-if-FOSS jobs
The
`* as-if-foss`
jobs run the GitLab test suite "as
-if-
FOSS", meaning as if the jobs would run in the context
The
`* as-if-foss`
jobs run the GitLab test suite "as
if
FOSS", meaning as if the jobs would run in the context
of the
`gitlab-org/gitlab-foss`
project. These jobs are only created in the following cases:
-
when the
`pipeline:run-as-if-foss`
label is set on the merge request
...
...
@@ -135,11 +135,26 @@ of the `gitlab-org/gitlab-foss` project. These jobs are only created in the foll
-
when any CI config file is changed (i.e.
`.gitlab-ci.yml`
or
`.gitlab/ci/**/*`
)
The
`* as-if-foss`
jobs are run in addition to the regular EE-context jobs. They have the
`FOSS_ONLY='1'`
variable
set and get the
ir EE-specific folders
removed before the tests start running.
set and get the
`ee/`
folder
removed before the tests start running.
The intent is to ensure that a change doesn't introduce a failure after the
`gitlab-org/gitlab`
project is synced to
the
`gitlab-org/gitlab-foss`
project.
## As-if-JH jobs
The
`* as-if-jh`
jobs run the GitLab test suite "as if JiHu", meaning as if the jobs would run in the context
of
[
the `gitlab-jh/gitlab` project
](
jh_features_review.md
)
. These jobs are only created in the following cases:
-
when the
`pipeline:run-as-if-jh`
label is set on the merge request
-
when the
`pipeline:run-all-rspec`
label is set on the merge request
-
when any code or backstage file is changed
-
when any startup CSS file is changed
The
`* as-if-jh`
jobs are run in addition to the regular EE-context jobs. The
`jh/`
folder is added before the tests start running.
The intent is to ensure that a change doesn't introduce a failure after the
`gitlab-org/gitlab`
project is synced to
the
`gitlab-jh/gitlab`
project.
## PostgreSQL versions testing
Our test suite runs against PG12 as GitLab.com runs on PG12 and
...
...
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