Hi,

A simple solution would be for Windows committers (I'm not sure there is any but me) 
would be to use "|git push --no-verify"|

|Anyway Buildbot will remind us with a fail if any new Codenarc issue is pushed
|

|What do you think?|

|TIA
|

|Jacques
|

|
|

Le 25/08/2023 à 19:58, Jacques Le Roux a écrit :
Hi,

While "./gradlew check" works in Linux (locally and Buildbot*). I have a 
problem in Windows (at least Win7).

It does not show "CodeNarc completed: (p1=0; p2=439; p3=4216)" and 
codenarcGroovyScripts fails.

I'm not sure why yet...

Would be great if someone with last Windows could test the same.

TIA

Jacques

* See check step in last build, eg: 
https://ci2.apache.org/#/builders/46/builds/574

Le 22/08/2023 à 09:51, Jacques Le Roux a écrit :
Thanks Gil,

Anyone else with an opinion before I consider it lazy?

TIA

Jacques

Le 18/08/2023 à 14:06, gil.portenseigne a écrit :
Hello Jacques,

Yes it could be a good enhancement to control codenarc check when
pushing.

Thanks,

Gil
On 02/08/23 07:42, Jacques Le Roux wrote:
Hi,

We have set a Git pre-push hook in order to stop pushes with Checkstyle issues.

I propose to do the same for Codenarc.

Currently Buildbot reports Codenarc issues but it's not a blocker.

What do you think ?

Jacques

Reply via email to