RE: relative path
Hi, I've submitted the issue CONTINUUM-1483, patch is attached. Regards. David. -Message d'origine- De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] Envoyé : vendredi 21 septembre 2007 18:00 À : continuum-dev@maven.apache.org Objet : Re: relative path It isn't too late for 1.1, we're releasing beta-3 and final won't be normally before one month. For your patch, please attach it to an issue. Emmanuel CAUSSE David MTP CAP GEM a écrit : > Hi, > > I send to the list a patch to add better support for SCM providers that > honour the relativePath field in ScmCheckoutResult. > The idea is to add a new field in project because I think it's project > specific and not build specific. This patch allow group builds to work > with SCM like clearcase or SYNERGY (I'll send a scm patch soon for this > one). > > I hope it is not too late for 1.1... > > -- > David Causse > DECLIC - DTE - Génie Logiciel - GCCL > Tél: 04 67 04 79 09 > > > > > > Post-scriptum La Poste > > Ce message est confidentiel. Sous réserve de tout accord conclu par > écrit entre vous et La Poste, son contenu ne représente en aucun cas un > engagement de la part de La Poste. Toute publication, utilisation ou > diffusion, même partielle, doit être autorisée préalablement. Si vous > n'êtes pas destinataire de ce message, merci d'en avertir immédiatement > l'expéditeur. > > Post-scriptum La Poste Ce message est confidentiel. Sous réserve de tout accord conclu par écrit entre vous et La Poste, son contenu ne représente en aucun cas un engagement de la part de La Poste. Toute publication, utilisation ou diffusion, même partielle, doit être autorisée préalablement. Si vous n'êtes pas destinataire de ce message, merci d'en avertir immédiatement l'expéditeur.
Re: "build definition used" on build result
olivier lamy a écrit : Hi, * Yes it's stored in the database with the buildResult (like a clone and add of the buildDefinition). * Yes it is in the email. * It looks we have to store the buildDefinition even if the scm update/checkout failed no, if the build fails in checkout/update, the build def must be hidden in the build result. Emmanuel -- Olivier 2007/9/23, Brett Porter <[EMAIL PROTECTED]>: A couple of questions/issues on this new feature: * is this stored with the build result, or is it referring to what is in the database now? (ie, what happens to the result if the build definition is later removed?) * is it in the email template? (haven't looked yet) * issue: it shows up on builds that are in error as empty: http:// maven.zones.apache.org/continuum/buildResult.action? buildId=23999&projectId=272&projectGroupId=8 Cheers, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Re: build in error fix not working?
Hmm, I'll look at it to fix it definitively Emmanuel Brett Porter a écrit : Hi, Note this build: http://maven.zones.apache.org/continuum/buildResults.action?projectId=272&projectGroupId=8 It is stuck in error - but I thought this was fixed in beta-3? Could it be because it is an error on SCM update that it isn't detected as fixed? - Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Re: "build definition used" on build result
also when it is in progress On 24/09/2007, at 6:50 PM, Emmanuel Venisse wrote: olivier lamy a écrit : Hi, * Yes it's stored in the database with the buildResult (like a clone and add of the buildDefinition). * Yes it is in the email. * It looks we have to store the buildDefinition even if the scm update/checkout failed no, if the build fails in checkout/update, the build def must be hidden in the build result. Emmanuel -- Olivier 2007/9/23, Brett Porter <[EMAIL PROTECTED]>: A couple of questions/issues on this new feature: * is this stored with the build result, or is it referring to what is in the database now? (ie, what happens to the result if the build definition is later removed?) * is it in the email template? (haven't looked yet) * issue: it shows up on builds that are in error as empty: http:// maven.zones.apache.org/continuum/buildResult.action? buildId=23999&projectId=272&projectGroupId=8 Cheers, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Re: "build definition used" on build result
Brett, you want to hide it when it is in progress or it is empty too? If it is empty, it's a bug but I don't want to hide it when the build is started. Emmanuel Brett Porter a écrit : also when it is in progress On 24/09/2007, at 6:50 PM, Emmanuel Venisse wrote: olivier lamy a écrit : Hi, * Yes it's stored in the database with the buildResult (like a clone and add of the buildDefinition). * Yes it is in the email. * It looks we have to store the buildDefinition even if the scm update/checkout failed no, if the build fails in checkout/update, the build def must be hidden in the build result. Emmanuel -- Olivier 2007/9/23, Brett Porter <[EMAIL PROTECTED]>: A couple of questions/issues on this new feature: * is this stored with the build result, or is it referring to what is in the database now? (ie, what happens to the result if the build definition is later removed?) * is it in the email template? (haven't looked yet) * issue: it shows up on builds that are in error as empty: http:// maven.zones.apache.org/continuum/buildResult.action? buildId=23999&projectId=272&projectGroupId=8 Cheers, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Documentation Plan
Hi, Here is the structure of the documentation I'd like to have for 1.1-final. Installation/Upgrade Guides Installation (standalone, webapp, service...) Release Notes Upgrade Administrator's Guides Managing Users and Security Adding Project Group Managing Builders Managing JDKs Managing Profiles Managing Schedules Managing General Configuration (configuration and appearance) Developer's Guides SVN repository structure XML-RPC TO BE DEFINED User's Guides Managing a project Add (maven1, maven2, Ant, Shell), Remove, Edit SCM security hints Managing Build Definitions Managing Notification mail to an address, mail to latest committers, irc, jabber, msn, wagon, alwaysSend... Building a project Release Management Knowledge Base FAQ (sorted by categories, maybe one menu entry by category) Old versions 1.0.x site About videos, I don't know yet where to put them. Maybe a video attached to a page (like Add Maven2 project) instead of a specific videos page in the menu. WDYT? Emmanuel
Re: "build definition used" on build result
It's empty too On 24/09/2007, at 7:30 PM, Emmanuel Venisse wrote: Brett, you want to hide it when it is in progress or it is empty too? If it is empty, it's a bug but I don't want to hide it when the build is started. Emmanuel Brett Porter a écrit : also when it is in progress On 24/09/2007, at 6:50 PM, Emmanuel Venisse wrote: olivier lamy a écrit : Hi, * Yes it's stored in the database with the buildResult (like a clone and add of the buildDefinition). * Yes it is in the email. * It looks we have to store the buildDefinition even if the scm update/checkout failed no, if the build fails in checkout/update, the build def must be hidden in the build result. Emmanuel -- Olivier 2007/9/23, Brett Porter <[EMAIL PROTECTED]>: A couple of questions/issues on this new feature: * is this stored with the build result, or is it referring to what is in the database now? (ie, what happens to the result if the build definition is later removed?) * is it in the email template? (haven't looked yet) * issue: it shows up on builds that are in error as empty: http:// maven.zones.apache.org/continuum/buildResult.action? buildId=23999&projectId=272&projectGroupId=8 Cheers, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/ -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Re: Documentation Plan
For 1.0.3 doc, we'll let it as is but we must remove specific 1.1 doc in it. Emmanuel Emmanuel Venisse a écrit : Hi, Here is the structure of the documentation I'd like to have for 1.1-final. Installation/Upgrade Guides Installation (standalone, webapp, service...) Release Notes Upgrade Administrator's Guides Managing Users and Security Adding Project Group Managing Builders Managing JDKs Managing Profiles Managing Schedules Managing General Configuration (configuration and appearance) Developer's Guides SVN repository structure XML-RPC TO BE DEFINED User's Guides Managing a project Add (maven1, maven2, Ant, Shell), Remove, Edit SCM security hints Managing Build Definitions Managing Notification mail to an address, mail to latest committers, irc, jabber, msn, wagon, alwaysSend... Building a project Release Management Knowledge Base FAQ (sorted by categories, maybe one menu entry by category) Old versions 1.0.x site About videos, I don't know yet where to put them. Maybe a video attached to a page (like Add Maven2 project) instead of a specific videos page in the menu. WDYT? Emmanuel
