Difference between revisions of "Committing code to MSL"

From MSL-Libraries
Jump to navigationJump to search
(Automated checkin)
(Automated checkin)
 
(5 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
''' submit.py miscUtils.py mslBuildTools.py''' .  The primary driver of svn submission is '''submit.py'''
 
''' submit.py miscUtils.py mslBuildTools.py''' .  The primary driver of svn submission is '''submit.py'''
  
 +
 +
* <font color="red">MUST SUBMIT FROM MSLDIR</font>
 +
> cd $MSLDIR
  
 
* To add new files, or to submit modified files, run:
 
* To add new files, or to submit modified files, run:
  >python ./submit.py -f <list of files> -m <description of changes,additions>
+
  >python ./scripts/submit.py --f <file1,file2,file3> --m <description of changes,additions>
  
 
Note, you can submit multiple files, each with different descriptions if you wish.  For instance, you can run:
 
Note, you can submit multiple files, each with different descriptions if you wish.  For instance, you can run:
  
  >python ./submit.py -f file1.cpp -m "This is a message for file 1."
+
  >python ./scripts/submit.py --f file1.cpp --m "This is a message for file 1."
  >python ./submit.py -f file2.cpp file2.h file3.cpp file3.h Makefile -m "This is a message for files 2 and 3, plus the Makefile."
+
  >python ./scripts/submit.py --f file2.cpp file2.h file3.cpp file3.h Makefile --m "This is a message for files 2 and 3, plus the Makefile."
  
 
When you run submit in this way, the files are not yet submitted.  The script simply keeps track of the files that you intend to submit.
 
When you run submit in this way, the files are not yet submitted.  The script simply keeps track of the files that you intend to submit.
  
 
* Once you are ready to submit all of your files, run:
 
* Once you are ready to submit all of your files, run:
  >python ./submit.py -now
+
  >python ./scripts/submit.py --now --user <Sourceforge username>
 
This will then pull a fresh tree, copy over the files you have indicated previously when running submit.py -f, and then build the tree.  Provided the build
 
This will then pull a fresh tree, copy over the files you have indicated previously when running submit.py -f, and then build the tree.  Provided the build
 
completes successfully, the files will then be submitted to the repository.  If the build fails, you'll see an error message.  You can correct the error and then run submit.py -now again.
 
completes successfully, the files will then be submitted to the repository.  If the build fails, you'll see an error message.  You can correct the error and then run submit.py -now again.
 +
 +
Use multiple cores (example 8):
 +
  >python ./scripts/submit.py --now 8
 +
 +
* Click here for instructions on how to enable [[Password-less submit to SVN]]

Latest revision as of 20:51, 29 May 2014

Automated checkin

In the MSL repository exists a "scripts" directory. Inside should be 3 files: submit.py miscUtils.py mslBuildTools.py . The primary driver of svn submission is submit.py


  • MUST SUBMIT FROM MSLDIR
> cd $MSLDIR
  • To add new files, or to submit modified files, run:
>python ./scripts/submit.py --f <file1,file2,file3> --m <description of changes,additions>

Note, you can submit multiple files, each with different descriptions if you wish. For instance, you can run:

>python ./scripts/submit.py --f file1.cpp --m "This is a message for file 1."
>python ./scripts/submit.py --f file2.cpp file2.h file3.cpp file3.h Makefile --m "This is a message for files 2 and 3, plus the Makefile."

When you run submit in this way, the files are not yet submitted. The script simply keeps track of the files that you intend to submit.

  • Once you are ready to submit all of your files, run:
>python ./scripts/submit.py --now --user <Sourceforge username>

This will then pull a fresh tree, copy over the files you have indicated previously when running submit.py -f, and then build the tree. Provided the build completes successfully, the files will then be submitted to the repository. If the build fails, you'll see an error message. You can correct the error and then run submit.py -now again.

Use multiple cores (example 8):

 >python ./scripts/submit.py --now 8