-
Notifications
You must be signed in to change notification settings - Fork 8
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
feat: Add Bitbucket Data Center support #227
base: main
Are you sure you want to change the base?
Conversation
4bc6d7d
to
92404d2
Compare
@@ -9,7 +9,7 @@ on: | |||
- main | |||
|
|||
env: | |||
IMAGE_NAME: ghcr.io/renovatebot/renovate-approve-bot-bitbucket-cloud | |||
IMAGE_NAME: ghcr.io/renovatebot/renovate-approve-bot-bitbucket |
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.
@maxbrunet @viceice do you have any concerns about this breaking change? Ideas on how to unbreak it for users, or alert them?
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.
no way to unbreak.
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 probably should publish both images for a while
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.
I wonder if we should bundle other breaking changes for v2?
- Upgrade to node v18 #166
- Migrate to ESM with upgrade to got v12 and jest v28
And the code getting larger, TypeScript (#58) starts making more sense
FYI I do not use Bitbucket anymore, so I will not be able to help testing this
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.
this PR should be split to multiple.
- repo rename
- code refactor
- server support
@@ -1,8 +1,8 @@ | |||
FROM docker.io/library/node:14.19.1-alpine@sha256:8845b4f88f64f8c56a39236648ba22946e806a6153c10911f77b70e5a2edb4ca | |||
|
|||
LABEL \ | |||
org.opencontainers.image.source="https://github.com/renovatebot/renovate-approve-bot-bitbucket-cloud" \ | |||
org.opencontainers.image.url="https://github.com/renovatebot/renovate-approve-bot-bitbucket-cloud" \ | |||
org.opencontainers.image.source="https://github.com/renovatebot/renovate-approve-bot-bitbucket" \ |
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.
repo rename should be a separate PR/ step with a major version bump.
should probably be done before this PR.
Alright, I will try to break up this pull request. If I understood correctly, the plan is to do this change amongst other things in version 2. Some questions came to my mind:
|
no, the repo rename can be done without a breaking change, we simply publish the old image additionally for a while and drop it on a later major bump.
Sure, but it needs somebody from community to do that. |
As discussed in #214 this pull request adds support for Bitbucket Data Center and Server. Existing Bitbucket Cloud users need to update the Docker image name since I removed the
-cloud
suffix, but the bot will still connect to Bitbucket Cloud by default. Only if you set theBITBUCKET_URL
environment variable, it will use the new Bitbucket Data Center specific code.