Implement Set Client func in Bitbucket Server #1894
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zakisk
commented
Jan 26, 2025
| "github.com/openshift-pipelines/pipelines-as-code/pkg/params/info" | ||
| "github.com/openshift-pipelines/pipelines-as-code/pkg/provider" | ||
| "github.com/openshift-pipelines/pipelines-as-code/pkg/provider/bitbucketserver/types" | ||
| "gotest.tools/v3/assert" | ||
| ) | ||
|
|
||
| var ( | ||
| defaultAPIURL = "/api/1.0" | ||
| buildAPIURL = "/build-status/1.0" | ||
| defaultAPIURL = "/rest/api/1.0" |
There was a problem hiding this comment.
In jenkins-x/go-scm, every api call has /rest appended so need to it here
chmouel
requested changes
Jan 27, 2025
zakisk
force-pushed
the
imple-set-client-func-in-bb-server
branch
from
2f9310f to
80f2fb1
Compare
implemented bitbucket server SetClient func, this is part of effort to replace Bitbucket server client library. Signed-off-by: Zaki Shaikh <[email protected]>
zakisk
force-pushed
the
imple-set-client-func-in-bb-server
branch
from
80f2fb1 to
1059efc
Compare
|
/test |
|
/lgtm |
|
/lgtm |
LGTM Vote Breakdown
Votes Summary:
|
![pipelines-as-code[bot]](https://avatars.githubusercontent.com/in/112592?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Pull Request Approved
Approval Status:
- Required Approvals: 1
- Current Approvals: 1
👥 Approved By:
| Reviewer | Permission | Status |
|---|---|---|
| @chmouel | admin |
✅ |
📝 Next Steps
- All required checks must pass
- Branch protection rules apply
- Get a maintainer to use the
/mergecommand to merge the PR
Thank you for your contributions! 🎉
|
/merge |
LGTM Vote Breakdown
Votes Summary:
|
There was a problem hiding this comment.
✅ Pull Request Approved
Approval Status:
- Required Approvals: 1
- Current Approvals: 1
👥 Approved By:
| Reviewer | Permission | Status |
|---|---|---|
| @chmouel | admin |
✅ |
📝 Next Steps
- All required checks must pass
- Branch protection rules apply
- Get a maintainer to use the
/mergecommand to merge the PR
Thank you for your contributions! 🎉
pipelines-as-code
bot
merged commit ed39772
into
openshift-pipelines:main
4 of 5 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
implemented bitbucket server SetClient func, this is part of effort to replace Bitbucket server client library.
Changes
Submitter Checklist
📝 Ensure your commit message is clear and informative. Refer to the How to write a git commit message guide. Include the commit message in the PR body rather than linking to an external site (e.g., Jira ticket).
♽ Run make test lint before submitting a PR to avoid unnecessary CI processing. Consider installing pre-commit and running pre-commit install in the repository root for an efficient workflow.
✨ We use linters to maintain clean and consistent code. Run make lint before submitting a PR. Some linters offer a --fix mode, executable with make fix-linters (ensure markdownlint and golangci-lint are installed).
📖 Document any user-facing features or changes in behavior.
🧪 While 100% coverage isn't required, we encourage unit tests for code changes where possible.
🎁 If feasible, add an end-to-end test. See README for details.
🔎 Address any CI test flakiness before merging, or provide a valid reason to bypass it (e.g., token rate limitations).
If adding a provider feature, fill in the following details:
(update the documentation accordingly)