[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title Rainer Weinhold commented on JENKINS-48067 Re: workspace-volume should be optional For me a part got 'fixed' when in one of the last Versions the EmptyDirectory got mounted at ~/agent instead of the ~ directory. But this won't fix the tools case. Which i'm currently not using, but I want, because of performance (time + traffic) issues, when with every new container Jenkins needs to download all tools again. Would it be possible to change the tools root folder to somthing like "~/agent-tools" ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186628.1510853986000.1545.1573807260530%40Atlassian.JIRA.
[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title
Alexander Komarov edited a comment on JENKINS-48067
Re: workspace-volume should be optional
Like many people here I pre-configure my docker images with everything including the autoinstalled contents of the [WORKDIR]/tools directory (maven, gradle, groovy, etc). This works great with the docker plugin, not so much with k8s.My current workaround is to move symlink the tools directory into the Working Directory in my ENTRYPOINT script if this is when running in k8s (my images are also used outside of k8s){code:java}NORMAL_WORKDIR=/data/jenkins-slaveif [ -n "$JENKINS_AGENT_WORKDIR" ] && [ "$JENKINS_AGENT_WORKDIR" != "$NORMAL_WORKDIR" ] ; then echo " Moving Linking preinstalled Jenkins tools into the active workdir: $JENKINS_AGENT_WORKDIR" mv ln -s $NORMAL_WORKDIR/tools $JENKINS_AGENT_WORKDIR/fi{code}(My ENTRYPOINT script is a wrapper around /usr/local/bin/jenkins-slave)
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186628.1510853986000.1433.1573763460507%40Atlassian.JIRA.
[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title
Alexander Komarov edited a comment on JENKINS-48067
Re: workspace-volume should be optional
Like many people here I pre-configure my docker images with everything including the autoinstalled contents of the [ WORKDIR ] /tools directory (maven, gradle, groovy, etc). This works great with the docker plugin, not so much with k8s.My current workaround is to move tools in my ENTRYPOINT script if this is k8s (my images are also used outside of k8s){code:java}NORMAL_WORKDIR=/data/jenkins-slaveif [ -n "$JENKINS_AGENT_WORKDIR" ] && [ "$JENKINS_AGENT_WORKDIR" != "$NORMAL_WORKDIR" ] ; then echo "Moving preinstalled Jenkins tools into the active workdir: $JENKINS_AGENT_WORKDIR" mv $NORMAL_WORKDIR/tools $JENKINS_AGENT_WORKDIR/fi{code}(My ENTRYPOINT script is a wrapper around /usr/local/bin/jenkins-slave)
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186628.1510853986000.1397.1573759740507%40Atlassian.JIRA.
[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title Alexander Komarov commented on JENKINS-48067 Re: workspace-volume should be optional Like many people here I pre-configure my docker images with everything including the WORKDIR/tools directory (maven, gradle, groovy, etc). This works great with the docker plugin, not so much with k8s. My current workaround is to move tools in my ENTRYPOINT script if this is k8s (my images are also used outside of k8s) NORMAL_WORKDIR=/data/jenkins-slave if [ -n "$JENKINS_AGENT_WORKDIR" ] && [ "$JENKINS_AGENT_WORKDIR" != "$NORMAL_WORKDIR" ] ; then echo "Moving preinstalled Jenkins tools into the active workdir: $JENKINS_AGENT_WORKDIR" mv $NORMAL_WORKDIR/tools $JENKINS_AGENT_WORKDIR/ fi (My ENTRYPOINT script is a wrapper around /usr/local/bin/jenkins-slave) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186628.1510853986000.1379.1573759681148%40Atlassian.JIRA.
[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-48067 workspace-volume should be optional Change By: Jesse Glick Assignee: Carlos Sanchez 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186628.1510853986000.13082.1563306226379%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title
Bernardo Corrêa edited a comment on JENKINS-48067
Re: workspace-volume should be optional
[~csanchez] Wouldn't adding subPath solve the issue (under Secret Volume)? Then we would be able to specify a subpath and mount secrets as shown bellow: {code:java}volumeMounts: - name: jenkins mountPath: "/home/jenkins/.npmrc" subPath: npmrc readOnly: false volumes: - name: jenkins secret: secretName: jenkins{code} We have a bunch of configuration files under JENKINS_HOME. Would also be nice to be able to have SecurityContext. Or if you have any suggestions on how to get around this issue... Or allowing users to change from emptyDir to secret or ConfigMap... Thanks in advance.
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-48067) workspace-volume should be optional
Title: Message Title
Bernardo Corrêa edited a comment on JENKINS-48067
Re: workspace-volume should be optional
[~csanchez] Wouldn't adding subPath solve the issue (under Secret Volume)? Then we would be able to specify a subpath and mount secrets as shown bellow: {code:java}volumeMounts: - name: jenkins mountPath: "/home/jenkins/.npmrc" subPath: npmrc readOnly: false volumes: - name: jenkins secret: secretName: jenkins{code} We have a bunch of configuration that go files under JENKINS_HOME. Would also be nice to be able to have SecurityContext. Or if you have any suggestions on how to get around this issue... Thanks in advance.
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-48067) workspace-volume should be optional
Title: Message Title Bernardo Corrêa commented on JENKINS-48067 Re: workspace-volume should be optional Carlos Sanchez Wouldn't adding subPath solve the issue (under Secret Volume)? Then we would be able to specify a subpath and mount secrets as shown bellow: volumeMounts: - name: jenkins mountPath: "/home/jenkins/.npmrc" subPath: npmrc readOnly: false volumes: - name: jenkins secret: secretName: jenkins We have a bunch of configuration that go under JENKINS_HOME. Would also be nice to be able to have SecurityContext. Or if you have any suggestions on how to get around this issue... Thanks in advance. 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-48067) workspace-volume should be optional
Title: Message Title Fran Garcia commented on JENKINS-48067 Re: workspace-volume should be optional Sometime after my first comment this was fixed for us but recently this behavior has been regressed. We are using Jenkins: 2.164.1. We thought the behavior had changed after updating to kubernetes-1.14.9, however we've tried downgrading it to 1.14.8 and the volume is still mounted over /home/jenkins. I don't see changes related to this issue on the changelog. Could this happen because of a change in a dependency? 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-48067) workspace-volume should be optional
Title: Message Title Jamison Greeley commented on JENKINS-48067 Re: workspace-volume should be optional This just bit me too. I don't want anything from my workspace after my build step, as it's all contained in the container which is built at the start of every run. The plugin is mounting workspace-volume on top of my working directory, which wipes out my app's code, leading to a crash loop where rails aborts ( Gemfile not found ), kills the pod, Jenkins reschedules it (because the pod contains a terminated container), and this keeps going until I manually abort the build. 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-48067) workspace-volume should be optional
Title: Message Title Rainer Weinhold commented on JENKINS-48067 Re: workspace-volume should be optional Love the idea with mounting the subfolder /home/jenkins/workspace, or basically just allow configuring the mountpoint. 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-48067) workspace-volume should be optional
Title: Message Title larsskj edited a comment on JENKINS-48067 Re: workspace-volume should be optional We're bitten by this as well: We really need to be able to preconfigure Jenkins home in the build containers we use.If the rationale for mounting a shared volume is to have a shared workspace, why not simply move the movepoint mountpoint to /home/jenkins/workspace?In that way we could build an image with a preconfigured Jenkins home and yet have a shared workspace. 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-48067) workspace-volume should be optional
Title: Message Title larsskj commented on JENKINS-48067 Re: workspace-volume should be optional We're bitten by this as well: We really need to be able to preconfigure Jenkins home in the build containers we use. If the rationale for mounting a shared volume is to have a shared workspace, why not simply move the movepoint to /home/jenkins/workspace? In that way we could build an image with a preconfigured Jenkins home and yet have a shared workspace. 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-48067) workspace-volume should be optional
Title: Message Title Stanley Shen commented on JENKINS-48067 Re: workspace-volume should be optional Is there any suggestion about this, if I pre-install something, and there are configurations under /home/ubuntu folder in my case? Thanks in advance. 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-48067) workspace-volume should be optional
Title: Message Title Carlos Sanchez commented on JENKINS-48067 Re: workspace-volume should be optional the workspace needs to be shared so all the containers can access for instance a git checkout 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-48067) workspace-volume should be optional
Title: Message Title Stanley Shen commented on JENKINS-48067 Re: workspace-volume should be optional I am new to kubernetes plugin on jenkins, and unfortunately I am using a customized docker image, and I install something under my user(ubuntu), for example the rvm. But when the pod is running, jenkins always try to install rvm because of it cannot find rvm related things under the home path of ubuntu user. It takes me quite lot time to figure out this fact that the home path of login user is mount by another emptyDir, thus the customization like rvm is always not there. I agree this one is quite a huge drawback for user 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-48067) workspace-volume should be optional
Title: Message Title Raphael Fraysse commented on JENKINS-48067 Re: workspace-volume should be optional Hello, We also have the same issue and while trying a lot of workarounds, we didn't manage to redirect the workspace to another directory while getting Jenkins to run in a non emptyDir volume. Persistent volume is not the solution to our problem as it adds more complexity to our clusters. Please make it so we can disable this workspace automated volume creation. Hardcoding this and not letting users to change it is a huge drawback to use Kubernetes pods slaves. Sincerely, Raphael Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
