Add "merge-requests" special keyword for only except

Currently, it is possible to specify regrexp and special keywords to filter the build branches at .gitlab-ci.yml

job:
  # use regexp
  only:
    - /^issue-.*$/
  # use special keyword
  except:
    - branches

I can't figure out how to specify to build merge-request branches (refs/merge-requests/<number>/head) only.

It would be useful to relax day-to-day branches checks without compromising full automation checks for merge requests. I noticed that will full-checks enabled for every branch developers are discouraged to upload their half-baked branches on server due to the flood of failing ci messages.

Added ~19173 label

Added feature proposal label

@plastiv Do you think that using a build environment variable, like described in issue https://gitlab.com/gitlab-org/gitlab-ce/issues/15280, would solve this problem for you?

You mean to check variable from shell, right?

mr_check_only:
  script:
    - if [ -n "${CI_BUILD_MR}" ]; then do_mr_check; fi

That would do. Does it mean, that mr_check_only will be marked as successfull for non-MR builds?

@plastiv Yes. I think that we can close this in favor of https://gitlab.com/gitlab-org/gitlab-ce/issues/15280, unless we want to add a new keyword to except. Leaving this to @ayufan.

mentioned in issue #15598 (closed)

@ayufan @grzesiek How hard do you think this would be. I have a large customer requesting the ability to build on merge request creation instead of on a push. https://gitlab.zendesk.com/agent/tickets/23387

@dblessing Right now it's still hard, because we are not yet tracking builds for MR. It will require about 2-3 releases to make it possible.

mentioned in issue #17686 (closed)

Milestone changed to %Backlog

ZD: https://gitlab.zendesk.com/agent/tickets/23387

Added ~313020 label

I created an external service with a workaround. Application allows to have a separate workflows for merge requests, the pipeline for merge requests is created using build triggers: https://gitlab.com/ayufan/merge-requests-triggers.

is there any updates on it? How far are we from getting it on MR only?

@mente We are currently evaluating possible solutions. For now you can use my workaround app for emulate the Merge Request workflow.

@ayufan will it show associated builds in merge request UI?

@mente Yes

mentioned in issue #18920 (closed)

mentioned in issue #14654 (moved)

mentioned in issue #19982 (closed)

mentioned in issue #20576 (moved)

mentioned in merge request !5485 (merged)

Mentioned in issue gitlab-com/support#179 (closed)

Mentioned in issue #22689 (closed)

added pipeline label

mentioned in issue #25099 (closed)

@ayufan Hey doing some bug bashing, do you think this should be closed in favor of #23902 (moved) as it contains more information/actual feature proposal? Maybe just ensure that the customer+ label on here moves over.

Yes

mentioned in issue #15238 (moved)

Per comment above, closing in favor of https://gitlab.com/gitlab-org/gitlab-ce/issues/23902 - customer+ already on the other issue.

closed