|
10 | 10 |
|
11 | 11 | [Browse the user guide here](docs/USER_GUIDE.adoc)
|
12 | 12 |
|
| 13 | +## Issue tracking (where file new issues?) |
| 14 | + |
| 15 | +At the time of writing, the Jenkins organisation let to the maintainer the choice of which issue tracker to use. Available are Github or [JIRA](https://issues.jenkins.io) issue tracker. |
| 16 | +For reason discussed in the Jenkins Developers Google Group the official issue tracking for this plugin is [JIRA](https://issues.jenkins.io/browse/JENKINS-74965?jql=project%20%3D%20JENKINS%20AND%20component%20%3D%20bitbucket-branch-source-plugin%20ORDER%20BY%20created%20DESC). |
| 17 | + |
| 18 | +What means: |
| 19 | +* new issues must be open at JIRA |
| 20 | +* the Github tracker will be froozen, that means no new issues will be accepted |
| 21 | +* depending on the progress I expect that by the date 01/06/2025 the Github issue tracker will be disabled at all |
| 22 | + |
| 23 | +What will happen to the issues opened in Github? |
| 24 | +* actual issues will be processed |
| 25 | +* maybe resolved |
| 26 | +* otherwise after 6 months, it will be manually migrated by me to JIRA if it doesn't already exist |
| 27 | + |
13 | 28 | ## Notes
|
14 | 29 |
|
15 |
| -* Unlike GitHub, in Bitbucket, [team admins do not have access to forks](https://bitbucket.org/site/master/issues/4828/team-admins-dont-have-read-access-to-forks). |
| 30 | +### General notes |
| 31 | + |
| 32 | +Unlike GitHub, in Bitbucket, [team admins do not have access to forks](https://bitbucket.org/site/master/issues/4828/team-admins-dont-have-read-access-to-forks). |
16 | 33 | This means that when you have a private repository, or a private fork of a public repository, the team admin will not be able to see the PRs within the fork.
|
17 | 34 |
|
18 |
| -## Developers and DevOps notes |
| 35 | +### Developers and DevOps notes |
19 | 36 |
|
20 | 37 | Classes under the packages `com.cloudbees.jenkins.plugins.bitbucket.api` is intended to be public api and can be used to extend functionality in other plugins. Changes in the method signature will be marked with @deprecated providing an alternative new signature or class to use. After a reasonable time (about a year) the method could be removed at all. If some methods are not intended to be used then are marked with `@Restricted(NoExternalUse.class)`.
|
21 | 38 |
|
@@ -55,9 +72,9 @@ multibranch:
|
55 | 72 | credentialsId: 'bitbucket-ssh-credentials'
|
56 | 73 | ```
|
57 | 74 |
|
| 75 | +## How-to run and test with Bitbucket Server locally |
58 | 76 |
|
| 77 | +* [Install the Atlassian SDK on Linux or Mac](https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-linux-or-mac-system/) |
| 78 | +* To run 8.0.0 server: `atlas-run-standalone --product bitbucket --version 8.0.0 --data-version 8.0.0` |
59 | 79 |
|
60 |
| -## How-to run and test with Bitbucket Server locally (deprecated) |
61 |
| - |
62 |
| -* [Install the Atlassian SDK on Linux or Mac](https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-linux-or-mac-system/) or [on Windows](https://developer.atlassian.com/server/framework/atlassian-sdk/install-the-atlassian-sdk-on-a-windows-system/) |
63 |
| -* To run 5.2.0 server: `atlas-run-standalone -u 6.3.0 --product bitbucket --version 5.2.0 --data-version 5.2.0` |
| 80 | +Support to run Server under Windows has been dismissed since version 7.14+ |
0 commit comments