Reputation: 1032
I need to checkout a previous version from my SVN and then make some changes to it, commit it and then prepare the build from this new revision from Jenkins.
How can this be done?
I know I can checkout a previous revision but when I will commit the changes to this revision, the new commit will still have all the other previous changes.
I am using TortoiseSVN.
Example of what I want to achieve: Say the current version is 111. and I want to revert to revision 99 and then be able to commit to this without all the changes from 100 till 111. Then build this new revision from Jenkins.
This SO question was also looking for something similar, is it still not possible to do something like this?
Upvotes: 1
Views: 980
Reputation: 5163
Every commit leads to a new revision. Your old commits will stay in log.
In your case you have to use "revert to this revision" (Tortoise context menu). Then make your changes and commit. This will create a commit which makes an "anti-commit" to the changes from 100 till 111 plus your new changes.
But I would recommend you to do this in two commits. First "revert to this revision" -> check in and a second commit with your new changes.
Maybe this helps to: What is Reverse Merge ( Revert Merge ) in SVN, a simple explanation and the step by step processes from start to finish
Upvotes: 3