-
-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Couldn't compile the CSS from LESS sources" if plugin is located on network folder #183
Comments
Hey @adaubner and thanks for reporting this. What version of java are you running your Jenkins on? And what version of Jenkins do you have? |
Hi Jan. Since yesterday we are running on Java 8u65. Best regards, Andreas Daubner Pepperl+Fuchs GmbH E-Mail: adaubner@de.pepperl-fuchs.commailto:adaubner@de.pepperl-fuchs.com Von: Jan Molak [mailto:notifications@github.com] Hey @adaubnerhttps://github.com/adaubner and thanks for reporting this. What version of java are you running your Jenkins on? — [e-news abonnieren]http://www.pepperl-fuchs.de/e-news [YouTube: Pepperl+Fuchs auf YouTube] http://www.youtube.com/user/PepperlFuchsGmbH [@PepperlFuchsDE folgen] https://twitter.com/PepperlFuchsDE [Pepperl+Fuchs auf XING] https://www.xing.com/companies/pepperl%252bfuchsgmbh [Pepperl+Fuchs GmbH]http://www.pepperl-fuchs.com SocialMedia2014 Pepperl+Fuchs GmbH, Mannheim Wichtiger Hinweis: |
@adaubner - would you like to check if the latest version - 1.6+build.168 - resolved the issue for you? Two things worth noting:
Please note: The version of Build Monitor mentioned in this ticket is not yet available on Jenkins Update Centre as it's a "beta" released to gather early feedback (changelog). Looking forward to hearing from you! Jan |
Hi Jan. Sorry, it´s not working yet: Nov 18, 2015 2:15:51 PM jenkins.InitReactorRunner$1 onTaskFailed After a short look at google, this has to do with the UNC path. ☹ Best regards, Von: Jan Molak [mailto:notifications@github.com] @adaubnerhttps://github.com/adaubner - would you like to check if the latest version - 1.6+build.168https://smartcode-opensource.ci.cloudbees.com/job/jenkins-build-monitor-plugin/168/artifact/target/build-monitor-plugin.hpi - resolved the issue for you? Two things worth noting:
Please note: The version of Build Monitor mentioned in this ticket is not yet available on Jenkins Update Centre as it's a "beta" released to gather early feedback (changeloghttps://github.com/jan-molak/jenkins-build-monitor-plugin/compare/release-1.6+build.164...release-1.6+build.168). Looking forward to hearing from you! Jan — [e-news abonnieren]http://www.pepperl-fuchs.de/e-news [YouTube: Pepperl+Fuchs auf YouTube] http://www.youtube.com/user/PepperlFuchsGmbH [@PepperlFuchsDE folgen] https://twitter.com/PepperlFuchsDE [Pepperl+Fuchs auf XING] https://www.xing.com/companies/pepperl%252bfuchsgmbh [Pepperl+Fuchs GmbH]http://www.pepperl-fuchs.com SocialMedia2014 Pepperl+Fuchs GmbH, Mannheim Wichtiger Hinweis: |
… the one applied in SBT: sbt/sbt#564) Build Monitor should load its LESS CSS assets correctly from a mapped network folder defined as a UNC path on Windows as long as: - Build Monitor runs on Jenkins 1.598 or later (due to a bug in Jenkins prior to that version: http://jenkins-ci.org/changelog#v1.598) - Jenkins runs on Java 7 u60 or later (due to a bug in Java prior to that version: http://bugs.java.com/view_bug.do?bug_id=8014394) Fixes #183
Hey Andreas, Yes, you're correct. The problem is caused by the Java File class not handling the Windows UNC paths correctly. As mentioned in my previous post, Java 7 update 60 fixed this problem, and if you're using Jenkins >= 1.598 it can use that fix. Many thanks for reporting the second problem, the one with the The latest build (1.6+build.169, available here) should work around that problem. Please give it a try and let me know your thoughts! Looking forward to hearing from you, |
Hello Jan. Good news. The new version works! Great job. Best regards, Von: Jan Molak [mailto:notifications@github.com] Hey Andreas, Yes, you're correct. The problem is caused by the Java File class not handling the Windows UNC paths correctly. As mentioned in my previous post, Java 7 update 60 fixed this problem, and if you're using Jenkins >= 1.598 it can use that fix. Many thanks for reporting the second problem, the one with the authority. This seems to be caused by a different issue with the File class, and the way it's interacting with the URI class... Oh joy ;-) The latest build (1.6+build.169, available herehttps://smartcode-opensource.ci.cloudbees.com/job/jenkins-build-monitor-plugin/169/artifact/target/build-monitor-plugin.hpi) should work around that problem. Please give it a try and let me know your thoughts! Looking forward to hearing from you, — [e-news abonnieren]http://www.pepperl-fuchs.de/e-news [YouTube: Pepperl+Fuchs auf YouTube] http://www.youtube.com/user/PepperlFuchsGmbH [@PepperlFuchsDE folgen] https://twitter.com/PepperlFuchsDE [Pepperl+Fuchs auf XING] https://www.xing.com/companies/pepperl%252bfuchsgmbh [Pepperl+Fuchs GmbH]http://www.pepperl-fuchs.com SocialMedia2014 Pepperl+Fuchs GmbH, Mannheim Wichtiger Hinweis: |
Excellent! Thanks for your help with testing :-) |
When installing the build monitor plugin on my Jenkins system I receive the following error in the log:
The Jenkins working directory including the plugins is located on a network share, which is accessed by UNC path:
\[Host]\[Share]\[Folder]\Jenkins\testjenkins\plugins\build-monitor-plugin\less\index.less
The path is displayed in the error message with only one leading backslash, instead of two.
If you need more details, please let me know.
Would be great if you could fix that.
The text was updated successfully, but these errors were encountered: