Bitbucket Datacenter reporter

[glenroy37]

Is your feature request related to a problem? Please describe.
The current Bitbucket Reporter only supports Bitbucket Cloud, but we have self-hosted Bitbucket Datacenter. Unfortunately it's not as easy as just making the URL configurable, because Bitbucket Datacenter only supports the old 1.0 Bitbucket API, while Bitbucket Cloud uses the much newer 2.0 Bitbucket API.

Describe the solution you'd like
A new reporter for Bitbucket Datacenter.

Describe alternatives you've considered
Integrating it into the existing reporter, but because of the different API calls I think a separate one is easier to maintain.

Additional context
I've already forked the repository and made a first test on our Bitbucket Datacenter instance: https://github.com/glenroy37/megalinter-bitbucket-datacenter/tree/issue-6675-bitbucket-datacenter

I still have to run the automated tests and look if the code is in line with your guidelines, before creating a PR

[nvuillam]

@glenroy37 isn't there a way to detect when you're with bitbucket data center ?

I would prefer to have everything managed in a single reporter file, no problem if some "switch" methods have to be created :)

[glenroy37]

nvuillam We could switch to Datacenter calls if BITBUCKET_URL is defined and doesn't match "https://bitbucket.org" or similar. I'll look into it

[nvuillam]

I'll gladly merge your Pull Request :)

[nvuillam]

@glenroy37 chatgpt says the following, if it can help :)

🔍 Simple Rule of Thumb
✔ If BITBUCKET_PIPELINE_UUID exists → Cloud
✔ If it does not exist → almost certainly Data Center

[glenroy37]

@nvuillam
The problem is we need different environment variables for Bitbucket Datacenter. For example instead of BITBUCKET_FULL_REPO_NAME we need a project key and repo slug as those are in different parts of the URL for the API. And then every API call is different between Datacenter and Cloud, therefore I don't find it very elegant to put it into the same Reporter as I did here: b18d0b0

Maybe I should do two different functions called by produce_report for datacenter and cloud. But that doesn't solve the need for different config env variables.