Open timja opened 9 years ago
It's not clear from your steps to reproduce how you 'update to revision'.
If this is something done in step 3, 'run the build' (e.g. svn update … in a script), there is no way for Jenkins to know about this, and it happens after the changelog computation anyway. You'll have to find a different solution.
Update to revision is not part of the build, it just means I went to the working copy before I started the build and updated the revision to a lower number (for example it was 70 and i updated it to 50).
now when i run the build it updates to 70 but all the log messages do not appear in the change log.
Jenkins uses the data recorded for the previous build as reference for changelog computation (or rather, the SVN plugin does). Your use case is simply not how it works, and it cannot work like you seem to expect it to due to distributed builds, deleted workspaces, etc.
In "Source Code Management" I choose Subversion and entered several urls.
when i commit a new change, it is writes it in the change log when i run a build, but if i "update to revision" the build just updates the file and doesn't add it to the change log.
Even if i delete the entire working copy folder, it creates the folder again with all the file but the changelog is empty.
any idea why?
Steps to reproduce :
1. select in "Source Code Management" Subversion .\builds\\changelog.xml you will see only
2. enter a URL of a subversion repository.
3. run the build.
4. in C:\Jenkins\jobs\
Originally reported by giladba, imported from: changelog.xml doesn't show any changes