[BitbucketServer] com.atlassian.bitbucket.DataStoreException when posting danger output
See original GitHub issueNode v10.6.0. Danger 3.7.20. Danger-swift cloned from master (most recent version).
I am running the following:
export DANGER_FAKE_CI="YEP"
export DANGER_TEST_REPO='repo'
export DANGER_TEST_PR='123'
export DEBUG="*"
danger process danger-swift
Everything works well, and danger is properly executed until the last moment. I even see what danger-swift returns to process, which seems fine (does not seem to be a danger-swift issue):
But just some lines after, when it is doing the post of the “no CHANGELOG entry added” comment to the Bitbucket API it fails with error 500:
Response: {
"errors": [
{
"context": null,
"message": "A database error has occurred.",
"exceptionName": "com.atlassian.bitbucket.DataStoreException"
}
]
}
I was pretty sure that was an issue with my bitbucket configuration, but after testing with curl and using the same POST request, the comment appeared in the PR successfully in all my tests.
Maybe an encoding issue?
I already spent several hours with this, and I run out of ideas. Any insight would be very much welcome. Thanks 😃
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top GitHub Comments
Be wary, danger is just a spare time project for me, over a day is very reasonable for me to get back to you.
However, no, not without writing code I’m afraid.
Not really, but ideally we don’t have an option like that - I mean, bitbucket supports emojis in comments, so I’m not sure why using the API it fails in your case, maybe try check out their API docs to see if there’s some special setting around content types?