Creation of the remoteFs for a slave

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Creation of the remoteFs for a slave

Francis UPTON IV
For a slave, is the remoteFs (like /var/jenkins) supposed to be created by the user or by Jenkins? I can't find any code where Jenkins creates it, and the description in the ec2 plugin is not clear. Should the ec2-plugin create this if it's not present (this seems wrong to me)? If the user is supposed to create it, then I need to make sure that's documented in the ec2-plugin.

In my testing, the remote FS does not appear to be created by Jenkins anywhere. If Jenkins is supposed to create it, can someone point me to the code that does this?

Thanks,
Francis

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9a902585-860b-4e28-b660-3a3c2f1c26b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Creation of the remoteFs for a slave

Robert Sandell-2

2017-11-30 12:30 GMT+01:00 Francis UPTON IV <[hidden email]>:
For a slave, is the remoteFs (like /var/jenkins) supposed to be created by the user or by Jenkins? I can't find any code where Jenkins creates it, and the description in the ec2 plugin is not clear. Should the ec2-plugin create this if it's not present (this seems wrong to me)? If the user is supposed to create it, then I need to make sure that's documented in the ec2-plugin.

In my testing, the remote FS does not appear to be created by Jenkins anywhere. If Jenkins is supposed to create it, can someone point me to the code that does this?

Thanks,
Francis

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9a902585-860b-4e28-b660-3a3c2f1c26b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Robert Sandell
Software Engineer
CloudBees Inc.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS3K2FaXaScTcyxvoV8WFkoxasHeQQ5Ohkj8PKzJubhEJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Creation of the remoteFs for a slave

Oleg Nenashev
remoteFs should be automatically created by agents on-demand. Robert has pointed to the right part of the code.

However, there are some tricky bits with that...
  1. Jenkins agent is able to connect and ACCEPT RUNS even if RemoteFs is not writable
  2. The runs will obviously fail, but it won't prevent Jenkins from scheduling new Jobs to there
In order to fix this problem, in Remoting 3.8 I have introduced support of Work Directories. If an agent starts with with the "-workDir" flag, it will check write-ability of the work directory (which is equal to remoteFS for Java Web Start launchers) and fail if the directory is not writable.

In order to enable such behavior, EC2 plugin just needs to pass the "-workDir" flag when the Remoting version supports it (Jenkins 2.68+).

BR, Oleg

четверг, 30 ноября 2017 г., 15:41:30 UTC+3 пользователь Robert Sandell написал:
One example I found <a href="https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L1200" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fcore%2Fsrc%2Fmain%2Fjava%2Fhudson%2Fmodel%2FAbstractProject.java%23L1200\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFeTw3f0o5YgVidd2cjC0NWvMqSvg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fjenkins%2Fblob%2Fmaster%2Fcore%2Fsrc%2Fmain%2Fjava%2Fhudson%2Fmodel%2FAbstractProject.java%23L1200\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFeTw3f0o5YgVidd2cjC0NWvMqSvg&#39;;return true;">https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L1200

/B

2017-11-30 12:30 GMT+01:00 Francis UPTON IV <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="VfZVjck1BQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">fran...@...>:
For a slave, is the remoteFs (like /var/jenkins) supposed to be created by the user or by Jenkins? I can't find any code where Jenkins creates it, and the description in the ec2 plugin is not clear. Should the ec2-plugin create this if it's not present (this seems wrong to me)? If the user is supposed to create it, then I need to make sure that's documented in the ec2-plugin.

In my testing, the remote FS does not appear to be created by Jenkins anywhere. If Jenkins is supposed to create it, can someone point me to the code that does this?

Thanks,
Francis

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="VfZVjck1BQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/9a902585-860b-4e28-b660-3a3c2f1c26b9%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/9a902585-860b-4e28-b660-3a3c2f1c26b9%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/9a902585-860b-4e28-b660-3a3c2f1c26b9%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/9a902585-860b-4e28-b660-3a3c2f1c26b9%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.



--
Robert Sandell
Software Engineer
CloudBees Inc.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3ebcae03-2b41-4dd6-ae18-1835c6548a18%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.