GitLab CI/CD is being triggered without a .gitlab-ci.yml file

Describe the bug

GitLab CI/CD is being triggered without a .gitlab-ci.yml file or any specific setup in GitLab

To Reproduce

Create a site with the preact-cli template. That will create a repo in your personal GitLab (but I wanted mine to be in a GitLab group). Move the GitLab repo into a group. Create a new Netlify site for the newly named repo (which is now in a group). Turn on identity and the git gateway in Netlify for the new site. Invite someone to edit and make a change to the site from within the https://site.netlify.app/admin panel.

Expected behavior

As far as I’m aware, the build is supposed to occur within Netlify, not in GitLab, right?

I don’t think this was happening until I moved the repo into the group and created the new site in Netlify.

Screenshots

GitLab:

Repo:

Applicable Versions:

• Netlify CMS version: netlify-cms-app 2.15.9, bootstrap.js:83 netlify-cms-core 2.40.5, index.js:27 netlify-cms 2.10.129
• Git provider: GitLab
• OS: N/A
• Browser version N/A

• Node.JS version: N/A

CMS configuration

backend:
  name: git-gateway
  branch: master
media_folder: src/assets
public_folder: /assets
collections:
  - name: "pages"
    label: "Pages"
    label_singular: "Page" # Used in the UI, ie: "New Post"
    folder: "content/blog"
    create: true
    fields:
      - { label: "Title", name: "title", widget: "string" }
      - { label: "Publish Date", name: "date", widget: "datetime" }
      - { label: "Subtitle", name: "subtitle", widget: "string", required: false }
      - { label: "Cover", name: "cover", widget: "image", required: false }
      - { label: "Tags", name: "tags", widget: "string" }
      - { label: "Body", name: "body", widget: "markdown" }

Additional context

I think I have 2 Netlify CMS sites pointing to the same repo (the original site and the new site). Would that affect anything?

I feel as though Netlify CMS is manually triggering the build via an API call, perhaps? I don’t think I have anything in GitLab that would cause a CI/CD to get triggered.

[paridigm]

Turns out it was just a problem with GitLab’s recent credit card validation system that just so happened to start right when I created the other project in Netlify.

Reply from GitLab support:

The issue you’ve described is a known issue with our new credit card validation. The validation and pipeline shouldn’t be running if you do not have a .gitlab-ci.yml so this is indeed unintentional and shouldn’t affect your repository otherwise.

If you are not using CI/CD, you can disable it by going to Settings > General > Visibility, project features, permissions > CI/CD. I hope that information helps! Please let us know if you have any additional questions or concerns.

Known issue link: https://gitlab.com/gitlab-org/gitlab/-/issues/331959

Good news is that there is a setting in GitLab to prevent it from happening!

[paridigm]

It seems like the pipeline doesn’t even start at all due to the error, so I don’t think any logs even exist for the pipeline. 🤔

I actually submitted a GitLab support ticket yesterday, so we shall see what they find out!