[JIRA] [core] (JENKINS-35206) NullPointerException on startup after update to 2.6
Title: Message Title Axel Behrens created an issue Jenkins / JENKINS-35206 NullPointerException on startup after update to 2.6 Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/May/30 5:52 AM Priority: Minor Reporter: Axel Behrens After updating to 2.6 from 2.5 I'm getting the following NPE directly at startup: hudson.util.HudsonFailedToLoad: java.lang.NullPointerException at hudson.WebAppMain$3.run(WebAppMain.java:244) Caused by: java.lang.NullPointerException at jenkins.install.InstallState.equals(InstallState.java:179) at jenkins.install.InstallUtil.proceedToNextStateFrom(InstallUtil.java:97) at jenkins.model.Jenkins.(Jenkins.java:888) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:227) The stacktrace didn't suggest a particular plugin so I chose 'core' as component. Please correct if necessary. jenkins.err.log Mai 30, 2016 7:23:10 AM org.eclipse.jetty.util.log.JavaUtilLog info INFO: Logging initialized @470ms Mai 30, 2016 7:23:10 AM winstone.Logger logInternal INFO: Beginning extraction from war file Mai 30, 2016 7:23:14 AM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: Empty
[JIRA] [other] (JENKINS-35094) unable to use grunt commands
Title: Message Title abhishek chandel resolved as Fixed Jenkins / JENKINS-35094 unable to use grunt commands Change By: abhishek chandel Status: Open Resolved Resolution: Fixed 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.
[JIRA] [other] (JENKINS-35094) unable to use grunt commands
Title: Message Title abhishek chandel commented on JENKINS-35094 Re: unable to use grunt commands yes, you are correct service account didn't had a PATH variable. So i used "SET PATH = %PATH%;c:/usr/Appdata/roaming/npm" and it is working. Thanks. 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.
[JIRA] [active-choices-plugin] (JENKINS-28735) Supporting Jobs triggered by plug-ins, API and scripts
Title: Message Title kishorerp commented on JENKINS-28735 Re: Supporting Jobs triggered by plug-ins, API and scripts Need this fix badly for our nightly builds trigger... 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.
[JIRA] [active-choices-plugin] (JENKINS-34618) Active Choice reactive parameter doesnt work on time triggered builds
Title: Message Title kishorerp updated an issue Jenkins / JENKINS-34618 Active Choice reactive parameter doesnt work on time triggered builds Change By: kishorerp Summary: Active Choice reactive parameter gives an exception in the following scenario doesnt work on time triggered builds 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.
[JIRA] [core] (JENKINS-35013) PluginManager not able to update
Title: Message Title Rens Hoskens edited a comment on JENKINS-35013 Re: PluginManager not able to update The server is behind a proxy, but it is configured correctly, and it worked in the past. Also, when I test the proxy with the Update URL, it succeeds. It also worked in the past.. :s 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.
[JIRA] [core] (JENKINS-35013) PluginManager not able to update
Title: Message Title Rens Hoskens commented on JENKINS-35013 Re: PluginManager not able to update The server is behind a proxy, but it is configured correctly, and it worked in the past. Also, when I test the proxy with the Update URL, it succeeds. 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.
[JIRA] [nodelabelparameter-plugin] (JENKINS-35204) Jenkins triggers a build twice on master / slave, when executing with "Node / Label" parameters & "Run on all nodes matching the label" checkbox chec
Title: Message Title Amit Pandey commented on JENKINS-35204 Re: Jenkins triggers a build twice on master / slave, when executing with "Node / Label" parameters & "Run on all nodes matching the label" checkbox checked. Here, please make sure that this label should assigned on single slave machine and its should be uniq label 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.
[JIRA] [github-organization-folder-plugin] (JENKINS-34246) Old repos aren't removed
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-34246 Re: Old repos aren't removed This is the expected behavior if the Discard Policy is either disabled or enabled for several days. I believe the ability to remove a repository job is an improvement to consider. 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.
[JIRA] [blueocean-plugin] (JENKINS-35202) "New Pipeline"does not work if context root is not /jenkins
Title: Message Title James Dumay commented on JENKINS-35202 Re: "New Pipeline"does not work if context root is not /jenkins Thanks for reporting. This isn't the final creation experience we had been thinking about but Michael Neale and I should have one soon to show on the user list. 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.
[JIRA] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Michael Neale commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat I think this will be a lot easier when this is published to the update center BTW 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.
[JIRA] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Michael Neale commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat Ivan Meredith can you share the plugins.txt you used to run this as an image with plugins installed? 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.
[JIRA] [checkstyle-plugin] (JENKINS-32501) Please update checkstyle plugin to latest checkstyle 6.14
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32501 Re: Please update checkstyle plugin to latest checkstyle 6.14 Code changed in jenkins User: Ulli Hafner Path: src/test/java/hudson/plugins/checkstyle/parser/CheckStyleParserTest.java http://jenkins-ci.org/commit/checkstyle-plugin/c576821e73855641d61540de9f0afaedc62238b5 Log: JENKINS-32501 Update of message in unit test due to checkstyle 6.18. 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.
[JIRA] [core] (JENKINS-34768) Smarter worker selection needed
Title: Message Title Christoph Obexer commented on JENKINS-34768 Re: Smarter worker selection needed Yes Please! Especially for matrix combinations scheduled on labels! 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.
[JIRA] [mongodb-plugin] (JENKINS-35205) Add option to write mongo log to a designated direcotry
Title: Message Title dan tran created an issue Jenkins / JENKINS-35205 Add option to write mongo log to a designated direcotry Issue Type: Bug Assignee: Unassigned Components: mongodb-plugin Created: 2016/May/29 6:38 PM Priority: Minor Reporter: dan tran we are using maven for our build and it is conventional to write to 'target' directory ATM, this plugin only write to $WORKSPLACE directoy Add Comment
[JIRA] [nodelabelparameter-plugin] (JENKINS-35204) Jenkins triggers a build twice on master / slave, when executing with "Node / Label" parameters & "Run on all nodes matching the label" checkbox chec
Title: Message Title Devaraj Ranganathan created an issue Jenkins / JENKINS-35204 Jenkins triggers a build twice on master / slave, when executing with "Node / Label" parameters & "Run on all nodes matching the label" checkbox checked. Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin Created: 2016/May/29 5:47 PM Priority: Critical Reporter: Devaraj Ranganathan The build gets triggered twice when I run the build parallelly using "Label" parameter of "Node Label Parameter" and only when "Run on all nodes matching the label" checkbox is checked. In the console output of second build - I can see the message that "this is started by the upstream project" build #. Kindly help resolving this ASAP. Add Comment
[JIRA] [klaros-testmanagement-plugin] (JENKINS-34334) java.io.NotSerializableException when plugin is executed on a slave node
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34334 Re: java.io.NotSerializableException when plugin is executed on a slave node Code changed in jenkins User: Torsten Stolpmann Path: pom.xml src/changes/changes.xml src/main/java/hudson/plugins/klaros/KlarosTestResultPublisher.java src/main/java/hudson/plugins/klaros/ResultFormat.java src/main/java/hudson/plugins/klaros/ResultSet.java http://jenkins-ci.org/commit/klaros-testmanagement-plugin/3175b5e35350c376210b38df11a1337c345ea1b3 Log: JENKINS-34334 : java.io.NotSerializableException when plugin is executed on a slave node Task-Url: https://issues.jenkins-ci.org/browse/JENKINS-34334 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.
[JIRA] [klaros-testmanagement-plugin] (JENKINS-34334) java.io.NotSerializableException when plugin is executed on a slave node
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34334 Re: java.io.NotSerializableException when plugin is executed on a slave node Code changed in jenkins User: Torsten Stolpmann Path: .classpath http://jenkins-ci.org/commit/klaros-testmanagement-plugin/4ce1f5120ddf665ca378a93e8f87d14ad405daa3 Log: JENKINS-34334 : java.io.NotSerializableException when plugin is executed on a slave node Task-Url: https://issues.jenkins-ci.org/browse/JENKINS-34334 Compare: https://github.com/jenkinsci/klaros-testmanagement-plugin/compare/41daedda6554...4ce1f5120ddf 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.
[JIRA] [core] (JENKINS-35203) Use ConcurrentSkipListMap instead of CopyOnWriteMap
Title: Message Title Vladimir Sitnikov moved an issue Jenkins / JENKINS-35203 Use ConcurrentSkipListMap instead of CopyOnWriteMap Change By: Vladimir Sitnikov Project: Infrastructure Jenkins Key: INFRA JENKINS - 724 35203 Workflow: classic default workflow JNJira Component/s: core Component/s: core 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
[JIRA] [blueocean-plugin] (JENKINS-35181) Docker image for Blue Ocean plugin
Title: Message Title Baptiste Mathus commented on JENKINS-35181 Re: Docker image for Blue Ocean plugin See https://github.com/jenkinsci/blueocean-plugin/pull/216 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.
[JIRA] [build-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name
Title: Message Title Łukasz Jąder commented on JENKINS-34512 Re: error in build-name-setter plugin - Set build name Devesh Kumar and Michael Merritt are you sure that your build finished with FAILURE? I'm asking because you wrote: > However the build fails... I've tried to recreate described enviromnent, and even if I see the message " Variable with name 'BUILD_DISPLAY_NAME' already exists...", my build ends with SUCCESS. 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.
[JIRA] [core] (JENKINS-35198) DelegatingComputerLauncher allowing to use other DelegatingComputerLauncher as delegate
Title: Message Title Giuseppe Landolfi resolved as Fixed Jenkins / JENKINS-35198 DelegatingComputerLauncher allowing to use other DelegatingComputerLauncher as delegate Change By: Giuseppe Landolfi Status: Open Resolved Resolution: Fixed 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.
[JIRA] [blueocean-plugin] (JENKINS-35202) "New Pipeline"does not work if context root is not /jenkins
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-35202
"New Pipeline"does not work if context root is not /jenkins
Change By:
Baptiste Mathus
I suspect the plugin has mostly been tested using {{hpi:run}}, so currently when deployed somewhere, the main link of the /blue page will lead to a 404.I think the problem is that /jenkins is prefixed here: https://github.com/batmat/blueocean-plugin/blob/f507cd9ccd98c594719dc4dd4ae32aa94ff3fa51/blueocean-dashboard/src/main/js/components/Pipelines.jsx#L41 when it should use {{Jenkins.getRootUrl()}} for the beginning of the PATH.E.g. the issue is visible when running the demo Docker image: {{ docker run -p 8080:8080 jenkinsci/blueocean }}I've set the priority to _Important_ since this is the main link of that page that's not working.
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.
[JIRA] [blueocean-plugin] (JENKINS-35202) "New Pipeline"does not work if context root is not /jenkins
Title: Message Title
Baptiste Mathus created an issue
Jenkins / JENKINS-35202
"New Pipeline"does not work if context root is not /jenkins
Issue Type:
Bug
Assignee:
Tom FENNELLY
Components:
blueocean-plugin
Created:
2016/May/29 11:50 AM
Priority:
Major
Reporter:
Baptiste Mathus
I suspect the plugin has mostly been tested using hpi:run, so currently when deployed somewhere, the main link of the /blue page will lead to a 404.
I think the problem is that /jenkins is prefixed here: https://github.com/batmat/blueocean-plugin/blob/f507cd9ccd98c594719dc4dd4ae32aa94ff3fa51/blueocean-dashboard/src/main/js/components/Pipelines.jsx#L41 when it should use Jenkins.getRootUrl() for the beginning of the PATH.
E.g. the issue is visible when running the demo Docker image: {{ docker run -p 8080:8080 jenkinsci/blueocean }}
I've set the priority to Important since this is the main link of that page that's not working.
Add Comment
[JIRA] [core] (JENKINS-35020) Fix JSHint errors
Title: Message Title Oleg Nenashev commented on JENKINS-35020 Re: Fix JSHint errors If we backport it, it also requires https://github.com/jenkinsci/jenkins/commit/a2e7661f212c4564fffa57ddc9b9ab92f2f2dc5b 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.
[JIRA] [core] (JENKINS-35201) Jenkins cannot be built on Windows due to NodeJS issues
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-35201 Jenkins cannot be built on Windows due to NodeJS issues Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed 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.
[JIRA] [core] (JENKINS-35201) Jenkins cannot be built on Windows due to NodeJS issues
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35201 Re: Jenkins cannot be built on Windows due to NodeJS issues Code changed in jenkins User: Damian Szczepanik Path: war/pom.xml http://jenkins-ci.org/commit/jenkins/155f850203ca69a6601acbddafa726a43a2f2244 Log: [FIXED JENKINS-35201] - NodeJS could not be built on Win x64 (#2381) 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.
[JIRA] [core] (JENKINS-35201) Jenkins cannot be built on Windows due to NodeJS issues
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-35201 Jenkins cannot be built on Windows due to NodeJS issues Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/May/29 10:41 AM Environment: It's a follow-up to https://github.com/jenkinsci/jenkins/pull/2381 from Damian Szczepanik > Since recent changes about NodeJS I could not built Jenkins on Windows x64. With this change the build success. Take a look and if no question, merge it Priority: Major Reporter: Oleg Nenashev Add Comment
[JIRA] [core] (JENKINS-35198) DelegatingComputerLauncher allowing to use other DelegatingComputerLauncher as delegate
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35198 Re: DelegatingComputerLauncher allowing to use other DelegatingComputerLauncher as delegate Code changed in jenkins User: peppelan Path: core/src/main/java/hudson/slaves/DelegatingComputerLauncher.java core/src/test/java/hudson/slaves/DelegatingComputerLauncherTest.java http://jenkins-ci.org/commit/jenkins/15ce24ae4dac23a732f193f29b6423bc03be7a49 Log: JENKINS-35198 - DelegatingComputerLauncher should accept child classes in its hooks (#2384) JENKINS-35198 Add failing test for clear identification of the issue and future regression test JENKINS-35198 Fix DelegatingComputerLauncher logic for filtering out subclasses as possible delegates this logic is by default, and subclasses can still allow the selection of other DelegatingComputerLauncher instances as delegates. 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.
[JIRA] [core] (JENKINS-35190) Improper PingThread handling
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35190 Re: Improper PingThread handling Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/slaves/ChannelPinger.java http://jenkins-ci.org/commit/jenkins/0ae6c42ed2cbda0ea4a1e196656ef1d6008d80ba Log: JENKINS-35190 Do not even consult PingFailureAnalyzer if ping fails on the agent side. (#2377) 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.
[JIRA] [core] (JENKINS-35190) Improper PingThread handling
Title: Message Title Oleg Nenashev commented on JENKINS-35190 Re: Improper PingThread handling Jenkins core fix has been integrated into 2.7 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.
[JIRA] [publish-over-ssh-plugin] (JENKINS-35200) publish-over-ssh-plugin build is missing Messages.java
Title: Message Title
Arnost Kvasinka edited a comment on JENKINS-35200
Re: publish-over-ssh-plugin build is missing Messages.java
It was actually way easier than I thought. IDEA has decompiled the {{Messages.class}} file for me and so I have created {{Messages.java}} from the scratch. (I know it's probably not the same one as there should be in the repository, but I've attached it). I've been able to successfully package the plugin (some tests also ran in the process and they all passed) with this decompiled {{Messages.java}} file.
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.
[JIRA] [publish-over-ssh-plugin] (JENKINS-35200) publish-over-ssh-plugin build is missing Messages.java
Title: Message Title Arnost Kvasinka updated an issue Jenkins / JENKINS-35200 publish-over-ssh-plugin build is missing Messages.java It was actually way easier than I thought. IDEA has decompiled the Messages.class file for me and so I have created Messages.java from the scratch. (I know it's probably not the same one as there should be in the repository, but I've attached it). Change By: Arnost Kvasinka Attachment: Messages.java 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.
[JIRA] [build-flow-plugin] (JENKINS-34961) Build flow sections, created in older jenkins versions disappeared in Jenkins 2
Title: Message Title Mor Shaked commented on JENKINS-34961 Re: Build flow sections, created in older jenkins versions disappeared in Jenkins 2 Critical bug for us, we cant upgrade to 2.x till it will be fixed . 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.
[JIRA] [publish-over-ssh-plugin] (JENKINS-35200) publish-over-ssh-plugin build is missing Messages.java
Title: Message Title Arnost Kvasinka created an issue Jenkins / JENKINS-35200 publish-over-ssh-plugin build is missing Messages.java Issue Type: Bug Assignee: bap Components: publish-over-ssh-plugin Created: 2016/May/29 10:18 AM Priority: Major Reporter: Arnost Kvasinka Hi, For some reason I am unable to compile the plugin itself. No matter what environment I use (tried JDK 1.7, 1.8; IntelliJ IDEA and NetBeans) it always fail because the jenkins.plugins.publish_over_ssh.Messages class cannot be found. Tried looking for the Messages.java in the sources, not there (I checked the repo on Github to rule out a bad git clone) googling Messages.java online (searching for some of the methods the plugin tries to call) and came up with this – it looks like the actual file, but it might be outdated, so I did not try using it ensuring I have all the required dependencies – the plugin uses maven and both my IDEs (IDEA and NetBeans) properly identified it as such and before giving me access to the source code they downloaded all the required libraries upfront (took nearly 30 minutes)
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-33013) Unable to execute test in HP Performance Center 12
Title: Message Title Hanan Bem closed an issue as Not A Defect Jenkins / JENKINS-33013 Unable to execute test in HP Performance Center 12 Change By: Hanan Bem Status: Open Closed Resolution: Not A Defect 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.
[JIRA] [publish-over-ssh-plugin] (JENKINS-26439) Build does not abort when «Send files or execute commands over SSH» fails
Title: Message Title Yao Li updated an issue Jenkins / JENKINS-26439 Build does not abort when «Send files or execute commands over SSH» fails Change By: Yao Li Comment: Hit the problem in Jenkins 2.0 shell step also.ssh @ip << EOF command_1 command_2EOFRun aborted on command_1 error, but job still finished "SUCCESS" 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.
[JIRA] [publish-over-ssh-plugin] (JENKINS-26439) Build does not abort when «Send files or execute commands over SSH» fails
Title: Message Title Yao Li commented on JENKINS-26439 Re: Build does not abort when «Send files or execute commands over SSH» fails Hit the problem in Jenkins 2.0 shell step also. ssh @ip << EOF command_1 command_2 EOF Run aborted on command_1 error, but job still finished "SUCCESS" 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.
