docs: update bitbucket server status
This commit is contained in:
Родитель
dbada62dc0
Коммит
ca77ce951d
|
@ -20,14 +20,6 @@ Note: we plan to add support for Bitbucket.org to the _hosted_ Renovate Bot _ser
|
|||
|
||||
How to use: run your own bot from npm, Docker or clone the repository. Follow the instructions from: [https://github.com/renovatebot/renovate/blob/master/docs/self-hosting.md#bitbucket-cloud](https://github.com/renovatebot/renovate/blob/master/docs/self-hosting.md#bitbucket-cloud).
|
||||
|
||||
### Bitbucket Server
|
||||
|
||||
Status: beta
|
||||
|
||||
Bitbucket Server (i.e. self-hosted Bitbucket) came after Bitbucket Cloud but has already had perhaps more testing than Cloud and may make GA first. Once we get a few more thumbs-ups from users testing it on "real" repositories we will elevate this to GA.
|
||||
|
||||
How to use: run your own bot from npm, Docker or clone the repository. Follow the instructions from [https://github.com/renovatebot/renovate/blob/master/lib/platform/bitbucket-server/README.md](https://github.com/renovatebot/renovate/blob/master/lib/platform/bitbucket-server/README.md).
|
||||
|
||||
### Bundler
|
||||
|
||||
Status: alpha
|
||||
|
|
|
@ -1,7 +1,5 @@
|
|||
# Bitbucket Server Support
|
||||
|
||||
Bitbucket Server support is considered in "alpha" release status. There are no known problems or limitations other than what is documented below, but we want to wait for a little more feedback and ideally 1-2 or the mising features below before moving it to beta and then GA.
|
||||
|
||||
## Unsupported platform features/concepts
|
||||
|
||||
- Adding assignees to PRs not supported (does not seem to be a Bitbucket concept)
|
||||
|
@ -10,7 +8,6 @@ Bitbucket Server support is considered in "alpha" release status. There are no k
|
|||
## Features awaiting implementation
|
||||
|
||||
- Creating issues not implemented yet, used to alert users when there is a config error
|
||||
- Adding comments to PRs not implemented yet, e.g. when a PR has been edited or has a lockfile error
|
||||
|
||||
## Testing
|
||||
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
# Bitbucket platform
|
||||
# Bitbucket Cloud
|
||||
|
||||
Bitbucket support is considered in "beta" release status.
|
||||
Bitbucket Cloud support is considered in "beta" release status. Mostly, it just needs more feedback/testing. If you have been using it and think it's reliable, please let us know.
|
||||
|
||||
## Unsupported platform features/concepts
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ Automated dependency updates. Multi-platform and multi-language.
|
|||
- Bot behaviour is extremely customisable via configuration files (config as code)
|
||||
- Use eslint-like shared config presets for ease of use and simplifying configuration
|
||||
- Lock files are natively supported and updated in the same commit, including immediately resolving conflicts whenever PRs are merged
|
||||
- Supports GitHub, GitLab, Bitbucket Cloud (beta release) and Azure DevOps.
|
||||
- Supports GitHub (.com and Enterprise), GitLab (.com and CE/EE), Bitbucket Server, and Azure DevOps. Bitbucket Cloud is also supported but considered in Beta until it gets the thumbs-up from more users
|
||||
- Open source (installable via npm/yarn or Docker Hub) so can be self-hosted or used via GitHub App
|
||||
|
||||
## Who Uses Renovate?
|
||||
|
|
|
@ -27,7 +27,7 @@ In order to achieve the above goals, preset configs have been implemented to all
|
|||
|
||||
## Preset Hosting
|
||||
|
||||
Presets can be defined using either npm packages, or with GitHub repositories. GitLab and Bitbucket-hosted presets are yet to be implemented.
|
||||
Presets can be defined using either npm packages, or with GitHub/GitLab repositories. Bitbucket-hosted presets are yet to be implemented.
|
||||
|
||||
The following namespace is used:
|
||||
|
||||
|
|
Загрузка…
Ссылка в новой задаче