Is there a way to configure Bitbucket to show compiler warnings in PRs?

Hakanai

5/21/23, 2:39 AM

A common problem we have at work is people committing code without having noticed that they're increasing the number of compiler warnings.

The ultimate goal is to make warnings errors, but until the count gets to zero, there's no clean way to do it.

We use Bitbucket for the pull request process, so it seems like that would be a fairly sensible place to display the warnings.

We use Jenkins for the build, and it already has a plugin which shows the compiler warnings in a report, but it isn't very visible when doing the PR.

I am also sitting on a Gradle plugin which can generate compiler warning reports without having to go to the build server, in case that will be of any use here.

Is there an integration where we can get the compiler warnings to show up on the Bitbucket PR?

(Note that SonarQube is not a valid answer to this question, as what it detects is a different subset of problems to what the compiler itself detects.)

0 + 0

continuous-integration

jenkins

bitbucket

anx

10/29/22, 3:35 PM

I'll just drop a reference to the [violation-comments-to-stash](https://www.jenkins.io/doc/pipeline/steps/violation-comments-to-stash/) plugin here which I have never used myself, in the hopes that an answer to this question will note whether it is helpful for the described use case.

Hakanai

10/30/22, 6:32 AM

@anx that particular one seems to be the option if you happen to use findbugs, which is an additional layer of checking on top of compilation. In our case, we're using errorprone, which produces normal compiler warnings. I know that some amount of tooling could be used to produce a findbugs report _from_ the compiler output, but that is, of course, work.

Denise Skidmore

12/2/22, 8:53 PM

You could do an approximation of the number of warnings with the number of lines of output from the build. Output the build console to a file, get the number of lines in that file, save that number to another file, and check that file in. (This would make for a pretty dirty history, every CI build would have an extra commit.) Then on next build you can compare numbers and see if it goes up.

Hakanai

12/4/22, 9:33 PM

@DeniseSkidmore it'd be messy because you'd have to do that to all the PR branches as well, but it has one plus that it would automatically track branching. I think the real goal though is to get a big number in front of the reviewers' faces during a PR, though. If it's just knowing whether the number is going up, we can get that from the Jenkins Warnings Plugin (Next Generation).

Denise Skidmore

12/5/22, 1:45 AM

@Hakanai Yes, the ugliness of the "solution" is why I didn't make it an answer.

Denise Skidmore

12/9/22, 6:05 PM

@hakanai you could use an anchored step to reuse between branches.

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: Is there a way to configure Bitbucket to show compiler warnings in PRs?

TH: มีวิธีการกำหนดค่า Bitbucket เพื่อแสดงคำเตือนคอมไพเลอร์ใน PR หรือไม่

RO: Există o modalitate de a configura Bitbucket pentru a afișa avertismentele compilatorului în PR-uri?

RU: Есть ли способ настроить Bitbucket для отображения предупреждений компилятора в PR?

VI: Có cách nào để định cấu hình Bitbucket để hiển thị các cảnh báo của trình biên dịch trong PR không?

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.