continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Lamy (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (CONTINUUM-1901) New Feature: ability to select alternate build definition when only change is an updated dependency
Date Sat, 06 Dec 2008 22:46:19 GMT

     [ http://jira.codehaus.org/browse/CONTINUUM-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Olivier Lamy updated CONTINUUM-1901:
------------------------------------

    Fix Version/s: 1.3.x

> New Feature: ability to select alternate build definition when only change is an updated
dependency
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-1901
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-1901
>             Project: Continuum
>          Issue Type: New Feature
>          Components: Core system
>            Reporter: Richard Ziegler
>             Fix For: 1.3.x
>
>
> I use continuum to keep my maven repo populated with all the latest snapshots of our
testing code. As such, my default build mvn definition includes deploy.
> When there are no code changes to a project, and only an updated dependency, I'd rather
not deploy because it:
> * wastes space
> * wastes time
> * wastes bandwidth
> * will cause the 100+ lab machines running tests to pull the updated SNAPSHOTs  for no
reason.
> So, what is needed is a way to choose an alternate build definition (one without deploy,
in my case) when it is discovered that the only change was an updated dependency.

-- 
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

        

Mime
View raw message