New URL for NEMO forge!

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
Developers/SVN_QuickReference – NEMO

Version 37 (modified by nicolasmartin, 6 years ago) (diff)


Working with SVN

Last edited at Wikinfo(changed_ts)? by Wikinfo(changed_by)?

Howtos with SVN

Create a new routine

Use the template source:trunk/NEMOGCM/NEMO/OPA_SRC/module_example
If not don't forget to set the SVN property of the routine in order to get the functionality of SVN Id keyword replacement

svn propset svn:keywords Id New_routine.f90


For branch naming conventions, see wiki:Developers/DevelopingCodeChanges

svn copy svn+ssh://'your_forge_login'                  \ 
         svn+ssh://'your_forge_login' \
         -m 'Create a specific branch for the New Surface Module'

For development branches, we tend to add one level of subdirectory corresponding to the current year, and an additional item in the name corresponding to the work-plan,for instance:

svn copy svn+ssh://'your_forge_login'                               \
         svn+ssh://'your_forge_login' \
         -m 'Create a specific branch for mpp evolution'


Extract with svn+http protocol or see section 'Switch from user to developer'.

svn co svn+ssh://'your_forge_login'

Commit message

Recommended syntax to be added in the commit message

  • If the commit is related to one or several tickets, we highly suggest to add the commit message as ticket comment.
    To do so, you can use one of the word in the list addresses re references refs see followed by usual ticket link(s).
    Ex: see #1948 somewhere in the commit message to link with #1948
  • If the commit is a fix for one or several tickets, you can close them with the commit.
    To do so, you can use one of the word in the list close closed closes fix fixed fixes followed by usual ticket link(s).
    Ex: fix #1948 somewhere in the commit message to close #1948 without a browser.

Be careful if you mix the 2.

Then in the appropriate directory

# Commit and write the log message (ticket link #.... and so on) in your editor
svn ci files_list
# `svn ci` without files list will commit all modified files recursively from the current directory
# or directly from the command line of the shell session
svn ci -m 'log_message' files_list
# Tip: set your editor for SVN for multi-lines commit message
# for sh  and other related shells, interesting to include it in ~/.profile or ~/.bash_profile)
export SVN_EDITOR='your_favourite_editor' 
# for csh  "    "      "      ""  ,      "      ""    "    "" "" ~/.login                     )
setenv SVN_EDITOR='your_favourite_editor'


svn copy svn+ssh://'your_forge_login'          \
         svn+ssh://'your_forge_login' \
         -m "Tagging nemo_v2_3"


To get all changes from the revision 746 to the current one (HEAD) on a specific directory

# (you have already downloaded the branch you are working on)
svn merge -r 746:HEAD -m 'Merge my local IOM directory with the trunk repository'                               \
          svn+ssh://'your_forge_login' \

Update of a file between branches

Suppose the downloaded NEMO directory corresponds to the tag nemo_v3 (i.e. from; the current revision number of the file sbcssm.F90 is 1196. To get the new revision (which has been committed on the trunk ) with the revision number 1214:

cd ./modeles/NEMO/OPA_SRC/SBC/
svn merge -r 1196:1214

Information about the sources

To get information such as the PATH/URL you are working on, .i.e. trunk, branches .. and so on

cd ./NEMO && svn info

To get all commits/revision performed/associated on/to your working repository since its creation

cd ./NEMO && svn log --verbose --stop-on-copy

Switch from user to developer

The following command is set for the trunk, adapt as required for your developing branch.

svn switch --relocate                                       \

Switch from a branch to the trunk

Your working copy was based on a given branch which has been moved to the trunk.

svn switch

Comments: takes some time and asks if conflicts

Delete a branch

svn del svn+ssh://'your_forge_login' \
        --message 'Delete defunct branch'