On 20/06/2019 13:30, sebb wrote:
On Thu, 20 Jun 2019 at 13:06, Alex Herbert <alex.d.herb...@gmail.com> wrote:
On 20/06/2019 12:45, Apache Jenkins Server wrote:
The Apache Jenkins build system has built commons-rng (build #361)

Status: Still Failing

Check console output at https://builds.apache.org/job/commons-rng/361/ to view 
the results.
Jenkins is failing the RAT check on JDK 1.6 with apparently 332
unapproved licences.

It passes on the JDK 1.9 build.

A vanilla git clone of the repo builds fine with this many files
included by rat:

[INFO] 81 implicit excludes (use -debug for more details).
[INFO] 19 explicit excludes (use -debug for more details).
[INFO] 138 resources included (use -debug for more details)

The same log output from Jenkins reads:

[INFO] 80 implicit excludes (use -debug for more details).
[INFO] 19 explicit excludes (use -debug for more details).
[INFO] 627 resources included (use -debug for more details)

The last successful build on Jenkins reads:

[INFO] 81 implicit excludes (use -debug for more details).
[INFO] 19 explicit excludes (use -debug for more details).
[INFO] 136 resources included (use -debug for more details)

Since this build I added two files so that matches with the 138
resources in the vanilla build.

So for some reason the latest builds have a lot more files in the
working directory.

Is there a way to see the working directory that Jenkins is using and
the rat.txt report? There is something that should not be there.
https://builds.apache.org/job/commons-rng/ws/

However AFAIK this will be updated for each build, so you may need to
suspend builds temporarily.
Thanks. The rat.txt shows that there is now the following directory

.repository

It belongs to Maven and contains poms, jars and sha1 hashes.

I'll add it to .gitignore.



Is this something for INFRA to fix?
Unlikely, most likely the job does not tidy up properly.

Alex


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to