RE: Forced builds
Thanks for the good news. -Original Message- From: Christian Edward Gruber [mailto:[EMAIL PROTECTED] Sent: Monday, November 20, 2006 4:20 PM To: continuum-users@maven.apache.org Subject: Re: Forced builds Complex projects with lots of external dependencies, particularly dependencies on external snapshot versions of code. Also, we run a nightly integration test against external systems (we only run Unit tests on the normal non-forced build, or they'd take too long), and changes in the underlying database, or changes in the test data would cause test failures that need to be identified. I feel that this attitude Wayne cites (no delta, no build) is quite common, but makes a lot of assumptions about one's environment, and I think is unrealistic in many large-scale development environments. It may be perfectly reasonable in Wayne's context, or many others, mind you. But especially in large, highly interconnected development environments (like a big bank), you want to have relevant information communicated between groups and architectural layers as quickly as possible to identify any defect or change in assumptions, so a set of system/integration tests run on a schedule (hourly, daily, whatever) are entirely appropriate, and may identify defects regardless of code-changes. The good news, Alexander, is that 1.1 will have such a feature (Jesse committed this a few weeks ago - not so much a forced build, but a fresh cut of the workspace, which has the same effect), so when 1.1 is released you can do exactly this. I frankly run a trunk build, because for all its little instabilities, it's so feature-superior to 1.0.3 that for me it's worth the hassle. One of the main gets for our organization is the forced scheduled build. Continuum (1.1-SNAPSHOT) has proven to be quite handy at decreasing latency in communication of API changes, underlying business cases (test data), or other issues by forcing the issues faster, when used this way... even when humans forget to talk to humans. Cheers, Christian. Wayne Fay wrote: No changes in code == no reason to build, right? I don't see the usefulness of this enhancement, personally... Unless of course some PHB has laid down a build all projects every 3 hrs kind of mandate in your organization. Wayne On 11/20/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: Not yet, why? Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : Is it possible to have Continuum force build every n hours even if the code in the source code repository hasn't changed? This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1] -- *christian** gruber + process coach and architect* *Israfil Consulting Services Corporation* *email** [EMAIL PROTECTED] + bus 905.640.1119 + mob 416.998.6023*
Forced builds
Is it possible to have Continuum force build every n hours even if the code in the source code repository hasn't changed? This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Re: Forced builds
No changes in code == no reason to build, right? I don't see the usefulness of this enhancement, personally... Unless of course some PHB has laid down a build all projects every 3 hrs kind of mandate in your organization. Wayne On 11/20/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: Not yet, why? Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : Is it possible to have Continuum force build every n hours even if the code in the source code repository hasn't changed? This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
RE: Forced builds
Well, for example, if a Maven dependency changes on the Maven repository but the version stays the same, the pom.xml will not change, but we will need to rebuild to get the new dependency into the build. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Monday, November 20, 2006 2:22 PM To: continuum-users@maven.apache.org Subject: Re: Forced builds Not yet, why? Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : Is it possible to have Continuum force build every n hours even if the code in the source code repository hasn't changed? This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
RE: Forced builds
Well, if dependencies change but the pom.xml's do not change, we would need to do a new build, like if a version of some dependency stays the same but the artifact changes at the Maven repository. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Monday, November 20, 2006 2:31 PM To: continuum-users@maven.apache.org Subject: Re: Forced builds No changes in code == no reason to build, right? I don't see the usefulness of this enhancement, personally... Unless of course some PHB has laid down a build all projects every 3 hrs kind of mandate in your organization. Wayne On 11/20/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: Not yet, why? Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : Is it possible to have Continuum force build every n hours even if the code in the source code repository hasn't changed? This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Re: Forced builds
Not yet, why? Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : Is it possible to have Continuum force build every n hours even if the code in the source code repository hasn't changed? This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Re: Forced builds
This would be useful if you are reverse engineering the database and there is a database change. No cvs change but a table got modified. -- tom
Re: Forced builds
Complex projects with lots of external dependencies, particularly dependencies on external snapshot versions of code. Also, we run a nightly integration test against external systems (we only run Unit tests on the normal non-forced build, or they'd take too long), and changes in the underlying database, or changes in the test data would cause test failures that need to be identified. I feel that this attitude Wayne cites (no delta, no build) is quite common, but makes a lot of assumptions about one's environment, and I think is unrealistic in many large-scale development environments. It may be perfectly reasonable in Wayne's context, or many others, mind you. But especially in large, highly interconnected development environments (like a big bank), you want to have relevant information communicated between groups and architectural layers as quickly as possible to identify any defect or change in assumptions, so a set of system/integration tests run on a schedule (hourly, daily, whatever) are entirely appropriate, and may identify defects regardless of code-changes. The good news, Alexander, is that 1.1 will have such a feature (Jesse committed this a few weeks ago - not so much a forced build, but a fresh cut of the workspace, which has the same effect), so when 1.1 is released you can do exactly this. I frankly run a trunk build, because for all its little instabilities, it's so feature-superior to 1.0.3 that for me it's worth the hassle. One of the main gets for our organization is the forced scheduled build. Continuum (1.1-SNAPSHOT) has proven to be quite handy at decreasing latency in communication of API changes, underlying business cases (test data), or other issues by forcing the issues faster, when used this way... even when humans forget to talk to humans. Cheers, Christian. Wayne Fay wrote: No changes in code == no reason to build, right? I don't see the usefulness of this enhancement, personally... Unless of course some PHB has laid down a build all projects every 3 hrs kind of mandate in your organization. Wayne On 11/20/06, Emmanuel Venisse [EMAIL PROTECTED] wrote: Not yet, why? Emmanuel Morgovsky, Alexander (US - Glen Mills) a écrit : Is it possible to have Continuum force build every n hours even if the code in the source code repository hasn't changed? This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1] -- *christian** gruber + process coach and architect* *Israfil Consulting Services Corporation* *email** [EMAIL PROTECTED] + bus 905.640.1119 + mob 416.998.6023*
