db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Leggett <minf...@sharp.fm>
Subject Re: Continuous integration
Date Tue, 22 Nov 2011 12:05:30 GMT
On 22 Nov 2011, at 5:37 AM, Thomas Fox wrote:

> The gump build for torque 4 fails for a long time now. Do we think  
> we need
> a gump build ? If yes, does anybody have hints why the build fails ?  
> If
> not, how do we remove it ?

Gump is good :)

According to the error at the bottom of the gump mail, it looks like  
the rat plugin is complaining about a licensing issue, and I see some  
commits around licensing, so it might fix it:

[INFO] [apache-rat:check {execution: default}]
[INFO] Exclude: velocity.log
[INFO] Exclude: .checkstyle
[INFO] Exclude: derby.log
[INFO]  
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]  
------------------------------------------------------------------------
[INFO] Too many unapproved licenses: 1
[INFO]  
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]  
------------------------------------------------------------------------
[INFO] Total time: 1 minute 8 seconds
[INFO] Finished at: Tue Nov 22 03:33:11 UTC 2011
[INFO] Final Memory: 42M/132M
[INFO]  
------------------------------------------------------------------------

> Then, I'd like to set up a jenkins build for torque 4. The idea  
> would be to
> build all torque components and then run the test project against an
> embeddable database (preferably derby). This will tell people in a
> reasonable time frame if the last commit broke anything. I'd  
> volunteer to
> administer the jenkins build.
>
> As I understand it jenkins is different from gump because gump  
> always takes
> the trunks as dependencies and only runs every day, whereas jenkins  
> takes
> the real dependency versions and runs after every commit.

The purpose of gump is to give early warning of when the trunk of  
project A breaks the trunk of project B. Without gump, you're only  
find out that project A broke project B way later on, when project A  
got released and you tried to use the new version.

That said, a jenkins build will also be useful, as it allows the build  
to be tested in more detail and more often.

Regards,
Graham
--


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


Mime
View raw message