Support

Support Options

Report a problem

About you
About the problem

NCIP Hub
A COLLABORATORY FOR CANCER RESEARCH

Help

Home / Wish List / Migrate svn archive with history to the hub

Wish List - Wish List: Wish #218

<Member picture

0 Like 0 Dislike

Brandon D. Gallas

Migrate svn archive with history to the hub

You may have heard that google code is shutting down. That is where I have been developing and sharing my software tools. I am considering moving the entire effort to NCIPhub: code development, documentation development, and user group.

Is there a way to migrate the svn archive with its history to the hub?

Thanks, Brandon

Comments (5)

  1. Patrick Mulligan

    Brandon,

    The process isn't very streamlined and will involve multiple steps, but I believe we can get the SVN repository transferred while maintaining the history.

    1. Ensure you have an SVN version 1.7 or greater (the workspace unfortunately doesn't have a compatible version for the command needed to run a dump).  You can obtain a copy for Windows at http://sourceforge.net/projects/win32svn/
       
    2. Launch the command line and navigate to the directory you want to create the dump file.  Run the following command:
      svnrdump dump URL_to_code > name_of_file.dump

      The URL will usually be without the /trunk path.  You can name the file whatever you'd like.  As an example for one of my tools:

      svnrdump dump https://hubzero.org/tools/mulligantest/svn > testproject.dump
      It should then show which revision is being dumped and go through the entire list.
    3. Create an initial tool on NCIPHub where you want this code to be hosted.
    4. Submit a ticket to request to have the dump file loaded into this project.  Provide the name of the tool in the ticket and attach the dump file you created.
    5. We will then load the dump file into the tool repository.  Doing so will remove all existing files, so eventually if you were to create a tool using this repository we would need to restore the default directories used for tools (e.g. bin, middleware, src, rappture, etc.)

    Let me know if you have any questions.

    Thank you,

    Patrick

     

     

    Reply Report abuse

    Please login to comment.

  2. Brandon D. Gallas

    When we muster the energy to make this happen (identify someone to take the lead), we will. It may happen at the end of summer rather than now. We will discuss and plan. We are happy to know that it is possible.

    Thank you.

    Reply Report abuse

    Please login to comment.

  3. Brandon D. Gallas

    I have some other colleagues affected by the google code shut down. One question that I am not able to answer definitively is the following.

    Is the svn archive public?

    Who has access to the svn archive?

    Reply Report abuse

    Please login to comment.

    1. Patrick Mulligan

      The SVN archive is by default only accessible to the Tool development team.

      If a tool is made using the code, if you set the tool to be "Open source" it will allow anybody to download a package containing the source.  However if you don't want this to happen, setting it to "closed source" will make it so that the source code is always only accessible to the users added to the development team.

      We are also currently pursuing alternate methods for those wanting to simply host the source code for archival purposes, but don't necessarily want to create a tool using the code.

      Reply Report abuse

      Please login to comment.

  4. Garrett Powers

    Your content is very helpful for students as my kids were looking for some bid 4 papers review assistance for their exams preparation.Your post is really good one.Thanks.

    Reply Report abuse

    Please login to comment.

  5. Garrett Powers

    Your content is very helpful for students as my kids were looking for some bid 4 papers review assistance for their exams preparation.Your post is really good one.Thanks.

    Reply Report abuse

    Please login to comment.