-
-
Notifications
You must be signed in to change notification settings - Fork 5
fix(ci) Fix the registry url for cloudbuild #35
Conversation
c20cf5e
to
5ef16a9
Compare
5ef16a9
to
f720f2e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the main issue here was using docker push $PROJECT_ID/$REPO_NAME
which translates into docker push sentryio/cdc
, right?
cloudbuild_public.yaml
Outdated
@@ -42,20 +42,24 @@ steps: | |||
- | | |||
# Only push to Docker Hub from master | |||
[ "$BRANCH_NAME" != "master" ] && exit 0 | |||
docker pull us.gcr.io/$PROJECT_ID/$REPO_NAME:$COMMIT_SHA | |||
docker pull $$SENTRY_IMAGE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please make this $$CDC_IMAGE
as SENTRY_IMAGE
has a special meaning in on-premise and it will interfere.
Also looks like we need a |
That was an issue. But I think also creating the |
@BYK thanks for adding the repo on docker. Now it works. |
The current cloudbuild cannot push the docker image because the url is wrong.
Anyway this fails as well for the lack of permissions, but it is more right than before.