[JIRA] (JENKINS-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"
Title: Message Title Nikolas Falco closed an issue as Fixed Thank you Jenkins / JENKINS-27170 "Provide Node & npm bin/ folder to PATH" not working for "npm install" Change By: Nikolas Falco Status: Reopened Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"
Title: Message Title Nikolas Falco edited a comment on JENKINS-27170 Re: "Provide Node & npm bin/ folder to PATH" not working for "npm install" Do you have EnvInject plugin installed?If yes than also you have fall in JENKINS-26583The 0.2.2 use a different way (and old) to inject node js in PATH variable that cause similar problem to other plugins. Workaround is remove EnvInject plugin, or make a custom build of workaround-26583 branch. (this branch will never merge into master, it's a EnvInject plugin issue not nodejs) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"
Title: Message Title Nikolas Falco edited a comment on JENKINS-27170 Re: "Provide Node & npm bin/ folder to PATH" not working for "npm install" Do you have EnvInject plugin installed?If yes than also you have fall in JENKINS-26583The 0.2.2 use a different old way (and old) to inject node js in PATH variable that cause problem similar problem to other plugin plugins . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"
Title: Message Title Nikolas Falco commented on JENKINS-27170 Re: "Provide Node & npm bin/ folder to PATH" not working for "npm install" Do you have EnvInject plugin installed? If yes than also you have fall in JENKINS-26583 The 0.2.2 use a different old way to inject node js in PATH variable that cause problem similar problem to other plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40624) nodejs installer not compatible with declarative pipeline definition
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-40624 nodejs installer not compatible with declarative pipeline definition Change By: Nikolas Falco Assignee: Dominik Bartholdi Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40624) nodejs installer not compatible with declarative pipeline definition
Title: Message Title Nikolas Falco started work on JENKINS-40624 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-20636) RVM and NodeJS plugins are incompatible
Title: Message Title Nikolas Falco edited a comment on JENKINS-20636 Re: RVM and NodeJS plugins are incompatible PATH enviroment is correctly setup using override method of EnvVars that append the PATH to the current PATH value.Pay attention to JENKINS-26583 caused by EnvInjectPlugin ( by your logs appear in the issue log ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-20636) RVM and NodeJS plugins are incompatible
Title: Message Title Nikolas Falco resolved as Fixed PATH enviroment is correctly setup using override method of EnvVars that append the PATH to the current PATH value. Pay attention to JENKINS-26583 caused by EnvInjectPlugin (by your logs) Jenkins / JENKINS-20636 RVM and NodeJS plugins are incompatible Change By: Nikolas Falco Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-20636) RVM and NodeJS plugins are incompatible
Title: Message Title Nikolas Falco commented on JENKINS-20636 Re: RVM and NodeJS plugins are incompatible Please update to the last release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-24381) NodeJS Plugin runs auto-install while other dependant jobs are running, breaking builds
Title: Message Title Nikolas Falco commented on JENKINS-24381 Re: NodeJS Plugin runs auto-install while other dependant jobs are running, breaking builds Very interesting issue. NodeJS installer delegates installation of archives to the DownloadFromUrlInstaller (as Maven, Ant and other do). In DownloadFromUrlInstaller I didn't notice any semaphore so, if you run more jobs at the same time on a jenkins node where that tool is not installed, they will try to perform install together. For this use case I think it's better open a issue to jenkins core component. In any case NodeJS decorates the installer with an extra step that provides installation of a list global npm packages. Reading your use case, seems that, when the refresh time (72 hours by default) expires and you run more jobs together, all of them perform a npm update of the global packages and maybe this could cause the concurrency issue. I could add a semaphore during the check of "are packages update?". Anyway this is not clear ... and all of the jobs try to use a package that has been removed by first the auto-install process. Supposing the same Node installer (this means same list of global packages) and more jobs running contemporaneously, how can the installer triggered by Job A remove a global package that the installer of job B would not have removed? Are you performing a npm install -g command in the job script? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You
[JIRA] (JENKINS-24381) NodeJS Plugin runs auto-install while other dependant jobs are running, breaking builds
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-24381 NodeJS Plugin runs auto-install while other dependant jobs are running, breaking builds Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27513) Nodejs plugin breaks node's require() mechanism
Title: Message Title Nikolas Falco commented on JENKINS-27513 Re: Nodejs plugin breaks node's require() mechanism Please provide in enviroment field a jenkins and plugin and OS version you are using. script in a "Execute Shell" / "Execute Windows batch command" build step is create in a tmp folder by design. Than the shell script is execute with workspace as basedir so when you perform a npm install/update/run build takes care of node_modules/ folder in the workspace folder not in tmp. Actually all our NodeJS projects (angularJS SPA or npm library) works without any trick, in the same manner you build the project in develop enviroment. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27513) Nodejs plugin breaks node's require() mechanism
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-27513 Nodejs plugin breaks node's require() mechanism Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-28117) NodeJS err=13; permission denied on fedora20
Title: Message Title Nikolas Falco commented on JENKINS-28117 Re: NodeJS err=13; permission denied on fedora20 Please update to recent version. The NodeJSInstaller delegates (except for msi) install to the standard DownloadFromUrlInstaller class (as Maven and Ant does). The download is performed in the Jenkins tools folder where is unzipped, no tmp is used. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-28117) NodeJS err=13; permission denied on fedora20
Title: Message Title Nikolas Falco edited a comment on JENKINS-28117 Re: NodeJS err=13; permission denied on fedora20 Please update to recent version.The NodeJSInstaller delegates (except for msi) install to the standard DownloadFromUrlInstaller class (as Maven and Ant does). The download is performed in the Jenkins tools folder where is unzipped, no tmp is used. Please provide also a plugin version. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-29172) NodeJS plugin attempts to unlink /usr/bin/npm; there is no way to set the auto-refresh to 'never'
Title: Message Title Nikolas Falco closed an issue as Fixed You have a nodejs installed in the system. When you launch a build after 72 hours it run again the npm command to update global packages. Instead to run the npm in the Jenkins tools folder it run the system nodejs updating wrong installation. Use last release please to fix this issue. Jenkins / JENKINS-29172 NodeJS plugin attempts to unlink /usr/bin/npm; there is no way to set the auto-refresh to 'never' Change By: Nikolas Falco Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-26583) Env-inject plugin suppress variables contributed by extension points
Title: Message Title Nikolas Falco commented on JENKINS-26583 Re: Env-inject plugin suppress variables contributed by extension points Sorry, I've rename personal branch for a dedicated workarounf on NodeJS plugin so JIRA should not bother anymore Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-29077) No selector is shown for installing NodeJS from nodejs.org
Title: Message Title Nikolas Falco closed an issue as Duplicate Jenkins / JENKINS-29077 No selector is shown for installing NodeJS from nodejs.org Change By: Nikolas Falco Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-28491) npm ERR! Linux 3.2.0-4-amd64 - Add version 0.12.4 in auto install
Title: Message Title Nikolas Falco closed an issue as Fixed Jenkins / JENKINS-28491 npm ERR! Linux 3.2.0-4-amd64 - Add version 0.12.4 in auto install Change By: Nikolas Falco Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-21953) NodeJs plugin doesn't work on windows based Jenkins machine
Title: Message Title Nikolas Falco edited a comment on JENKINS-21953 Re: NodeJs plugin doesn't work on windows based Jenkins machine Windows support As declared in wiki page windows was not supported.Support was added with on JENKINS-26828 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-21953) NodeJs plugin doesn't work on windows based Jenkins machine
Title: Message Title Nikolas Falco closed an issue as Fixed Windows support added with JENKINS-26828 Jenkins / JENKINS-21953 NodeJs plugin doesn't work on windows based Jenkins machine Change By: Nikolas Falco Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-21953) NodeJs plugin doesn't work on windows based Jenkins machine
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-21953 NodeJs plugin doesn't work on windows based Jenkins machine Change By: Nikolas Falco Assignee: Deluan Quintão Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco commented on JENKINS-22102 Re: NodeJS plugin does not remember the saved "NodeJS Installation" Released in 1.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-26828) Add support for installing the NodeJS windows msi
Title: Message Title Nikolas Falco commented on JENKINS-26828 Re: Add support for installing the NodeJS windows msi Release 1.0 with windows support Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-21726) Nodejs path not set correctly when running on Windows master, linux slave
Title: Message Title Nikolas Falco closed an issue as Fixed Verified on windows 7 and vs (windows master, macos slave) Jenkins / JENKINS-21726 Nodejs path not set correctly when running on Windows master, linux slave Change By: Nikolas Falco Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-30134) java.lang.ArrayIndexOutOfBoundsException: 2 error
Title: Message Title Nikolas Falco closed an issue as Fixed Jenkins / JENKINS-30134 java.lang.ArrayIndexOutOfBoundsException: 2 error Change By: Nikolas Falco Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31485) NodeJS Invalid Tool ID
Title: Message Title Nikolas Falco commented on JENKINS-31485 Re: NodeJS Invalid Tool ID Try new version 1.0 please Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-30380) Downloads of NodeJS binaries are now in https
Title: Message Title Nikolas Falco closed an issue as Fixed Verified Jenkins / JENKINS-30380 Downloads of NodeJS binaries are now in https Change By: Nikolas Falco Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31945) Cannot find dropdown list for NodeJS plugin
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-31945 Cannot find dropdown list for NodeJS plugin Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31945) Cannot find dropdown list for NodeJS plugin
Title: Message Title Nikolas Falco commented on JENKINS-31945 Re: Cannot find dropdown list for NodeJS plugin Try the new 1.0 release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-33698) NodeJS plugin npm install without root permissions
Title: Message Title Nikolas Falco closed an issue as Duplicate Jenkins / JENKINS-33698 NodeJS plugin npm install without root permissions Change By: Nikolas Falco Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco closed an issue as Fixed Released in 1.0 Jenkins / JENKINS-40364 Support npm configuration file Change By: Nikolas Falco Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-26583) Env-inject plugin suppress variables contributed by extension points
Title: Message Title Nikolas Falco commented on JENKINS-26583 Re: Env-inject plugin suppress variables contributed by extension points any news on this?? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-22102 NodeJS plugin does not remember the saved "NodeJS Installation" Change By: Nikolas Falco Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco updated JENKINS-22102 Jenkins / JENKINS-22102 NodeJS plugin does not remember the saved "NodeJS Installation" Change By: Nikolas Falco Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-31945) Cannot find dropdown list for NodeJS plugin
Title: Message Title Nikolas Falco commented on JENKINS-31945 Re: Cannot find dropdown list for NodeJS plugin This is already resolve in master code. Also Jenkins 2x is supported. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35182) Support credential plugin to handle publish
Title: Message Title Nikolas Falco closed an issue as Fixed The JENKINS-40364 provides setup of registry and credentials to use. Jenkins / JENKINS-35182 Support credential plugin to handle publish Change By: Nikolas Falco Status: Open Closed Assignee: Nikolas Falco Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because
[JIRA] (JENKINS-36166) Internal Server Error on creating new job from Jenkins API written in Node.js
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-36166
Internal Server Error on creating new job from Jenkins API written in Node.js
Change By:
Nikolas Falco
I'm using Node JS version 5.10.I could build a job in Jenkins using Jenkins API written in Node.js from my MEAN stack application. I got the Internal server error (500) while creating a new job using *Jenkins API written in Node.js*, i used config.xml of already created job (which was directly created in Jenkins) with new Job Name.I used Jenkins and Jenkins-api modules in NodeJs.Sample code:{code:_javascript_}var jenkinsapi2 = require('jenkins');var jenkinsapi = require('jenkins-api');var jenkins = jenkinsapi.init("http://username:password@ip:8080/");var jenkins2 = require('jenkins')("http://username:password@ip:8080/");var config = __dirname +'../config/config.xml'; // config.xml file of directly created job in jenkins/*using Jenkins-api*/jenkins2.job.create('test', config, function(err) {if (err){ throw err;}console.log("success"); });/*using Jenkins*/ jenkins.create_job('test', config, function(err, data) { if (err) { console.log(err); // throw err; } console.log("success"); });{code}I used the sample config.xml file as :{code:xml} false true false false falsefalse {code}And i'm getting the an issue as :{noformat}java.io.IOException: Failed to persist config.xml\n\tat hudson.model.ItemGroupMixIn.createProjectFromXML(ItemGroupMixIn.java:299)\n\tat hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:194)\n\tat jenkins.model.Jenkins.doCreateItem(Jenkins.java:3102)\n\tat jenkins.model.Jenkins.doCreateItem(Jenkins.java:308)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat java.lang.reflect.Method.invoke(Method.java:606)\n\tat org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320)\n\tat org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163)\n\tat org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)\n\tat org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)\n\tat org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)\n\tat org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)\n\tat org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)\n\tat org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)\n\tat org.kohsuke.stapler.Stapler.service(Stapler.java:238)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:848)\n\tat org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)\n\tat org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)\n\tat hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)\n\tat hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126)\n\tat
[JIRA] (JENKINS-36166) Internal Server Error on creating new job from Jenkins API written in Node.js
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-36166
Internal Server Error on creating new job from Jenkins API written in Node.js
Change By:
Nikolas Falco
I'm using Node JS version 5.10.I could build a job in Jenkins using Jenkins API written in Node.js from my MEAN stack application. I got the Internal server error (500) while creating a new job using *Jenkins API written in Node.js*, i used config.xml of already created job (which was directly created in Jenkins) with new Job Name.I used Jenkins and Jenkins-api modules in NodeJs.Sample code: {code:_javascript_} var jenkinsapi2 = require('jenkins');var jenkinsapi = require('jenkins-api');var jenkins = jenkinsapi.init("http://username:password@ip:8080/");var jenkins2 = require('jenkins')("http://username:password@ip:8080/");var config = __dirname +'../config/config.xml'; // config.xml file of directly created job in jenkins/*using Jenkins-api*/jenkins2.job.create('test', config, function(err) {if (err){ throw err;}console.log("success"); });/*using Jenkins*/ jenkins.create_job('test', config, function(err, data) { if (err) { console.log(err); // throw err; } console.log("success"); }); {code} I used the sample config.xml file as : {code:xml} false true false false falsefalse {code} And i'm getting the issue as : {noformat} Stack trace java.io.IOException: Failed to persist config.xml\n\tat hudson.model.ItemGroupMixIn.createProjectFromXML(ItemGroupMixIn.java:299)\n\tat hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:194)\n\tat jenkins.model.Jenkins.doCreateItem(Jenkins.java:3102)\n\tat jenkins.model.Jenkins.doCreateItem(Jenkins.java:308)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n\tat sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)\n\tat sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)\n\tat java.lang.reflect.Method.invoke(Method.java:606)\n\tat org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320)\n\tat org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163)\n\tat org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)\n\tat org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)\n\tat org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)\n\tat org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)\n\tat org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)\n\tat org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)\n\tat org.kohsuke.stapler.Stapler.service(Stapler.java:238)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:848)\n\tat org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)\n\tat org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)\n\tat hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)\n\tat hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126)\n\tat
[JIRA] (JENKINS-38188) The filename, directory name, or volume label syntax is incorrect when running the apigeetool command on build step
Title: Message Title Nikolas Falco commented on JENKINS-38188 Re: The filename, directory name, or volume label syntax is incorrect when running the apigeetool command on build step Why NodeJS should involved in this? Which version fo NodeJS plugin do you use? Do you enable NodeJS action to have Nodejs.exe in the PATH enviroment? In this scenario NodeJS plugin only provide a NodeJS installation and node.exe to the classpath. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-30615) Allow specifying global NMP settings
Title: Message Title Nikolas Falco closed an issue as Fixed This feature is totally supported by implementation of JENKINS-40364 Jenkins / JENKINS-30615 Allow specifying global NMP settings Change By: Nikolas Falco Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-41291) Implement a select widget to show configuration in custom Builder
Title: Message Title Nikolas Falco commented on JENKINS-41291 Re: Implement a select widget to show configuration in custom Builder This issue it's just to keep track of discussion in JENKINS-40364 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41291) Implement a select widget to show configuration in custom Builder
Title: Message Title
Nikolas Falco created an issue
Jenkins / JENKINS-41291
Implement a select widget to show configuration in custom Builder
Issue Type:
New Feature
Assignee:
Dominik Bartholdi
Components:
config-file-provider-plugin
Created:
2017/Jan/22 8:57 PM
Environment:
config-file-provider-plugin 2.15.5 Jenkins 1.625.3
Priority:
Minor
Reporter:
Nikolas Falco
If I would integrate in a build step the choosen of a config file to use (similar settings.xml in Maven step) actually I have to do a lot of manual work to properly render an HTML select with a filtered list of config and eventually manage verification of file content. So i ask to implement a custom select jelly widget (like that credential plugin) to facilitate integrations of configuration in custom build step/wrapper a sort of
xmlns:cf="/lib/configfiles">
"${%Config File}" field="configId">
"${descriptor.class}" includeEmpty="true" />
This widget attributes could be:
field - Used for databinding.
filter - (optional) list only configuration that match this FQN of descriptor class
default - default value of the text box, in case both @value is and 'instance[field]' is null.
includeEmpty - an empty
[JIRA] (JENKINS-41289) Create a shared jelly page for commons attribute of config to use in view mode
Title: Message Title Nikolas Falco commented on JENKINS-41289 Re: Create a shared jelly page for commons attribute of config to use in view mode This issue it's just to keep track of discussion in JENKINS-40364 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41289) Create a shared jelly page for commons attribute of config to use in view mode
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-41289 Create a shared jelly page for commons attribute of config to use in view mode Issue Type: Improvement Assignee: Dominik Bartholdi Components: config-file-provider-plugin Created: 2017/Jan/22 8:34 PM Environment: config-file-provider-plugin 2.15.5 Jenkins 1.625.3 Priority: Minor Reporter: Nikolas Falco Create a shared jelly page for common attributes of config to use in view mode A config extension point must implement the edit-config.jelly to render attributes of configuration. Most of actual implementation in the edit jelly includes a page named id-name-and-comment that render in a standard way common attributes but from what I can see instead for show-config.jelly file common fields are rewritten from scratch (with readonly attribute). Creating a similar jelly page it's a good way to render common attributes for view mode in the same manner of all extension points (however a user always can customize) inheriting translations or other behaviours.
[JIRA] (JENKINS-41288) Maven settings of configs are editable in view mode
Title: Message Title Nikolas Falco commented on JENKINS-41288 Re: Maven settings of configs are editable in view mode This issue it's just to keep track of discussion in JENKINS-40364 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41288) Maven settings of configs are editable in view mode
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-41288 Maven settings of configs are editable in view mode Issue Type: Bug Assignee: Dominik Bartholdi Components: config-file-provider-plugin Created: 2017/Jan/22 8:20 PM Environment: config-file-provider-plugin 2.15.5 Jenkins 1.625.3 Priority: Trivial Reporter: Nikolas Falco When you enable "Provide Configuration files" in "Build environment" and add a new file and click "view selected file", server credentials fields of Maven Settings and Maven Global Settings are editable instead readonly. Add Comment
[JIRA] (JENKINS-41258) Config File Provider Plugin doesn't update files
Title: Message Title Nikolas Falco commented on JENKINS-41258 Re: Config File Provider Plugin doesn't update files Duplicate of JENKINS-41202 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco edited a comment on JENKINS-40364 Re: Support npm configuration file Thanks very much to you for support. I will release actual implementations and than will update to when new API be available I will change it . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco commented on JENKINS-40364 Re: Support npm configuration file Thanks very much to you for support. I will release actual implementations and than will update to new API. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title
Nikolas Falco edited a comment on JENKINS-40364
Re: Support npm configuration file
# I got it. I've fixedJust a question: your edit-config.jelly files includes a page named _id-name-and-comment_ for the common attributes but from what I can see instead for show-config.jelly file common fields are rewritten from scratch (with readonly attribute). What do you think to create a common page also for view mode? so for example translations are inherited or changes to the base page will be reported to all extension point for free. (Please note that in 2.15.5 server credentials of maven settings in view mode are editable)# I mean imagine that a user creates 10 new configuration and 50% of them are not valid. When user will configure the NodeJS step in a jenkins job he will see only 5 configuration in the combobox, not 10. How can user understand that missing configuration in combobox is becuase configuration are not valid and not a plugin bug?I have resolved doing a select widget (a dirty html/css work) that invoke a doCheckXyz method on Build descriptor delegating the task of verification on Config implementation. !config-file-validation.png|thumbnail! Could I suggest:* +implement a custom select jelly widget (like that credential plugin) to facilitate integrations of configuration in custom build step/wrapper a sort of+{code:xml} {code}* add a verify method on Config base class (by default empty {} ) so each implementation could have an own logic (for example XML/JSON check well-formed) and this The verify method is on the "interface" and could be also used to validate the content during _supplyFile_ method after token replace. This reduce user analisys on build failure. Keept in mind that in this way we could enforce the same failure behavior when the configuration file is handled directly by a custom build step (like maven or NodeJS) or ConfigFileBuildWrapper is used.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40364) Support npm configuration file
Title: Message Title
Nikolas Falco commented on JENKINS-40364
Re: Support npm configuration file
I got it. I've fixed Just a question: your edit-config.jelly files includes a page named id-name-and-comment for the common attributes but from what I can see instead for show-config.jelly file common fields are rewritten from scratch (with readonly attribute). What do you think to create a common page also for view mode? so for example translations are inherited or changes to the base page will be reported to all extension point for free. (Please note that in 2.15.5 server credentials of maven settings in view mode are editable)
I mean imagine that a user creates 10 new configuration and 50% of them are not valid. When user will configure the NodeJS step in a jenkins job he will see only 5 configuration in the combobox, not 10. How can user understand that missing configuration in combobox is becuase configuration are not valid and not a plugin bug? I have resolved doing a select widget (a dirty html/css work) that invoke a doCheckXyz method on Build descriptor delegating the task of verification on Config implementation.
Could I suggest:
implement a custom select jelly widget (like that credential plugin) to facilitate integrations of configuration in custom build step/wrapper a sort of
xmlns:cf="/lib/configfiles">
"${%Config File}" field="configId">
"${descriptor.class}" allowEmpty="true" />
add a verify method on Config base class (by default empty {} ) so each implementation could have an own logic (for example XML/JSON check well-formed) and this method is on the "interface" and could be also used to validate the content during supplyFile method after token replace. This reduce user analisys on build failure.
Add Comment
[JIRA] (JENKINS-40364) Support npm configuration file
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-40364 Support npm configuration file Change By: Nikolas Falco Attachment: config-file-validation.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco commented on JENKINS-40364 Re: Support npm configuration file release must be posticipate to depends on the minimun working version of this config-file plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-40364 Support npm configuration file Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco commented on JENKINS-40364 Re: Support npm configuration file Dominik Bartholdi I have a severe issue with 2.15.4 (2.13 works), when I create a new config file it is persistend fine but any chages on that configuration is no more persisted. This issue does not happens only on my custom configuration but also with other files. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco commented on JENKINS-40364 Re: Support npm configuration file Dominik Bartholdi thanks for short answer. About first question I did not intent how to test by junit, but how I could see the view mode of a configuration. I had try enable security, add a new configuration with admin, but no way other users could access in manage jenkins to see the configured files. Which is the use case when the view.jelly is invoked? 2) Actually in the job configuration when you choose NodeJS step there is a combo box to choose the configuration file (like maven does for global and settings.xml) Do you mean propose in the combobox only valid configuration? In this case how does user understand that configuration is wrong instead a bug of plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-40364 Support npm configuration file Change By: Nikolas Falco Attachment: build-step.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco commented on JENKINS-40364 Re: Support npm configuration file Thanks Dominik Bartholdi for availability. I've complete task a week ago and I'm just write test cases. But I have two question for you: How test the jellys view of configuration files? Is it possible implement a doCheck method of config file descriptor to disable submit button until (FormValidation?) is ok? The reason I would check that only a NPM registry could be set as global (a.k.a. without any scope). I know that I could check anything using _javascript_ but I would avoid that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-40364 Support npm configuration file Change By: Nikolas Falco Attachment: config page.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco commented on JENKINS-40364 Re: Support npm configuration file Miss only test cases. I have implement against config-file-plugin 2.13 becuase initially with latest version 2.15.3 fails render config jelly files. If do you have free time any option will be appreciated. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco started work on JENKINS-40364 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-14807) AbstractBuild.getEnvironment does not set EnvVars.platform and breaks EnvVars.override
Title: Message Title
Nikolas Falco commented on JENKINS-14807
Re: AbstractBuild.getEnvironment does not set EnvVars.platform and breaks EnvVars.override
This 2012 bug hit again (nodejs plugin). It break all SimpleBuildWrapper that override PATH+VAR launched on node with different platform (Unix->Windows and vs). The issue seems to be in Run#getEnvironment(TaskListener) that returns an enviroment EnvVars not built from Computer class (the unique way to have platform field setup correctly)
Run.java
* Unlike earlier {@link #getEnvVars()}, this map contains the whole environment,
* not just the overrides, so one can introspect values to change its behavior.
* ...
*/
public @Nonnull EnvVars getEnvironment(@Nonnull TaskListener listener) throws IOException, InterruptedException {
Computer c = Computer.currentComputer();
Node n = c==null ? null : c.getNode();
EnvVars env = getParent().getEnvironment(n,listener);
env.putAll(getCharacteristicEnvVars());
...
}
I think that something similar fix the issue
Run.java
public @Nonnull EnvVars getEnvironment(@Nonnull TaskListener listener) throws IOException, InterruptedException {
Computer c = Computer.currentComputer();
Node n = c==null ? null : c.getNode();
EnvVars env = c.getEnvironment();
env = env.putAll(getParent().getEnvironment(n,listener));
env.putAll(getCharacteristicEnvVars());
...
}
untill a fix is released my dirty workaround is create a EnvironmentContributor that by reflection inject correct platform value
FixEnvVarEnvironmentContributor.java
@Extension(ordinal = -200)
public class FixEnvVarEnvironmentContributor extends EnvironmentContributor {
@Override
public void buildEnvironmentFor(@SuppressWarnings("rawtypes") @Nonnull Run run, @Nonnull EnvVars envs, @Nonnull TaskListener listener) throws IOException, InterruptedException {
Computer c = Computer.currentComputer();
if (c != null) {
Field platformField = ReflectionUtils.findField(EnvVars.class, "platform", Platform.class);
ReflectionUtils.makeAccessible(platformField);
Platform currentPlatform = (Platform) ReflectionUtils.getField(platformField, envs);
if (currentPlatform == null) {
[JIRA] (JENKINS-40752) Server Credentials remove the configuration element
Title: Message Title Nikolas Falco commented on JENKINS-40752 Re: Server Credentials remove the configuration element This bug is a duplicate of JENKINS-39991. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco commented on JENKINS-40364 Re: Support npm configuration file Ok, great. I Will have a look into a short Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-30615) Allow specifying global NMP settings
Title: Message Title
Nikolas Falco commented on JENKINS-30615
Re: Allow specifying global NMP settings
Just now a workaround you could use config-file-plugin. Configure a "Custom file", put there your npm settings and then in the job configuration enable Provide Configuration files settings and as target put $ {WORKSPACE} /.npmrc That location is one of 4/5 default location where npm lookup for the configuration file. That file will be deleted after jenkins job ends or is stopped.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-30615) Allow specifying global NMP settings
Title: Message Title Nikolas Falco commented on JENKINS-30615 Re: Allow specifying global NMP settings For portable and secure configuration the config-file-plugin could be useful Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40364) Support npm configuration file
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-40364 Support npm configuration file Issue Type: New Feature Assignee: Dominik Bartholdi Components: config-file-provider-plugin, nodejs-plugin Created: 2016/Dec/11 6:02 PM Priority: Major Reporter: Nikolas Falco Hi, to make easier configure nodejs installations across multiple node and setup them to an internal nodejs.org repository would be great add support to the npm config file. The npm config file is an ini file but with only one single section. https://docs.npmjs.com/files/npmrc This config file will take advantage of credential support to configure authentication in case of internal npm repository. That I know, npm does not have an option where you could specify in the CLI the npmrc file, but there are four relevant places where this file is lookup. It's also possible transform each settings into enviroment variable or in a CLI option. https://docs.npmjs.com/misc/config Add Comment
[JIRA] (JENKINS-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"
Title: Message Title Nikolas Falco commented on JENKINS-27170 Re: "Provide Node & npm bin/ folder to PATH" not working for "npm install" This issue was resolved by ndeloof in the commit https://github.com/jenkinsci/nodejs-plugin/commit/f38e0a5d20a747d235dd1c439ebb92eef4b0fe8f I've try without any local system nodejs package and I have same issue. With local system nodejs package (nodejs >=6) I get the JENKINS-33698 behaviour. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-33698) NodeJS plugin npm install without root permissions
Title: Message Title Nikolas Falco resolved as Duplicate This is the same issue of JENKINS-27170 but happens when you also have a nodejs package system in the jenkins node. If the NodeJS is not in the PATH variable enviroment the npm install command use the system package that try to install global packages into system directory using the jenkins user instead root. This bug was insidious, and I found it only because I could no reproduce anymore after removing system nodejs package. Resolving the JENKINS-27170 resolve also this. Jenkins / JENKINS-33698 NodeJS plugin npm install without root permissions Change By: Nikolas Falco Status: In Progress Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33698) NodeJS plugin npm install without root permissions
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-33698 NodeJS plugin npm install without root permissions Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-33698) NodeJS plugin npm install without root permissions
Title: Message Title Nikolas Falco started work on JENKINS-33698 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-27170 "Provide Node & npm bin/ folder to PATH" not working for "npm install" Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-26828) Add support for installing the NodeJS windows msi
Title: Message Title Nikolas Falco commented on JENKINS-26828 Re: Add support for installing the NodeJS windows msi I've try the PR and does not work. Should be fixed the URL construction Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-26828) Add support for installing the NodeJS windows msi
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-26828 Add support for installing the NodeJS windows msi Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-26828) Add support for installing the NodeJS windows msi
Title: Message Title Nikolas Falco started work on JENKINS-26828 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37459) Unresolvable nodeJS installer for WINDOWS with amd64 cpu
Title: Message Title Nikolas Falco closed an issue as Fixed Jenkins / JENKINS-37459 Unresolvable nodeJS installer for WINDOWS with amd64 cpu Change By: Nikolas Falco Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39991) Credential replacement in settings.xml losts configuration, filePermissions and directoryPermissions elements
Title: Message Title Nikolas Falco commented on JENKINS-39991 Re: Credential replacement in settings.xml losts configuration, filePermissions and directoryPermissions elements I proposed a PR#23 on github Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39991) Credential replacement in settings.xml losts configuration, filePermissions and directoryPermissions elements
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-39991 Credential replacement in settings.xml losts configuration, filePermissions and directoryPermissions elements Issue Type: Bug Assignee: Dominik Bartholdi Components: config-file-provider-plugin Created: 2016/Nov/23 11:01 PM Environment: Jenkins 1.625.3 config-file-provider 2.13 Priority: Critical Reporter: Nikolas Falco Hi, I have enhanced our maven settings.xml for distributionManagement (deploy of maven site). I've create credential and bind them with a server id "docserver". The settings.xml text contains that server node because the configuration element needed to configure wagon protocol. When the file is generated any attribute that is not username, password, privateKey, passphrase are lost. Add Comment
[JIRA] (JENKINS-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-27170
"Provide Node & npm bin/ folder to PATH" not working for "npm install"
Change By:
Nikolas Falco
I followed the plugin doc that checked "Provide Node & npm bin/ folder to PATH", but it not works for npm install. You can see my screenshots.The execute shell command can works very well, but the console log shows "node: command not found", maybe not export the "$PATH"? {code} $ /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/npm install -g karma karma-cli karma-jasmine karma-junit-reporter karma-phantomjs-launcher karma-spec-reporter gulp gulp-concat gulp-sass gulp-minify-css gulp-renamenpm WARN engine karma-cli@0.0.4: wanted: {"node":"~0.8 || ~0.10"} (current: {"node":"0.12.0","npm":"2.5.1"})npm WARN engine karma@0.12.31: wanted: {"node":"~0.8 || ~0.10"} (current: {"node":"0.12.0","npm":"2.5.1"})/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/karma -> /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/karma-cli/bin/karmanpm WARN optional dep failed, continuing fsevents@0.3.5> phantomjs@1.9.15 install /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/karma-phantomjs-launcher/node_modules/phantomjs> node install.jssh: node: Command not found> ws@0.4.32 install /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws> (node-gyp rebuild 2> builderror.log) || (exit 0)/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/gulp -> /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/gulp/bin/gulp.js> node-sass@2.0.1 install /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/lib/node_modules/gulp-sass/node_modules/node-sass> node scripts/install.jssh: node: Command not foundnpm ERR! Linux 3.16.0-31-genericnpm ERR! argv "/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/node" "/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-0.12.0/bin/npm" "install" "-g" "karma" "karma-cli" "karma-jasmine" "karma-junit-reporter" "karma-phantomjs-launcher" "karma-spec-reporter" "gulp" "gulp-concat" "gulp-sass" "gulp-minify-css" "gulp-rename"npm ERR! node v0.12.0npm ERR! npm v2.5.1npm ERR! code ELIFECYCLEnpm ERR! phantomjs@1.9.15 install: `node install.js`npm ERR! Exit status 127npm ERR! npm ERR! Failed at the phantomjs@1.9.15 install script 'node install.js'.npm ERR! This is most likely a problem with the phantomjs package,npm ERR! not with npm itself.npm ERR! Tell the author that this fails on your system:npm ERR! node install.jsnpm ERR! You can get their info via:npm ERR! npm owner ls phantomjsnpm ERR! There is likely additional logging output above.npm
[JIRA] (JENKINS-37459) Unresolvable nodeJS installer for WINDOWS with amd64 cpu
Title: Message Title Nikolas Falco commented on JENKINS-37459 Re: Unresolvable nodeJS installer for WINDOWS with amd64 cpu It is a known limitations of this version reported in the plugin page There is a PR#5 to support this and will be reviewed and test soon. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37459) Unresolvable nodeJS installer for WINDOWS with amd64 cpu
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-37459 Unresolvable nodeJS installer for WINDOWS with amd64 cpu Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco commented on JENKINS-22102 Re: NodeJS plugin does not remember the saved "NodeJS Installation" I've attached a snapshot build with the changes so also you could test the bugfix. Due a previous refactor (more than one year ago) of this plugin to be compliant with more recent jenkins api if you have the envinject plugin the action of "Provide Node & npm bin/ folder to PATH" will not work because JENKINS-26583 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-22102 NodeJS plugin does not remember the saved "NodeJS Installation" Change By: Nikolas Falco Attachment: nodejs.hpi Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco updated JENKINS-22102 Jenkins / JENKINS-22102 NodeJS plugin does not remember the saved "NodeJS Installation" Change By: Nikolas Falco Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco commented on JENKINS-22102 Re: NodeJS plugin does not remember the saved "NodeJS Installation" The PR was merged and the fix was completed with other commit. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco started work on JENKINS-22102 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco commented on JENKINS-22102 Re: NodeJS plugin does not remember the saved "NodeJS Installation" I can confirm the issue. The PR#7 with recent changes on master does not work alone, it's necessary to expose getter and setter otherwise the value of nodeJSInstallationName could not be taken. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-22102) NodeJS plugin does not remember the saved "NodeJS Installation"
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-22102 NodeJS plugin does not remember the saved "NodeJS Installation" Change By: Nikolas Falco Assignee: Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39936) Any AQL in Download Spec file causes NPE
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-39936 Any AQL in Download Spec file causes NPE Issue Type: Bug Assignee: Eyal Ben Moshe Components: artifactory-plugin Created: 2016/Nov/22 11:10 AM Environment: Jenkins 1.651.3 artifactory plugin 2.8.1 Artifactory server 4.14.0 (Pro License) Labels: aql free-style jekins Priority: Critical Reporter: Nikolas Falco We have a jenkins free style job that with a Generic-Artifactory Integration enabled. The Download Details have is filled with an aql. Any "correct" aql query cause an NPE when job starts. Jenkins Artifactory Plugin version: 2.8.1 ERROR: null java.lang.NullPointerException at org.jfrog.build.extractor.clientConfiguration.util.spec.SpecsHelper.pathToUnixFormat(SpecsHelper.java:106) at org.jfrog.build.extractor.clientConfiguration.util.spec.SpecsHelper.getDownloadUploadSpec(SpecsHelper.java:98) at org.jfrog.hudson.generic.GenericArtifactsResolver.retrieveDependenciesBySpec(GenericArtifactsResolver.java:73) at org.jfrog.hudson.generic.ArtifactoryGenericConfigurator.setUp(ArtifactoryGenericConfigurator.java:329) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at
[JIRA] (JENKINS-26799) Multiple SCMs plugin support
Title: Message Title Nikolas Falco commented on JENKINS-26799 Re: Multiple SCMs plugin support Boguslaw Klimas I have some doubts about FIRST and ALL value option. FIRST not work if no SCM defined and maybe I would have the commit or TAG value to do some kinds of work based on parameter value without source code (for example download binary deployed on artifactory with release tag). ALL could be a very confusing if BRANCH or REVISION are selected and more than one SCM is defined So the really useful choise is MATCH_REPOSITRY_URL but also in this case you could not use it when no SCM is defined. The SVN strategy is very simple and usable You always put the complete git URL and you could also select credential stored in jenkins so more issue JENKINS-28597 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-26799) Multiple SCMs plugin support
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-26799 Multiple SCMs plugin support Change By: Nikolas Falco Attachment: git parameter.jpg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-26583) Env-inject plugin suppress variables contributed by extension points
Title: Message Title
Nikolas Falco commented on JENKINS-26583
Re: Env-inject plugin suppress variables contributed by extension points
same here I confirm that the EnvInjectPluginAction.buildEnvVars() overrides all enviroment variables contribuited to the context (for example by NodeJS plugin in master code in a SimpleBuildWrapper) in the AbstractBuild.getEnvironment() method when cycles on actions. So the PATH variable contributed by context.env("PATH+NODEJS", path) is override with old one. Now this is blocking because no command are available in the shell resetting any action of the plugin.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-33698) NodeJS plugin npm install without root permissions
Title: Message Title Nikolas Falco commented on JENKINS-33698 Re: NodeJS plugin npm install without root permissions There is a PR#13 for this issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-33698) NodeJS plugin npm install without root permissions
Title: Message Title Nikolas Falco commented on JENKINS-33698 Re: NodeJS plugin npm install without root permissions I've posted a workaround. Currently I'm working on a workaround, I will post a PR Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-33698) NodeJS plugin npm install without root permissions
Title: Message Title Nikolas Falco commented on JENKINS-33698 Re: NodeJS plugin npm install without root permissions The same here, issue happends wtith NodeJS >= 6.0. Debugging a bit the issue it's clear is in the NodeJS because since 6.x it's changed the prefix value from the local NodeJS installation folder to new one in the (/usr in linux) that obvious only root have access there. I found a workaround to keept global modules separated per Node version. Following this documentation after the tar.gz is installed if we put an npmrc file into lib/node_modules/npm with right prefix value works. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-26799) Multiple SCMs plugin support
Title: Message Title
Nikolas Falco updated an issue
Jenkins / JENKINS-26799
Multiple SCMs plugin support
Change By:
Nikolas Falco
Comment:
This is only a working POC (proof of concept)https://github.com/nfalco79/git-parameter-plugin/tree/feature/JENKINS-26799 !screenshot-1.png|thumbnail! !screenshot-2.png|thumbnail! *It works but*:* here MultiSCM is not an real optional dependency (I do not know if jenkins have some API to avoid Class.forName("") to know if a plugin is installed)* missing test case* missing handle event when you change repo URL and you have not set an SCM name (why if you not set any SCM Name the SCM key it's the string "git " + repoURL)* maybe some faultback for backward compatibility
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-26799) Multiple SCMs plugin support
Title: Message Title
Nikolas Falco commented on JENKINS-26799
Re: Multiple SCMs plugin support
This is only a working POC (proof of concept) https://github.com/nfalco79/git-parameter-plugin/tree/feature/JENKINS-26799 It works but:
here MultiSCM is not an real optional dependency (I do not know if jenkins have some API to avoid Class.forName("") to know if a plugin is installed)
missing test case
missing handle event when you change repo URL and you have not set an SCM name (why if you not set any SCM Name the SCM key it's the string "git " + repoURL)
maybe some faultback for backward compatibility
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-26799) Multiple SCMs plugin support
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-26799 Multiple SCMs plugin support Change By: Nikolas Falco Attachment: screenshot-4.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-26799) Multiple SCMs plugin support
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-26799 Multiple SCMs plugin support Change By: Nikolas Falco Attachment: screenshot-3.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
