Help! .gitlab-ci.yml file being ignored, or something else preventing pipelines from working!

Hey everyone,

Judging from other threads CI functionality seems to be having a few issues. The one I’ve been stumbling on in the past few days is that I can’t see to get the repos to recognize the .gitlab-ci.yml file.

What I mean by that is: I create a repo with a ci file that I know is valid (because it’s from another repo which successfully uses that ci file), but the new repo won’t enable the ci functionality, i.e. the pipelines page will show the “get started” message.

I even ended up cloning an identical repository with its own ci working into a new repository, and the same problem persists.

I have tried really hard to identify any settings which could be turned on/off by default and affect this, but I can’t seem to get any luck. The “Settings > General > Permissions” has all functionality enabled, including the “Pipelines”.

Has anyone had any of these issues recently? CI related issues have already occurred a few times for me and it honestly makes me worry that it will fail me at critical times in which I need to build/deploy.

Any help is really appreciated.

Thanks.

1 Like

Same issue, I think it may be related to the status issues they have here: http://status.gitlab.com/

Lots of people reporting stuck pipelines and such. Hopefully they resolve this today.

Thanks for answering.

The status page shows everything green right now.

This is also an issue I’ve had a few times in the past, it would be awesome to hear from the dev team about it and whether there have been regressions.

I mean the twitter feed, seems there’s issues with redis and people complaining about pipeline issues on there.

Hello, Look, do you have a symbolic link from the Hook directory to the GitLab directory

hooks -> /opt/gitlab/embedded/service/gitlab-shell/hooks

I deleted this link and until I recovered I did not see the gitlab file of the gitlab-ci.yml until I have restored this link