Skip to content
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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

brushmate
Copy link

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 the BITBUCKET_URL environment variable, it will use the new Bitbucket Data Center specific code.

@brushmate brushmate force-pushed the bitbucket-data-center-support branch from 4bc6d7d to 92404d2 Compare May 16, 2022 12:39
@@ -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
Copy link
Collaborator

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?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no way to unbreak.

Copy link
Member

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

Copy link
Collaborator

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?

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

Copy link
Member

@viceice viceice left a 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" \
Copy link
Member

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.

@brushmate
Copy link
Author

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:

  1. Are you planning to create a development brnach for v2 so that I can create pull requests against this branch instead of main?
  2. I also felt like TypeScript would have been the better language for the changes I have introduced. Should I wait splitting up the pull request until Migrate from JavaScript to TypeScript #58 has been tackled?

@viceice
Copy link
Member

viceice commented Aug 7, 2023

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:

  1. Are you planning to create a development brnach for v2 so that I can create pull requests against this branch instead of main?

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.

  1. I also felt like TypeScript would have been the better language for the changes I have introduced. Should I wait splitting up the pull request until Migrate from JavaScript to TypeScript #58 has been tackled?

Sure, but it needs somebody from community to do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants