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
fefe975e
Commit
fefe975e
authored
Sep 29, 2019
by
Marcel Amirault
Committed by
Evan Read
Sep 29, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Give issue links more descriptive text
parent
dd63fda6
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
7 additions
and
7 deletions
+7
-7
doc/ci/directed_acyclic_graph/index.md
doc/ci/directed_acyclic_graph/index.md
+1
-1
doc/ci/yaml/README.md
doc/ci/yaml/README.md
+6
-6
No files found.
doc/ci/directed_acyclic_graph/index.md
View file @
fefe975e
...
...
@@ -73,4 +73,4 @@ A directed acyclic graph is a complicated feature, and as of the initial MVC the
are certain use cases that you may need to work around. For more information:
-
[
`needs` requirements and limitations
](
../yaml/README.md#requirements-and-limitations
)
.
-
Related epic
[
#1716
](
https://gitlab.com/groups/gitlab-org/-/epics/1716
)
.
-
Related epic
[
tracking planned improvements
](
https://gitlab.com/groups/gitlab-org/-/epics/1716
)
.
doc/ci/yaml/README.md
View file @
fefe975e
...
...
@@ -1897,14 +1897,14 @@ This example creates three paths of execution:
-
For self-managed instances, the limit is:
-
Five by default (
`ci_dag_limit_needs`
feature flag is enabled).
-
50 if the
`ci_dag_limit_needs`
feature flag is disabled.
-
It is impossible for now to have
`needs: []`
(empty needs),
the job always needs to depend on something, unless this is the job
in the first stage (see
[
issue #65504
](
https://gitlab.com/gitlab-org/gitlab-foss/issues/65504
)
).
-
It is impossible for now to have
`needs: []`
(empty needs),
the job always needs to
depend on something, unless this is the job in the first stage. However, support for
an empty needs array
[
is planned
](
https://gitlab.com/gitlab-org/gitlab/issues/30631
)
.
-
If
`needs:`
refers to a job that is marked as
`parallel:`
.
the current job will depend on all parallel jobs created.
-
`needs:`
is similar to
`dependencies:`
in that it needs to use jobs from
prior stages, meaning it is impossible to create circular
dependencies or depend on jobs in the current stage (see
[
issue #65505
](
https://gitlab.com/gitlab-org/gitlab-foss/issues/65505
)
).
-
`needs:`
is similar to
`dependencies:`
in that it needs to use jobs from
prior stages,
meaning it is impossible to create circular dependencies. Depending on jobs in the
current stage is not possible either, but support
[
is planned
](
https://gitlab.com/gitlab-org/gitlab/issues/30632
)
.
-
Related to the above, stages must be explicitly defined for all jobs
that have the keyword
`needs:`
or are referred to by one.
...
...
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