Bitbucket's API kind of supports REST workflows, but the clearly use it
like an RPC API (the hardcoded schema in PROJECT_API_URL_FORMAT
make it particularly clear)
Details
Details
- Reviewers
zack - Group Reviewers
Reviewers - Commits
- rDLS18b68bd8c789: s/REST( API)?/API/
Diff Detail
Diff Detail
- Repository
- rDLS Listers
- Branch
- master
- Lint
No Linters Available - Unit
No Unit Test Coverage - Build Status
Buildable 21065 Build 32696: Phabricator diff pipeline on jenkins Jenkins console · Jenkins Build 32695: arc lint + arc unit
Event Timeline
Comment Actions
Build is green
Patch application report for D5631 (id=20072)
Rebasing onto 40e1916510...
Current branch diff-target is up to date.
Changes applied before test
commit 18b68bd8c7894933c0fea2a8b7c92d485dd03294 Author: Valentin Lorentz <vlorentz@softwareheritage.org> Date: Tue Apr 27 18:13:09 2021 +0200 s/REST( API)?/API/ Bitbucket's API kind of supports REST workflows, but the clearly use it like an RPC API (the hardcoded schema in `PROJECT_API_URL_FORMAT` make it particularly clear)
See https://jenkins.softwareheritage.org/job/DLS/job/tests-on-diff/270/ for more details.