[JIRA] [jabber-plugin] (JENKINS-25513) jabber-plugin 1.30 fails IPv6 DNS resolve, throws NumberFormatException.
Florian Schmaus commented on JENKINS-25513 jabber-plugin 1.30 fails IPv6 DNS resolve, throws NumberFormatException. I don't think that's it's related to JENKINS-25505. It may appears now because the new Smack version does DNS lookups in case where the old one didn't. It's a 4 year old java bug: https://bugs.openjdk.java.net/browse/JDK-6991580 The workaround is to configure the host and port of the XMPP server in Smack, which will avoid DNS lookups. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-14269) Archive the artifacts does not preserve file exec permissions
Andreas Hindborg commented on JENKINS-14269 Archive the artifacts does not preserve file exec permissions I have uploaded a possible fix for this issue at https://github.com/metaspace/jenkins/commit/87a49efa0bdc99844455461db7db86fe3546e5e2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven-plugin] (JENKINS-25633) maven pom analysis does not cover maven plugins' dependencies
Mr Cinquero
updated JENKINS-25633
maven pom analysis does not cover maven plugins dependencies
Change By:
Mr Cinquero
(15/Nov/14 11:33 AM)
Description:
Jenkinsanalyzesthemavenpom.xmlduringexecutionofthemavenbuild,whichincludesanalyzingthedependencies.However,itdoesnotseemtoworkforpluginsdependencies,namelymy.pkg:artIdinthefollowingexample:
{noformat}
plugingroupIdorg.codehaus.mojo/groupIdartifactIdexec-maven-plugin/artifactIdexecutionsexecutionphaseprocess-resources/phasegoalsgoaljava/goal/goals/execution/executionsconfigurationincludePluginDependenciestrue/includePluginDependenciesexecutableDependencygroupIdmy.pkg/groupIdartifactIdartId/artifactId/executableDependencymainClassmy.pkg.bla.App/mainClass/configurationdependenciesdependencygroupIdmy.pkg/groupIdartifactIdartId/artifactIdversion1.0-SNAPSHOT/version/dependency/dependencies/plugin
{noformat}
Isthereanyway(exceptmanuallyconfiguringtheJenkinsjobs)totellJenkinstoconsidermy.pkg:artIdasoneoftheprojectsdependencies?Itriedputtingthedependencydeclarationintothebuilddependencylistusingtheprovidedscope.That,however,hasside-effects:forexample,NetBeanswillconsidertransitivedependenciesofmy.pkg:artIdaspresent,therebynotindicatingmissingdependenciesinthebuildetc:
{noformat}
dependenciesdependencygroupIdmy.pkg/groupIdartifactIdartId/artifactIdscopeprovided/scopeexclusionsexclusiongroupId*/groupIdartifactId*/artifactId/exclusion/exclusions/dependency...
{noformat}
Theexclusionssomewhatmitigatetheproblemintroducedbymis-usingtheprovdedscopeandreduceittoresources/classescontainedinmy.pkg:artId.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [maven-plugin] (JENKINS-25633) maven pom analysis does not cover maven plugins' dependencies
Mr Cinquero created JENKINS-25633 maven pom analysis does not cover maven plugins dependencies Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 15/Nov/14 11:32 AM Description: Jenkins analyzes the maven pom.xml during execution of the maven build, which includes analyzing the dependencies. However, it does not seem to work for plugins' dependencies, namely "my.pkg:artId" in the following example: plugin groupIdorg.codehaus.mojo/groupId artifactIdexec-maven-plugin/artifactId executions execution phaseprocess-resources/phase goals goaljava/goal /goals /execution /executions configuration includePluginDependenciestrue/includePluginDependencies executableDependency groupIdmy.pkg/groupId artifactIdartId/artifactId /executableDependency mainClassmy.pkg.bla.App/mainClass /configuration dependencies dependency groupIdmy.pkg/groupId artifactIdartId/artifactId version1.0-SNAPSHOT/version /dependency /dependencies /plugin Is there any way (except manually configuring the Jenkins jobs) to tell Jenkins to consider my.pkg:artId as one of the project's dependencies? I tried putting the dependency declaration into the build dependency list using the provided scope. That, however, has side-effects: for example, NetBeans will consider transitive dependencies of my.pkg:artId as present, thereby not indicating missing dependencies in the build etc: dependencies dependency groupIdmy.pkg/groupId artifactIdartId/artifactId scopeprovided/scope exclusions exclusion groupId*/groupId artifactId*/artifactId /exclusion /exclusions /dependency ... The exclusions somewhat mitigate the problem introduced by mis-using the provded scope and reduce it to resources/classes contained in my.pkg:artId. Project: Jenkins Priority: Minor Reporter: Mr Cinquero This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven-plugin] (JENKINS-25633) maven pom analysis does not cover maven plugins' dependencies
Mr Cinquero
updated JENKINS-25633
maven pom analysis does not cover maven plugins dependencies
Change By:
Mr Cinquero
(15/Nov/14 11:34 AM)
Description:
Jenkinsanalyzesthemavenpom.xmlduringexecutionofthemavenbuild,whichincludesanalyzingthedependencies.However,itdoesnotseemtoworkforpluginsdependencies,namelymy.pkg:artIdinthefollowingexample:{noformat}plugingroupIdorg.codehaus.mojo/groupIdartifactIdexec-maven-plugin/artifactIdexecutionsexecutionphaseprocess-resources/phasegoalsgoaljava/goal/goals/execution/executionsconfigurationincludePluginDependenciestrue/includePluginDependenciesexecutableDependencygroupIdmy.pkg/groupIdartifactIdartId/artifactId/executableDependencymainClassmy.pkg.bla.App/mainClass/configurationdependenciesdependencygroupIdmy.pkg/groupIdartifactIdartId/artifactIdversion1.0-SNAPSHOT/version/dependency/dependencies/plugin{noformat}Isthereanyway(exceptmanuallyconfiguringtheJenkinsjobs)totellJenkinstoconsidermy.pkg:artIdasoneoftheprojectsdependencies?Itriedputtingthedependencydeclarationintothebuilddependencylistusingtheprovidedscope.That,however,hasside-effects:forexample,NetBeanswillconsidertransitivedependenciesofmy.pkg:artIdaspresent,therebynotindicatingmissingdependenciesinthebuildetc:{noformat}dependenciesdependencygroupIdmy.pkg/groupIdartifactIdartId/artifactIdscopeprovided/scopeexclusionsexclusiongroupId*/groupIdartifactId*/artifactId/exclusion/exclusions/dependency...{noformat}Theexclusionssomewhatmitigatetheproblemintroducedbymis-usingthe
provded
provided
scopeandreduceittoresources/classescontainedinmy.pkg:artId.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [gradle-plugin] (JENKINS-25634) Ignore error code for Gradle builds
Nathan Bruning created JENKINS-25634 Ignore error code for Gradle builds Issue Type: New Feature Assignee: Gregory Boissinot Components: gradle-plugin Created: 15/Nov/14 12:57 PM Description: Some Gradle builds will fail "on purpose", which should not stop the entire build process. For example, Androids :connectedCheck or :lint will return an error code when an error is detected. In Jenkins, we would like to continue the build and publish results later on. The Gradle plugin could add a checkbox "Ignore Gradle error code" to support this. Project: Jenkins Priority: Minor Reporter: Nathan Bruning This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-25567) Matrix-based security does not allow read-only on Configure System
Daniel Beck updated JENKINS-25567 Matrix-based security does not allow read-only on Configure System Extended read permission does not cover system configuration, only nodes and items. Since the plugin only enables a core feature hidden behind a system property switch, changing type to Feature, and component to Core. Change By: Daniel Beck (15/Nov/14 2:08 PM) Issue Type: Bug NewFeature Description: Hi,Idonotexactlyknowitthisisabugornot. ForourjenkinssetupweuseMatrix-basedsecurityusing2groups(CI_AdminsandCI_Users)WewanttopreventthatCI_UsersALTERJenkinsconfiguration(SothestuffunderManageJenkins),however,theyshouldbeabletoVIEWtheJenkinsconfiguration,andmostnotablytheGlobalpropertiesunderConfigureSystem.Idonotseeawaytodothisusingthesecuritymatrix.Overall--ReadisenabledforCI_Users Labels: authorisationconfigurationjenkins Component/s: core Component/s: extended-read-permission-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Daniel Beck updated JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. Change By: Daniel Beck (15/Nov/14 2:12 PM) Labels: jenkins selenium Component/s: slave-utilization This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Daniel Beck commented on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. To clarify, this completely breaks Selenium plugin, and it started with 1.587? 1.580.1 is also affected? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-11962) Symlinking lastSuccessful build shouldn't fail with concurrent jobs
Daniel Beck commented on JENKINS-11962 Symlinking lastSuccessful build shouldnt fail with concurrent jobs I think the Java 1.6 implementation needs JNA to work or something similar. Maybe try running Jenkins on Java 7. Also, it doesn't look like you need the builds to run in parallel, as they are all done within milliseconds. Disabling that would likely prevent issues like that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-with-parameters-plugin] (JENKINS-24008) Jobs stuck while waiting for an executor (and executors are available)
Andrew P commented on JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) I believe that I have hit the same issue. I am calling the job from a flow. The flow is triggered manually. The job makes use of Build with parameters. It has a Dynamic Extended Choice Plugin aka Moded Extended Choice Parameter and an Extended Choice Parameter. We don't even have to use "Bind with field" to expose the unwanted behavior. Just by having both Extended Choice Parameter and Extended Choice Parameter in the same job makes it hang when called from a Flow. -Verisons and modules --- Using Jenkins ver. 1.557 Build Flow Plugin Manage jobs orchestration as a dedicated "build flow" top level item 0.12 Dynamic Extended Choice Parameter Plug-In This plugin is a sample plugin to explain how to write a Hudson plugin. 1.0.1 Extended Choice Parameter plugin Adds extended functionality to Choice parameter 0.30 Extensible Choice Parameter plugin Extensible Choice Parameter provides several ways to retrieve choices, including the way to share choices among all jobs. 1.2.2 ---Configurations --- Base job with Bind to Field jenkins@usaxqkr017cczra xx_job1$ cat config.xml ?xml version='1.0' encoding='UTF-8'? project actions/ description/description keepDependenciesfalse/keepDependencies properties hudson.model.ParametersDefinitionProperty parameterDefinitions com.moded.extendedchoiceparameter.ExtendedChoiceParameterDefinition plugin="dynamic_extended_choice_parameter@1.0.1" nameSITE/name description/description quoteValuefalse/quoteValue svnPathfalse/svnPath roleBasedFilterfalse/roleBasedFilter visibleItemCount5/visibleItemCount typePT_SINGLE_SELECT/type value/value propertyFile/dimp/zzz/sites/jenkins_choices/management.sites/propertyFile propertyKeykey/propertyKey defaultValue/defaultValue defaultPropertyFile/defaultPropertyFile defaultPropertyKey/defaultPropertyKey multiSelectDelimiter,/multiSelectDelimiter bindFieldNameINDEX/bindFieldName projectName/projectName svnUrl/svnUrl svnUserName/svnUserName svnPassword/svnPassword /com.moded.extendedchoiceparameter.ExtendedChoiceParameterDefinition com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition plugin="extended-choice-parameter@0.30" nameINDEX/name description/description quoteValuefalse/quoteValue visibleItemCount5/visibleItemCount typePT_SINGLE_SELECT/type value/value propertyFile/propertyFile propertyKeykey/propertyKey defaultValue/defaultValue defaultPropertyFile/defaultPropertyFile defaultPropertyKey/defaultPropertyKey multiSelectDelimiter,/multiSelectDelimiter /com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition /parameterDefinitions /hudson.model.ParametersDefinitionProperty /properties scm class="hudson.scm.NullSCM"/ canRoamtrue/canRoam disabledfalse/disabled blockBuildWhenDownstreamBuildingfalse/blockBuildWhenDownstreamBuilding blockBuildWhenUpstreamBuildingfalse/blockBuildWhenUpstreamBuilding triggers/ concurrentBuildfalse/concurrentBuild builders hudson.tasks.Shell commandenv/command /hudson.tasks.Shell /builders publishers/ buildWrappers/ Base job without Bind to field jenkins@usaxqkr017cczra xx_job1$ cat config.xml ?xml version='1.0' encoding='UTF-8'? project actions/ description/description keepDependenciesfalse/keepDependencies properties hudson.model.ParametersDefinitionProperty parameterDefinitions com.moded.extendedchoiceparameter.ExtendedChoiceParameterDefinition plugin="dynamic_extended_choice_parameter@1.0.1" nameSITE/name description/description quoteValuefalse/quoteValue svnPathfalse/svnPath roleBasedFilterfalse/roleBasedFilter visibleItemCount5/visibleItemCount typePT_SINGLE_SELECT/type value/value propertyFile/dimp/zzz/sites/jenkins_choices/management.sites/propertyFile propertyKeykey/propertyKey defaultValue/defaultValue defaultPropertyFile/defaultPropertyFile
[JIRA] [cobertura-plugin] (JENKINS-25635) Cobertura plugin should show still reachable errors on the trens graph
Csaba Kertesz created JENKINS-25635 Cobertura plugin should show still reachable errors on the trens graph Issue Type: New Feature Assignee: stephenconnolly Components: cobertura-plugin Created: 15/Nov/14 4:02 PM Description: I don't know if it is relevant for Java projects, but I use for C++ code with valgrind - gcovr - cobertura plugin and the trend graphs of cobertura does not contain the "still reachable" errors. Project: Jenkins Priority: Minor Reporter: Csaba Kertesz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-pipeline-plugin] (JENKINS-25578) Internet Explorer Compatibility
Daniel Beck updated JENKINS-25578 Internet Explorer Compatibility Change By: Daniel Beck (15/Nov/14 4:28 PM) Labels: ieuser-experience This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [configurationslicing-plugin] (JENKINS-25320) UnsupportedOperationException when updating Max # of builds to keep
Ninian commented on JENKINS-25320 UnsupportedOperationException when updating Max # of builds to keep The exception looks like it is the result of configuration being done on the matrix configuration rather than the Project itself. I'd therefore expect it to be fixed by the fix for JENKINS-18455. Can you attempt to reproduce with version 1.40 of the configuration-slicing plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [configurationslicing-plugin] (JENKINS-18455) all modules of all maven projects are listed separately
Ninian resolved JENKINS-18455 as Fixed all modules of all maven projects are listed separately Should be fixed in version 1.40 of the plugin. Change By: Ninian (15/Nov/14 5:02 PM) Status: Reopened Resolved Assignee: NicolasDeLoof Ninian Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16887) Allow usage of environment variables in the Data Directory field
Christian Gahlert commented on JENKINS-16887 Allow usage of environment variables in the Data Directory field That would also be nice for the "Port" field... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [multijob-plugin] (JENKINS-25636) multijob does not finish if phase contains same job multiple times
Sebastian Schuberth created JENKINS-25636 multijob does not finish if phase contains same job multiple times Issue Type: Bug Assignee: Unassigned Attachments: multijob-config.jpg, multijob-does-not-finish.jpg Components: multijob-plugin Created: 15/Nov/14 7:13 PM Description: I have configured a multijob with a single phase that runs to builds of the same job (with different parameters) in parallel. See the attached screenshot for the job configuration. When the two builds succeed, the multijob does not finish. It keep running forever, see the second screenshot. Project: Jenkins Priority: Major Reporter: Sebastian Schuberth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [teamconcert-plugin] (JENKINS-18284) Team Concert plugin doesn't load components as root folders
Ivan Rossier commented on JENKINS-18284 Team Concert plugin doesnt load components as root folders No news on "We will consider adding this option in the future when you select, "Just accept and fetch from a build workspace" ? Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [teamconcert-plugin] (JENKINS-18284) Team Concert plugin doesn't load components as root folders
Ivan Rossier reopened JENKINS-18284 Team Concert plugin doesnt load components as root folders This issue has not been fixed when the option "Just accept and fetch from a build workspace" is selected. I haven't seen any other issue to track it. Thanks Change By: Ivan Rossier (15/Nov/14 9:38 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Richard Lavoie commented on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. It seems that a new version of Jenkins has added a method call to Jenkins.getInstance() when create a new Channel (the trick I use to create multiple selenium slaves per node) which makes this error occur when the code is executed on the slave. When the code is executed on the slave, Jenkins.getInstance() returns null. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [xshell-plugin] (JENKINS-25600) XShell does not kill running process if job is getting aborted
Jeremy Marshall started work on JENKINS-25600 XShell does not kill running process if job is getting aborted Change By: Jeremy Marshall (16/Nov/14 12:17 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [xshell-plugin] (JENKINS-25600) XShell does not kill running process if job is getting aborted
Jeremy Marshall assigned JENKINS-25600 to Jeremy Marshall XShell does not kill running process if job is getting aborted Change By: Jeremy Marshall (16/Nov/14 12:17 AM) Assignee: JeremyMarshall This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-24063) Would be nice to have a console output area for template testing
Alex Earl resolved JENKINS-24063 as Fixed Would be nice to have a console output area for template testing Fixed in c137a9. Should be part of 2.39. Change By: Alex Earl (16/Nov/14 3:15 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-23990) Output more helpful messages for cases where emails can't or won't be sent
Alex Earl assigned JENKINS-23990 to Alex Earl Output more helpful messages for cases where emails cant or wont be sent Change By: Alex Earl (16/Nov/14 3:16 AM) Assignee: AlexEarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [token-macro-plugin] (JENKINS-18271) TokenMacro.expand() duplicates private macros when called multiple times
Alex Earl resolved JENKINS-18271 as Fixed TokenMacro.expand() duplicates private macros when called multiple times This has already been resolved. See the linked issue. Change By: Alex Earl (16/Nov/14 3:19 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
