You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Julien S (JIRA)" <ji...@codehaus.org> on 2008/08/18 22:36:26 UTC
[jira] Created: (CONTINUUM-1847) Allow a build definition to
actually be a template
Allow a build definition to actually be a template
--------------------------------------------------
Key: CONTINUUM-1847
URL: http://jira.codehaus.org/browse/CONTINUUM-1847
Project: Continuum
Issue Type: Improvement
Components: Web - UI
Affects Versions: 1.1
Reporter: Julien S
Currently, only when creating a new project can one use a default template. It is not possible to add a default template when changing the default build definition or when adding a new definition. Also, it seems that a change to a build template will only affect newly created projects, not projects previously created with the template.
A very nice and time-saving feature would be the ability to add a build definition which IS the build template (e.g. non-editable) and not a create time copy of the said template (as I understand it currently is). By doing this, a change in the template would be reflected in all the projects using it.
--
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-1847) Allow a build definition to
actually be a template
Posted by "Julien S (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146169#action_146169 ]
Julien S commented on CONTINUUM-1847:
-------------------------------------
Fair enough. I did not mean to be critical of the vocabulary. Nevertheless, I believe that "global build definitions" would be a great addition. Should I fill a new JIRA for this ? Such as "Implement global build definitions" ? Or keep this one ?
> Allow a build definition to actually be a template
> --------------------------------------------------
>
> Key: CONTINUUM-1847
> URL: http://jira.codehaus.org/browse/CONTINUUM-1847
> Project: Continuum
> Issue Type: Improvement
> Components: Web - UI
> Affects Versions: 1.1
> Reporter: Julien S
>
> Currently, only when creating a new project can one use a default template. It is not possible to add a default template when changing the default build definition or when adding a new definition. Also, it seems that a change to a build template will only affect newly created projects, not projects previously created with the template.
> A very nice and time-saving feature would be the ability to add a build definition which IS the build template (e.g. non-editable) and not a create time copy of the said template (as I understand it currently is). By doing this, a change in the template would be reflected in all the projects using it.
--
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-1847) Allow a build definition to
actually be a template
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145844#action_145844 ]
Wendy Smoak commented on CONTINUUM-1847:
----------------------------------------
I think template is the correct name for what we have. A template is something that you use to create a new thing.
I would call what you are describing a "global build definition" -- one definition, and a change in it affects anything currently using it.
> Allow a build definition to actually be a template
> --------------------------------------------------
>
> Key: CONTINUUM-1847
> URL: http://jira.codehaus.org/browse/CONTINUUM-1847
> Project: Continuum
> Issue Type: Improvement
> Components: Web - UI
> Affects Versions: 1.1
> Reporter: Julien S
>
> Currently, only when creating a new project can one use a default template. It is not possible to add a default template when changing the default build definition or when adding a new definition. Also, it seems that a change to a build template will only affect newly created projects, not projects previously created with the template.
> A very nice and time-saving feature would be the ability to add a build definition which IS the build template (e.g. non-editable) and not a create time copy of the said template (as I understand it currently is). By doing this, a change in the template would be reflected in all the projects using it.
--
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] Updated: (CONTINUUM-1847) Implement global build definitions
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Smoak updated CONTINUUM-1847:
-----------------------------------
Issue Type: New Feature (was: Improvement)
Summary: Implement global build definitions (was: Allow a build definition to actually be a template)
No need for a new issue, I just changed the summary on this one. :)
> Implement global build definitions
> ----------------------------------
>
> Key: CONTINUUM-1847
> URL: http://jira.codehaus.org/browse/CONTINUUM-1847
> Project: Continuum
> Issue Type: New Feature
> Components: Web - UI
> Affects Versions: 1.1
> Reporter: Julien S
>
> Currently, only when creating a new project can one use a default template. It is not possible to add a default template when changing the default build definition or when adding a new definition. Also, it seems that a change to a build template will only affect newly created projects, not projects previously created with the template.
> A very nice and time-saving feature would be the ability to add a build definition which IS the build template (e.g. non-editable) and not a create time copy of the said template (as I understand it currently is). By doing this, a change in the template would be reflected in all the projects using it.
--
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] Updated: (CONTINUUM-1847) Implement global build definitions
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Smoak updated CONTINUUM-1847:
-----------------------------------
Fix Version/s: Future
> Implement global build definitions
> ----------------------------------
>
> Key: CONTINUUM-1847
> URL: http://jira.codehaus.org/browse/CONTINUUM-1847
> Project: Continuum
> Issue Type: New Feature
> Components: Web - UI
> Affects Versions: 1.1
> Reporter: Julien S
> Fix For: Future
>
>
> Currently, only when creating a new project can one use a default template. It is not possible to add a default template when changing the default build definition or when adding a new definition. Also, it seems that a change to a build template will only affect newly created projects, not projects previously created with the template.
> A very nice and time-saving feature would be the ability to add a build definition which IS the build template (e.g. non-editable) and not a create time copy of the said template (as I understand it currently is). By doing this, a change in the template would be reflected in all the projects using it.
--
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-1847) Implement global build
definitions
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146940#action_146940 ]
Wendy Smoak commented on CONTINUUM-1847:
----------------------------------------
The more I work with build definitions and templates, the more I suspect that the ones added when a group is created *do* behave as global build definitions, so that changing the definition changes it for all the projects using it.
Needs more testing, or even better, someone who knows the code to comment.
Either way, we need to make it possible to choose an existing build definition when you add one to a project, as well as make this configurable, so templates can either add the shared build def, or a copy that belongs only to the newly created project group.
> Implement global build definitions
> ----------------------------------
>
> Key: CONTINUUM-1847
> URL: http://jira.codehaus.org/browse/CONTINUUM-1847
> Project: Continuum
> Issue Type: New Feature
> Components: Web - UI
> Affects Versions: 1.1
> Reporter: Julien S
>
> Currently, only when creating a new project can one use a default template. It is not possible to add a default template when changing the default build definition or when adding a new definition. Also, it seems that a change to a build template will only affect newly created projects, not projects previously created with the template.
> A very nice and time-saving feature would be the ability to add a build definition which IS the build template (e.g. non-editable) and not a create time copy of the said template (as I understand it currently is). By doing this, a change in the template would be reflected in all the projects using it.
--
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