Resolve "Ensure after_script is called for timed out pipelines"
What does this MR do?
This MR improves the documentation regarding RUNNER_SCRIPT_TIMEOUT
and RUNNER_AFTER_SCRIPT_TIMEOUT
by adding an example of how to configure correctly jobs so that after_script
runs through.
Related issues
Related to #15603
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding a new page, add the product availability details under the H1 topic title. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. -
Technical writer review items: -
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. -
If relevant to this MR, ensure content topic type principles are in use, including: -
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. -
If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Merge request reports
Activity
changed milestone to %Backlog
added Category:Continuous Integration GitLab Free Support Interest auto updated customer devopsverify direction grouppipeline execution missed-deliverable missed:12.3 missed:12.4 missed:13.0 missed:13.5 pipeline processing popular proposal potential proposal sectionci typefeature workflowblocked labels
assigned to @daniel-prause
added 264 commits
-
153e41c8...75ad21cd - 263 commits from branch
master
- b8137499 - Clarify documentation for script and after script timeouts
-
153e41c8...75ad21cd - 263 commits from branch
added docs-only label
added documentation label
1 Message This merge request adds or changes documentation files and requires Technical Writing review. The review should happen before merge, but can be post-merge if the merge request is time sensitive. Documentation review
The following files require a review from a technical writer:
-
doc/ci/runners/configure_runners.md
(Link to current live version) -
doc/ci/yaml/_index.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
DangerEdited by ****-
added maintenancerefactor label
added typemaintenance label and removed typefeature label
added 1 commit
- bb2bb343 - Clarify documentation for script and after script timeouts
mentioned in issue #15603
- Resolved by Axel von Bertoldi
added Technical Writing label
requested review from @marcel.amirault
removed Technical Writing label
removed workflowblocked label
- Resolved by Daniel P.
- Resolved by Lysanne Pinto
@lyspin Could you take a look?
requested review from @lyspin
removed review request for @marcel.amirault
- Resolved by Daniel P.
- Resolved by Lysanne Pinto
@daniel-prause Thanks for this MR! I added a couple suggestions
changed milestone to %17.10
- Resolved by Lysanne Pinto
Hi
@lyspin
,GitLab Bot has added the Technical Writing label because a Technical Writer has approved or merged this MR.
This message was generated automatically. Improve it or delete it.
added Technical Writing label
@daniel-prause I pushed a small change, approved, and set this to merge
started a merge train
mentioned in commit 4adb4560
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-production label and removed workflowproduction label