Skip to content

GitLab CI fails when triggered from GitHub #33

Description

@Mellich

Currently, it seems that the CI pipeline fails with an yaml invalid error if the pipeline is triggered automatically from GitHub.
Manually creating a new pipeline from the same commit in GitLab resolves this issue.

See screenshot of failing pipeline in GitLab CI:
Bildschirmfoto 2024-08-05 um 14 52 45

Since re-running fixes the invalid YAML error, this issue may be related to something else. A very similar open GitLab issue exists here: https://gitlab.com/gitlab-org/gitlab/-/issues/207320

Metadata

Metadata

Assignees

No one assigned

    Labels

    CIbugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions