-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
I'd like the Bitbucket Server Integration plugin to provide a stable Java API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an SCMSource and wants to know:
- Whether this SCMSource came from the Bitbucket Server Integration plugin.
- The root URI for Bitbucket Server REST APIs.
- The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration.
- Project key
- Repository slug
All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as public. However, all the classes are within the package com.atlassian.bitbucket.jenkins.internal (javadoc), which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any @Restricted annotations at all.
Context: https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815 and https://jira.atlassian.com/browse/BSERV-11477?focusedCommentId=2647677&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2647677
- relates to
-
JENKINS-74987 Provide stable API for reading Bitbucket REST API parameters
-
- Open
-
[JENKINS-64691] Stable API for reading REST URL from BitbucketSCMSource
Kalle Niemitalo
created issue -
Kalle Niemitalo
made changes -
| Description |
Original:
I'd like the Bitbucket Server Integration to provide a stable API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an [SCMSource|https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMSource.html] and wants to know:
* Whether this SCMSource came from the Bitbucket Server Integration plugin. * The root URI for Bitbucket Server REST APIs. * The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration. * Project key * Repository slug All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as {{public}}. However, all the classes are within the package {{com.atlassian.bitbucket.jenkins.internal}}, which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any {{@Restricted}} annotations at all. Context: [https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815] |
New:
I'd like the Bitbucket Server Integration plugin to provide a stable API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an [SCMSource|https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMSource.html] and wants to know:
* Whether this SCMSource came from the Bitbucket Server Integration plugin. * The root URI for Bitbucket Server REST APIs. * The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration. * Project key * Repository slug All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as {{public}}. However, all the classes are within the package {{com.atlassian.bitbucket.jenkins.internal}}, which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any {{@Restricted}} annotations at all. Context: [https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815] |
Kalle Niemitalo
made changes -
| Description |
Original:
I'd like the Bitbucket Server Integration plugin to provide a stable API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an [SCMSource|https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMSource.html] and wants to know:
* Whether this SCMSource came from the Bitbucket Server Integration plugin. * The root URI for Bitbucket Server REST APIs. * The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration. * Project key * Repository slug All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as {{public}}. However, all the classes are within the package {{com.atlassian.bitbucket.jenkins.internal}}, which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any {{@Restricted}} annotations at all. Context: [https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815] |
New:
I'd like the Bitbucket Server Integration plugin to provide a stable API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an [SCMSource|https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMSource.html] and wants to know:
* Whether this SCMSource came from the Bitbucket Server Integration plugin. * The root URI for Bitbucket Server REST APIs. * The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration. * Project key * Repository slug All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as {{public}}. However, all the classes are within the package {{com.atlassian.bitbucket.jenkins.internal}} ([javadoc|https://javadoc.jenkins.io/plugin/atlassian-bitbucket-server-integration/]), which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any {{@Restricted}} annotations at all. Context: [https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815] |
Kalle Niemitalo
made changes -
| Description |
Original:
I'd like the Bitbucket Server Integration plugin to provide a stable API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an [SCMSource|https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMSource.html] and wants to know:
* Whether this SCMSource came from the Bitbucket Server Integration plugin. * The root URI for Bitbucket Server REST APIs. * The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration. * Project key * Repository slug All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as {{public}}. However, all the classes are within the package {{com.atlassian.bitbucket.jenkins.internal}} ([javadoc|https://javadoc.jenkins.io/plugin/atlassian-bitbucket-server-integration/]), which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any {{@Restricted}} annotations at all. Context: [https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815] |
New:
I'd like the Bitbucket Server Integration plugin to provide a stable API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an [SCMSource|https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMSource.html] and wants to know:
* Whether this SCMSource came from the Bitbucket Server Integration plugin. * The root URI for Bitbucket Server REST APIs. * The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration. * Project key * Repository slug Perhaps also similar APIs for freestyle jobs and single-branch pipelines. All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as {{public}}. However, all the classes are within the package {{com.atlassian.bitbucket.jenkins.internal}} ([javadoc|https://javadoc.jenkins.io/plugin/atlassian-bitbucket-server-integration/]), which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any {{@Restricted}} annotations at all. Context: [https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815] |
Kalle Niemitalo
made changes -
| Description |
Original:
I'd like the Bitbucket Server Integration plugin to provide a stable API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an [SCMSource|https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMSource.html] and wants to know:
* Whether this SCMSource came from the Bitbucket Server Integration plugin. * The root URI for Bitbucket Server REST APIs. * The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration. * Project key * Repository slug Perhaps also similar APIs for freestyle jobs and single-branch pipelines. All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as {{public}}. However, all the classes are within the package {{com.atlassian.bitbucket.jenkins.internal}} ([javadoc|https://javadoc.jenkins.io/plugin/atlassian-bitbucket-server-integration/]), which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any {{@Restricted}} annotations at all. Context: [https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815] |
New:
I'd like the Bitbucket Server Integration plugin to provide a stable Java API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an [SCMSource|https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMSource.html] and wants to know:
* Whether this SCMSource came from the Bitbucket Server Integration plugin. * The root URI for Bitbucket Server REST APIs. * The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration. * Project key * Repository slug Perhaps also similar APIs for freestyle jobs and single-branch pipelines. All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as {{public}}. However, all the classes are within the package {{com.atlassian.bitbucket.jenkins.internal}} ([javadoc|https://javadoc.jenkins.io/plugin/atlassian-bitbucket-server-integration/]), which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any {{@Restricted}} annotations at all. Context: [https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815] |
Kalle Niemitalo
made changes -
| Description |
Original:
I'd like the Bitbucket Server Integration plugin to provide a stable Java API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an [SCMSource|https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMSource.html] and wants to know:
* Whether this SCMSource came from the Bitbucket Server Integration plugin. * The root URI for Bitbucket Server REST APIs. * The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration. * Project key * Repository slug Perhaps also similar APIs for freestyle jobs and single-branch pipelines. All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as {{public}}. However, all the classes are within the package {{com.atlassian.bitbucket.jenkins.internal}} ([javadoc|https://javadoc.jenkins.io/plugin/atlassian-bitbucket-server-integration/]), which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any {{@Restricted}} annotations at all. Context: [https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815] |
New:
I'd like the Bitbucket Server Integration plugin to provide a stable Java API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an [SCMSource|https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMSource.html] and wants to know:
* Whether this SCMSource came from the Bitbucket Server Integration plugin. * The root URI for Bitbucket Server REST APIs. * The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration. * Project key * Repository slug All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as {{public}}. However, all the classes are within the package {{com.atlassian.bitbucket.jenkins.internal}} ([javadoc|https://javadoc.jenkins.io/plugin/atlassian-bitbucket-server-integration/]), which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any {{@Restricted}} annotations at all. Context: [https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815] |
Kalle Niemitalo
made changes -
| Description |
Original:
I'd like the Bitbucket Server Integration plugin to provide a stable Java API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an [SCMSource|https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMSource.html] and wants to know:
* Whether this SCMSource came from the Bitbucket Server Integration plugin. * The root URI for Bitbucket Server REST APIs. * The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration. * Project key * Repository slug All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as {{public}}. However, all the classes are within the package {{com.atlassian.bitbucket.jenkins.internal}} ([javadoc|https://javadoc.jenkins.io/plugin/atlassian-bitbucket-server-integration/]), which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any {{@Restricted}} annotations at all. Context: [https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815] |
New:
I'd like the Bitbucket Server Integration plugin to provide a stable Java API from which other plugins can read parameters for Bitbucket Server REST APIs. The other plugin has an [SCMSource|https://javadoc.jenkins.io/plugin/scm-api/jenkins/scm/api/SCMSource.html] and wants to know:
* Whether this SCMSource came from the Bitbucket Server Integration plugin. * The root URI for Bitbucket Server REST APIs. * The credential ID for Bitbucket Server REST APIs, or the credential itself. Not the admin token from the global configuration. * Project key * Repository slug All of this information is already available from classes and methods that the Bitbucket Server Integration plugin declares as {{public}}. However, all the classes are within the package {{com.atlassian.bitbucket.jenkins.internal}} ([javadoc|https://javadoc.jenkins.io/plugin/atlassian-bitbucket-server-integration/]), which suggests that Atlassian might not want to support them as a stable API. The Bitbucket Server Integration plugin does not have any {{@Restricted}} annotations at all. Context: [https://github.com/jenkinsci/checks-api-plugin/issues/65#issuecomment-765024815] and [https://jira.atlassian.com/browse/BSERV-11477?focusedCommentId=2647677&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2647677] |
| Assignee | Original: Kristy Hughes [ khughes ] |
Kalle Niemitalo
made changes -
| Link | New: This issue relates to JENKINS-74987 [ JENKINS-74987 ] |