Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
E
elsa
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34
    • Issues 34
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 10
    • Merge Requests 10
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • IP
  • elsa
  • Issues
  • #58

Closed
Open
Opened Mar 27, 2020 by David Frank@david.frankMaintainer

Pipeline for merge request

It would be nice to run the master pipeline on branches before merging.

Gitllab CI supports this in a couple of different stages.

  1. Merge request pipelines, these run jobs specifically if a merge request is created or updated. The pipeline fetches the latest code from the source branch and run the specified jobs against it. We could define the jobs, we usually run nightly (such as sanitizer and code coverage), to run against merge requests as well.

  2. Pipelines for merge requests, this feature can be activated for the project. Quote from the documentation: "With pipelines for merged results, the pipeline runs as if the changes from the source branch have already been merged into the target branch.". And if the pipelines fails, the merge will be rejected.

I think, these two features will improve our merge process. I hope they remove the need to trigger the nightly pipeline manually and rather do that, before we actually merge things into master.

Any thoughts?

Assignee
Assign to
v0.6 release
Milestone
v0.6 release (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: IP/elsa#58