Re: Your Gump Build(s)

[Stefan Bodewig]

On 2013-07-23, David Crossley wrote:

> Yes, if possible then Apache Forrest would like to continue.

TBH, I had expected that :-)

Noted.

> So Forrest could re-jig ours to use the up-to-the-minute
> version of whatever Gump does provide, and then use our
> local copies for the rest.

I think that should work.  We'll very likely not build Cocoon anymore,
but at least the XML stack, Ant, FOP and Batik will be available.

Stefan

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

Re: Your Gump Build(s)

[David Crossley]

Stefan Bodewig wrote:
> Dear Community
> 
> Apache Gump builds some of your projects and it is quite possible you
> don't know or have by now forgotten about it.
> 
> More than half a year ago a technical problem has forced us to turn off
> emails on build failures as we would have been sending out lots of false
> alarms.
> 
> Before we re-enable emails we'd like to know whether you are still
> interested in the service Gump provides, so please tell us. :-)

Sorry for the late reply.

Yes, if possible then Apache Forrest would like to continue.

Forrest is a consumer of many other projects.
Our gump metadata have been configured to utilise our local
copy of some of those. For others we use the gump-built one.

Gump has a special copy of Cocoon-2.1 but we could change to
use the abovementioned approach.

So Forrest could re-jig ours to use the up-to-the-minute
version of whatever Gump does provide, and then use our
local copies for the rest.

-David

> Metadata for many projects have been neglected for a long time and it is
> quite possible they'd need some love for results to be meaningful.  All
> Apache committers have write access to Gump's metadata.
> 
> In case you don't know what this Gump stuff is about:
> 
> Apache Gump builds the full stack of the latest commits of software in
> order to ensure integrity over releases.  Build failures surface API
> discontinuities between projects before they impact releases, and Gump's
> e-mail notifications hope to promote the conversations between teams to
> resolve those discontinuities.
> 
> When responding to this mail please shorten the CC list as appropriate.
> 
> Cheers
> 
> Stefan
> 
>  on behalf of the Gump PMC

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

Re: Your Gump Build(s)

[Stefan Bodewig]

On 2013-07-04, Vincent Hennebert wrote:

> At XML Graphics we still use Gump for CI, so please re-enable email
> notification for the following projects: xmlgraphics-commons,
> xml-batik, xml-fop.

Noted, thanks.

Right now we'll need to make some adjustments and weight our options
before going forward.

Thanks

Stefan

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

Re: Your Gump Build(s)

[Stefan Bodewig]

On 2013-06-25, Michael Glavassevich wrote:

> Stefan Bodewig  wrote on 06/25/2013 03:59:56 AM:

>> No email doesn't mean no downstream has been broken.

> True, but if that occurred I'd expect the broken project (who would have
> been notified by Gump) would at some point open a discussion with us about
> the problem we caused

Yes, that's the idea :-)

> and I don't recall the last time that happened either, if it ever
> did. That's more of a statement about the stability of Xerces and
> Xalan than anything else. The rate of change is nowhere near like it
> was 10 years ago.

Coming out of Ant land myself I know pretty well what you are talking
about.

Thanks

Stefan

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

Re: Your Gump Build(s)

[Vincent Hennebert]

Hi Stefan,

At XML Graphics we still use Gump for CI, so please re-enable email
notification for the following projects: xmlgraphics-commons, xml-batik,
xml-fop.

Thanks,
Vincent


On 24/06/13 15:20, Stefan Bodewig wrote:
> Dear Community
> 
> Apache Gump builds some of your projects and it is quite possible you
> don't know or have by now forgotten about it.
> 
> More than half a year ago a technical problem has forced us to turn off
> emails on build failures as we would have been sending out lots of false
> alarms.
> 
> Before we re-enable emails we'd like to know whether you are still
> interested in the service Gump provides, so please tell us. :-)
> 
> Metadata for many projects have been neglected for a long time and it is
> quite possible they'd need some love for results to be meaningful.  All
> Apache committers have write access to Gump's metadata.
> 
> In case you don't know what this Gump stuff is about:
> 
> Apache Gump builds the full stack of the latest commits of software in
> order to ensure integrity over releases.  Build failures surface API
> discontinuities between projects before they impact releases, and Gump's
> e-mail notifications hope to promote the conversations between teams to
> resolve those discontinuities.
> 
> When responding to this mail please shorten the CC list as appropriate.
> 
> Cheers
> 
> Stefan
> 
>  on behalf of the Gump PMC
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: general-h...@xmlgraphics.apache.org
> 

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

Re: Your Gump Build(s)

[Michael Glavassevich]

Stefan Bodewig  wrote on 06/25/2013 03:59:56 AM:

> On 2013-06-24, Michael Glavassevich wrote:
> 
> > Projects like Xerces and Xalan are near the bottom of the food chain. 
I've
> > always thought the projects higher up in the stack got more value from
> > Gump.
> 
> Unless Xalan or Xerces breaks something :-) In this case you get the
> early warning by other project's builds failing.  That's why monitoring
> your dependee's builds is a crucial part of getting anything useful out
> of Gump.

I don't think we ever did that.

> Shall I translate this to "we're not too eager on keeping our Gump
> builds"?

I'd translate that to "we don't get much out of it but others might".

> > I don't remember the last time we got a notification for a legitimate
> > build failure at our level. It was a rather rare occurrence, even
> > while e-mail notifications were still being sent out.
> 
> Well, yes, see above.  No email doesn't mean no downstream has been
> broken.

True, but if that occurred I'd expect the broken project (who would have 
been notified by Gump) would at some point open a discussion with us about 
the problem we caused and I don't recall the last time that happened 
either, if it ever did. That's more of a statement about the stability of 
Xerces and Xalan than anything else. The rate of change is nowhere near 
like it was 10 years ago.

> Thanks
> 
> Stefan
> 
> -
> To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org
> For additional commands, e-mail: j-dev-h...@xerces.apache.org

Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: mrgla...@ca.ibm.com
E-mail: mrgla...@apache.org


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

Re: Your Gump Build(s)

[Stefan Bodewig]

On 2013-06-24, Michael Glavassevich wrote:

> Projects like Xerces and Xalan are near the bottom of the food chain. I've
> always thought the projects higher up in the stack got more value from
> Gump.

Unless Xalan or Xerces breaks something :-) In this case you get the
early warning by other project's builds failing.  That's why monitoring
your dependee's builds is a crucial part of getting anything useful out
of Gump.

Shall I translate this to "we're not too eager on keeping our Gump
builds"?

> I don't remember the last time we got a notification for a legitimate
> build failure at our level. It was a rather rare occurrence, even
> while e-mail notifications were still being sent out.

Well, yes, see above.  No email doesn't mean no downstream has been
broken.

Thanks

Stefan

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

Re: Your Gump Build(s)

[Stefan Bodewig]

On 2013-06-24, Nick Burch wrote:

> On Mon, 24 Jun 2013, Stefan Bodewig wrote:

>> Before we re-enable emails we'd like to know whether you are still
>> interested in the service Gump provides, so please tell us. :-)

> We are.

Noted, thanks.

> Is there any easy way to check if gump is currently happy with our
> build before we turn emails back on?

For some strange reason we don't seem to have a direct navigation from
module to project - at least I don't find it.  Use
 and
similar links by replacing "poi-ooxml-deps" with your project name from
the poi Gump descriptor.

Right now thinks look pretty good, I think

has all POI Gump builds as dependees.

Of your downstream dependencies Tika's parser project currently fails
but I don't think it is related to POI.

Stefan

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

Re: Your Gump Build(s)

[Stefan Bodewig]

On 2013-06-24, Mark Thomas wrote:

> On 24/06/2013 14:20, Stefan Bodewig wrote:

>> Before we re-enable emails we'd like to know whether you are still
>> interested in the service Gump provides, so please tell us. :-)

> Yes please!

Noted, thanks.

> As an aside, there were (and probably still are) a number of projects
> with dependencies on very old (and no longer supported) Tomcat versions.
> It would be good to get those cleaned up. Finding the time to do that
> has been on my TODO list for a while.

It is pretty likely we'll end up with a smaller set of projects after
this poll.  Tomcat 4 is used by Ant - and only by Ant AFAICT - for the
deprecated jcpc task.  I don't see any project using Tomcat 5.x or 6.x
on first glance.

Stefan

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

Re: Your Gump Build(s)

[Stefan Bodewig]

On 2013-06-24, Dominik Psenner wrote:

> Talking for log4net, yes. We use Gump.

and does it help log4net? (feeling kind of strange about juggling hats
right now :-)

IMHO log4net uses Gump as nightly build system and not because of its
"Gumpness".  log4net doesn't have any dependencies apart from the CLR
and we Gump folks have never figured out how to make "replace a
dependency with the one we've just built" properly anyway.

> Bringing up the discussion again. Is it possible to publish nightly builds
> using gump? It has been requested several times and it would be a lot easier
> than setting up/migrate to a second build system.

I'm not sure whether there is NAnt installed on any Jenkins slave, but
at least you'd get Windows nodes with "real" .NET platforms.  A start
might by to run MSBuild on one of the solution files.

Philosphically Gump isn't suitable as a nightly build system as you
don't know what you are building against in general - somebody attacking
the VCS of project X could easily undermine nightly builds of all
projects dependending on X.

Stefan

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

Re: Your Gump Build(s)

[Michael Glavassevich]

Hi,

Projects like Xerces and Xalan are near the bottom of the food chain. I've 
always thought the projects higher up in the stack got more value from 
Gump. I don't remember the last time we got a notification for a 
legitimate build failure at our level. It was a rather rare occurrence, 
even while e-mail notifications were still being sent out.

Thanks.

Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: mrgla...@ca.ibm.com
E-mail: mrgla...@apache.org

Stefan Bodewig  wrote on 06/24/2013 09:20:47 AM:

> Dear Community
> 
> Apache Gump builds some of your projects and it is quite possible you
> don't know or have by now forgotten about it.
> 
> More than half a year ago a technical problem has forced us to turn off
> emails on build failures as we would have been sending out lots of false
> alarms.
> 
> Before we re-enable emails we'd like to know whether you are still
> interested in the service Gump provides, so please tell us. :-)
> 
> Metadata for many projects have been neglected for a long time and it is
> quite possible they'd need some love for results to be meaningful.  All
> Apache committers have write access to Gump's metadata.
> 
> In case you don't know what this Gump stuff is about:
> 
> Apache Gump builds the full stack of the latest commits of software in
> order to ensure integrity over releases.  Build failures surface API
> discontinuities between projects before they impact releases, and Gump's
> e-mail notifications hope to promote the conversations between teams to
> resolve those discontinuities.
> 
> When responding to this mail please shorten the CC list as appropriate.
> 
> Cheers
> 
> Stefan
> 
>  on behalf of the Gump PMC
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
> For additional commands, e-mail: dev-h...@xalan.apache.org


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

Re: Your Gump Build(s)

[sebb]

On 24 June 2013 14:58, Dominik Psenner  wrote:
> Hey Stefan,
>
> Talking for log4net, yes. We use Gump.
>
> See: http://vmgump.apache.org/gump/public/logging-log4net/logging-log4net/
>
> Bringing up the discussion again. Is it possible to publish nightly builds
> using gump? It has been requested several times and it would be a lot easier
> than setting up/migrate to a second build system.

Sorry, but I don't think that's a good idea.

Snapshot builds should be done using the same dependencies as the
release build would use.

Also publishing builds will increase the Gump run time, which is
already very long.

> Cheers
>
>>-Ursprüngliche Nachricht-
>>Von: Stefan Bodewig [mailto:bode...@apache.org]
>>Gesendet: Montag, 24. Juni 2013 15:21
>>An: d...@apr.apache.org; d...@activemq.apache.org; d...@ant.apache.org;
>>d...@camel.apache.org; d...@cocoon.apache.org;
>>d...@commons.apache.org; d...@creadur.apache.org;
>>d...@directory.apache.org; d...@forrest.apache.org; d...@hc.apache.org;
>>d...@httpd.apache.org; d...@jmeter.apache.org;
>>gene...@james.apache.org; d...@lenya.apache.org;
>>gene...@logging.apache.org; d...@lucene.apache.org; d...@poi.apache.org;
>>bridges-...@portals.apache.org; pluto-...@portals.apache.org;
>>d...@tapestry.apache.org; d...@tika.apache.org; d...@tomcat.apache.org;
>>d...@turbine.apache.org; d...@velocity.apache.org; d...@ws.apache.org;
>>gene...@xmlgraphics.apache.org; gene...@xerces.apache.org;
>>d...@xalan.apache.org; d...@pdfbox.apache.org
>>Cc: general@gump.apache.org
>>Betreff: Your Gump Build(s)
>>
>>Dear Community
>>
>>Apache Gump builds some of your projects and it is quite possible you
>>don't know or have by now forgotten about it.
>>
>>More than half a year ago a technical problem has forced us to turn off
>>emails on build failures as we would have been sending out lots of false
>>alarms.
>>
>>Before we re-enable emails we'd like to know whether you are still
>>interested in the service Gump provides, so please tell us. :-)
>>
>>Metadata for many projects have been neglected for a long time and it is
>>quite possible they'd need some love for results to be meaningful.  All
>>Apache committers have write access to Gump's metadata.
>>
>>In case you don't know what this Gump stuff is about:
>>
>>Apache Gump builds the full stack of the latest commits of software in
>>order to ensure integrity over releases.  Build failures surface API
>>discontinuities between projects before they impact releases, and Gump's
>>e-mail notifications hope to promote the conversations between teams to
>>resolve those discontinuities.
>>
>>When responding to this mail please shorten the CC list as appropriate.
>>
>>Cheers
>>
>>Stefan
>>
>> on behalf of the Gump PMC
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
> For additional commands, e-mail: general-h...@gump.apache.org
>

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

Re: Your Gump Build(s)

[Nick Burch]

On Mon, 24 Jun 2013, Stefan Bodewig wrote:
Apache Gump builds some of your projects and it is quite possible you 
don't know or have by now forgotten about it.


I think we had noticed it being quieter than normal!

Before we re-enable emails we'd like to know whether you are still 
interested in the service Gump provides, so please tell us. :-)


We are. Is there any easy way to check if gump is currently happy with our 
build before we turn emails back on?


Nick

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

Re: Your Gump Build(s)

[Mark Thomas]

On 24/06/2013 14:20, Stefan Bodewig wrote:
> Dear Community
> 
> Apache Gump builds some of your projects and it is quite possible you
> don't know or have by now forgotten about it.
> 
> More than half a year ago a technical problem has forced us to turn off
> emails on build failures as we would have been sending out lots of false
> alarms.
> 
> Before we re-enable emails we'd like to know whether you are still
> interested in the service Gump provides, so please tell us. :-)

Yes please!

As an aside, there were (and probably still are) a number of projects
with dependencies on very old (and no longer supported) Tomcat versions.
It would be good to get those cleaned up. Finding the time to do that
has been on my TODO list for a while.

Mark

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