diff options
Diffstat (limited to 'doc/ci')
| -rw-r--r-- | doc/ci/examples/deployment/composer-npm-deploy.md | 2 | ||||
| -rw-r--r-- | doc/ci/jenkins/index.md | 6 | ||||
| -rw-r--r-- | doc/ci/pipelines/schedules.md | 2 | ||||
| -rw-r--r-- | doc/ci/review_apps/index.md | 3 | ||||
| -rw-r--r-- | doc/ci/services/postgres.md | 2 | ||||
| -rw-r--r-- | doc/ci/services/redis.md | 2 | ||||
| -rw-r--r-- | doc/ci/triggers/README.md | 2 | ||||
| -rw-r--r-- | doc/ci/yaml/README.md | 12 |
8 files changed, 22 insertions, 9 deletions
diff --git a/doc/ci/examples/deployment/composer-npm-deploy.md b/doc/ci/examples/deployment/composer-npm-deploy.md index 4ca817908ed..ae0880adef2 100644 --- a/doc/ci/examples/deployment/composer-npm-deploy.md +++ b/doc/ci/examples/deployment/composer-npm-deploy.md @@ -23,7 +23,7 @@ before_script: - php -r "unlink('composer-setup.php');" ``` -This will make sure we have all requirements ready. Next, we want to run `composer install` to fetch all PHP dependencies and `npm install` to load Node.js packages, then run the `npm` script. We need to append them into `before_script` section: +This will make sure we have all requirements ready. Next, we want to run `composer install` to fetch all PHP dependencies and `npm install` to load Node.js packages, then run the `npm` script. We need to append them into `before_script` section: ```yaml before_script: diff --git a/doc/ci/jenkins/index.md b/doc/ci/jenkins/index.md index fe937bb1f3a..2678936ae70 100644 --- a/doc/ci/jenkins/index.md +++ b/doc/ci/jenkins/index.md @@ -53,7 +53,7 @@ There are some high level differences between the products worth mentioning: - by [webhook](../triggers/README.md#triggering-a-pipeline-from-a-webhook) - by [ChatOps](../chatops/README.md) - You can control which jobs run in which cases, depending on how they are triggered, +- You can control which jobs run in which cases, depending on how they are triggered, with the [`rules` syntax](../yaml/README.md#rules). - GitLab [pipeline scheduling concepts](../pipelines/schedules.md) are also different than with Jenkins. - All jobs within a single stage always run in parallel, and all stages run in sequence. We are planning @@ -78,7 +78,9 @@ There are some high level differences between the products worth mentioning: also leverage [`protected environments`](../yaml/README.md#protecting-manual-jobs-premium) to control who is able to approve them. - GitLab comes with a [container registry](../../user/packages/container_registry/index.md), and we recommend using - container images to set up your build environment. + container images to set up your build environment. For example, set up one pipeline that builds your build environment + itself and publish that to the container registry. Then, have your pipelines use this instead of each building their + own environment, which will be slower and may be less consistent. We have extensive docs on [how to use the Container Registry](../../user/packages/container_registry/index.md). - Totally stuck and not sure where to turn for advice? The [GitLab community forum](https://forum.gitlab.com/) can be a great resource. ## Groovy vs. YAML diff --git a/doc/ci/pipelines/schedules.md b/doc/ci/pipelines/schedules.md index 3bd42899542..ea98638ae53 100644 --- a/doc/ci/pipelines/schedules.md +++ b/doc/ci/pipelines/schedules.md @@ -86,7 +86,7 @@ To change the Sidekiq worker's frequency: 1. Edit the `gitlab_rails['pipeline_schedule_worker_cron']` value in your instance's `gitlab.rb` file. 1. [Reconfigure GitLab](../../administration/restart_gitlab.md#omnibus-gitlab-reconfigure) for the changes to take effect. -For GitLab.com, refer to the [dedicated settings page](../../user/gitlab_com/index.md#cron-jobs). +For GitLab.com, refer to the [dedicated settings page](../../user/gitlab_com/index.md#gitlab-cicd). ## Working with scheduled pipelines diff --git a/doc/ci/review_apps/index.md b/doc/ci/review_apps/index.md index bdef2eca1f2..e19167f6d9a 100644 --- a/doc/ci/review_apps/index.md +++ b/doc/ci/review_apps/index.md @@ -200,7 +200,8 @@ Feature.enable(:anonymous_visual_review_feedback) The feedback form is served through a script you add to pages in your Review App. If you have [Developer permissions](../../user/permissions.md) to the project, you can access it by clicking the **Review** button in the **Pipeline** section -of the merge request. +of the merge request. The form modal will also show a dropdown for changed pages +if [route maps](#route-maps) are configured in the project.  diff --git a/doc/ci/services/postgres.md b/doc/ci/services/postgres.md index bd389783a1d..4cf3e429c63 100644 --- a/doc/ci/services/postgres.md +++ b/doc/ci/services/postgres.md @@ -119,7 +119,7 @@ We have set up an [Example PostgreSQL Project][postgres-example-repo] for your convenience that runs on [GitLab.com](https://gitlab.com) using our publicly available [shared runners](../runners/README.md). -Want to hack on it? Simply fork it, commit and push your changes. Within a few +Want to hack on it? Simply fork it, commit and push your changes. Within a few moments the changes will be picked by a public runner and the job will begin. [hub-pg]: https://hub.docker.com/_/postgres diff --git a/doc/ci/services/redis.md b/doc/ci/services/redis.md index b04b36f7a04..f22ee87a9d3 100644 --- a/doc/ci/services/redis.md +++ b/doc/ci/services/redis.md @@ -66,5 +66,5 @@ We have set up an [Example Redis Project](https://gitlab.com/gitlab-examples/red that runs on [GitLab.com](https://gitlab.com) using our publicly available [shared runners](../runners/README.md). -Want to hack on it? Simply fork it, commit and push your changes. Within a few +Want to hack on it? Simply fork it, commit and push your changes. Within a few moments the changes will be picked by a public runner and the job will begin. diff --git a/doc/ci/triggers/README.md b/doc/ci/triggers/README.md index 4e597b883d0..00070594ded 100644 --- a/doc/ci/triggers/README.md +++ b/doc/ci/triggers/README.md @@ -123,7 +123,7 @@ settings page which provides self-explanatory examples. When a rerun of a pipeline is triggered, the information is exposed in GitLab's UI under the **Jobs** page and the jobs are marked as triggered 'by API'. - + --- diff --git a/doc/ci/yaml/README.md b/doc/ci/yaml/README.md index 84bd67b42c3..e0c41d821a6 100644 --- a/doc/ci/yaml/README.md +++ b/doc/ci/yaml/README.md @@ -867,6 +867,10 @@ CAUTION: **Warning:** There are some points to be aware of when [using this feature with new branches or tags *without* pipelines for merge requests](#using-onlychanges-without-pipelines-for-merge-requests). +CAUTION: **Warning:** +There are some points to be aware of when +[using this feature with scheduled pipelines](#using-onlychanges-with-scheduled-pipelines). + ##### Using `only:changes` with pipelines for merge requests With [pipelines for merge requests](../merge_request_pipelines/index.md), @@ -931,6 +935,12 @@ This could result in some unexpected behavior, including: - When pushing a new commit, the changed files are calculated using the previous commit as the base SHA. +##### Using `only:changes` with scheduled pipelines + +`only:changes` always evaluates as "true" in [Scheduled pipelines](../pipelines/schedules.md). +All files are considered to have "changed" when a scheduled pipeline +runs. + ### `rules` > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/29011) in GitLab 12.3. @@ -3042,7 +3052,7 @@ include: > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/53903) in GitLab 11.7. To include files from another private project under the same GitLab instance, -use `include:file`. This file is referenced using full paths relative to the +use `include:file`. This file is referenced using full paths relative to the root directory (`/`). For example: ```yaml |