Skip to content

GitLab Next

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

Closed
Open
Created Jul 19, 2019 by Jason Yavorska@jyavorska💬Contributor

`allow_failure` action for pipeline rules

Problem to solve

Building on flexible rules for CI pipelines, some teams will need a way to allow certain rules to fail without causing a pipeline failure. As of the MVC, allow_failure: is only settable at the job level, not per-rule.

Proposal

We will introduce a new rule action called allow_failure. This action defines the behavior of job after the rule is matched, allowing us to conditionally set allowed to fail in given conditions. This replaces job-level allow_failure:. The default value is false.

Example:

rules:
  - changes: *.doc
    allow_failure: true

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

Links / references

Assignee
Assign to
12.8
Milestone
12.8 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#30235