|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Please provide more details about the conditions around the bug you're reporting.
If that type of bug is happening in common configurations, I'd expect many reports from users of the git plugin.
Have you configured the "Branch to build" as a branch which is not changing?
I attempted to duplicate your report by creating a job which performs a checkout, then appends text to one of the tracked files. Each time I run the job, it correctly resets the workspace to the state of the git repository, then appends a single line to the tracked file and completes successfully. If the repository were not being reset, the append would have caused those lines to accumulate, but there is always only one line visible at the end of the file.