As far as I remember, you are not allowed to enable Bitbucket Pipelines in Cloud unless you enable SSH in Personal Settings. Why is such configuration is required or recommended?
There's no setting like that!
Maybe your workspace is enforced to have 2FA in place which is causing this result
Here's a public repo I just tested it out without SSH Key --> Link here
May I know the Bitbucket pipelines you have enabled has some tasks related to SSH Authentication?
Thanks,
Pramodh
Ohh yes, I do enable 2FA. Is that the whole reason? I do not have SSH authentication in my pipelines and its steps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, then 2FA is the reason!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But why enabling pipelines need 2FA enable thus SSH setup became a requirements.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We don't need a 2FA or SSH key to run pipelines!!
We need an SSH key in order to enable 2FA.
Can you please confirm whether you have added the SSH key?
Or try with adding an SSH Key and updating the 2FA setting, then work with repos you have in your workspace and all is working well and confirm once
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe your workspace admin has made it required for the repos in your workspace
Try enabling 2FA and then running the pipelines?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My account is the owner and admin, I don't remember making it required in my repo, maybe because they were set to private.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Bitwise DEVS
Yep, @Theodora Boudale has given the reason in the thread!! This is it.
To prevent abuse from misusing the Pipelines feature, these are some pre-checks that they have implemented.
So go ahead and enable SSH Key, 2FA on your account which makes it secure!!
Let me know if you have need any clarification.
Thanks,
Pramodh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
FYI
I just created a Pipeline in my account with private access, I was able to run it.
May be if you are using the Bitbucket pipelines feature extensively, that is causing it to enable the SSH Keys
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great, many thanks! This is a helpful clarification.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.