Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • Morello CI Pipelines Morello CI Pipelines
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Morello
  • Morello CI PipelinesMorello CI Pipelines
  • Issues
  • #28
Closed
Open
Created Apr 14, 2022 by Jagadeesh Ujja@jagadeeshujjaDeveloper

MR patch CI job is not running on targeted branch (example forked out branch like morello/release-1.4 )

There are a MR patche targeted for only forked out branch like morello/release-1.4, it is expected to run the MR patch CI on forked out branch only not on mainline branch. Currently there is no way to specify which MANIFEST_BRANCH should be used in the MR for testing and it defaults to morello/mainline.

Similar issue is observed in MR build-scripts!63 (merged)
This needs to fixed and MR CI should be run against targeted branch only not on the mainline.

Assignee
Assign to
Time tracking