git-plugin icon indicating copy to clipboard operation
git-plugin copied to clipboard
verified publisher icon jenkinsci

[JENKINS-70897] Add support for personal access token authentication

Open Gagarmel opened this issue 1 year ago • 1 comments

JENKINS-70897 - summarize pull request in one line

On Bitbucket Datacenter/Cloud and Azure it is required to use personal access tokens instead of username/password authentication.

Resolves jenkinsci/bitbucket-branch-source-plugin#716 Requires jenkinsci/git-client-plugin/pull/1104

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. This is simply a reminder of what we are going to look for before merging your code. If a checkbox or line does not apply to this pull request, delete it. We prefer all checkboxes to be checked before a pull request is merged

  • [x] I have read the CONTRIBUTING doc
  • [x] I have referenced the Jira issue related to my changes in one or more commit messages
  • [x] Unit tests pass locally with my changes
  • [x] I have added documentation as necessary
  • [x] No Javadoc warnings were introduced with my changes
  • [x] No spotbugs warnings were introduced with my changes
  • [x] Documentation in README has been updated as necessary
  • [x] Online help has been added and reviewed for any new or modified fields
  • [x] I have interactively tested my changes
  • [ ] Any dependent changes have been merged and published in upstream modules (like git-client-plugin)

Types of changes

What types of changes does your code introduce? Put an x in the boxes that apply. Delete the items in the list that do not apply

  • [ ] Dependency or infrastructure update
  • [ ] Bug fix (non-breaking change which fixes an issue)
  • [x] New feature (non-breaking change which adds functionality)
  • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Further comments

If this is a relatively large or complex change, start the discussion by explaining why you chose the solution you did and what alternatives you considered.

Gagarmel avatar Mar 21 '24 19:03 Gagarmel

Please kindly add these changes.

habazie avatar Nov 21 '24 14:11 habazie

Hi, what is a status of this PR? Looks like it stuck. Is anything missing?

jangalda-nsc avatar Aug 20 '25 08:08 jangalda-nsc

Pretty sure, the Jenkins webhook job is stack and missing to push the results to github. An empty commit would already help to retrigger..

rpasche avatar Oct 28 '25 19:10 rpasche