[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cbi-dev] /home/jenkins/.m2 is read-only in orb-gmbal-pfl-release-build project
|
(also, of course the jobs have write permission on the ~/.m2/repository folder)
Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation 🐦 @mikbarbero
Hi Russel,
You don't need to do that anymore. We have a toolchains.xml automatically mounted with the proper values. Current content can be found here https://github.com/eclipse-cbi/jiro/blob/master/templates/k8s/m2-dir.libsonnet
Cheers,
Mikaël Barbero
Team Lead - Release Engineering | Eclipse Foundation 🐦 @mikbarbero
Hi,
I am an administrator on this projec , and we are now attempting to do a release for the first time in over a year. The project uses maven, which needs to write at least into the .m2/repository directory. In addition, it requires a toolchain, so we need a way to copy a file from the project into some location that can be accessed during the build. In the past, that location was /home/jenkins/.m2.
Now, however, any attempt to do so results in the error:
+ cp eclipse-jenkins/toolchains.xml /home/jenkins/.m2
cp: cannot create regular file '/home/jenkins/.m2/toolchains.xml': Read-only file system
I suspect that there is something wrong with the Kubernetes Pod configuration; specifically, the volume mounts. How do I change them? It’s using subpath, when it is not necessary and not designating the volumes as writeable.
Thanks, Russ _______________________________________________ cbi-dev mailing list cbi-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cbi-dev
|
Attachment:
signature.asc
Description: Message signed with OpenPGP
