Pipeline fail in project with no CI configuration

Hello,
we’re receving a pipeline failed error (“The pipeline failed due to the user not being verified”) whenever a member of our staff (and only him) pushes something on a project that isn’t using any pipeline. No .gitlab-ci.yml exists in the repository.

The user has a valid, verified email:

Can anybody help me understand why this happens?
Thanks.

Fabio.

5 Likes

We have purchased 10x100=10k CI minutes & few of our users are getting error “The pipeline failed due to the user not being verified”

CC details are updated, we are buying CI min’s & associating it to Group,

All this happened after this was downgraded back to previous plan. old user’s are un effected however newly added user having this issues.

Please Help Us here

Same here, we have a new employee, with a new Gitlab User, and he is unable to trigger pipelines on push. We can not demand that the employee links a credit card to his account.

How can we solve this?

Same here

Same here with new member

We are also seeing this issue with just our newest member of the team.

Hi, we delivered a fix for this yesterday New users shouldn't get a failed pipeline warning without having a gitlab-ci.yml file (#331959) · Issues · GitLab.org / GitLab · GitLab.

Please let us know if you are still having issues!

1 Like

The issue appears to have been solved. Thank you!

1 Like

I still have this issue.
We have an account for our business @ecomerciar, and we recently added a new team member, a new employee, and his pushes make the pipelines for the team projects fail. He is a verified user.

We are also seeing this issue.

It looks like this is related to safeguards added to GitLab to prevent abuse from crypto mining: How to prevent crypto mining abuse on GitLab.com SaaS | GitLab

Hello, we also have an paid Account hand have the same issue for new user.

We are still seeing this issue here at our end too.

We are also experiencing this problem, we are using the free plan, and we are within 2000 minutes per month.

image

1 Like

Same problem and it’s very urgent … To be more explicit : before my new dev (him = maintainer role and I = owner) didn’t add his own credit card pipeline build failed, but after adding its own credit card… pipelines run!
It’s a big issue because I’ve already add a card for the group account, so it’s a big pain if my team also need to add their credit card.

Same Issue here.
Pipelines triggered by our new employee with new gitlab account are crashing with the error message ‘The pipeline failed due to the user not being verified’.
Pipelines triggered by old users are uneffected

See New users shouldn't get a failed pipeline warning without having a gitlab-ci.yml file (#331959) · Issues · GitLab.org / GitLab · GitLab.

Also see How to prevent crypto mining abuse on GitLab.com SaaS | GitLab.

1 Like

It’s a big issue because I’ve already add a card for the group account, so it’s a big pain if my team also need to add their credit card.

Do you mean that this group is on a paid plan? Can you provide the group and/or project ID in question?

No we use the free plan but to enable pipelines, a credit card was needed.