installer_mac issue with file permission issue.

[archanaNogriya]

jdk11u-mac-x64-openj9
https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-mac-x64-openj9/622/console

04:47:56 Starting building: build-scripts » release » create_installer_mac #3352
[Pipeline] copyArtifacts
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] echo
05:04:38 Execution error: Unable to get file permissions
[Pipeline] }
looks like something went wrong in overwriting file ?, there is no other error or explanation I can see. Might require cleaning machine if it is not done auto clearing before build.

[Haroon-Khel]

Its odd, as the stage view says the installer job has failed, but the status page of that installer job says its passed https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_mac/3352/

[Haroon-Khel]

Ahh, the Copy artifacts from another project part of the installer stage failed. The failure log isnt helpful

[Haroon-Khel]

https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-mac-x64-openj9/623/
On the same machine, the latest build does not fail, so im putting this down to an intermittent failure.
Will keep an eye on it

[M-Davies]

@karianna I'm still seeing this on a few builds except the installer are passing this time (in the case of the windows job below anyway, I don't have the perms to view the mac ones). Do the installers need the same change you made with George yesterday?

Only the artifacts are failing to be copied across for JRE job. FYI @douph1

• https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-mac-x64-hotspot/613/console
• https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk14u/job/jdk14u-mac-x64-openj9-macosXL/101/console
• https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk14u/job/jdk14u-windows-x86-32-hotspot/98/console

23:18:39  Scheduling project: build-scripts » release » create_installer_windows
23:18:48  Starting building: build-scripts » release » create_installer_windows #4502
[Pipeline] copyArtifacts
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] echo
23:22:10  Execution error: Unable to get file permissions

[karianna]

@karianna I'm still seeing this on a few builds except the installer are passing this time (in the case of the windows job below anyway, I don't have the perms to view the mac ones). Do the installers need the same change you made with George yesterday?

Only the artifacts are failing to be copied across for JRE job. FYI @douph1

• https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-mac-x64-hotspot/613/console
• https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk14u/job/jdk14u-mac-x64-openj9-macosXL/101/console
• https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk14u/job/jdk14u-windows-x86-32-hotspot/98/console

23:18:39  Scheduling project: build-scripts » release » create_installer_windows
23:18:48  Starting building: build-scripts » release » create_installer_windows #4502
[Pipeline] copyArtifacts
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] echo
23:22:10  Execution error: Unable to get file permissions

We updated all of the jobs that were impacted (mac install, win installer, and sign release). Will need to do some more digging on this one. Let's meet up on slack

[M-Davies]

Seen again on https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-windows-x64-openj9/630/console
@Haroon-Khel @archanaNogriya Can this be reopened?

@karianna We never managed to meet up the other day to discuss this. Is today better for you?

[M-Davies]

From https://plugins.jenkins.io/copyartifact/

Specify projects who can copy artifacts

• Scripted pipeline

properties([
    copyArtifactPermission('job1,job2,...'),
]);
node {
    ...
}

• You can specify multiple jobs separated by commas.
• You can use wildcard character ('*') to specify name patterns.

After a quick search, we only seem to use,

copyArtifactPermissionProperty {
  projectNames('*')
}

not copyArtifactPermission. Is it possible that copyArtifactPermission is deprecated now that we've switched to Production mode @karianna ?

[karianna]

@M-Davies - It could well be, worth trying I reckon if you're happy to submit a PR?

[M-Davies]

Mac looks ok now. Windows is still having issues with this #1878 (comment)