[JIRA] (JENKINS-41191) read-only artifact files and build slaves
Title: Message Title Andrew Johnson closed an issue as Cannot Reproduce Not a bug according to the maintainer, easily worked around. Jenkins / JENKINS-41191 read-only artifact files and build slaves Change By: Andrew Johnson Status: Resolved Closed 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.
[JIRA] (JENKINS-41191) read-only artifact files and build slaves
Title: Message Title Andrew Johnson commented on JENKINS-41191 Re: read-only artifact files and build slaves Presumably the behavior on the master has been fixed in a newer version of Jenkins than we're currently running. It still seems weird to me though that an upstream job can break downstream jobs that use this plugin merely by changing the permission of the files that it provides as artifacts. The permissions of the artifact files are not visible anywhere in the Jenkins GUI that I can see, so there's no easy way for a downstream job's author to know in advance whether they have to allow for this or not. This is obviously trivial to fix in a build script or with some other plugin so it's not really a problem once you realize what's causing the failure, just slightly annoying. Thanks anyway - Andrew 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.
[JIRA] (JENKINS-41191) read-only artifact files and build slaves
Title: Message Title ikedam resolved as Cannot Reproduce Could not reproduce. Read-only files fail to be overwritten even on the master. It's a correct behavior that copyartifact fail to overwrite read-only files. Steps to reproduce: Tested with Ubuntu 12.04, Jenkins 2.32.1, Copyartifact 1.38.1 Create a slave "slave1" Create a freestyle project "copiee" Restrict where this project can be run: slave1 To avoid JENKINS-13128 Execute shell rm -rf * touch readwrite.txt touch readonly.txt chmod 400 readonly.txt Archive the artifacts Files to archive: **/* Run copiee See that artifacts are archived as expected: $ ls -l /var/lib/jenkins/jobs/copiee/builds/2/archive/ total 0 -r 1 jenkins jenkins 0 Jan 22 12:03 readonly.txt -rw-rw-r-- 1 jenkins jenkins 0 Jan 22 12:03 readwrite.txt Create a freestyle project "copier" Restrict where this project can be run: master Copy artifacts from another project Project name: copiee Artifacts to copy: **/* Run copier (1st time). The build succeeds. See that artifacts are copied as expected: $ ls -l /var/lib/jenkins/workspace/copier/ total 0 -r 1 jenkins jenkins 0 Jan 22 12:03 readonly.txt -rw-rw-r-- 1 jenkins jenkins 0 Jan 22 12:03 readwrite.txt
[JIRA] (JENKINS-41191) read-only artifact files and build slaves
Title: Message Title ikedam commented on JENKINS-41191 Re: read-only artifact files and build slaves Failing writing non-writeble files doesn't sound a bug, but a correct behavior (Rather, it sounds strange that it succeeds on the master). You should consider to use Workspace Cleanup Plugin. 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.
[JIRA] (JENKINS-41191) read-only artifact files and build slaves
Title: Message Title
Andrew Johnson created an issue
Jenkins / JENKINS-41191
read-only artifact files and build slaves
Issue Type:
Bug
Assignee:
ikedam
Components:
copyartifact-plugin
Created:
2017/Jan/18 11:37 PM
Environment:
Jenkins 1.658 with Copy Artifact plugin 1.38.1 Master on 64-bit RHEL6, build slaves on 32-bit RHEL6, MacOS and Solaris.
Labels:
slave
Priority:
Minor
Reporter:
Andrew Johnson
If an artifact file was created read-only (i.e. with permissions rrr-) when it was archived, the copyartifact plugin installs it as read-only too, which is what I would expect. Unfortunately when the build job runs a second time, the next attempt to copy the same artifact file then fails because it's trying to overwrite a read-only file. This doesn't seem to cause a problem with builds running on the master node, but it fails on my Linux, macOS and Solaris build slaves (I'm using a multi-config job to build the same code on all 4 OSs). The console output from one such slave job is shown below. If I wipe out the workspaces on the slaves, the next build that runs will succeed. {{FATAL: Failed to copy /var/lib/jenkins/jobs/extensions-3.14-ezca/configurations/axis-OS/linux32/builds/5/archive/include/ezca.h to /local/jenkins/workspace/extensions-3.14-ezcaScan/OS/linux32/include/ezca.h hudson.util.IOException2: Failed to copy /var/lib/jenkins/jobs/extensions-3.14-ezca/configurations/axis-OS/linux32/builds/5/archive/include/ezca.h to /local/jenkins/workspace/extensions-3.14-ezcaScan/OS/linux32/include/ezca.h at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(Fin
