[JIRA] (JENKINS-60415) Deleting project does not delete artifacts from S3
Title: Message Title Luke Last created an issue Jenkins / JENKINS-60415 Deleting project does not delete artifacts from S3 Issue Type: Bug Assignee: Unassigned Components: artifact-manager-s3-plugin Created: 2019-12-10 04:40 Environment: Jenkins ver. 2.190.3, Artifact Manager on S3 plugin 1.7 Priority: Major Reporter: Luke Last Note that I have the "-Dio.jenkins.plugins.artifact_manager_jclouds.s3.S3BlobStoreConfig.deleteArtifacts=true" value set. If I delete a single build then the corresponding artifacts are deleted from S3. If I delete the whole project then none of the artifacts are deleted in S3. Add Comment
[JIRA] (JENKINS-57317) Exception when checking 'Validate S3 Bucket configuration'
Title: Message Title Luke Last commented on JENKINS-57317 Re: Exception when checking 'Validate S3 Bucket configuration' Seems like the "s3:GetBucketLocation" permission is required for validation to work. 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.199086.1556866104000.3258.1575949320218%40Atlassian.JIRA.
[JIRA] (JENKINS-50591) Files and paths with ampersand cause exception
Title: Message Title Luke Last commented on JENKINS-50591 Re: Files and paths with ampersand cause exception jclouds 2.1.1 was released. Also I tested with it and it fixed the issue for me. 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-13515) Copy failed on windows machine because of timestamp
[ https://issues.jenkins-ci.org/browse/JENKINS-13515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162357#comment-162357 ] Luke Last commented on JENKINS-13515: - I also had this problem with copy artifacts plugin v1.22 copying from an Ubuntu master to a windows 7 64bit slave. Going back to v1.21 solved the problem. Copy failed on windows machine because of timestamp --- Key: JENKINS-13515 URL: https://issues.jenkins-ci.org/browse/JENKINS-13515 Project: Jenkins Issue Type: Bug Components: copyartifact Environment: Jenkins ver. 1.460, debian master. XP slave. Reporter: Bertrand Latinville Assignee: Kohsuke Kawaguchi After upgrading Copy artifacts plugin to 1.22 I have some problems of copy on a windows XP slave. Downgrading to 1.21 solves the problem. This is the same issue as https://issues.jenkins-ci.org/browse/JENKINS-11073 ERROR: Failed to copy artifacts from job with filter: **/* hudson.util.IOException2: Failed to copy /var/lib/jenkins/jobs/(filepath).html to C:\jenkins\workspace\(filepath).html at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:91) at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyAll(FingerprintingCopyMethod.java:63) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:243) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:211) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:705) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475) at hudson.model.Run.run(Run.java:1421) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: hudson.util.IOException2: remote file operation failed: C:\jenkins\workspace\(filepath).html at hudson.remoting.Channel@2b0857d2:build-w7 at hudson.FilePath.act(FilePath.java:828) at hudson.FilePath.act(FilePath.java:814) at hudson.FilePath.touch(FilePath.java:1160) at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:79) ... 12 more Caused by: java.io.IOException: Failed to set the timestamp of C:\jenkins\workspace\(filepath).html to 1334755712000 at hudson.FilePath$19.invoke(FilePath.java:1166) at hudson.FilePath$19.invoke(FilePath.java:1160) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:60) at java.lang.Thread.run(Unknown Source) Build step 'Copy artifacts from another project' marked build as failure -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1
[ https://issues.jenkins-ci.org/browse/JENKINS-11933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159324#comment-159324 ] Luke Last commented on JENKINS-11933: - Can someone please update to SVNKIT 1.3.7? This is preventing us from upgrading our server to Subversion 1.7 Subversion plugin doesn't probably work correctly with svn server version 1.7.1 --- Key: JENKINS-11933 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Environment: svn server 1.7.1 ubuntu Reporter: Nikita Aznauryan Priority: Blocker Labels: plugin Attachments: 0001-imported-1.3.7.patch, 0002-Adjust-version-number-in-pom.patch, 0003-update-version-and-add-second-maven-repository-to-ge.patch, 0005_subversion_plugin_svnkit_1_3_7.patch I use usernames in my svn path like: svn+ssh://jenkins@somepath but I get a warning ... doesn't exist in the repository I think it started after svn server has been updated to 1.7.1 version It worked fine before. Subversion pooling log : Started on Nov 30, 2011 8:11:31 PM Location 'svn+ssh://jenkins@path' does not exist One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@3937bf4[], project will be disabled. Done. Took 1.3 sec No changes -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
