[JIRA] [workflow-plugin] (JENKINS-28187) redefining "node" causes unrecoverable hang
Anshu Arya
created JENKINS-28187
redefining "node" causes unrecoverable hang
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
02/May/15 2:44 AM
Description:
if you "def node = my_node" and then try to do a node allocation via "node {}", the job will hang at that allocation, requiring a hard kill described in (JENKINS-25550)
Project:
Jenkins
Priority:
Minor
Reporter:
Anshu Arya
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] [deploy-plugin] (JENKINS-24096) Jenkins Tomcat deploymet error
Charlie Hubbard edited a comment on JENKINS-24096 Jenkins Tomcat deploymet error I get this error once I try to redeploy the app. There doesn't seem to be a way to fix this without erasing the war and exploded directory then it will deploy without error. I find debugging this from looking at the output from the plugin is seriously obtuse. There is nothing printed out about what the server returned. The access logs on tomcat say a 200 success was returned, but nothing else. Just this obtuse exception with no real explanation. I also don't get any errors in the manager logs on tomcat. I feel like there could be a bug here, but because there is no actual error message it's impossible to tell what's really wrong. Actually I think you are experiencing the same thing. Notice this line: projs.war is not deployed. Doing a fresh deployment. I'm not sure why the plugin can't undeploy or redeploy, but it's not working. I've checked my logs and stopping the app should work, but I don't see it trying to stop it. 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-27739) Changes to slave environment variables are ignored by master
A C commented on JENKINS-27739 Changes to slave environment variables are ignored by master Verified the same behavior on Jenkins 1.611 with EnvInject. Changing a slave node's PATH has no effect on what Jenkins sets the PATH to during a build even after a slave service restart. Restarting the slave operating system still has no effect, the PATH is not refreshed. Restarting the master Jenkins server finally did allow PATH to get refreshed. The server is definitely caching an old PATH and then re-assigning it (via EnvInject?) to the slave node process. This is very bad. Since changing environment variables necessitates at least a slave process restart, it would seem the proper fix is to refresh the master server's cache of a node's environment during slave-service startup. 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-28145) Editable E-Mail Notification PreSend not loading CLASSPATH
Alex Earl resolved JENKINS-28145 as Fixed Editable E-Mail Notification PreSend not loading CLASSPATH Added expansion of variables to classpath resolution. Change By: Alex Earl (02/May/15 1:07 AM) Status: In Progress 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-28145) Editable E-Mail Notification PreSend not loading CLASSPATH
SCM/JIRA link daemon commented on JENKINS-28145 Editable E-Mail Notification PreSend not loading CLASSPATH Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherTest.java http://jenkins-ci.org/commit/email-ext-plugin/1a52cc262fda8de69128cc277bb03d6c8fe3b7de Log: Fix JENKINS-28145 Added resolution of variables to the classpath expansion. 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-28145) Editable E-Mail Notification PreSend not loading CLASSPATH
Alex Earl started work on JENKINS-28145 Editable E-Mail Notification PreSend not loading CLASSPATH Change By: Alex Earl (02/May/15 1:07 AM) Status: Open In Progress 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] [deploy-plugin] (JENKINS-24096) Jenkins Tomcat deploymet error
Charlie Hubbard commented on JENKINS-24096 Jenkins Tomcat deploymet error I get this error once I try to redeploy the app. There doesn't seem to be a way to fix this without erasing the war and exploded directory then it will deploy without error. I find debugging this from looking at the plugin is seriously obtuse. There is nothing printed out about what the server returned. The access logs on tomcat say a 200 success was returned, but nothing else. Just this obtuse exception with no real explanation. I also don't get any errors in the manager logs on tomcat. I feel like there could be a bug here, but because there is no actual error message it's impossible to tell what's really wrong. 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] [git-plugin] (JENKINS-28165) git ls-remote fails to connect to repo - status code 128
Mark Waite commented on JENKINS-28165 git ls-remote fails to connect to repo - status code 128 The credentials mechanism in Jenkins will allow you to limit the use of a private key to a specific domain and/or a specific URL scheme (https, ssh, etc.). That allows a private key dedicated to the Jenkins user, with users not allowed to apply that private key anywhere other than the domains for which it is intended. 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-24869) POM_VERSION is not resetted
Kenneth Younger commented on JENKINS-24869 POM_VERSION is not resetted Can reproduce. 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] [copyartifact-plugin] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
george trubisky commented on JENKINS-22002 Copy Artifact doesn't support jobs in different Folders I had exact same issue, using "*" in permission to copy artifact worked for use also because access control for the artifacts is not important. 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] [remoting] (JENKINS-26759) FileSystemJarCache not defensive enough
SCM/JIRA link daemon commented on JENKINS-26759 FileSystemJarCache not defensive enough Code changed in jenkins User: Akshay Dayal Path: src/main/java/hudson/remoting/Checksum.java src/main/java/hudson/remoting/FileSystemJarCache.java src/main/java/hudson/remoting/JarLoaderImpl.java src/main/java/hudson/remoting/RemoteClassLoader.java src/test/java/hudson/remoting/ChecksumTest.java src/test/java/hudson/remoting/FileSystemJarCacheTest.java http://jenkins-ci.org/commit/remoting/07509891ab5c16b85e115b2174a59ffdfe55db60 Log: JENKINS-26759 Make FileSystemJarCache more defensive. After a jar is fetched verify the checksum matches the expected value, if not throw an exception. 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] [remoting] (JENKINS-26759) FileSystemJarCache not defensive enough
SCM/JIRA link daemon commented on JENKINS-26759 FileSystemJarCache not defensive enough Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/Checksum.java src/main/java/hudson/remoting/FileSystemJarCache.java src/main/java/hudson/remoting/JarLoaderImpl.java src/test/java/hudson/remoting/ChecksumTest.java src/test/java/hudson/remoting/FileSystemJarCacheTest.java http://jenkins-ci.org/commit/remoting/94ce96d639b7b32f64a29afc632fbded4ba3a4b8 Log: Merge pull request #44 from akshayabd/JENKINS-26759 JENKINS-26759 Make FileSystemJarCache more defensive Compare: https://github.com/jenkinsci/remoting/compare/846b3e0527aa...94ce96d639b7 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] [workflow-plugin] (JENKINS-28179) Workspace suffix should respect hudson.slaves.WorkspaceList
SCM/JIRA link daemon resolved JENKINS-28179 as Fixed Workspace suffix should respect hudson.slaves.WorkspaceList Change By: SCM/JIRA link daemon (01/May/15 9:40 PM) 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] [workflow-plugin] (JENKINS-28179) Workspace suffix should respect hudson.slaves.WorkspaceList
SCM/JIRA link daemon commented on JENKINS-28179 Workspace suffix should respect hudson.slaves.WorkspaceList Code changed in jenkins User: Jesse Glick Path: CHANGES.md http://jenkins-ci.org/commit/workflow-plugin/408efbcfbc2f8603c23219321bb6ddbafb0117f6 Log: [FIXED JENKINS-28179] Noting merge of #124. 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] [workflow-plugin] (JENKINS-28179) Workspace suffix should respect hudson.slaves.WorkspaceList
SCM/JIRA link daemon commented on JENKINS-28179 Workspace suffix should respect hudson.slaves.WorkspaceList Code changed in jenkins User: Jesse Glick Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java http://jenkins-ci.org/commit/workflow-plugin/b888a17b1af1fa0501c323c409985f4cfc887380 Log: Merge pull request #124 from rpocase/master JENKINS-28179 Workspace suffix should respect hudon.slaves.WorkspaceList property Compare: https://github.com/jenkinsci/workflow-plugin/compare/0201a1211f28...b888a17b1af1 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] [packer-plugin] (JENKINS-28186) Packer installer from packer.io just a text box
Darren Hartford commented on JENKINS-28186 Packer installer from packer.io just a text box JENKINS_HOME/updates/biz.neustar.jenkins.plugins.paker.PackerInstaller has the JSON list of all the downloads on a sample system that works, while on the fresh system there is no file. 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] [active-directory-plugin] (JENKINS-8119) Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user 'kgraham' or incorrect password, when 1.1
marlene cote commented on JENKINS-8119 Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user 'kgraham' or incorrect password, when 1.16 does not jenkins version 1.611 - ldap, active directory and ssh plugins all installed an up to date. trying to login via cli:C:\Windows\system32\java.exe -jar d:\jenkins\jenkins-cli.jar -s http:// WARNING: AD chain lookup is taking too long (22ms). Falling back to recursive lookup May 01, 2015 4:39:15 PM hudson.cli.CLICommand main INFO: CLI login attempt failed: c665d7b1-4032-4be9-acd8-66bb3f4b0475 hudson.security.UserMayOrMayNotExistException: Unable to retrieve the user information without bind DN/password configured at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:330) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:219) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:163) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:53) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.loadUserByUsername(ActiveDirectorySecurityRealm.java:657) at hudson.cli.ClientAuthenticationCache.set(ClientAuthenticationCache.java:99) at hudson.cli.LoginCommand.run(LoginCommand.java:37) at hudson.cli.CLICommand.main(CLICommand.java:237) at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:326) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:325) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63) at hudson.remoting.CallableDecoratorAdapter.call(CallableDecoratorAdapter.java:18) at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 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] [packer-plugin] (JENKINS-28186) Packer installer from packer.io just a text box
Darren Hartford created JENKINS-28186 Packer installer from packer.io just a text box Issue Type: Improvement Assignee: Unassigned Components: packer-plugin Created: 01/May/15 8:38 PM Description: When given the option to checkbox 'install automatically' on an older (several days since packer plugin install), there is now a way to "install from packer site" with a pulldown list of the options (i.e. Packer 0.7.5 linux-386). Problem: Fresh installs only get 4 options, with bare text boxes: extract from *.gz Install from packer site (just a textbox to fill in, no options) Run Batch Run Shell Desired outcome: a way to get the "install from packer site" to force a 'pull' or 'refresh' so there is a pulldown option to select like the other system that has been just sitting for days (versus a fresh install that is not useful). Environment: Jenkins 1.596.2 (LTS), packer plugin 1.0 Project: Jenkins Priority: Minor Reporter: Darren Hartford 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] [parameterized-remote-trigger-plugin] (JENKINS-28185) Parameterized Remote Trigger fails when calling a job with Matrix Combination parameter
abayer created JENKINS-28185 Parameterized Remote Trigger fails when calling a job with Matrix Combination parameter Issue Type: Bug Assignee: Maurice W. Components: parameterized-remote-trigger-plugin Created: 01/May/15 8:35 PM Description: When calling a remote parameterized job that has as one of its parameters the Matrix Combination parameter, the Parameterized Remote Trigger plugin fails: FATAL: JSONObject["value"] not found. net.sf.json.JSONException: JSONObject["value"] not found. at net.sf.json.JSONObject.getString(JSONObject.java:2040) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.compareParameters(RemoteBuildConfiguration.java:681) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:572) at org.jenkinsci.plugins.conditionalbuildstep.BuilderChain.perform(BuilderChain.java:71) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154) at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105) at org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuilder.perform(ConditionalBuilder.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) at hudson.model.Run.execute(Run.java:1665) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) This seems to be because the .../api/json for the parameters of the build it kicked off only has a name field, no value, for the Matrix Combination parameter. Project: Jenkins Priority: Minor Reporter: abayer 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] [copyartifact-plugin] (JENKINS-28184) "Downstream build of" only selects most recent build
Simon Weber created JENKINS-28184 "Downstream build of" only selects most recent build Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 01/May/15 8:26 PM Description: The downstream build selector does not work with multiple downstream builds; only artifacts from the most recent downstream build are copied. Environment: Jenkins 1.593 copyartifact 1.35 Project: Jenkins Priority: Minor Reporter: Simon Weber 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] [mstest-plugin] (JENKINS-28166) Add checkbox to ignore missing TRX Files
SCM/JIRA link daemon commented on JENKINS-28166 Add checkbox to ignore missing TRX Files Code changed in jenkins User: Ivo Bellin Salarin Path: src/main/java/hudson/plugins/mstest/MSTestPublisher.java src/main/java/hudson/plugins/mstest/MSTestTransformer.java src/main/resources/hudson/plugins/mstest/MSTestPublisher/config.jelly http://jenkins-ci.org/commit/mstest-plugin/de9d45a3d686e594e78467d09b46810ee2a023bb Log: Merge pull request #7 from cjbush/master JENKINS-28166 Added checkbox to ignore missing TRX files Compare: https://github.com/jenkinsci/mstest-plugin/compare/74404cc62a70...de9d45a3d686 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] [mstest-plugin] (JENKINS-28166) Add checkbox to ignore missing TRX Files
SCM/JIRA link daemon commented on JENKINS-28166 Add checkbox to ignore missing TRX Files Code changed in jenkins User: Chris Bush Path: src/main/java/hudson/plugins/mstest/MSTestPublisher.java src/main/java/hudson/plugins/mstest/MSTestTransformer.java src/main/resources/hudson/plugins/mstest/MSTestPublisher/config.jelly http://jenkins-ci.org/commit/mstest-plugin/2e42acb57c2c635049ef0a5b3970332f8319d5f7 Log: JENKINS-28166 Added checkbox to ignore missing TRX files 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] [git-plugin] (JENKINS-28165) git ls-remote fails to connect to repo - status code 128
Ken Keefe commented on JENKINS-28165 git ls-remote fails to connect to repo - status code 128 Thank you for working on this. The only workaround I've discovered so far is to manually ssh into my master and slaves and set up password-less public key authentication between the master and slaves and the repo server. My fetch now works successfully. However, this is very inconvenient since I can't manage my credentials in Jenkins and password-less keys make me very nervous about sharing my Jenkins server with other developers. I really wish there was some nice way to debug the authentication problem when trying to use username/password Jenkins credentials with the git 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] [core] (JENKINS-27922) Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread
Jamie Doornbos edited a comment on JENKINS-27922 Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread This is becoming more serious for us as we approach full rollout. Currently, jenkins needs to be restarted every 6 hours and this is sometimes not enough. It also means builds that take longer than 6 hours currently have to be run out of band (from a separate command shell). This means we may be forced to replace jenkins at the last minute, which would make me sad. BUT... my employer want to sponsor this issue. How much money would be a good enough incentive? I suggested $500. Do you have any reproducible case or some idea of how to fix? Would it be okay to state the terms as something like "my jenkins instance does not fail due to SSH Agent after 2 days"? 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-27922) Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread
Jamie Doornbos commented on JENKINS-27922 Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread Hi, are you able to replicate this problem? This is becoming more serious for us as we approach full rollout. Currently, jenkins needs to be restarted every 6 hours and this is sometimes not enough. It also means builds that take longer than 6 hours currently have to be run out of band (from a separate command shell). This means we may be forced to replace jenkins at the last minute, which would make me sad. BUT... my employer want to sponsor this issue. How much money would be a good enough incentive? I suggested $500. Do you have any reproducible case or some idea of how to fix? Would it be okay to state the terms as something like "my jenkins instance does not fail due to SSH Agent after 2 days"? 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] [workflow-plugin] (JENKINS-28179) Workspace suffix should respect hudson.slaves.WorkspaceList
Robby Pocase commented on JENKINS-28179 Workspace suffix should respect hudson.slaves.WorkspaceList This has been addressed in the following pull request: https://github.com/jenkinsci/workflow-plugin/pull/124 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] [active-directory-plugin] (JENKINS-13940) I'm trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works.
marlene cote edited a comment on JENKINS-13940 I'm trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works. I am having a heck of time trying to setup ssh access to jenkins cli.. Is this issue still in the latest version of jenkins? org.jenkins-ci.main:jenkins-war:1.611 AD 1.39 I have tried using username password, ssh keys, etc. to no avail. 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] [workflow-plugin] (JENKINS-28183) Hard killed job's stage blocks stage in following jobs
Jesse Glick commented on JENKINS-28183 Hard killed job's stage blocks stage in following jobs Hmm, you might need to edit $JENKINS_HOME/org.jenkinsci.plugins.workflow.support.steps.StageStep.xml as a last resort. I am surprised at this report since there is a cleanUp function specifically to remove entries corresponding to builds that disappeared somehow without a clean exit. For some reason it is not getting called here, or is failing to detect the deleted build. It should have printed a warning to your log at some point saying Cleaning up apparently deleted job-name#480. I wonder if your job was renamed/moved at any point, or anything else unusual occurred? 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] [active-directory-plugin] (JENKINS-13940) I'm trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works.
marlene cote commented on JENKINS-13940 I'm trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works. I am having a heck of time trying to setup ssh access to jenkins cli.. Is this issue still in the latest version of jenkins? org.jenkins-ci.main:jenkins-war:1.611 AD 1.39 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] [mstest-plugin] (JENKINS-28166) Add checkbox to ignore missing TRX Files
Chris Bush commented on JENKINS-28166 Add checkbox to ignore missing TRX Files Created a pull request on GitHub. Seems to work on my test server. https://github.com/jenkinsci/mstest-plugin/pull/7 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] [workflow-plugin] (JENKINS-28183) Hard killed job's stage blocks stage in following jobs
Anshu Arya created JENKINS-28183 Hard killed job's stage blocks stage in following jobs Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 01/May/15 5:29 PM Description: Build #480 of my job hung in Stage 'Imaging' and I had to do a hard kill using BUILD_URL/doDelete Now all builds of my job hang on: Running: Imaging Entering stage Imaging Waiting for builds [480] Project: Jenkins Priority: Major Reporter: Anshu Arya 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] [workflow-plugin] (JENKINS-28183) Hard killed job's stage blocks stage in following jobs
Anshu Arya updated JENKINS-28183 Hard killed job's stage blocks stage in following jobs Change By: Anshu Arya (01/May/15 5:30 PM) Description: Build #480 of my job hung in Stage 'Imaging' and I had to do a hard kill using BUILD_URL/doDeleteNow all builds of my job hang on:Running: ImagingEntering stage ImagingWaiting for builds [480] Restarting Jenkins does not help. 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.
Available consultant hot list
*Greetings from Humac Inc.,* *Dear business partner, here is the updated list of available consultants from Humac for your daily requirements.* *Kindly contact us over email / **phone for quick response**. * Technology Visa Relocation Availability Contact Vmware & Windows Administrator H1b OPEN immediate g*i...@humacinc.com* 623-748-4392 *GIS SPECIALIST* H1B OPEN immediate COGNOS BI DEVELOPER H1b NC only immediate -- Gino Senior IT Recruiter Humac Inc Phone: 623-748-4392 Email: g...@humacinc.com -- 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.
Available consultant hot list
*Greetings from Humac Inc.,* *Dear business partner, here is the updated list of available consultants from Humac for your daily requirements.* *Kindly contact us over email / **phone for quick response**. * Technology Visa Relocation Availability Contact Vmware & Windows Administrator H1b OPEN immediate g*i...@humacinc.com* 623-748-4392 *GIS SPECIALIST* H1B OPEN immediate COGNOS BI DEVELOPER H1b NC only immediate -- Gino Senior IT Recruiter Humac Inc Phone: 623-748-4392 Email: g...@humacinc.com -- 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-25657) JUnit crashes during recording of test results in 1.580.1
Bob Rockers commented on JENKINS-25657 JUnit crashes during recording of test results in 1.580.1 I am getting this same error on 1.611 with JUnit 1.5 Project completes successfully and completed packages are moved. Then ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception hudson.AbortException: No test report files were found. Configuration error? 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] [ircbot-plugin] (JENKINS-22042) IRCBot disconnects after long idle
kutzi commented on JENKINS-22042 IRCBot disconnects after long idle @urras: as you changed this to Critical: can you provide more information. I.e. how to reproduce, error entries in log file etc? 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] [ircbot-plugin] (JENKINS-22042) IRCBot disconnects after long idle
kutzi commented on JENKINS-22042 IRCBot disconnects after long idle Herman, on further thoughts your issue seems to be pretty different from the originally reported issue - disconnecting and hanging on notifications is actually a totally different thing. Isn't it actually what you reported in JENKINS-26491? 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] [ircbot-plugin] (JENKINS-22042) IRCBot disconnects after long idle
kutzi commented on JENKINS-22042 IRCBot disconnects after long idle That is: for the error that Herman is reporting. Alexej's error might be a completely different one. No way to be sure until he clarifies what it means that the bot 'dies' 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] [ircbot-plugin] (JENKINS-22042) IRCBot disconnects after long idle
Nick Hovaker updated JENKINS-22042 IRCBot disconnects after long idle Change By: Nick Hovaker (01/May/15 2:13 PM) Priority: Major Critical 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-timeout-plugin] (JENKINS-16875) Builds do not timeout when job hangs in post build actions
Nick Hovaker commented on JENKINS-16875 Builds do not timeout when job hangs in post build actions The issue with the IRC notifications is really becoming a major pain, as we're getting it quite often now. It would be great to see some progress on this issue, given it's severity. 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] [xcode-plugin] (JENKINS-21375) XCode 5 needs more parameters to store xcarchive
John Doe commented on JENKINS-21375 XCode 5 needs more parameters to store xcarchive This is also an issue with Xcode 6. I'm not sure what "Generate Archive" is supposed to do if it's not to save out an archive. It does cause the .ipa creation to fail (if selected) and the build output directory is set. I can't see how to get a .xcarchive file with it either way. 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] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
kutzi commented on JENKINS-28175 config change deadlock Jenkins when pircx.shutdown() is invoked Opened an issue against PircBotX: https://code.google.com/p/pircbotx/issues/detail?id=240 Not sure if the issue persists in PircBotX 2.x as a lot has changed there. Trying to update to PircBotX 2.0.1 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] [git-plugin] (JENKINS-28165) git ls-remote fails to connect to repo - status code 128
Mark Waite commented on JENKINS-28165 git ls-remote fails to connect to repo - status code 128 That line usually means the call to "git fetch" failed. In your case, the message from the git fetch command: Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. indicates that it is trying to authenticate you and failing. I created a multi-configuration job in my test network using various operating systems and git versions with two different forms of username / password authentication. My ssh server in these tests is a Ubuntu 14.04 machine hosting a repository in the directory /var/lib/git/mwaite/bugs/JENKINS-28165.git. The master node is that Ubuntu 14.04 machine with the process running as the jenkins user. The repository is owned by the user mwaite. I've run out of time this morning to experiment with this, so won't be able to add more comments on this until after the end of the working day today. 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] [workflow-plugin] (JENKINS-28182) Revisit use of $JENKINS_SERVER_COOKIE and Launcher.kill
Jesse Glick
created JENKINS-28182
Revisit use of $JENKINS_SERVER_COOKIE and Launcher.kill
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
01/May/15 1:31 PM
Description:
PlaceholderExecutable needs an environment variable to add to the context to ensure that Launcher.kill, called when the block exits, will clean up any stray external processes run on this node.
Originally the name of this variable was chosen to be JENKINS_SERVER_COOKIE, which is set by Job (to a confidential hex key) and normally used by AbstractBuild for this purpose. Unlike in that case, for Workflow the value is overridden (to a random UUID) for each node block, since there may be several. I think the intent was to use the same variable name to suppress any unwanted kills coming from Jenkins core code, but there seem to be none. Anyway after the many refactorings of environment variable handling in Workflow, it turns out this is dead code!
FileMonitoringTask sets its own value for JENKINS_SERVER_COOKIE, to durable-, which overrides any other value, and is used by stop. So within a shell step, $JENKINS_SERVER_COOKIE is the one from durable-task, not PlaceholderExecutable.
env.JENKINS_SERVER_COOKIE picks up the value from Job, due to the precedence order in getEffectiveEnvironment.
So it seems that while the intention is still good (we would like a final check that any processes started inside node are killed when the block exits), the implementation is not right. Probably PlaceholderExecutable just needs to pick an unrelated environment variable for this purpose. And this logic needs to be tested; for example:
def file = new File(...);
node {
sh "(sleep 5; touch $file) &"
}
sleep 10
assert !file.exists()
Project:
Jenkins
Labels:
process-killer
envinronment-variables
Priority:
Major
Reporter:
Jesse Glick
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] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
kutzi commented on JENKINS-28175 config change deadlock Jenkins when pircx.shutdown() is invoked Quite difficult to reproduce this. Seems only to happen when the channel mode is stale while PircBot is shut down. And stale mode seem only to happen, when the server returns something for mode, what Pircbot cannot parse. 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] [docker-build-step-plugin] (JENKINS-24800) docker plugin accept variables in pull image
Dave Shepherd resolved JENKINS-24800 as Cannot Reproduce docker plugin accept variables in pull image I think this has been fixed. I tested it by creating a job with two parameters: APP_NAME and TAG Added a "Pull image" step that defined the following: Name of the image to pull (repository/image): $APP_NAME Tag: $TAG The values of the parameters are used when this step is executed and is successful when the appropriate values are specified, e.g. APP_NAME=busybox, TAG=latest Jenkins v1.604 docker-build-step plugin v1.23 Change By: Dave Shepherd (01/May/15 11:01 AM) Status: Open Resolved Resolution: Cannot Reproduce 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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
SCM/JIRA link daemon resolved JENKINS-26077 as Fixed Multiple Test Reports Graphs and Links in Job Page Change By: SCM/JIRA link daemon (01/May/15 10:51 AM) Status: In Progress 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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
SCM/JIRA link daemon commented on JENKINS-26077 Multiple Test Reports Graphs and Links in Job Page Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/tasks/junit/TestResultAction.java http://jenkins-ci.org/commit/junit-plugin/081305a2f7bfc25a6dee20f6b1e617fa6dcd2a70 Log: [FIXED JENKINS-26077] Be sure not to add two copies of TestResultProjectAction to the job. 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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
SCM/JIRA link daemon commented on JENKINS-26077 Multiple Test Reports Graphs and Links in Job Page Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/tasks/junit/TestResultAction.java http://jenkins-ci.org/commit/junit-plugin/49139a4854e7eb596980e95d22e16f7c7258e877 Log: Merge pull request #18 from jglick/duplicated-TestResultProjectAction-JENKINS-26077 JENKINS-26077 Duplicated TestResultProjectAction Compare: https://github.com/jenkinsci/junit-plugin/compare/4e0eaee03105...49139a4854e7 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] [delivery-pipeline-plugin] (JENKINS-28146) Manual trigger step fails with the new version
Nicolae Ghimbovschi commented on JENKINS-28146 Manual trigger step fails with the new version Version 0.8.11 fixed this issue. 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] [delivery-pipeline-plugin] (JENKINS-28146) Manual trigger step fails with the new version
Nicolae Ghimbovschi resolved JENKINS-28146 as Fixed Manual trigger step fails with the new version Is fixed in v0.8.11 of the delivery pipeline Change By: Nicolae Ghimbovschi (01/May/15 10:44 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] [additional-identities-plugin] (JENKINS-28181) Incompatible with email-ext?
Daniel Beck resolved JENKINS-28181 as Fixed Incompatible with email-ext? Fixed in https://github.com/jenkinsci/additional-identities-plugin/commit/dc49902e0599324964e5f2a2a2ae824eb7b962e6, but unreleased so far. Change By: Daniel Beck (01/May/15 9:55 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.
