Re: Build marked unstable due to Sonar, but it's there and green

2020-02-18 Thread Bertrand Delacretaz
Hi, On Fri, Jan 31, 2020 at 3:32 PM Bertrand Delacretaz wrote: > The build at [1] is marked unstable "due to missing SonarCloud > onboarding"... FWIW, I have now changed [1] this potentially misleading message to say ""Marking build unstable due to mvn sonar:sonar failing" as we don't know the e

Re: Build marked unstable due to Sonar, but it's there and green

2020-02-03 Thread Robert Munteanu
Hi Betrand, On Fri, 2020-01-31 at 15:37 +0100, Bertrand Delacretaz wrote: > On Fri, Jan 31, 2020 at 3:32 PM Bertrand Delacretaz > wrote: > > ...The Jenkins code at [3] outputs this "unstable" message > > regardless of > > what fails in the Maven build, we might need to provide more > > details >

Re: Build marked unstable due to Sonar, but it's there and green

2020-01-31 Thread Bertrand Delacretaz
On Fri, Jan 31, 2020 at 3:32 PM Bertrand Delacretaz wrote: > ...The Jenkins code at [3] outputs this "unstable" message regardless of > what fails in the Maven build, we might need to provide more details > there on what failed?.. ...in the meantime I read [4] and apparently getting the Maven err

Build marked unstable due to Sonar, but it's there and green

2020-01-31 Thread Bertrand Delacretaz
Hi, The build at [1] is marked unstable "due to missing SonarCloud onboarding", but if I look in Sonar at [2] that module is there and says "passed". The Jenkins code at [3] outputs this "unstable" message regardless of what fails in the Maven build, we might need to provide more details there on