Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properly handle value "https" in clone link name #806

Merged

Conversation

andrey-fomin
Copy link
Contributor

@andrey-fomin andrey-fomin commented Feb 12, 2024

In Bitbucket Server "http" is used as http link name, but in Bitbucket Cloud "https" is used.

Bug was introduced in #796. Fixes #804.

Your checklist for this pull request

  • Make sure you are requesting to pull a topic/feature/bugfix branch (right side) and not your master branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or in Jenkins JIRA
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Did you provide a test-case? That demonstrates feature works or fixes the issue.

In Bitbucket Server "http" is used as http link name,
but in Bitbucket Cloud "https" is used.

Bug was introduced in jenkinsci#796. Fixes jenkinsci#804.
@andrey-fomin andrey-fomin force-pushed the fix-protocol-check-for-cloud branch from a02cbdf to 2fff462 Compare February 12, 2024 18:19
@lifeofguenter
Copy link
Contributor

Thanks for the quick fix 🙇🏽 ❤️

@lifeofguenter lifeofguenter merged commit b8fa891 into jenkinsci:master Feb 12, 2024
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

IllegalStateException: "Can't find clone link for protocol HTTP" after plugin update
2 participants