1

I just started having a problem when I commit to my repo:

  1. commit doesn't trigger CI pipeline, even though it should
  2. commit doesn't show up in the Activity feed

I have a repo on GitLab, and have been using GitLab Pages to publish a static site when I push changes to the repo.

I haven't used it in a month, and today, for some reason, it is not triggering the pipeline as it usually does. I have not changed anything about my .gitlab-ci.yml, which consists of the following YAML:

stages:
  - build
  - test
  - deploy

pages:
  stage: deploy
  script:
    - mkdir .public
    - cp -r path_to_my_rendered_site/* .public
    - mv .public public
  artifacts:
    paths:
      - public
  rules:
    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH

It's not that the pipeline is failing, it's simply not being triggered at all.

If I look in Repository > Commits, I see that earlier commits triggered the pipeline, and deployed the site:

enter image description here

But for my commit today (and other ones I've tried since), there's nothing:

enter image description here

For the second, maybe related problem: I noticed as well that my recent commits do not show up in the Project Information > Activity feed. Under All, I see all my older commits, but the ones today are not there. I imagine this is related.

postylem
  • 1,185
  • 12
  • 26
  • Now I checked back a few days later, and the commits have all triggered their pipelines like they should. It must have simply been delayed (?). – postylem Mar 31 '23 at 01:56

0 Answers0