You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2010/03/22 20:50:22 UTC

[jira] Created: (CONTINUUM-2492) Provide a utility to move projects/groups to a different server

Provide a utility to move projects/groups to a different server
---------------------------------------------------------------

                 Key: CONTINUUM-2492
                 URL: http://jira.codehaus.org/browse/CONTINUUM-2492
             Project: Continuum
          Issue Type: New Feature
    Affects Versions: 1.3.6 (Beta)
            Reporter: Wendy Smoak


We need to move projects from one server to another, for example when one becomes overloaded.  Currently the only way to do it is to use the Web UI to add them to the new server and then delete them from the old.

At a minimum, moving an entire project group and retaining all of the configuration would work.  

We can live without the build history if that's too hard to move.

Ideally we would be able to move individual projects.

Moving the project(s) into the same project group on the target server is a reasonable assumption.


-- 
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-2492) Provide a utility to move projects/groups to a different server

Posted by "Maria Catherine Tan (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/CONTINUUM-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maria Catherine Tan updated CONTINUUM-2492:
-------------------------------------------

    Fix Version/s:     (was: 1.4.1 (Beta))
                   1.4.2 (Beta)

> Provide a utility to move projects/groups to a different server
> ---------------------------------------------------------------
>
>                 Key: CONTINUUM-2492
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2492
>             Project: Continuum
>          Issue Type: New Feature
>    Affects Versions: 1.3.6
>            Reporter: Wendy Smoak
>             Fix For: 1.4.2 (Beta)
>
>
> We need to move projects from one server to another, for example when one becomes overloaded.  Currently the only way to do it is to use the Web UI to add them to the new server and then delete them from the old.
> At a minimum, moving an entire project group and retaining all of the configuration would work.  
> We can live without the build history if that's too hard to move.
> Ideally we would be able to move individual projects.
> Moving the project(s) into the same project group on the target server is a reasonable assumption.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (CONTINUUM-2492) Provide a utility to move projects/groups to a different server

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/CONTINUUM-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated CONTINUUM-2492:
------------------------------------

    Fix Version/s: 1.4.1 (Beta)

> Provide a utility to move projects/groups to a different server
> ---------------------------------------------------------------
>
>                 Key: CONTINUUM-2492
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2492
>             Project: Continuum
>          Issue Type: New Feature
>    Affects Versions: 1.3.6 (Beta)
>            Reporter: Wendy Smoak
>             Fix For: 1.4.1 (Beta)
>
>
> We need to move projects from one server to another, for example when one becomes overloaded.  Currently the only way to do it is to use the Web UI to add them to the new server and then delete them from the old.
> At a minimum, moving an entire project group and retaining all of the configuration would work.  
> We can live without the build history if that's too hard to move.
> Ideally we would be able to move individual projects.
> Moving the project(s) into the same project group on the target server is a reasonable assumption.

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