I am building an app with technologies I'm not familiar with (sails.js, AWS). I am trying to set up CI between Bitbucket and an AWS Ubuntu EC2 instance.
I have created a couple of repositories in Bitbucket and I am the owner of these repositories. The instructions I have found say that you need to log in to Bitbucket as an admin and click on the admin link. For some reason, I cannot see an admin link in Bitbucket.
Why is this? Do I need to create an admin account? Why can't the owner see the admin link in Bitbucket?
Related
I have IAM roles like Editor/Cloud Run Admin in my gcp projects (multiple Projects) I am facing this issue,
When I am trying to deploy the container image from Cloud Run's "Edit & Deploy New Revision" screen.
It's not listing the Images in the Project and gives error refer this screenshot for the error message .
Its not only for me other users also facing same issue, but with the same editor and admin roles I am able to list all images in the other project. I have also checked with other developers
If the "Artifact Registry API" is enabled in GCP. then we can list the images from the project.
To enable this API, Search for 'Artifact Registry API' and click enable.
Only if you have this 'Service Usage Admin' IAM role, you can enable API.
Thanks to my Support Team in Project
I'm using GCP build triggers connected to Bitbucket repositories. The connection is made using user credentials. Bitbucket has announced they're ending support for account password usage:
Beginning March 1, 2022, Bitbucket users will no longer be able to use
their Atlassian account password when using Basic authentication with
the Bitbucket API or Git over HTTPS. For security reasons, we require
all users to use Bitbucket app passwords.
Problem is, when trying to connect to a repository in GCP, the only option to supply Bitbucket credentials is via a web login (which to the point of app passwords, you cannot login via the bitbucket.org with an app password).
GCP Bitbucket login prompt via bitbucket.org
Expected behavior: GCP provides an option to submit app password credentials when connecting to a Bitbucket repository.
I followed directions for GCP Cloud Build integration with Bitbucket Cloud and successfully built out a functioning trigger for my repository here. I only built the trigger in GCP and used the generated webhook URL when creating the webhook in Bitbucket: I didn't create SSH keys, nor is my cloudbuild.yaml entirely valid - so the builds are failing.
Access to the Bitbucket repository was provided through GCP GUI in Cloud Build.
I have been informed of this change as well. I am trying to understand the scope of the change and its impact. It states that you cannot log in Atlassian account and password. However, besides using app passwords, you can also log in using OAuth2. https://developer.atlassian.com/cloud/bitbucket/oauth-2/
In the case of GCP Build Triggers, when I first set up the Bitbucket repository to connect to, I need to go through the "Authorization Code Grant" flow and acknowledge what access I am granting to Google Cloud Source Repository. If you check the Bitbucket API endpoints being called, they are URLs that are being used for "Authorization Code Grant" flow.
Based on these findings, am I right to say that there is no necessity to change existing triggers or mirrored repositories on GCP since they are using OAuth2 in the first place instead of Atlassian accounts and passwords?
If you can setup the build trigger to be done by a webhook you can configure the build with ssh key. But if you have to configure it as a manual trigger then using the bitbucket login credentials is the only option. Personally, I don't like this config with user login though.
The only good thing is even now(after bitbucket stopped supporting the login credentials for code checkout) the code checkout in GCP is working fine.
I am trying to set up a cloud build trigger from a public github repository with the Cloud Build GitHub App. I installed the app on my repository and authorized it but when I was redirected to GCP to connect the repository to a project this error message came up:
Failed to retrieve GitHub repositories.
The caller does not have permission
error
I suspect it may have something to do with having two factor authentication enabled on my github account, which I need for an organization.
I was able to mirror the same github repository from cloud source repositories without any issues though. I am the owner of the repository and gcp project.
*edit
Looks like the issue is due to having 2 factor authentication enabled on my github account. I disabled it and cloud build was able to connect with my repository. However I will need to have 2 factor enabled as my github organization requires it.
*edit
I hadn't mentioned the github organization i was part of had an ip whitelist configured on top of requiring 2 factor auth. I left the organization and reenabled 2 factor auth and cloud build was able to connect to my repo. Not sure why I would get the original issue if the repo is not in the github organization.
After looking more into this problem you either need to add GCE IP address ranges to the github organization IP whitelist https://cloud.google.com/compute/docs/faq#find_ip_range or just disable the whitelist if able to.
I'm GCP project owner and trying to connect a BitBucket repo as mirror in Cloud Source Repos. Also have a Cloud Build trigger based on a BitBucket repo.
In Cloud Source Repositories, after granting access to my account, while configuring a mirror, no repositories from BitBucket appear and the following is displayed:
The Bitbucket account [username] doesn't have access to any
Bitbucket repositories. You will need to grant this account permission
to repositories in Bitbucket before you can connect them.
In Cloud Build triggers, after the grant permissions dialog, Select repository lists no BitBucket repos and the Continue button is greyed out.
This error message will appear if your Bitbucket account only has Read or Write access to the repository you want to mirror. Check that you have Admin access on Bitbucket and try again. Also, make sure you're logged into the right Bitbucket account when attempting to make the connection.
I had CodeBuild authorised with my GitHub through the AWS Console, but then I revoked the GitHub OAuth (in preparation for attaching a CI GitHub user). Now it insists "Failed to login to GitHub, please reconnect your account", but I honestly cannot find where to do so -- thoughts?
screenshot of error message
On the CodeBuild console/UI, you will find an option to "disconnect from GitHub" when creating a CodeBuild project or editing the source provider of an existing project. Once you have disconnected on the UI, you would also want to sign off of GitHub if you have an authenticated browser session with you non-CI GitHub login. Then simply click on connect to GitHub when creating or editing the CodeBuild project. You will need to sign-in as the GitHub user that you want CodeBuild to access repositories from.
Note CodeBuild only supports one GitHub login/OAuth per AWS account Id. So all projects in your AWS account share the same GitHub repo access. Hope that helps.