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 35,751
    • Issues 35,751
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,292
    • Merge Requests 1,292
  • 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
  • #205494

Closed
Open
Opened Feb 13, 2020 by Mark Pundsack@markpundsackContributor

Simultaneous GitLab CI/CD pipeline and external pipeline

Problem to solve

If a user has an external pipeline, say a Jenkins pipeline, and a GitLab CI/CD pipeline, say running Security testing, whichever pipeline finishes last sets the commit status. We should support having two (or more) simultaneous pipelines, with the commit status being the logical AND of the various pipelines.

Intended users

  • Rachel (Release Manager)
  • Delaney (Development Team Lead)
  • Sasha (Software Developer)
  • Devon (DevOps Engineer)

Further details

This could be solved via #22187, but could be solved in other ways as well. I swear there was an issue for this yeas ago, about treating pipelines with different inputs or different structure and context as distinct and logically ANDing the results, but I can't find it.

Proposal

Set commit status to the logical AND of all pipelines.

Care will have to be taken to do this right. If a pipeline fails and then is re-run, only the latest one should count. Not sure what we should do if there are scheduled pipelines or manual pipeline runs with different status results.

Permissions and Security

Documentation

Availability & Testing

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

What is the type of buyer?

Links / references

Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#205494