I implemented Code Insights result (ESLint report) as parameter to do merge checking and it shows that I do not have any errors of warnings regarding ESLint report, see picture below:
However, it said that one issue prevents me from merging the PR due to 'Report 'ESLint report' has not passed' which exactly strange since I do not have any error or so (Please neglect the other issues preventing me from merging the PR):
Moreover, I did put the correct report key on Project settings
>
Code Insights
console such that:
I wonder if I am missing something here since I followed all the steps shown here: https://confluence.atlassian.com/bitbucketserver/checks-for-merging-pull-requests-776640039.html?_ga=2.137328176.189084255.1594985895-2080399425.1585579922
I am using Bitbucket 7.1.4 here and I could use some help here :)
Steps I've already done:
- Change the Annotations requirements, all gives the same result
- Check the console output on the build and make sure if the report correctly posted
Thanks in advance!
It seems that your code insight post doesn't have a 'result' field on the create report request. Otherwise it would show a "Passed" lozenge in the sidebar of that dialog.
For example, it would look like this:
What is the JSON payload that you are sending to Bitbucket Server? Does it have a 'result' field?
Hi,
thank you for the clear and insightful answer. I have checked the JSON payload and it is accurately missing 'result' field. It might be good to add this as well in here: https://developer.atlassian.com/server/bitbucket/tutorials-and-examples/code-insights-tutorial/ since I follow this really nice tutorial (Perhaps add this 'result' field in order to apply additional 'merge check' based on Code Insights result). In any case, the problem is now solved in my case :)
Kind regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.