[JIRA] (JENKINS-55611) Make EXECUTOR_NUMBER available for yaml definition
Title: Message Title Drum Big commented on JENKINS-55611 Re: Make EXECUTOR_NUMBER available for yaml definition hmm. Is it possible for the kubernetes plugin to allocate and provide some variable like this by itself? (Some kind of unique id that does not collide with other concurrent run, but is reused once the job is finished). 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-55611) Make EXECUTOR_NUMBER available for yaml definition
Title: Message Title
Drum Big commented on JENKINS-55611
Re: Make EXECUTOR_NUMBER available for yaml definition
I'm talking about the environment variable "EXECUTOR_NUMBER" that jenkins defined (see https://wiki.jenkins.io/display/JENKINS/Building+a+software+project) Basically, we would like to assign the pod with a PVC with name "workspace-cache-${env.JOB_NAME}-${env.EXECUTOR_NUMBER}", this name will be unique across all concurrent build. But it is still reusable for builds that are not overlapping in theirs durations. Does that make sense?
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-55611) Make EXECUTOR_NUMBER available for yaml definition
Title: Message Title Drum Big created an issue Jenkins / JENKINS-55611 Make EXECUTOR_NUMBER available for yaml definition Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-01-16 04:16 Priority: Minor Reporter: Drum Big We have a use case that we would like to attach persistent volume to the pod during the build (to store cache data). To support concurrent build, we would like to assign volume claim based on the EXECUTOR_NUMBER, so that different concurrent build can use different volume. Currently, this is impossible since EXECUTOR_NUMBER is not available in the agent definition. Add Comment
