Difference between revisions of "Development and submission steps using SVN - OOP344 20121"
(→Checkout and prepare your team repository) |
(→Create your own workspace) |
||
Line 16: | Line 16: | ||
== Create your own workspace == | == Create your own workspace == | ||
− | # create your own sub-directory under branches and name it using your seneca id | + | # create your own sub-directory under '''branches''' and name it using your seneca id |
− | #: add this sub-directory to the repository (right click on the sub-dir | + | #: add this sub-directory to the repository (right click on the sub-dir, select '''TortoiseSVN/Add''', and click OK) |
− | #: commit your addition to the repo (right click on the sub-dir | + | #: commit your addition to the repo (right click on the sub-dir, select '''SVN Commit''', add a note describing your change under Messages, and click OK) this will save your addition on the server |
#: note that this sub-dir is referred as your '''workspace''' | #: note that this sub-dir is referred as your '''workspace''' | ||
+ | : you are now ready to start working on your own tasks | ||
== Branch trunk for development == | == Branch trunk for development == |
Revision as of 18:22, 19 January 2012
OOP344 | Weekly Schedule | Student List | Teams | Project | Student Resources
Contents
Checkout and prepare your team repository
- create a directory for your repo on your local workstation. Usually, you do this only once on each workstation that you use for development.
- checkout the repository into the directory that you have created (the repo directory)
- using TortoiseSVN (or other GUI) right click on the directory and select SVN Checkout
- enter the URL of the team repository and click OK
- you should see the files being added to your local repo directory. Click OK when completed.
- you should now have a copy of the whole repo on your workstation.
- check that your local repo directory contains sub-directories named branches, tags, and trunk. If not
- create these three sub-directories under the repo directory
- add them to the repository (right-click on the repo directory, select TortoiseSVN/Add, and click OK)
- commit them to the repo (right-click on the repo directory, select SVN Commit, add a note describing your change under Message, and click OK)
- you are now ready to create your own workspace
Create your own workspace
- create your own sub-directory under branches and name it using your seneca id
- add this sub-directory to the repository (right click on the sub-dir, select TortoiseSVN/Add, and click OK)
- commit your addition to the repo (right click on the sub-dir, select SVN Commit, add a note describing your change under Messages, and click OK) this will save your addition on the server
- note that this sub-dir is referred as your workspace
- you are now ready to start working on your own tasks
Branch trunk for development
- branch the trunk into a sub-dir under your own workspace under branches
- Right-click on the trunk directory
- Choose TortoiseSVN and click on branch/tag...
- Click on the [...] button to the right of "To URL:"
- Click on the root directory, then on branches, then on your workspace, then press "OK"
- Edit the URL created by adding a slash and the name that you want to give to your new sub-directory (a.k.a create a new directory)
- The name of your new sub-directory should refer to your particular task (whatever you are going to work on)
- Type in a log message that describes what you are doing and press "OK"
- update your repository to get the branch on your local machine
Start coding and complete your task
- code
- compile
- test
- compile
- commit (commit changes back to repo on server)
Merge your work back to trunk
- make sure that you have committed your branch
- right click on trunk and select TortoiseSVN/merge
- select your branch
- merge by default settings and resolve possible conficts
Test and commit trunk
- recompile and test merged trunk
- update trunk status on wiki team page to commiting
- if the status is already commiting wait for it to be done
- commit trunk
- resolve possible problems
- commit again
- update trunk status on wiki team page to commited