This page (revision-21) was last changed on 07-Dec-2016 14:14 by RonYurow

This page was created on 28-Jun-2010 19:43 by RonYurow

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
21 07-Dec-2016 14:14 6 KB RonYurow to previous

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed one line
Here are some tips for using the command line tools for working with the EIS subversion repository:
[{ALLOW edit EISMainUsers}]
[{ALLOW view Anonymous}]
At line 3 changed one line
Note (1) -- I don't have access to a Mac, but I will assume everything works the same as on a Windows or Linux box.
!!! __The EIS Subversion Repository__
At line 5 changed one line
Note (2) -- There are a ton of graphical clients that are currently available for Subversion. You may wish to look into using one of those.
EIS software is now available through a Subversion repository. Historically, EIS software has been distributed through Solarsoft (SSW). The EIS repository provides an additional channel to access the software. In addition, developers of most EIS software modules must now update their files through subversion.
At line 7 changed one line
For windows users, I highly recommend TortoiseSVN:
__What is Subversion?__
At line 9 changed one line
http://tortoisesvn.tigris.org/
Subversion is a free/open-source version control system sponsored by CollabNet Inc. That is, Subversion manages files and directories, and the changes made to them, over time. This allows you to recover older versions of your files or examine the history of how your data has changed. Subversion makes easy for multiple authors to collaborate on a project by providing a robust set of tools for conflict resolution.
At line 11 changed one line
Note (3) -- The repository is currently on version 1.6.x of Subversion. Clients designed to work with earlier versions of Subversion can be used, however not all features may be available.
Subversion is very well documented. The complete Subversion book is available online at: [http://svnbook.red-bean.com/]
In particular, the chapter on the basic work cycle has lot of good information and will quickly get a novice user up and running.
At line 13 changed one line
Location:
It is located at:
At line 15 changed one line
The EIS repository is served from hyperion (http://hyperion.nascom.nasa.gov) located at GSFC and can be accessed at https://hyperion.nascom.nasa.gov/svn/eis/
[http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html/]
At line 17 changed one line
Due to NASA regulations and difficulties in accessing the repository from RAL, the repository is only available using SSL. Unfortunately, I had to use a self-signed certificate. This means that when you try to access the repository, you may be bombarded with dire warning messages because the certificate is not in your computer’s certificate chain. Just ignore these warnings. You may be able to add the certificate to your store and thus avoid future warning messages. Or you may not. This seems to work better on Linux then on Windows.
__About the EIS Software Repository__
At line 19 changed one line
Most of the operations on a repository are the same no matter if you are accessing a remote or local repository. In general, the only time it matters is when you initially check out the repository. Once that is done, SVN knows where it is and you no longer have to specify a location.
The EIS repository is served from hyperion ( [http://hyperion.nascom.nasa.gov/] ) located at GSFC.
At line 21 changed one line
Documentation:
It can be accessed at [https://hyperion.nascom.nasa.gov/svn/eis/]
At line 23 changed one line
Subversion is very well documented. The complete Subversion book is available online at:
Due to NASA regulations and difficulties in accessing the repository from RAL, the repository is only available using SSL. Unfortunately, the server uses a self-signed certificate. This means that when you try to access the repository, you may be bombarded with dire warning messages because the certificate is not in your computer’s certificate chain. Just ignore these warnings. You may be able to add the certificate to your store and thus avoid future warning messages. Or you may not. This seems to work better on Linux then on Windows.
At line 25 changed one line
http://svnbook.red-bean.com/
Although anyone my download the current version (or any previous version) of the repository, you must have a developer account in order to upload content to the repository.
At line 27 changed one line
In particular, the chapter on the basic work cycle has lot of good information and will quickly get a novice user up and running.
In order to get developer access, please send your preferred username and password to [mailto:yurow@grace.nascom.nasa.gov] . No restrictions currently exist on account names or passwords.
At line 29 changed one line
It is located at:
The repository is organized into a dev branch and a release branch. Files placed in the release branch will copied to Solarsoft (SSW) on a regular basis.
At line 31 changed one line
http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html
The dev branch exists as a place for developers to test their software (and make it available for others to try out as well) before releasing it as a finished product. Files placed in the dev branch will NOT be pushed to solarsoft. Before placing files in the dev branch, it is best create subdirectory with your account name in order to keep your files in same place and separate from other developers. For example, developer John Doe might create dev/doe and then place files he wishes to work with under the doe subdirectory.
At line 33 changed one line
As a quick reference, here are some basic commands.
__Accessing the Repository from the Web__
At line 38 added 14 lines
The EIS Subversion repository can be accessed with only your web browser. Go to [https://hyperion.nascom.nasa.gov/svn/eis/] to view the current revision of the repository. Clicking on a file will download it to your local machine.
Unfortunately, previous revisions of the repository cannot be accessed by this method.
__Accessing the Repository from a Subversion Client__
More complex operations, including uploading files and accessing previous revisions of the repository, will require you to use a subversion client.
A command line client is available for just about every system in existence. However, many users will want to use a graphical client. For windows users, TortoiseSVN is highly recommended. Pleas see http://tortoisesvn.tigris.org/.
Please note: repository is currently on version 1.6.x of Subversion. Clients designed to work with earlier versions of Subversion can be used, however not all features may be available.
As a quick reference, here are some basic subversion commands.
At line 37 changed one line
svn checkout https://hyperion.nascom.nasa.gov/svn/eis/release <localdir>
{{svn checkout https://hyperion.nascom.nasa.gov/svn/eis/release <localdir>}}
At line 45 changed one line
''svn add <file1>'' Add a file (<file1>)
{{''svn add <file1>'' Add a file (<file1>)}}
At line 47 changed one line
''svn add <dir1>'' Add a directory (<dir1>) and all subdirectories
{{''svn add <dir1>'' Add a directory (<dir1>) and all subdirectories}}
At line 49 changed one line
''svn add -force *'' Add all files not currently under version control.
{{''svn add -force *'' Add all files not currently under version control.}}
At line 55 changed one line
|(width:200px)''svn delete <path>/<file1>'' |Delete a file (<file1>)
{{''svn delete <path>/<file1>'' Delete a file (<file1>)}}
At line 57 changed one line
''svn delete <dir1>'' Delete a directory (<dir1>)
{{''svn delete <dir1>'' Delete a directory (<dir1>)}}
At line 63 changed one line
''svn revert <path>/<file1>''
{{''svn revert <path>/<file1>''}}
At line 69 changed one line
''svn status''
{{''svn status''}}
At line 75 changed one line
''svn update''
{{''svn update''}}
At line 83 changed one line
''svn commit -m "<Message>" --username <user>''
{{''svn commit -m "<Message>" --username <user>''}}
At line 86 removed one line