Re: Multiple scheduled builds on the same project...
Dne středa 31. října 2007 Emmanuel Venisse napsal(a): Antonín Faltýnek a écrit : Dne středa 31. října 2007 Eric D. Nielsen napsal(a): I'm a little confused over how multiple build definitiions on different schedules interact within a project. After reading several threads it looks like my understand was correct, yet my installation doesn't seem to behave as expected. I have three schedules set up: Hourly Every four hours Nightly I have four build definitions Hourly: clean test Every four hours: clean integration-test Nightly: clean install Nightly: clean site site:deploy When a SVN commit occurs, the next hourly build shows that it detects the changes and builds. The nightly and four-hourly builds don't seem to respond. I thought that each schedule had its own dirty checker for SCM, so that the fact that their were no changes since the hourly build shouldn't stop these other schedules from running. However when I looked in the continuum working directly, I see only a single checked out project directory, so I wouldn't expect it to think that the project needs to be built So my questions are a) should the different builds function independently of each others updated-ness b) if yes, where should I look to debug this? c) if no, what's the correct configuration to establish my desired build schedules? Thank you. Eric I had same issues Eric with version 1.0.3, then we upgraded to 1.1b3, which enables configuration, that specific build definition should be performed ALWAYS, and that should be used CVS CO instead of CVS UPDATE. With the latest 1.1 beta (1.1-beta-4), you don't need to run a clean build with a checkout. All build definitions are independant and found all changes from other builds since last execution even if the update return nothing. Thats great. This will help very much. Many thanks to whole continuum team. These two features can help you. Also there is issue, that if you have several build definitions (as in your example), then if your nightly clean install fail, but nightly site site:deploy performs successfully, you will se green success icon in project list and you have not good view on project state until you check build results. We'll try to find a solution for this in 1.2, but your 2 nightly builddef clean install + site site:deploy can be rewrite with one builddef clean install site-deploy Some times we had situation, that we need site even if, for example, fail any junit test. So we've divided these to execuions into separate build defs. Tonda
Re: Problem in 1.1-beta-4
Christian Edward Gruber a écrit : Hmm. further to this, it works on my Mac, and doesn't on my OpenBSD box, running jdk 1.5.0. Before I had some problems with hte database not being created, which turned out to be related simply to available file descriptors. At this point, I have pushed every ulimit category to its maximum, and I get no actual errors or problems that wuould indicate why it's not accepting the login. I tried more ways, and explicitly tried bad passwords and bad usernames to ensure that it does, indeed, fail in more obvious ways in those cases. It does. In this case, it take it, accepts the password, but fails to set soemthing somewhere that is necessary for it to determine that the user IS logged in. Maybe it's not creating a session properly? I'm not sure. Can I run continuum such that I get the debug output? I'm sure I can, but I'm not sure what files to edit to do so. Maybe something's showing in the logs. Btu there are no ERROR logs showing at all. Very frustrating. It's probably configuration of the user, but I can't see what, since I've maxed it all out. You can modify log levels in $CONTINUUM_HOME/apps/continuum/webapp/WEB-INF/classes/log4j.xml Emmanuel Christian. On 30-Oct-07, at 4:29 PM, Christian Edward Gruber wrote: Hi, I've unzipped beta4, run it, and it asks to create the admin user. I do that, and it goes to what seems like it should be system configuration, but it requires login. I then attempt to login as admin (which was just created) and for a minute it looks like it was about to succeed, but then returns to the login screen. This is distinct from a bad username/password, which show an error. this just goes there like if you go to any url and you haven't been authenticated. No matter what, whether I login or go elsewhere it just sends me back to the login page. The log doesn't say much - just: 2007-10-30 11:37:45,428 [SocketListener0-0] INFO com.opensymphony.xwork.Action:redback-admin-account - user = UserCredentials[username=admin,fullName=Build User,[EMAIL PROTECTED],password=***,confirmPassword=***] 2007-10-30 11:37:46,123 [SocketListener0-0] INFO com.opensymphony.xwork.interceptor.Interceptor:redbackForceAdminUserInterceptor - Admin user found. No need to configure admin user. 2007-10-30 11:37:47,172 [SocketListener0-0] INFO com.opensymphony.xwork.Action:configuration - baseUrl='http://207.188.87.165:8080/continuum' 2007-10-30 11:38:17,102 [SocketListener0-0] INFO com.opensymphony.xwork.Action:configuration - baseUrl='http://207.188.87.165:8080/continuum' These last two are the results of logging in as admin in the subsequently delivered login screens. Any thoughts? Christian.
Re: Multiple scheduled builds on the same project...
Eric D Nielsen a écrit : With the latest 1.1 beta (1.1-beta-4), you don't need to run a clean build with a checkout. All build definitions are independant and found all changes from other builds since last execution even if the update return nothing. Thanks. I'll update ASAP and see how it goes. We'll try to find a solution for this in 1.2, but your 2 nightly builddef clean install + site site:deploy can be rewrite with one builddef clean install site-deploy I have the same issue as Tonda, I want the site built and deployed, even if the build fails -- for instance I want the new Surefire report and the new Cobertura report to be deployed. (For instance if a cobertura check test or unit test failed, that should be reflected on the site.) I'm almost tempted to add the project multiple times to the project group, but I'm not sure how legit that would be. Ie if I could add the project times. Instance A: With the Unit/Integration Test builds Instance B: Nightly Builds Instance C: Site Builds Of course there's no way of giving a project an alias, or alternate description from whats in the POM, so that would get confusing fast. On the upside, it would also separate the nearly always successful site builds from masking a failed nightly build. I could do the same with three different project groups... all containing the same project... Are any of these options more normal for people's continuum configurations? I don't recommend to add more than one instance of a project (same groupId/artifactId/version) because it can generate some weird result like wrong ordering or wrong dependencies check result. Emmanuel
Re: automate an ant build scripts work in Continuum
Serkan Costu a écrit : Hello, I need your advice about ant with continuum. I have an Ant script; that does some tasks in particular order; 1- Checks-out about 60 projects from the CVS to a local folder in my computer, accordingly to some tag version. 2- Compiles all of the projects and generate .class files of Java resources. 3- Then packages projects as Jars/wars. 4- After that generates an ear file and deploy to the web application server. Is there a way to automate this work by Continuum? I could set-up one ant project in Continuum, but exactly I want to do is; Continuum will just execute my ant script at a certain time and post the resulting output to my mail. I dont want to configure all of my projects one by one. 1- Create your Ant file 2- Add your ant file in your CVS 3- Add a ANT project in Continuum that use the scm url of your Ant file 4- Configure a schedule you want to use 5- Set the build definition to always build (in 1.1-beta-4) and attach the schedule Emmanuel
1.1-beta-3 Commiter build failure notifier Continuum-605
Is this feature enabled on a clean install? What are the steps to configure it? I can't find any documentation in the Administrator guides for this. Currently our committers are not receiving a failure email and they are a developer in the pom. The declared notifiers are receiving emails however. Bryan -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
Continuum Release Process Documentation
I noticed that Continuum provides a Release function. So far I failed located documentation on this function. We are using the Maven Release process and I am exited about the possibility to execute a release from within Continuum. Unfortunately I do not have the time to play with the function and rather would like to see some examples before considering digging into it. Is there any documentation about the Continuum Release function available and ideally a tutorial that walks through a few examples? Andreas
RE: 1.1-beta-3 Commiter build failure notifier Continuum-605
Does the id in the pom have to exactly match the id of the committer? I would hope this is equivalent: SP012456 vs sp012456 From build email: SCM Changes: Changed: SP012456 @ Tue 30 Oct 2007 13:26:00 -0500 In the pom: developer idsp012456/id emailthe address/email /developer -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 10:42 AM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 Do they have their id defined in pom set to their committer id? Do you have changes authors in build results? Emmanuel Madsen,Bryan a écrit : Is this feature enabled on a clean install? What are the steps to configure it? I can't find any documentation in the Administrator guides for this. Currently our committers are not receiving a failure email and they are a developer in the pom. The declared notifiers are receiving emails however. Bryan -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
Re: Continuum Release Process Documentation
Andreas Guther a écrit : I noticed that Continuum provides a Release function. So far I failed located documentation on this function. We are using the Maven Release process and I am exited about the possibility to execute a release from within Continuum. Unfortunately I do not have the time to play with the function and rather would like to see some examples before considering digging into it. Is there any documentation about the Continuum Release function available and ideally a tutorial that walks through a few examples? Not yet but a page will be available in few days. Emmanuel
Re: 1.1-beta-3 Commiter build failure notifier Continuum-605
Do they have their id defined in pom set to their committer id? Do you have changes authors in build results? Emmanuel Madsen,Bryan a écrit : Is this feature enabled on a clean install? What are the steps to configure it? I can't find any documentation in the Administrator guides for this. Currently our committers are not receiving a failure email and they are a developer in the pom. The declared notifiers are receiving emails however. Bryan -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
Re: 1.1-beta-3 Commiter build failure notifier Continuum-605
I mean the notifier configuration (where you set the TO mail address) in the Continuum interface. Emmanuel Madsen,Bryan a écrit : Where do I find that configuration? This is my current config and it is working for notifiers. This is my config in .\installdir\conf\plexus.xml component roleorg.codehaus.plexus.naming.Naming/role implementationorg.codehaus.plexus.naming.DefaultNaming/implementation role-hintdataSources/role-hint configuration resources !-- Mail Session -- resource namemail/Session/name typejavax.mail.Session/type properties property namemail.smtp.host/name valuemail.company.net/value /property property namemail.smtp.port/name value25/value /property ... This is the config in the .\installdir\apps\continuum\webapp\WEB-INF\classes\META-INF\plexus\application.xml !-- | The mail notifier |-- component roleorg.codehaus.plexus.notification.notifier.Notifier/role role-hintmail/role-hint implementationorg.apache.maven.continuum.notification.mail.MailContinuumNotifier/implementation requirements requirement roleorg.codehaus.plexus.velocity.VelocityComponent/role /requirement requirement roleorg.apache.maven.continuum.store.ContinuumStore/role role-hintjdo/role-hint /requirement requirement roleorg.codehaus.plexus.mailsender.MailSender/role /requirement requirement roleorg.apache.maven.continuum.configuration.ConfigurationService/role /requirement requirement roleorg.apache.maven.continuum.Continuum/role /requirement /requirements configuration from-mailbox[EMAIL PROTECTED]/from-mailbox from-nameContinuum 1.1-Beta-3/from-name timestamp-formatEEE d MMM HH:mm:ss Z/timestamp-format includeBuildResulttrue/includeBuildResult alwaysSendtrue/alwaysSend /configuration /component -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 12:48 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 Do you have configured you mail notifier to send to committers too? Emmanuel Madsen,Bryan a écrit : I had the committer update the pom to match the SCM sign-on and they still did not receive an email. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 10:59 AM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 yes, it must match exactly. SP012456 != sp012456 Madsen,Bryan a écrit : Does the id in the pom have to exactly match the id of the committer? I would hope this is equivalent: SP012456 vs sp012456 From build email: SCM Changes: Changed: SP012456 @ Tue 30 Oct 2007 13:26:00 -0500 In the pom: developer idsp012456/id emailthe address/email /developer -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 10:42 AM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 Do they have their id defined in pom set to their committer id? Do you have changes authors in build results? Emmanuel Madsen,Bryan a écrit : Is this feature enabled on a clean install? What are the steps to configure it? I can't find any documentation in the Administrator guides for this. Currently our committers are not receiving a failure email and they are a developer in the pom. The declared notifiers are receiving emails however. Bryan -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024.
RE: 1.1-beta-3 Commiter build failure notifier Continuum-605
I understand now. I never went to that screen since I declare my notifiers in the pom. It is working for me now. Thank you. Is there a way to enable this for the entire box instead of on a per project group basis? That would cut down on my admin time. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 2:20 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 I mean the notifier configuration (where you set the TO mail address) in the Continuum interface. Emmanuel Madsen,Bryan a écrit : Where do I find that configuration? This is my current config and it is working for notifiers. This is my config in .\installdir\conf\plexus.xml component roleorg.codehaus.plexus.naming.Naming/role implementationorg.codehaus.plexus.naming.DefaultNaming/implementation role-hintdataSources/role-hint configuration resources !-- Mail Session -- resource namemail/Session/name typejavax.mail.Session/type properties property namemail.smtp.host/name valuemail.company.net/value /property property namemail.smtp.port/name value25/value /property ... This is the config in the .\installdir\apps\continuum\webapp\WEB-INF\classes\META-INF\plexus\application.xml !-- | The mail notifier |-- component roleorg.codehaus.plexus.notification.notifier.Notifier/role role-hintmail/role-hint implementationorg.apache.maven.continuum.notification.mail.MailContinuumNotifier/implementation requirements requirement roleorg.codehaus.plexus.velocity.VelocityComponent/role /requirement requirement roleorg.apache.maven.continuum.store.ContinuumStore/role role-hintjdo/role-hint /requirement requirement roleorg.codehaus.plexus.mailsender.MailSender/role /requirement requirement roleorg.apache.maven.continuum.configuration.ConfigurationService/role /requirement requirement roleorg.apache.maven.continuum.Continuum/role /requirement /requirements configuration from-mailbox[EMAIL PROTECTED]/from-mailbox from-nameContinuum 1.1-Beta-3/from-name timestamp-formatEEE d MMM HH:mm:ss Z/timestamp-format includeBuildResulttrue/includeBuildResult alwaysSendtrue/alwaysSend /configuration /component -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 12:48 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 Do you have configured you mail notifier to send to committers too? Emmanuel Madsen,Bryan a écrit : I had the committer update the pom to match the SCM sign-on and they still did not receive an email. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 10:59 AM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 yes, it must match exactly. SP012456 != sp012456 Madsen,Bryan a écrit : Does the id in the pom have to exactly match the id of the committer? I would hope this is equivalent: SP012456 vs sp012456 From build email: SCM Changes: Changed: SP012456 @ Tue 30 Oct 2007 13:26:00 -0500 In the pom: developer idsp012456/id emailthe address/email /developer -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 10:42 AM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 Do they have their id defined in pom set to their committer id? Do you have changes authors in build results? Emmanuel Madsen,Bryan a écrit : Is this feature enabled on a clean install? What are the steps to configure it? I can't find any documentation in the Administrator guides for this. Currently our committers are not receiving a failure email and they are a developer in the pom. The declared notifiers are receiving emails however. Bryan -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and
RE: 1.1-beta-3 Commiter build failure notifier Continuum-605
I'm not configuring the notifiers in the Continuum interface. They are all pulled in from the pom. The committer in this scenario is not a notifier in the pom. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 2:20 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 I mean the notifier configuration (where you set the TO mail address) in the Continuum interface. Emmanuel Madsen,Bryan a écrit : Where do I find that configuration? This is my current config and it is working for notifiers. This is my config in .\installdir\conf\plexus.xml component roleorg.codehaus.plexus.naming.Naming/role implementationorg.codehaus.plexus.naming.DefaultNaming/implementation role-hintdataSources/role-hint configuration resources !-- Mail Session -- resource namemail/Session/name typejavax.mail.Session/type properties property namemail.smtp.host/name valuemail.company.net/value /property property namemail.smtp.port/name value25/value /property ... This is the config in the .\installdir\apps\continuum\webapp\WEB-INF\classes\META-INF\plexus\application.xml !-- | The mail notifier |-- component roleorg.codehaus.plexus.notification.notifier.Notifier/role role-hintmail/role-hint implementationorg.apache.maven.continuum.notification.mail.MailContinuumNotifier/implementation requirements requirement roleorg.codehaus.plexus.velocity.VelocityComponent/role /requirement requirement roleorg.apache.maven.continuum.store.ContinuumStore/role role-hintjdo/role-hint /requirement requirement roleorg.codehaus.plexus.mailsender.MailSender/role /requirement requirement roleorg.apache.maven.continuum.configuration.ConfigurationService/role /requirement requirement roleorg.apache.maven.continuum.Continuum/role /requirement /requirements configuration from-mailbox[EMAIL PROTECTED]/from-mailbox from-nameContinuum 1.1-Beta-3/from-name timestamp-formatEEE d MMM HH:mm:ss Z/timestamp-format includeBuildResulttrue/includeBuildResult alwaysSendtrue/alwaysSend /configuration /component -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 12:48 PM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 Do you have configured you mail notifier to send to committers too? Emmanuel Madsen,Bryan a écrit : I had the committer update the pom to match the SCM sign-on and they still did not receive an email. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 10:59 AM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 yes, it must match exactly. SP012456 != sp012456 Madsen,Bryan a écrit : Does the id in the pom have to exactly match the id of the committer? I would hope this is equivalent: SP012456 vs sp012456 From build email: SCM Changes: Changed: SP012456 @ Tue 30 Oct 2007 13:26:00 -0500 In the pom: developer idsp012456/id emailthe address/email /developer -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 31, 2007 10:42 AM To: continuum-users@maven.apache.org Subject: Re: 1.1-beta-3 Commiter build failure notifier Continuum-605 Do they have their id defined in pom set to their committer id? Do you have changes authors in build results? Emmanuel Madsen,Bryan a écrit : Is this feature enabled on a clean install? What are the steps to configure it? I can't find any documentation in the Administrator guides for this. Currently our committers are not receiving a failure email and they are a developer in the pom. The declared notifiers are receiving emails however. Bryan -- CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state
