Hmm, I lost the correct indentation in the message, but the yaml
indentation is correct in my project.
On Tuesday, April 28, 2020 at 2:56:40 PM UTC-4, David Warburton wrote:
>
> Hi mailing list,
>
> I'm building a pipeline for neural net training that needs to operate on
> around 650G of data using the kubernetes plugin to run agents in pods. In
> between builds I'd like the data to stick around in a persistent volume for
> the workspace. It seems like the persistentVolumeClaimWorkspaceVolume is
> perfect for this, but the way I have it configure is not working.
>
> Jenkinsfile:
>
> pipeline {
> agent {
>kubernetes {
> yamlFile 'jenkins/pv-pod.yaml'
> defaultContainer 'tree'
>}
> }
> options {
>podTemplate(workspaceVolume: persistentVolumeClaimWorkspaceVolume(
> claimName: 'workspace', readOnly: false))
> }
> stages {
>stage('read workspace') {
> steps {
>echo 'current env'
>sh 'env'
>sh '/usr/bin/tree'
>echo 'previous env'
>sh 'cat old-env.txt || true'
>sh 'env > old-env.txt'
> }
>}
> }
> }
>
> jenkins/pv-pod.yaml:
>
> apiVersion: v1
> kind: Pod
> spec:
> containers:
> - name: tree
> image: iankoulski/tree
> resources: {}
> command:
> - /bin/cat
> tty: true
>
>
> I have already defined the PersistentVolumeClaim and applied it to the
> same namespace the jenkins pods are running in (default)
> pv-claim.yaml:
>
> apiVersion: v1
> kind: PersistentVolumeClaim
> metadata:
> name: workspace
> spec:
> accessModes:
> - ReadWriteOnce
> resources:
> requests:
> storage: 100Gi
>
> Is there a mistake in this setup or have I misunderstood how this is
> supposed to work?
>
> Thanks
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/5faff1c4-60c9-4d10-8c6f-b08e420da769%40googlegroups.com.
