User validation required?

We have a new developer whose pipelines are not running due to an error with a message that starts User validation required To use free pipeline minutes on shared runners, you’ll need to validate your account with a credit or debit card....

I don’t remember validating my account like this, is it now the normal workflow?

Thanks,

Sarah

Hi @snim2 Gitlab added this recently, because of abuse of their platform with people mining crypto via the shared runners, pipelines. So now, all accounts need to be verified first so that the abuse can be reduced.

This is the post relating to that change: Preventing Crypto Mining abuse on GitLab.com SaaS

1 Like

Thanks @iwalker

2 Likes

all accounts need to be verified

Thank you for the correct answer, @iwalker. A small correction: only new accounts need to be verified.

From the forum post you linked (emphasis mine):

starting May 17th, 2021, GitLab will require new free users to provide a valid credit card in order to use shared runners on GitLab.com.

2 Likes

Hello, will there be another option besides ‘credit card’ to use as validation? I could imagine that a lot people in the EU don’t use creditcards but debitcards. Wondering how I can validate my account now :sleepy:

@CEikelboom apparently it is possible:

2 Likes

Same issue, here and I’ve already validated with a valid debit card. HOwever, it still asks for validations after refresh

At present the validation banner will still show on pipelines that failed to run before you validated. This is a bit confusing, admittedly and our team is working on making it less so.

In the mean time, please try your pipeline again by pushing a new commit or triggering a pipeline manually.

Using gitlab as a company this is no solution for us because every new employee would have to use his private creditcard (or debitcard) but none of them would like to do so.
Is that the recommended way? Is there a sort of Company-Account where we can manage accounts by ourselves?

1 Like

Hi @thiagocsf understood that only new accounts need to be verified but has anybody thought through the onboarding user experience of this? A new Gitlab user joins a team, they will not be able to run pipelines, they will be stuck and confused why they’re being asked for a credit credit when they are onboarding as a member of a company group. Both resolutions are not ideal:

  • They enter their private card details to GitLab or
  • We share company card details to the new user to enter, this is not ideal either.

Am I missing something cleaner that can be done?

Hi, @vicken.papaya.

has anybody thought through the onboarding user experience of this?

Yes; we’re working on it. You’re not missing anything, as far as I know.

Unfortunately I have no public issue to share since discussions around this topic are being treated as confidential. I’ve asked internally for help providing a better answer here.

I’m sorry I have no better answer for you right now.

@thiagocsf any updates? we’re experiencing the same issue. This is far from ideal. We’ve purchased additional minutes, but new users are unable to run pipelines.

Hi @ thiagocsf! I understand the motivation driving this restriction. But what happens with purchased pipeline minutes?, I purchased additional minutes that I can not use with new developers because of this restriction. Is there away to disable free minutes and only use the minutes I purchased?. Purchased pipeline minutes shouldn’t be affected.

@ricardo000, I’m trying to open-up issue https://gitlab.com/gitlab-org/gitlab/-/issues/334341 which is currently confidential so anyone can see the latest updates.

@mauricios, I’ve asked internally for help answering questions in this thread. Unfortunately I couldn’t find any answers for you.

For anyone who’s covered by support, I would recommend using it as a channel for requesting updates: https://support.gitlab.com/.

/cc @lkozloff