Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gitlab-runner
gitlab-runner
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,057
    • Issues 2,057
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 215
    • Merge Requests 215
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitlab-runnergitlab-runner
  • Issues
  • #2716

Closed
Open
Created Aug 31, 2017 by Tom Elliff@tomelliffContributor

Allow configurable after_script timeouts

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

Assignee
Assign to
Awaiting further demand
Milestone
Awaiting further demand
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-runner#2716