Commit 192eaa41 authored by Evan Read's avatar Evan Read

Fix spelling and remove quoting for bridge jobs

parent 23e9b9b1
...@@ -68,7 +68,7 @@ staging: ...@@ -68,7 +68,7 @@ staging:
``` ```
In the example above, as soon as `rspec` job succeeds in the `test` stage, In the example above, as soon as `rspec` job succeeds in the `test` stage,
the `staging` "bridge" job is going to be started. The initial status of this the `staging` bridge job is going to be started. The initial status of this
job will be `pending`. GitLab will create a downstream pipeline in the job will be `pending`. GitLab will create a downstream pipeline in the
`my/deployment` project and, as soon as the pipeline gets created, the `my/deployment` project and, as soon as the pipeline gets created, the
`staging` job will succeed. `my/deployment` is a full path to that project. `staging` job will succeed. `my/deployment` is a full path to that project.
...@@ -85,8 +85,8 @@ GitLab does not support status attribution yet, however adding first-class ...@@ -85,8 +85,8 @@ GitLab does not support status attribution yet, however adding first-class
[status attribution](https://gitlab.com/gitlab-org/gitlab-ce/issues/39640). [status attribution](https://gitlab.com/gitlab-org/gitlab-ce/issues/39640).
NOTE: **Note:** NOTE: **Note:**
"Bridge" jobs do not support every configuration entry that a user can use Bridge jobs do not support every configuration entry that a user can use
in the case of regular jobs. "Bridge" jobs will not to be picked by a Runner, in the case of regular jobs. Bridge jobs will not to be picked by a Runner,
thus there is no point in adding support for `script`, for example. If a user thus there is no point in adding support for `script`, for example. If a user
tries to use unsupported configuration syntax, YAML validation will fail upon tries to use unsupported configuration syntax, YAML validation will fail upon
pipeline creation. pipeline creation.
...@@ -136,13 +136,13 @@ pipeline. It will be available as an environment variable when GitLab Runner pic ...@@ -136,13 +136,13 @@ pipeline. It will be available as an environment variable when GitLab Runner pic
### Limitations ### Limitations
Because "bridge" jobs are a little different to regular jobs, it is not Because bridge jobs are a little different to regular jobs, it is not
possible to use exactly the same configuration syntax here, as one would possible to use exactly the same configuration syntax here, as one would
normally do when defining a regular job that will be picked by a runner. normally do when defining a regular job that will be picked by a runner.
Some features are not implemented yet. For example, support for environments. Some features are not implemented yet. For example, support for environments.
[Configuration keywords](yaml/README.md) available for "bridge" jobs are: [Configuration keywords](yaml/README.md) available for bridge jobs are:
- `trigger` (to define a downstream pipeline trigger) - `trigger` (to define a downstream pipeline trigger)
- `stage` - `stage`
......
...@@ -1539,7 +1539,7 @@ test: ...@@ -1539,7 +1539,7 @@ test:
from `trigger` definition is started by GitLab, a downstream pipeline gets from `trigger` definition is started by GitLab, a downstream pipeline gets
created. created.
Learm more about [multi-project pipelines](../multi_project_pipelines.md#creating-cross-project-pipelines-from-gitlab-ci-yml). Learn more about [multi-project pipelines](../multi_project_pipelines.md#creating-cross-project-pipelines-from-gitlab-ci-yml).
### Simple `trigger` syntax ### Simple `trigger` syntax
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment