Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • gitlab-runner gitlab-runner
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 3.5k
    • Issues 3.5k
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 94
    • Merge requests 94
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • gitlab-runnergitlab-runner
  • Issues
  • #2716
Closed
Open
Issue created Aug 31, 2017 by Tom Elliff@tomelliff

Allow configurable after_script timeouts

Status update (2023-03-13)

  • This feature is now a candidate for 16.2 at the earliest as we still need to refine the implementation proposal.
  • Ahead of that, we will work on adding an error message if the after_script timeout is exceeded.

Description

Allow configurable after_script timeouts so that post script cleanup can be done here even when it takes longer than 5 minutes.

This can be nice for semantically breaking up when things happen but also if you want something to always run even if the script failed but it takes more than 5 minutes.

I'm currently just moving it into a script action because I don't really need it to fire on failure (waiting for an ECS deployment to finish draining previous tasks).

Proposal

The after_script timeout is currently hardcoded to 5 minutes. It would be nice to make this optionally configurable just like the main script actions are.

In the original issue raised about adding after_script it was noted that this was planned to be some arbitrary timeout with a later configuration option

Links to related issues and merge requests / references

https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/102#note_11665572

Please paste a link of the related issues or/and merge requests

Edited Mar 13, 2023 by Darren Eastman: Offline for U.S Memorial Day weekend - back on 2023-05-30
Assignee
Assign to
Time tracking