[jira] Commented: (CONTINUUM-509) Ability to process scheduled builds the same as forced builds.
[ http://jira.codehaus.org/browse/CONTINUUM-509?page=comments#action_81217 ] Brill Pappin commented on CONTINUUM-509: Have another argument for this ability: with the one component per module style of Maven, modules that have been stable but have unstable dependent modules can get out of sync. e.g. two source modules, one nobody spends time in and another that is being reworked all the time. Since the "stable" module doesn't change, it will never be built and the changes that broken it from module 2 will not be detected. For a fix: - Dependency change checking. - scheduled force build. I don't care which way I have to do it, but some way would be helpful. > Ability to process scheduled builds the same as forced builds. > -- > > Key: CONTINUUM-509 > URL: http://jira.codehaus.org/browse/CONTINUUM-509 > Project: Continuum > Issue Type: Improvement > Components: Core system >Affects Versions: 1.0.2 >Reporter: Shinobu Kawai >Priority: Minor > Fix For: 1.1 > > > It would be great if you could configure a build schedule to act like a > forced build on the scheduled build. > The use case for this is when you have two build definitions: > - One will be set to default for a forced, light build. For example, install > the artifact. > - Another will be set to a scheduled, heavy build. For example, deploy the > artifact and the project site. > If the default build is triggered, the other build will be skipped since > nothing has been updated since the forced build. And we do not want to do > heavy stuff in the default build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-509) Ability to process scheduled builds the same as forced builds.
[ http://jira.codehaus.org/browse/CONTINUUM-509?page=comments#action_78207 ] Wilfred Springer commented on CONTINUUM-509: +1 I would also love to have the ability to force the site build. In fact, it seems that most of us want this because we either run a different lifecycle (site build vs. software build) or let it run up to different phases (test vs. integration-test). IMHO, it makes sense that Continuum would be able to understand that having a build that ran up to the test phase didn't include the integration-test phase; as a result, Continuum should be able to recognize that a midnight integration test still requires the build to run, even if the test build already ran and there were no changes in the repository. The same applies for the difference between a site build and a software build. You would expect Continuum would be able to see the difference between the different lifecycles. Because of that, it should simply be running the nightly site build, even if the software build already completed successfully during the day. > Ability to process scheduled builds the same as forced builds. > -- > > Key: CONTINUUM-509 > URL: http://jira.codehaus.org/browse/CONTINUUM-509 > Project: Continuum > Issue Type: Improvement > Components: Core system >Affects Versions: 1.0.2 >Reporter: Shinobu Kawai >Priority: Minor > Fix For: 1.1 > > > It would be great if you could configure a build schedule to act like a > forced build on the scheduled build. > The use case for this is when you have two build definitions: > - One will be set to default for a forced, light build. For example, install > the artifact. > - Another will be set to a scheduled, heavy build. For example, deploy the > artifact and the project site. > If the default build is triggered, the other build will be skipped since > nothing has been updated since the forced build. And we do not want to do > heavy stuff in the default build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-509) Ability to process scheduled builds the same as forced builds.
[ http://jira.codehaus.org/browse/CONTINUUM-509?page=comments#action_78232 ] Okke Harsta commented on CONTINUUM-509: --- + 1 For us it would be already a great (really great) help just to have a checkbox "Force build" or "Build always" as an attribute of a build defintion. The priority minor does not correctly reflect our need for such a feature. > Ability to process scheduled builds the same as forced builds. > -- > > Key: CONTINUUM-509 > URL: http://jira.codehaus.org/browse/CONTINUUM-509 > Project: Continuum > Issue Type: Improvement > Components: Core system >Affects Versions: 1.0.2 >Reporter: Shinobu Kawai >Priority: Minor > Fix For: 1.1 > > > It would be great if you could configure a build schedule to act like a > forced build on the scheduled build. > The use case for this is when you have two build definitions: > - One will be set to default for a forced, light build. For example, install > the artifact. > - Another will be set to a scheduled, heavy build. For example, deploy the > artifact and the project site. > If the default build is triggered, the other build will be skipped since > nothing has been updated since the forced build. And we do not want to do > heavy stuff in the default build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-509) Ability to process scheduled builds the same as forced builds.
[ http://jira.codehaus.org/browse/CONTINUUM-509?page=comments#action_72705 ] Brill Pappin commented on CONTINUUM-509: We could really use this feature *right now (need it yesterday)* Because we only do a site build/publish build once a day, it must run even if one of the hourly builds have already updated the source. Currently we're forced to run the nightly build and deployment in a cron outside of Continuum. > Ability to process scheduled builds the same as forced builds. > -- > > Key: CONTINUUM-509 > URL: http://jira.codehaus.org/browse/CONTINUUM-509 > Project: Continuum > Issue Type: Improvement > Components: Core system >Affects Versions: 1.0.2 >Reporter: Shinobu Kawai >Priority: Minor > Fix For: 1.1 > > > It would be great if you could configure a build schedule to act like a > forced build on the scheduled build. > The use case for this is when you have two build definitions: > - One will be set to default for a forced, light build. For example, install > the artifact. > - Another will be set to a scheduled, heavy build. For example, deploy the > artifact and the project site. > If the default build is triggered, the other build will be skipped since > nothing has been updated since the forced build. And we do not want to do > heavy stuff in the default build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-509) Ability to process scheduled builds the same as forced builds.
[ http://jira.codehaus.org/browse/CONTINUUM-509?page=comments#action_68720 ] Sharmarke Aden commented on CONTINUUM-509: -- The priority of this issue shouldn't be "minor" as it is an essential feature of a Continuous Integration Systems. I'd like to fix this bug and would appreciate it if anyone give me a hint as to what components I need to look at to resolve the bug. Thanks. > Ability to process scheduled builds the same as forced builds. > -- > > Key: CONTINUUM-509 > URL: http://jira.codehaus.org/browse/CONTINUUM-509 > Project: Continuum > Type: Improvement > Components: Core system > Versions: 1.0.2 > Reporter: Shinobu Kawai > Priority: Minor > Fix For: 1.1 > > > It would be great if you could configure a build schedule to act like a > forced build on the scheduled build. > The use case for this is when you have two build definitions: > - One will be set to default for a forced, light build. For example, install > the artifact. > - Another will be set to a scheduled, heavy build. For example, deploy the > artifact and the project site. > If the default build is triggered, the other build will be skipped since > nothing has been updated since the forced build. And we do not want to do > heavy stuff in the default build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-509) Ability to process scheduled builds the same as forced builds.
[ http://jira.codehaus.org/browse/CONTINUUM-509?page=comments#action_66245 ] toli kuznets commented on CONTINUUM-509: Having an ability to always execute a scheduled build is very useful, regardless of whether or not there were any code changes checked in. This is a great way to uncover race conditions - the more often the tests run, the safer you feel. Isn't that the whole idea of unit testing? the hourly/nightly builds are always running and always testing, even if you are out on vacation. So I strongly believe that being able to always have the build run even if there were no changes is a core part of Continuum functionality > Ability to process scheduled builds the same as forced builds. > -- > > Key: CONTINUUM-509 > URL: http://jira.codehaus.org/browse/CONTINUUM-509 > Project: Continuum > Type: Improvement > Components: Core system > Versions: 1.0.2 > Reporter: Shinobu Kawai > Priority: Minor > Fix For: 1.1 > > > It would be great if you could configure a build schedule to act like a > forced build on the scheduled build. > The use case for this is when you have two build definitions: > - One will be set to default for a forced, light build. For example, install > the artifact. > - Another will be set to a scheduled, heavy build. For example, deploy the > artifact and the project site. > If the default build is triggered, the other build will be skipped since > nothing has been updated since the forced build. And we do not want to do > heavy stuff in the default build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
