David Crossley wrote: > Francesco Chicchiriccò wrote: > > David Crossley wrote: > > > > > >Reminder to the Cocoon project: > > > > > >We have a number of Gump builds: > > >See http://svn.apache.org/repos/asf/gump/metadata/project/ > > >for the "cocoon" entries. > > > > > >For example, the output from the vmgump machine is here: > > >http://vmgump.apache.org/gump/public/cocoon3/ > > >and > > >http://vmgump.apache.org/gump/public/cocoon/ for c2.2 > > >(IIRC then cocoon-2.1 is "packaged" rather than built.) > > > > > >The metadata for each Cocoon "project" probably > > >needs some care and attention from us. > > > > Hi David, > > I am not familiar with Gump at all, but at least for Cocoon 3 [1] and > > Cocoon 2.1 [2] we have Jenkins jobs defined. > > Gump is very different. See Stefan's message below. > > I reckon that both are useful in different ways.
This is the description from their home page: "Gump is unique in that it builds and compiles software against the latest development versions of those projects. This allows gump to detect potentially incompatible changes to that software just a few hours after those changes are checked into the version control system." and from their Board reports: "Apache Gump is a cross-project continuous integration server. Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate." -David > > I don't think we still need Gump, at least for C3 and C2.1 (and we might > > define a job on Jenkins for C2.2 as well), right? > > > > WDYT? Should we safely remove cocoon entries from Gump? How could this > > be done? > > > > Regards. > > > > [1] https://builds.apache.org/job/Cocoon%203.0/ > > [2] https://builds.apache.org/job/Cocoon%202.1.X/ > > > > >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 > > > > -- > > Francesco Chicchiriccò > > > > ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member > > http://people.apache.org/~ilgrosso/ > >
