[JIRA] (JENKINS-41716) Upgrade Breaks NodeJS Tool Installations
Title: Message Title Matthew Sexton closed an issue as Duplicate I have validated that this fix was applied with the 1.0.1 update, and that an upgrade to 2.45 also did not reintroduce this issue. Duplicate of JENKINS-41535. Closing. Jenkins / JENKINS-41716 Upgrade Breaks NodeJS Tool Installations Change By: Matthew Sexton Status: Open Closed Resolution: Duplicate 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
[JIRA] (JENKINS-41716) Upgrade Breaks NodeJS Tool Installations
Title: Message Title Matthew Sexton created an issue Jenkins / JENKINS-41716 Upgrade Breaks NodeJS Tool Installations Issue Type: Bug Assignee: Unassigned Components: nodejs-plugin Created: 2017/Feb/03 9:33 PM Environment: CentOS 7 x64 Jenkins 2.43 and 2.44 NodeJS Plugin 1.0 Priority: Major Reporter: Matthew Sexton All NodeJS Installations are completely removed from the Global Tool Configuration Upgrade from 2.42 to 2.43 wiped out all NodeJS versions Upgrade from 2.43 to 2.44 (after reinstalling tools) wiped out all NodeJS versions All jobs utilizing a NodeJS installation then break, even after the installations are re-added. To fix this you have to enter the job and simply hit 'Save' for the tool to update the configuration for the job to account for the newly installed version(s). To my knowledge, this is not due to the upgrade to v1.0 of the NodeJS plugin (certainly before the 2.44 upgrade), but I would like to validate that.
[JIRA] (JENKINS-41577) Properly Sort Jobs Numerically
Title: Message Title Matthew Sexton created an issue Jenkins / JENKINS-41577 Properly Sort Jobs Numerically Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Jan/30 9:50 PM Environment: CentOS 7 x64 v2.43 Priority: Trivial Reporter: Matthew Sexton This is primarily a cosmetic issue, but numerical ordering of jobs should take into account the ordering of double-digit numbers (i.e. 10 is on the list immediately after 1). So instead of the following: Project (1) - DEV - Build and Test Project (10) - PRD - Build and Test Project (11) - PRD - Deploy to Production Project (2) - DEV - Deploy to Development I should see: Project (1) - DEV - Build and Test Project (2) - DEV - Deploy to Development ... Project (10) - PRD - Build and Test Project (11) - PRD - Deploy to Production
[JIRA] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Title: Message Title Matthew Sexton commented on JENKINS-10191 Re: JDK selection is hidden even when a JDK is configured Correct, however I am confirming that the JDK selection from a maven job is not visible even though it is specified in the job's configuration. That was a side-effect I noticed at the same time (may or may not be related). 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-34815) NodeJS plugin unable to install global NPM packages
Title: Message Title Matthew Sexton closed an issue as Won't Do Closing due to it not being a issue with Jenkins itself, but that the NodeJS plugin has a newer version that is not automatically upgraded by the plugin manager, requiring a manual build of the plugin. Jenkins / JENKINS-34815 NodeJS plugin unable to install global NPM packages Change By: Matthew Sexton Status: Open Closed Resolution: Won't Do 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 t
[JIRA] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Title: Message Title Matthew Sexton commented on JENKINS-10191 Re: JDK selection is hidden even when a JDK is configured I can confirm this is still present in v2.19. I noticed sometime after 2.17 that all of my JDK tool installations were gone, and that the UI selection for the JDK for all maven jobs was no longer visible, but was still set in the config.xml. 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-34815) NodeJS plugin unable to install global NPM packages
Title: Message Title Matthew Sexton commented on JENKINS-34815 Re: NodeJS plugin unable to install global NPM packages No worries! I was not aware that version was even available given the lack of updates to the GitHub and plugin page. I did however build and install v0.3 of the nodejs-plugin and that appeared to solve the problem (using NodeJS 6.3.1). Is there anything in particular that keeps this plugin from being updated by the Plugin Manager? The POM has the updated version number (0.3-SNAPSHOT): nodejs 0.3-SNAPSHOT I can still go ahead and close this out since this is resolved with the update, though I may create another issue for making sure said plugin can get updated automatically for other users. 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-34815) NodeJS plugin unable to install global NPM packages
Title: Message Title Matthew Sexton commented on JENKINS-34815 Re: NodeJS plugin unable to install global NPM packages Davi Koscianski Vidal - By 0.3 you mean v6.3.0? I will test again with NodeJS 6.3.0 now that I am on Jenkins 2.14. 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-33776) Cannot start from preview rpm
Title: Message Title Matthew Sexton commented on JENKINS-33776 Re: Cannot start from preview rpm toby cabot - I agree that this needs to be remedied from a base install. Have you tried installing with the latest version (2.13) to test? There's nothing that points to that being removed or changed for the RPM, but it never hurts to try. Since there is a workaround in place (and since it's marked as resolved) it's not a high priority for the devs. 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-36163) Spaces in Job Name Cause Maven Test Failures for File Input
Title: Message Title
Matthew Sexton updated an issue
Jenkins / JENKINS-36163
Spaces in Job Name Cause Maven Test Failures for File Input
Change By:
Matthew Sexton
Issue set as minor due to available workaround.*Problem:*Where maven job names have spaces and files are used within the workspace, Jenkins cannot locate the file in the workspace because the url-encoded values do not match the literal value of the path on the host.Job name: "KEY (3) - Package email app (DEV)"{code}java.nio.file.NoSuchFileException: /var/lib/jenkins/jobs/foldername/jobs/KEY%20(3)%20-%20Package% 20email 20app %20(DEV)/workspace/email/target/test-classes/data/ TextEmail TestText .txtat sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)at java.nio.file.Files.newByteChannel(Files.java:317)at java.nio.file.Files.newByteChannel(Files.java:363)at java.nio.file.Files.readAllBytes(Files.java:2981)at com.company.a.e.ParserTest.setUp(ParserTest.java:50){code}Where the file is validated and the literal path is /var/lib/jenkins/jobs/foldername/jobs/KEY (3) - Package email app (DEV)/workspace/email/target/test-classes/data/ TextEmail TextTest .txt*Workaround:*Change the job name to " KEY3PackageEmailDEV KEY3PackageAppDEV " removing all spaces allows the tests to locate the appropriate filepaths correctly - and the tests can be run without errors.
Add Comment
[JIRA] (JENKINS-36163) Spaces in Job Name Cause Maven Test Failures for File Input
Title: Message Title Matthew Sexton created an issue Jenkins / JENKINS-36163 Spaces in Job Name Cause Maven Test Failures for File Input Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2016/Jun/22 11:35 PM Environment: Jenkins 2.10, CentOS 7 x64, OpenJDK 1.8 Priority: Minor Reporter: Matthew Sexton Issue set as minor due to available workaround. Problem: Where maven job names have spaces and files are used within the workspace, Jenkins cannot locate the file in the workspace because the url-encoded values do not match the literal value of the path on the host. Job name: "KEY (3) - Package email (DEV)" java.nio.file.NoSuchFileException: /var/lib/jenkins/jobs/foldername/jobs/KEY%20(3)%20-%20Package%20email%20(DEV)/workspace/email/target/test-classes/data/TextEmail.txt at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) at java.nio.file.Files.newByteChannel(Files.java:317) at java.nio.file.Files.newByteChannel(Files.java:363) at java.nio.file.Files.readAllBytes(Files.java:2981) at com.company.a.e.ParserTest.setUp(ParserTest.java:50) Where the file is validated and the literal path is /var/lib/jenkins/jobs/foldername/jobs/KEY (3) - Package email (DEV)/workspace/email/ta
[JIRA] (JENKINS-34815) NodeJS plugin unable to install global NPM packages
Title: Message Title
Matthew Sexton edited a comment on JENKINS-34815
Re: NodeJS plugin unable to install global NPM packages
I can also validate this issue. I have tested it on a fresh install of Jenkins 2.0 (v2.9 to be specific) with NodeJS v6.2.2. I have also done this for NodeJS 5.9, 6.0, 6.1, and 6.2.1. It appears that no version of NodeJS 6+ this works, but continues to work for versions <6.0. When the tool itself is installing modules, the PATH is not set correctly. When running the build job, the PATH gets set correctly, so node and npm are available and I can print out the versions.{code}Unpacking https://nodejs.org/dist/v6.2.2/node-v6.2.2-linux-x64.tar.gz to /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node-6.2.2 on Jenkins$ /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node-6.2.2/bin/npm install -g mocha istanbul eslint grunt-cli forever mocha-junit-reporter/usr/bin/env: node: No such file or directory # Build Step [testnode1] $ /bin/sh -xe /tmp/hudson4410243541713209879.sh+ echo /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node-6.2.2/bin:/sbin:/usr/sbin:/bin:/usr/bin/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node-6.2.2/bin:/sbin:/usr/sbin:/bin:/usr/bin+ npm -v3.9.5+ node -vv6.2.2{code}
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
[JIRA] (JENKINS-34815) NodeJS plugin unable to install global NPM packages
Title: Message Title Matthew Sexton commented on JENKINS-34815 Re: NodeJS plugin unable to install global NPM packages I can also validate this issue. I have tested it on a fresh install of Jenkins 2.0 (v2.9 to be specific) with NodeJS v6.2.2. I have also done this for NodeJS 5.9, 6.0, 6.1, and 6.2.1. It appears that no version of NodeJS 6+ this works, but continues to work for versions <6.0. When the tool itself is installing modules, the PATH is not set correctly. When running the build job, the PATH gets set correctly, so node and npm are available and I can print out the versions. Unpacking https://nodejs.org/dist/v6.2.2/node-v6.2.2-linux-x64.tar.gz to /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node-6.2.2 on Jenkins $ /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node-6.2.2/bin/npm install -g mocha istanbul eslint grunt-cli forever mocha-junit-reporter /usr/bin/env: node: No such file or directory [testnode1] $ /bin/sh -xe /tmp/hudson4410243541713209879.sh + echo /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node-6.2.2/bin:/sbin:/usr/sbin:/bin:/usr/bin /var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/node-6.2.2/bin:/sbin:/usr/sbin:/bin:/usr/bin + npm -v 3.9.5 + node -v v6.2.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] [packaging] (JENKINS-33776) Cannot start from preview rpm
Title: Message Title Matthew Sexton commented on JENKINS-33776 Re: Cannot start from preview rpm I ran into this problem myself going from 1.656 to 2.1 via yum. First I attempted to create and apply patches from /etc/sysconfig/jenkins, /etc/sysconfig/jenkins.rpmnew, /etc/init.d/jenkins and /etc/init.d/jenkins.rpmnew. I validated that the AJP settings were returned into the configuration however I was still getting the stacktrace reported with this issue. My resolution was to: Set JENKINS_AJP_PORT="-1" Validate that Jenkins would start (meaning I wasn't utilizing AJP, which I knew) Upgrade from 1.656 to 2.1 via yum So ultimately it would appear that you have to disable AJP and then the settings in /etc/init.d/jenkins mean nothing. My example shows that I had to disable AJP before I even did the upgrade. Food for thought. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
