-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(bitbucket-pipelines): authenticated registries #21096
docs(bitbucket-pipelines): authenticated registries #21096
Conversation
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.
we should extend manager support instead
Agree, and there is an open issue to track that. But until then, why not improve the docs? Can easily remove the regexs manager examples if and when the bitbucket-pipelines manager parses the yml, which would only improve authenticated image handling, I cannot see it supporting moving from unauthenticated to authenticated image structures |
Moving to draft until feedback re: #21107 |
|
||
Bitbucket Pipelines supports using an authenticated Docker registry, including self-hosted private registries, Docker Hub, Amazon ECR and Google GCR. | ||
|
||
More details can be found on the Atlassian [Bitbucket Pipeline documentation](https://support.atlassian.com/bitbucket-cloud/docs/use-docker-images-as-build-environments) site |
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.
More details can be found on the Atlassian [Bitbucket Pipeline documentation](https://support.atlassian.com/bitbucket-cloud/docs/use-docker-images-as-build-environments) site | |
More details can be found on the Atlassian [Bitbucket Pipeline documentation](https://support.atlassian.com/bitbucket-cloud/docs/use-docker-images-as-build-environments) site. |
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.
Thanks @HonkingGoose
Co-authored-by: HonkingGoose <[email protected]>
Co-authored-by: HonkingGoose <[email protected]>
🎉 This issue has been resolved in version 35.25.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes
Add documentation for
Context
Publishing examples from these two sources
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: