[JIRA] (JENKINS-22795) git plugin cleans workspace on initial clone
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-22795 git plugin cleans workspace on initial clone Change By: Mark Waite Assignee: Cristian Cureliuc Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154609.1398727863000.6577.1586047620324%40Atlassian.JIRA.
[JIRA] (JENKINS-22795) git plugin cleans workspace on initial clone
Title: Message Title Mark Waite edited a comment on JENKINS-22795 Re: git plugin cleans workspace on initial clone [~roydahan] you may want to check the agent where that job is running. The removal of the contents only happens on the * initial * creation of the workspace, not on later requests to * update an existing workspace * . Something on the agent running the build may be causing the plugin to believe that it needs to perform a fresh clone rather than performing an incremental update.If you're using a Pipeline, you may also want to check the Pipeline definition that it does not include a separate call to deleteDir(). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154609.1398727863000.11273.1573229760735%40Atlassian.JIRA.
[JIRA] (JENKINS-22795) git plugin cleans workspace on initial clone
Title: Message Title Mark Waite edited a comment on JENKINS-22795 Re: git plugin cleans workspace on initial clone [~roydahan] you may want to check the agent where that job is running. The removal of the contents only happens on the *initial* creation of the workspace, * not * on later requests to *update an existing workspace*. Something on the agent running the build may be causing the plugin to believe that it needs to perform a fresh clone rather than performing an incremental update.If you're using a Pipeline, you may also want to check the Pipeline definition that it does not include a separate call to deleteDir(). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154609.1398727863000.11283.1573229761159%40Atlassian.JIRA.
[JIRA] (JENKINS-22795) git plugin cleans workspace on initial clone
Title: Message Title Mark Waite commented on JENKINS-22795 Re: git plugin cleans workspace on initial clone The log entry you provided which mentions ssh-agent is from the ssh-agent plugin, not from the Jenkins agent. It is unlikely to be related to the deletion of files which exist in the workspace of a job before the first clone into the workspace. This bug report is describing a very specific condition which only exists when the workspace of a job is not empty the very first time that Jenkins uses the workspace. That is quite rare. Freestyle jobs usually create the workspace on the Jenkins agent the first time the job is run, then they reuse that workspace on later execution of the same job. When the workspace is created, it is empty and the deletion that is described in this bug report is harmless. There are Jenkins plugins which will allow Freestyle jobs to write files into the workspace after the job starts and before the git repository is cloned into the workspace. The deletion behavior described here will delete those files that are created in the workspace before the git repository is first cloned. I was trying to suggest earlier that you should confirm that the workspace where the files are being deleted has not been damaged or partially deleted by some other scripts or changes in your environment. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-22795) git plugin cleans workspace on initial clone
Title: Message Title
Roy Dahan edited a comment on JENKINS-22795
Re: git plugin cleans workspace on initial clone
I don't know if it's related, but few lines in the log before the delete it seems like the agent is started.It happens every run.(It's not a pipeline job) {code:java} [ssh-agent] Looking for ssh-agent implementation... * 20:02:23 * [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) * 20:02:23 * $ ssh-agent*20:02:24* SSH_AUTH_SOCK=/tmp/ssh-3IVCGhG3LDLW/agent.20456*20:02:24* SSH_AGENT_PID=20458*20:02:24* [ssh-agent] Started. {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-22795) git plugin cleans workspace on initial clone
Title: Message Title Roy Dahan commented on JENKINS-22795 Re: git plugin cleans workspace on initial clone I don't know if it's related, but few lines in the log before the delete it seems like the agent is started. It happens every run. (It's not a pipeline job) [ssh-agent] Looking for ssh-agent implementation...20:02:23 [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine)20:02:23 $ ssh-agent*20:02:24* SSH_AUTH_SOCK=/tmp/ssh-3IVCGhG3LDLW/agent.20456*20:02:24* SSH_AGENT_PID=20458*20:02:24* [ssh-agent] Started. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-22795) git plugin cleans workspace on initial clone
Title: Message Title Mark Waite commented on JENKINS-22795 Re: git plugin cleans workspace on initial clone Roy Dahan you may want to check the agent where that job is running. The removal of the contents only happens on the initial creation of the workspace, not on later requests to update an existing workspace. Something on the agent running the build may be causing the plugin to believe that it needs to perform a fresh clone rather than performing an incremental update. If you're using a Pipeline, you may also want to check the Pipeline definition that it does not include a separate call to deleteDir(). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-22795) git plugin cleans workspace on initial clone
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-22795 git plugin cleans workspace on initial clone Change By: Mark Waite Summary: git plugin always cleans workspace , even when instructed not to on initial clone Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
