Unable to manually trigger master-build when "except" is used.

Summary

Having following rudimentary ".gitlab-ci.yml":

stages:
    - setup
    - build
    - package
    - deploy

setup-frontend:
    stage: setup
    except:
      changes:
        - ".gitlab-ci.yml"
    script:
        - echo foo

i try to manually trigger a "master"-branch build using "Pipepines"-"Run pipeline"-Button in the WebUI.

The pipeline start fails with following error:

If i do comment out the "except:" section (lines 10-12 in https://gitlab.com/v2b1n/test/blob/master/.gitlab-ci.yml) then i can start the pipeline normally.

Steps to reproduce

Use the mentioned .gitlab-ci.yml and try to start a Pipeline on a "master"-branch using "Pipepines"-"Run pipeline"-Button.

If i do comment out the "except:" section (lines 10-12 in https://gitlab.com/v2b1n/test/blob/master/.gitlab-ci.yml) then i can start the pipeline normally.

Example Project

https://gitlab.com/v2b1n/test/pipelines

What is the current bug behavior?

The pipeline does not start.

What is the expected correct behavior?

The pipeline should start.

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com.

I also was able to reproduce this behaviour in v11.11.8 of self-managed gitlab foss instance.

changed the description

Thanks for submitting this issue. Since GitLab's development now happens in a single codebase, the canonical GitLab issue tracker is now at https://gitlab.com/gitlab-org/gitlab/issues.

This issue will automatically be moved there.

added automation:to-be-locked in GitLab FOSS label

moved from gitlab-foss#67540 (moved)

mentioned in issue #37401 (closed)

@v2b1n This works as expected because the pipeline would pick up the last commit and detect the changes in it.

In this example https://gitlab.com/v2b1n/test/pipelines, there is only one job that runs for any change except on gitlab-ci.yml. We can see that the pipeline was able to run when README.md is added.

I'll close this issue for now as the behaviour matches the example project given.

If you also encounter this issue in your own project with more jobs involved, feel free to create a new issue with an example of gitlab-ci.yml that more closely mirrors the actual gitlab-ci.yml?

closed

@caalberts, the problem wasn't that the pipeline run's at all.

The problem was and is that if the mentioned "except" directive is present in the ".gitlab-ci.yml" the pipeline cannot be triggered through the web-ui using the "pipelines"-"run pipeline" button.

Again,

i try to manually trigger a "master"-branch build using "Pipepines"-"Run pipeline"-Button in the WebUI.

And yes, the pipeline works on pushes/merges. But that's not the point.

The problem was and is that if the mentioned "except" directive is present in the ".gitlab-ci.yml" the pipeline cannot be triggered through the web-ui using the "pipelines"-"run pipeline" button.

When you attempt to trigger the pipeline on master branch, what files are changed in the latest commit on master branch?

reopened

In the very last commit in my repo i've changed the README.md.

mentioned in issue #37487 (closed)

added devopsverify grouppipeline execution labels

@caalberts, should we label it as a ~bug then?

Setting Category:Continuous Integration based on ~"group::continuous integration".

added Category:Continuous Integration label

Facing the same issue. Following.

changed the description

changed milestone to %Backlog

added [deprecated] Accepting merge requests label

added CI rules label

added sectionops label

added grouppipeline authoring + 1 deleted label and removed grouppipeline execution label

same issue. Following.

got same issue

@caalberts Any updates on this one?

added typebug label

added severity3 label

added priority2 label

added vintage label

Hi @v2b1n ,

Thanks for raising this bug.

Contributions like this are vital to help make GitLab a better product.

We would be grateful for your help in verifying whether your bug report requires further attention from the team. If you think this bug still exists, and is reproducible with the latest stable version of GitLab, please comment on this issue.

This issue has been inactive for more than 12 months now and based on the policy for inactive bugs, will be closed in 7 days.

Thanks for your contributions to make GitLab better!

added stale label

Hi @v2b1n ,

Based on the policy for inactive bugs, this issue is now being closed.

If you think this bug still exists, and is reproducible with the latest stable version of GitLab, please reopen this issue.

Thanks for your contributions to make GitLab better!

closed

added auto closed label

added Category:Pipeline Composition label

still an issue

reopened

removed stale label

added UX + 1 deleted label

added usability label

added SLOMissed label

Hi @v2b1n ,

Thanks for raising this bug.

Contributions like this are vital to help make GitLab a better product.

We would be grateful for your help in verifying whether your bug report requires further attention from the team. If you think this bug still exists, and is reproducible with the latest stable version of GitLab, please comment on this issue.

This issue has been inactive for more than 12 months now and based on the policy for inactive bugs, will be closed in 7 days.

Thanks for your contributions to make GitLab better!

added stale label

added sectionci label and removed sectionops label

Hi @v2b1n ,

Based on the policy for inactive bugs, this issue is now being closed.

If you think this bug still exists, and is reproducible with the latest stable version of GitLab, please reopen this issue.

Thanks for your contributions to make GitLab better!

closed