Project settings for merge trains not visible

  • What are you seeing, and how does that differ from what you expect to see?

With a self managed EE Premium instance, I’m unable to see the checkboxes for pipelines for merged results or merge trains.

Our instance was previously running CE about a year ago, so I’m wondering if there was some issue transferring to EE that is preventing the options from showing.

  • Consider including screenshots, error messages, and/or other helpful visuals
    Project settings:
    I’m expecting a checkbox to “Enable merged results pipelines”, but there isn’t one.

  • What version are you on? Are you using self-managed or

    • GitLab (Hint: /help): 13.11.1-ee (self managed)
    • Runner (Hint: /admin/runners): 13.11.0
  • Add the CI configuration from .gitlab-ci.yml and other configuration if relevant (e.g. docker-compose.yml)

Not really relevant, but I do have the relevant workflow rules enabled:

  rules:                                         # Run on... (if not matched, don't run)
    - if: $CI_MERGE_REQUEST_IID                    # creation of / changes to merge requests
    - if: $CI_COMMIT_TAG                           # created git tags
    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH  # main branch
  • What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?

As linked above I’ve looked through the doc pages for pipelines for merged results and merge trains, and looked through the suggested troubleshooting there.

I’ve looked at the rails console to see if there was some issue with feature flags.

 Ruby:         ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-linux]
 GitLab:       13.11.1-ee (557bbaae5b1) EE
 GitLab Shell: 13.17.0
 PostgreSQL:   12.5
Loading production environment (Rails
irb(main):001:0> Feature.enabled?(:merge_ref_auto_sync)
=> true
irb(main):002:0> Feature.enabled?(:merge_pipelines)
=> true
irb(main):003:0> Feature.enabled?(:merge_trains)
=> true

Really not sure where to go from here.

Looking further into things, I believe this is because our instance is associated to a Starter license, not premium. The documentation has mostly removed any references to the tier, so I was confused and misunderstood the available features.