[JIRA] [git] (JENKINS-23424) Existing working directory is not updated
Mark Waite edited a comment on JENKINS-23424 Existing working directory is not updated I can duplicate this bug. Thanks for the bug report. The command line git implementation in the git client plugin performs a force checkout of the files associated with the SHA1 being built. That causes changes to tracked files to be discarded from one build to the next. The JGit implementation in the git client plugin seems to not perform a force checkout of the files associated with the SHA1 being built. If there are changes in a tracked file, a new build with the JGit implementation leaves the modified file, rather than overwriting it with the version in the repository. I duplicated 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 using the command line git implementation, 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. Each time I run the job with the JGit implementation, the workspace is not reset and the new content to be added is appended to the target file. One work around is to switch to the command line git implementation. 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.
[JIRA] [git] (JENKINS-23424) Existing working directory is not updated
Mark Waite edited a comment on JENKINS-23424 Existing working directory is not updated I can duplicate this bug. Thanks for the bug report. The command line git implementation in the git client plugin performs a force checkout of the files associated with the SHA1 being built. That causes changes to tracked files to be discarded from one build to the next. The JGit implementation in the git client plugin seems to not perform a force checkout of the files associated with the SHA1 being built. If there are changes in a tracked file, a new build with the JGit implementation leaves the modified file, rather than overwriting it with the version in the repository. I duplicated 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 using the command line git implementation, 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. Each time I run the job with the JGit implementation, the workspace is not reset and the new content to be added is appended to the target file. One work around is to switch to the command line git implementation. Does my description match the bug you're seeing, or is the bug I've detected something different than your problem? 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.
[JIRA] [git] (JENKINS-23424) Existing working directory is not updated
Mark Waite updated JENKINS-23424 Existing working directory is not updated Change By: Mark Waite (14/Jun/14 7:32 PM) Component/s: git-client 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.
[JIRA] [git] (JENKINS-23424) Existing working directory is not updated
chrisabit commented on JENKINS-23424 Existing working directory is not updated Thanks for the fast reply Your description seems to hit the point. I suppose most of the users will use the command line implementation of git, which works. Unfortunately we (company) are stucked with jGit. Our workaround is to clean the working directory and to perform a full clone. This will be sufficient 'til the bug is fixed 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.
[JIRA] [git] (JENKINS-23424) Existing working directory is not updated
chrisabit edited a comment on JENKINS-23424 Existing working directory is not updated Thanks for the fast reply Your description seems to hit the point. I suppose most of the users will use the command line implementation of git, which works. Unfortunately we (company) are stucked with jGit. Our workaround is to clean the working directory and to perform a full clone. This will be sufficient 'til the bug is fixed (Spooky ticket id by the way - don't panic and keep the towel dry) 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.
[JIRA] [git] (JENKINS-23424) Existing working directory is not updated
chrisabit created JENKINS-23424 Existing working directory is not updated Issue Type: Bug Assignee: Nicolas De Loof Components: git, git-client Created: 13/Jun/14 9:25 AM Description: Existing working dirs are not updated after a build is started. The git fetch works,moreover the correct commit hashcode is used (visible in console log) A manual (commandline!) "git reset --hard" updates the working dir. Our workaround: Force delete jenkins working dir. Environment: Jenkins 1.566 git plugin 2.2.1 git client plugin 1.9.1 JGit Tomcat 7 Java 1.7.0_60 RHEL6 gitblit Repos / http Project: Jenkins Priority: Critical Reporter: chrisabit 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.
[JIRA] [git] (JENKINS-23424) Existing working directory is not updated
Mark Waite commented on JENKINS-23424 Existing working directory is not updated 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. 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.
[JIRA] [git] (JENKINS-23424) Existing working directory is not updated
Mark Waite updated JENKINS-23424 Existing working directory is not updated Change By: Mark Waite (13/Jun/14 11:22 PM) Component/s: git-client 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.
