[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title Kim Abbott commented on JENKINS-33056 Re: Please add clean remote option Where is this released? The latest release I see is 1.20.1. Was this release pulled? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168385.1455974353000.13960.1562041500232%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title Andrew Gray commented on JENKINS-33056 Re: Please add clean remote option Thank you Alex. Tested and confirmed working as expected. 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-33056) Please add clean remote option
Title: Message Title Alex Earl closed an issue as Fixed Jenkins / JENKINS-33056 Please add clean remote option Change By: Alex Earl Status: Reopened Closed Resolution: Fixed 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-33056) Please add clean remote option
Title: Message Title Alex Earl commented on JENKINS-33056 Re: Please add clean remote option 1.21.1 released 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-33056) Please add clean remote option
Title: Message Title Alex Earl commented on JENKINS-33056 Re: Please add clean remote option Yes, that would be because the other file that got missed 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-33056) Please add clean remote option
Title: Message Title Andrew Gray edited a comment on JENKINS-33056 Re: Please add clean remote option As you can see from the above 2^nd^ 2nd sshPublisher() line above the cleanRemote: true appears to be totally ignored.Monitoring the remote directory while the the job executes I see no deletion of anything in the remote directory. Hence why I had to add the 1^st^ 1st sshPublisher() line as a workaround. 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-33056) Please add clean remote option
Title: Message Title Andrew Gray edited a comment on JENKINS-33056 Re: Please add clean remote option As you can see from the 2nd sshPublisher() line above the cleanRemote: true appears to be totally ignored.Monitoring the remote directory while the the job executes I see no deletion of anything in the remote directory. Hence why I had to add the 1st sshPublisher() line as a workaround. 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-33056) Please add clean remote option
Title: Message Title Andrew Gray commented on JENKINS-33056 Re: Please add clean remote option As you can see from the above 2^nd^ sshPublisher() line above the cleanRemote: true appears to be totally ignored. Monitoring the remote directory while the the job executes I see no deletion of anything in the remote directory. Hence why I had to add the 1^st^ sshPublisher() line as a workaround. 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-33056) Please add clean remote option
Title: Message Title Alex Earl commented on JENKINS-33056 Re: Please add clean remote option No, one other file got missed when I pushed. It would be cleanRemote: true. If it works for scripted, it should work for declarative. There is nothing special that needs to be done for declarative as far as I know. 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-33056) Please add clean remote option
Title: Message Title Andrew Gray commented on JENKINS-33056 Re: Please add clean remote option Thanks Alex. It is only the jelly (UI?) files? Has this functionality been implemented for Declarative Pipeline to function as I am expecting? If so, what should the attribute be if not "cleanRemote: true" "clean-Remote: true"? Many Thanks. 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-33056) Please add clean remote option
Title: Message Title Alex Earl commented on JENKINS-33056 Re: Please add clean remote option Ok, my bad, I didn't update one of the jelly files to allow this to work. I will add that and try and get an 1.20.1 out soon (I am getting on a plane in a few minutes so it may be tomorrow). 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-33056) Please add clean remote option
Title: Message Title Alex Earl commented on JENKINS-33056 Re: Please add clean remote option Ok, thanks. I'll keep looking on my end. 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-33056) Please add clean remote option
Title: Message Title Andrew Gray commented on JENKINS-33056 Re: Please add clean remote option Jenkins 2.138.1 (Latest LTS release) I see that I already have 0.22 of the publish-over plugin installed in my Installed tab. Infrastructure plugin for Publish Over X Send build artifacts somewhere. 0.22 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-33056) Please add clean remote option
Title: Message Title Alex Earl commented on JENKINS-33056 Re: Please add clean remote option Can you check what version of the publish-over (NOT publish-over-ssh) plugin you have installed? If it is 0.21, can you try upgrading it to 0.22? 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-33056) Please add clean remote option
Title: Message Title
Andrew Gray edited a comment on JENKINS-33056
Re: Please add clean remote option
{code:java}pipeline { stages {... stage("Deploy") { //Next line needs to be removed pending SSH Plugin fixes sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: "rd /s /q E:\\Absolute\\path\\to\\MyApplication", execTimeout: 12, flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: '', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false)]) sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: '', execTimeout: 12, flatten: false, makeEmptyDirs: true, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: "${env.RELATIVE_REMOTE_FOLDER}", remoteDirectorySDF: false, removePrefix: 'parameterisedpackage', sourceFiles: '/parameterisedpackage/**')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false, cleanRemote: true)]) } }}{code}The first sshPublisher() line is the nasty absolute path workaround at the moment. This line has the effect of deleting the entire remote directory on the target machine and its contents recursively. Kind of gets the job done BUT... it is not going to work well as the drive letter is different across test environments. I would like to remove this line entirely.The second sshPublisher() line copies the required files but the cleanRemote: true doesn't do anything in the remote directory on the target machine.I would like cleanRemote to respect the RELATIVE_REMOTE_FOLDER in the remoteDirectory field (which the copying function part of the plugin is) and delete the entire remote directory on the target machine and its contents recursively and see it execute BEFORE the transfer of new files executes. Note: parameterisedpackage is a result directory that has had msdeploy run to apply a properties file for the target environment over the Web.config file. Let me know if you have any other questions.
Add Comment
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title
Andrew Gray edited a comment on JENKINS-33056
Re: Please add clean remote option
{code:java}pipeline { stages {... stage("Deploy") { //Next line needs to be removed pending SSH Plugin fixes sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: "rd /s /q E:\\Absolute\\path\\to\\MyApplication", execTimeout: 12, flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: '', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false)]) sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: '', execTimeout: 12, flatten: false, makeEmptyDirs: true, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: "${env.RELATIVE_REMOTE_FOLDER}", remoteDirectorySDF: false, removePrefix: 'parameterisedpackage', sourceFiles: '/parameterisedpackage/**')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false, cleanRemote: true)]) } }}{code}The first sshPublisher() line is the nasty absolute path workaround at the moment. This line has the effect of deleting the entire remote directory on the target machine and its contents recursively. Kind of gets the job done BUT... it is not going to work well as the drive letter is different across test environments. I would like to remove this line entirely.The second sshPublisher() line copies the required files but the cleanRemote: true doesn't do anything in the remote directory on the target machine.I would like cleanRemote to respect the RELATIVE_REMOTE_FOLDER in the remoteDirectory field (which the copying function part of the plugin is) and delete the entire remote directory on the target machine and its contents recursively and see it execute BEFORE the transfer of new files executes. Note: parameterisedpackage is a result directory that has had msdeploy run to apply a properties file for the target environment over the Web.config file.
Add Comment
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title
Andrew Gray edited a comment on JENKINS-33056
Re: Please add clean remote option
{code:java}pipeline { stages {... stage("Deploy") { //Next line needs to be removed pending SSH Plugin fixes sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: "rd /s /q E:\\Absolute\\path\\to\\MyApplication", execTimeout: 12, flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: '', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false)]) sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: '', execTimeout: 12, flatten: false, makeEmptyDirs: true, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: "${env.RELATIVE_REMOTE_FOLDER}", remoteDirectorySDF: false, removePrefix: 'parameterisedpackage', sourceFiles: '/parameterisedpackage/**')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false, cleanRemote: true)]) } }}{code}The first sshPublisher() line is the nasty workaround at the moment. This line has the effect of deleting the entire remote directory on the target machine and its contents recursively. Kind of gets the job done BUT... it is not going to work well as the drive letter is different across test environments. I would like to remove this line entirely.The second sshPublisher() line copies the required files but the cleanRemote: true doesn't do anything in the remote directory on the target machine.I would like cleanRemote to respect the RELATIVE_REMOTE_FOLDER in the remoteDirectory field (which the copying function part of the plugin is) and delete the entire remote directory on the target machine and its contents recursively and see it execute BEFORE the transfer of new files executes . Note: parameterisedpackage is a result directory that has had msdeploy run to apply a properties file for the target environment over the Web.config file.
Add Comment
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title
Andrew Gray edited a comment on JENKINS-33056
Re: Please add clean remote option
{code:java}pipeline { stages {... stage("Deploy") { //Next line needs to be removed pending SSH Plugin fixes sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: "rd /s /q E:\\Absolute\\path\\to\\MyApplication", execTimeout: 12, flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: '', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false)]) sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: '', execTimeout: 12, flatten: false, makeEmptyDirs: true, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: "${env.RELATIVE_REMOTE_FOLDER}", remoteDirectorySDF: false, removePrefix: 'parameterisedpackage', sourceFiles: '/parameterisedpackage/**')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false, cleanRemote: true)]) } }}{code}The first sshPublisher() line is the nasty workaround at the moment. This line has the effect of deleting the entire remote directory on the target machine and its contents recursively. Kind of gets the job done BUT... it is not going to work well as the drive letter is different across test environments. I would like to remove this line entirely.The second sshPublisher() line copies the required files but the cleanRemote: true doesn't do anything in the remote directory on the target machine.I would like cleanRemote to respect the RELATIVE_REMOTE_FOLDER in the remoteDirectory field (which the copying function part of the plugin is) and delete the entire remote directory on the target machine and its contents recursively. Note: parameterisedpackage is a result directory that has had msdeploy run to apply a properties file for the target environment over the Web.config file.
Add Comment
This message
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title
Andrew Gray edited a comment on JENKINS-33056
Re: Please add clean remote option
{code:java}pipeline { stages {... stage("Deploy") { //Next line needs to be removed pending SSH Plugin fixes sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: "rd /s /q E:\\Absolute\\path\\to\\MyApplication", execTimeout: 12, flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: '', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false)]) sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: '', execTimeout: 12, flatten: false, makeEmptyDirs: true, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: "${env.RELATIVE_REMOTE_FOLDER}", remoteDirectorySDF: false, removePrefix: 'parameterisedpackage', sourceFiles: '/parameterisedpackage/**')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false, cleanRemote: true)]) } }}{code}The first sshPublisher() line is the nasty workaround at the moment to remove the remote directory but it has to be an absolute path with is not going to be work as the drive letter is different across test environments . This line has the effect of deleting the entire remote directory on the target machine and its contents recursively. Kind of gets the job BUT... it is not going to work well as the drive letter is different across test environments. I would like to remove this line entirely. The second sshPublisher() line copies the required files but the cleanRemote: true doesn't do anything in the remote directory on the target machine.I would like cleanRemote to respect the RELATIVE_REMOTE_FOLDER in the remoteDirectory field (which the copying function part of the plugin is) and delete the entire remote directory on the target machine and its contents recursively. Note: parameterisedpackage is a result directory that has had msdeploy run to apply a properties file for the target environment over the Web.config file.
Add Comment
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title
Andrew Gray edited a comment on JENKINS-33056
Re: Please add clean remote option
{code:java}pipeline { stages { ... stage("Deploy") { //Next line needs to be removed pending SSH Plugin fixes sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: "rd /s /q E:\\Absolute\\path\\to\\MyApplication", execTimeout: 12, flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: '', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false)]) sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: '', execTimeout: 12, flatten: false, makeEmptyDirs: true, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: "${env.RELATIVE_REMOTE_FOLDER}", remoteDirectorySDF: false, removePrefix: 'parameterisedpackage', sourceFiles: '/parameterisedpackage/**')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false, cleanRemote: true)]) } }}{code}The first sshPublisher() line is the nasty workaround at the moment to remove the remote directory but it has to be an absolute path with is not going to be work as the drive letter is different across test environments. This line has the effect of deleting the entire remote directory on the target machine and its contents recursively.The second sshPublisher() line copies the required files but the cleanRemote: true doesn't do anything in the remote directory on the target machine.I would like cleanRemote to respect the RELATIVE_REMOTE_FOLDER in the remoteDirectory field (which the copying function part of the plugin is) and delete the entire remote directory on the target machine and its contents recursively. Note: parameterisedpackage is a result directory that has had msdeploy run to apply a properties file for the target environment over the Web.config file.
Add Comment
This message was sent by
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title
Andrew Gray edited a comment on JENKINS-33056
Re: Please add clean remote option
{code:java}pipeline { stages { stage("Deploy") { //Next line needs to be removed pending SSH Plugin fixes sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: "rd /s /q E:\\Absolute\\path\\to\\MyApplication", execTimeout: 12, flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: '', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false)]) sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: '', execTimeout: 12, flatten: false, makeEmptyDirs: true, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: "${env.RELATIVE_REMOTE_FOLDER}", remoteDirectorySDF: false, removePrefix: 'parameterisedpackage', sourceFiles: '/parameterisedpackage/**')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false, cleanRemote: true)]) } }}{code}The first sshPublisher() line is the nasty workaround at the moment to remove the remote directory but it has to be an absolute path with is not going to be work as the drive letter is different across test environments. This line has the effect of deleting the entire remote directory on the target machine and its contents recursively.The second sshPublisher() line copies the required files but the cleanRemote: true doesn't do anything in the remote directory on the target machine.I would like cleanRemote to respect the RELATIVE_REMOTE_FOLDER in the remoteDirectory field (which the copying function part of the plugin is) and delete the entire remote directory on the target machine and its contents recursively. Note: parameterisedpackage is a result directory that has had msdeploy run to apply a properties file for the target environment over the Web.config file.
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title
Andrew Gray edited a comment on JENKINS-33056
Re: Please add clean remote option
{code:java}pipeline { stages { stage("Deploy") { //Next line needs to be removed pending SSH Plugin fixes sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: "rd /s /q E:\\Absolute\\path\\to\\MyApplication", execTimeout: 12, flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: '', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false)]) sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: '', execTimeout: 12, flatten: false, makeEmptyDirs: true, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: "${env.RELATIVE_REMOTE_FOLDER}", remoteDirectorySDF: false, removePrefix: 'parameterisedpackage', sourceFiles: '/parameterisedpackage/**')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false, cleanRemote: true)]) } }}{code}The first sshPublisher () line is the nasty workaround at the moment to remove the remote directory but it has to be an absolute path with is not going to be work as the drive letter is different across test environments. This line has the effect of deleting the entire remote directory on the target machine and its contents recursively.The second sshPublisher () line copies the required files but the cleanRemote: true doesn't do anything in the remote directory on the target machine.I would like cleanRemote to respect the RELATIVE_REMOTE_FOLDER in the remoteDirectory field (which the copying function part of the plugin is) and delete the entire remote directory on the target machine and its contents recursively.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title
Andrew Gray commented on JENKINS-33056
Re: Please add clean remote option
pipeline {
stages {
stage("Deploy") {
//Next line needs to be removed pending SSH Plugin fixes
sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: "rd /s /q E:\\Absolute\\path\\to\\MyApplication", execTimeout: 12, flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: '', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false)])
sshPublisher(publishers: [sshPublisherDesc(configName: "MyApplication_${env.ENVIRONMENT}", transfers: [sshTransfer(excludes: '', execCommand: '', execTimeout: 12, flatten: false, makeEmptyDirs: true, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: "${env.RELATIVE_REMOTE_FOLDER}", remoteDirectorySDF: false, removePrefix: 'parameterisedpackage', sourceFiles: '/parameterisedpackage/**')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false, cleanRemote: true)])
}
}
}
The first sshPublisher line is the nasty workaround at the moment to remove the remote directory but it has to be an absolute path with is not going to be work as the drive letter is different across test environments. This line has the effect of deleting the entire remote directory on the target machine and its contents recursively. The second sshPublisher line copies the required files but the cleanRemote: true doesn't do anything in the remote directory on the target machine. I would like cleanRemote to respect the RELATIVE_REMOTE_FOLDER in the remoteDirectory field (which the copying function part of the plugin is) and delete the entire remote directory on the target machine and its contents recursively.
Add Comment
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title Alex Earl commented on JENKINS-33056 Re: Please add clean remote option I don't use declarative so I am not sure how to use it there. I will have to refresh my memory on how it's used in pipeline. Can you attach your Jenkinsfile? 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-33056) Please add clean remote option
Title: Message Title
Andrew Gray edited a comment on JENKINS-33056
Re: Please add clean remote option
Thanks for this release [~slide_o_mix]. Much appreciated.Is this supported in Declarative Pipeline?How is it used? Do we just add{code:java}cleanRemote: true{code}as an attribute on the sshPublisher() command?Also I don't see a cleanRemote option in the Pipeline Syntax generator. Has that been implemented?I tested cleanRemote: true and in an sshPublisher() call. it passes validation and runs but doesn't do anything. Nothing is deleted in the remoteDirectory. I would expect it to delete the contents of the remoteDirectory recursively leaving it an empty directory so that the transfer then filled up the remoteDirectory again with fresh files from source.
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-33056) Please add clean remote option
Title: Message Title Andrew Gray reopened an issue Functionality doesn't appear to be implemented for Declarative Pipeline or shown in Pipeline Syntax Generator. Expected to be able to add cleanRemote: true to an sshPublisher() call in declarative pipeline. Jenkins / JENKINS-33056 Please add clean remote option Change By: Andrew Gray Resolution: Fixed Status: Closed Reopened 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-33056) Please add clean remote option
Title: Message Title
Andrew Gray edited a comment on JENKINS-33056
Re: Please add clean remote option
Thanks for this release [~slide_o_mix]. Much appreciated.Is this supported in Declarative Pipeline?How do I use this is it used ? Do I we just add{code:java}cleanRemote: true{code}as an attribute on the sshPublisher() command? Also I don't see a cleanRemote option in the Pipeline Syntax generator. Has that been implemented?I tested cleanRemote: true and it runs but doesn't do anything.
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-33056) Please add clean remote option
Title: Message Title Andrew Gray commented on JENKINS-33056 Re: Please add clean remote option Thanks for this release Alex. Much appreciated. Is this supported in Declarative Pipeline? How do I use this? Do I just add cleanRemote: true as an attribute on the sshPublisher() command? 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-33056) Please add clean remote option
Title: Message Title
Andrew Gray edited a comment on JENKINS-33056
Re: Please add clean remote option
Thanks for this release Alex [~slide_o_mix] . Much appreciated.Is this supported in Declarative Pipeline?How do I use this? Do I just add{code:java}cleanRemote: true{code}as an attribute on the sshPublisher() command?
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-33056) Please add clean remote option
Title: Message Title Alex Earl closed an issue as Fixed Released 1.20 Jenkins / JENKINS-33056 Please add clean remote option Change By: Alex Earl Status: Resolved Closed 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-33056) Please add clean remote option
Title: Message Title Andrew Gray edited a comment on JENKINS-33056 Re: Please add clean remote option [~slide_o_mix] Can this functionality please be published. It seems a long time since v1.19.1 was released. Is this plugin still being maintained? Thank you, Andrew github.com/agray 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-33056) Please add clean remote option
Title: Message Title Andrew Gray commented on JENKINS-33056 Re: Please add clean remote option Alex Earl Can this functionality please be published. It seems a long time since v1.19.1 was released. Is this plugin still being maintained? Thank you, Andrew 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-33056) Please add clean remote option
Title: Message Title Alex Earl resolved as Fixed Will be in next version (1.20) Jenkins / JENKINS-33056 Please add clean remote option Change By: Alex Earl Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-33056) Please add clean remote option
Title: Message Title Alex Earl stopped work on JENKINS-33056 Change By: Alex Earl Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-33056) Please add clean remote option
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33056 Re: Please add clean remote option Code changed in jenkins User: Alex Earl Path: pom.xml src/main/java/jenkins/plugins/publish_over_ssh/BapSshClient.java src/main/resources/jenkins/plugins/publish_over_ssh/Messages.properties src/main/resources/jenkins/plugins/publish_over_ssh/options/SshOverrideTransferDefaults/config.jelly src/test/java/jenkins/plugins/publish_over_ssh/BapSshClientTest.java http://jenkins-ci.org/commit/publish-over-ssh-plugin/5b80db4f084cae85be0b7c510dafe89b18123d7b Log: Fix JENKINS-33056 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-33056) Please add clean remote option
Title: Message Title Alex Earl started work on JENKINS-33056 Change By: Alex Earl Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-33056) Please add clean remote option
Title: Message Title Alex Earl commented on JENKINS-33056 Re: Please add clean remote option Will add this soon, sorry for the long wait time! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-33056) Please add clean remote option
Title: Message Title Alex Earl assigned an issue to Alex Earl Jenkins / JENKINS-33056 Please add clean remote option Change By: Alex Earl Assignee: bap Alex Earl Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-33056) Please add clean remote option
Title: Message Title Giovanni Tirloni commented on JENKINS-33056 Re: Please add clean remote option Even though JJB lists a 'clean-remote' option, enabling it causes a "null" error when publishing. Tested with Publish over SSH plugin version 1.14. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
