>-----Original Message----- >From: Ryan Baxter [mailto:[email protected]] >Sent: Tuesday, August 28, 2012 9:06 AM >To: [email protected] >Subject: Re: Reminder About License Headers > >The workspace for the build is kept around though on the Jenkins server, >right?
Yes. >If we see it fail because the RAT plugin is upset we should be able >to go back to the target folder int he workspace on the server and find the >file. > >On Tue, Aug 28, 2012 at 8:14 AM, Franklin, Matthew B. ><[email protected]>wrote: > >> >-----Original Message----- >> >From: Ryan Baxter [mailto:[email protected]] >> >Sent: Tuesday, August 28, 2012 7:26 AM >> >To: [email protected] >> >Subject: Re: Reminder About License Headers >> > >> >When I am doing a release the build fails when RAT detects missing >> >license file. It does not seem to take to long to run when doing the >> >release so I would assume it would not impact the build too much. >> >> It will fail on the first project where too many unapproved headers are >> found (in the case of everything that inherits from the Apache Maven >> project, this is >1 files) >> >> I believe that you will need to manually browse the workspace to find the >> rat.txt for the failing sub-project though. I don't think there is a >> Jenkins plugin for archiving & displaying Rat failures. >> >> > >> >-Ryan >> > >> >On Aug 28, 2012, at 7:13 AM, Stanton Sievers <[email protected]> >wrote: >> > >> >> I have not tried this but it seems possible. >> >> >> >> RAT has a couple maven goals we can run but it is unclear to me if they >> >> will fail the build automatically or if we need extra Jenkins tooling to >> >> read and act on the output. It is also unclear what the cost of running >> RAT >> >> is, i.e., their maven documentation implies it is non-trivial. >> >> >> >> I'll look into this more and will send an update if I get something >> working. >> >> >> >> -Stanton >> >> On Aug 27, 2012 8:56 PM, "Ryan Baxter" <[email protected]> wrote: >> >> >> >>> This is just a reminder for all the developers committing code to >> Shindig, >> >>> we need to make sure that new files have the Apache license header >> >included >> >>> in them. Every time I have gone to do a release the RAT tool catches >> files >> >>> which are missing header files, so please be more cautious. >> >>> >> >>> Stanton do you know if Jenkins could run the RAT plugin in our builds? >> I >> >>> assume it can just wondering if you have tried this. >> >>> >> >>> -Ryan >> >>> >>
