You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-16Lines changed: 1 addition & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,22 +8,7 @@
8
8
9
9
## User Guide
10
10
11
-
[Browse the user guide here](docs/USER_GUIDE.adoc)
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
11
+
To configure this plugin correctly, read the [user guide here](docs/USER_GUIDE.adoc)
0 commit comments