Saturday, December 18, 2010
"I do" or "I don't"??
Some how "marriage" and "death" are things that happen to other people.. It's really not something that you expect to happen to you (especially at 25!)
Wednesday, December 8, 2010
403 Forbidden!
"403 Forbidden" error is the one of the most ambiguous errors of SVN and the most frequently occurring too!
My earlier understanding was that it would typically occur only when the user did not have appropriate access rights to the svn path that he was trying to access.
But that's not the only reason. It could also occur due to a incorrect path.
It's kind of strange that we can checkout and browse the repository using this path but cannot commit to it!
You have to ensure that the letter casing is exactly the same as the repository name on SVN server.
For example, your working copy may work with the URL "https://server:8443/svn/Project/Trunk" whereas the server side URL would be "https://server:8443/svn/Project/trunk".
In this case, you need to use the relocate option of TortoiseSVN and relocate your working copy to the correct URL. You can also checkout the folder again if you have no uncommitted local modifications on your working copy.
So the next time you come across a 403, remember to check the letter cases of the SVN repository name!
My earlier understanding was that it would typically occur only when the user did not have appropriate access rights to the svn path that he was trying to access.
But that's not the only reason. It could also occur due to a incorrect path.
It's kind of strange that we can checkout and browse the repository using this path but cannot commit to it!
You have to ensure that the letter casing is exactly the same as the repository name on SVN server.
For example, your working copy may work with the URL "https://server:8443/svn/Project/Trunk" whereas the server side URL would be "https://server:8443/svn/Project/trunk".
In this case, you need to use the relocate option of TortoiseSVN and relocate your working copy to the correct URL. You can also checkout the folder again if you have no uncommitted local modifications on your working copy.
So the next time you come across a 403, remember to check the letter cases of the SVN repository name!
Thursday, December 2, 2010
Defect & Code Traceability
In large projects, it becomes exceptionally difficult to maintain traceability between the code changes and the defects and features. This traceability enables us to easily switch between code changes, revert to earlier repository state, review & tracking of changes made with respect to a particular defect number or feature number.
There are several defect tracker & CM tool integrations available. SVN in particular is integrable with most of the popular defect trackers like
Being slightly partial to the user friendly Redmine, the tortoisesvn - redmine plugin is very very easy to start with.
Once you configure the plugin to work with Redmine, you can see all the Redmine tasks in Tortoise SVN.
If you want to see the changesets in Redmine, you will need to click on the Repositories tab and then Redmine refreshes the changesets (Bug has been reported)
Or you can write a refresh script which can refresh repositories whenever a commit is made in SVN.
There are several defect tracker & CM tool integrations available. SVN in particular is integrable with most of the popular defect trackers like
Being slightly partial to the user friendly Redmine, the tortoisesvn - redmine plugin is very very easy to start with.
Once you configure the plugin to work with Redmine, you can see all the Redmine tasks in Tortoise SVN.
If you want to see the changesets in Redmine, you will need to click on the Repositories tab and then Redmine refreshes the changesets (Bug has been reported)
Or you can write a refresh script which can refresh repositories whenever a commit is made in SVN.
Subscribe to:
Posts (Atom)