[JIRA] [build-publisher] (JENKINS-21250) NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+
Lucie Votypkova commented on JENKINS-21250 NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+ I will look at it, it seems that something was changed. 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/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-20176) Disk usage plugin write job config.xml after every build
Lucie Votypkova commented on JENKINS-20176 Disk usage plugin write job config.xml after every build I tested and it seemed ok. I will test it again and I wrote some tests for 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Alexey Kislin commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Thanks, Adrian Smith. I have got this issue on Linux server and replacing "/bin/echo " with "/bin/echo" helps me. 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21369) Git client fails to remove files/directories with "git clean -fdx"
Hannu Piki created JENKINS-21369 Git client fails to remove files/directories with "git clean -fdx" Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git-client Created: 14/Jan/14 8:50 AM Description: This all has worked fine previously, but latest updates for some reason there have been these kind of issues, as described below. 1. Start Jenkins service 2. Trigger ex. 20 builds 3. Wait and see if one of them fails to build 4. See if the reason is Jenkins issue, not msbuild/unit test 5. Rest of builds that starts after failed one, will fail also with same output as below 6. Wipe workspaces manually 7. Builds will most likely start working again Triggered by Gerrit: http://xxx002:8080/4195 [EnvInject] - Loading node environment variables. Building on master in workspace r:\jenkins-workspaces Fetching changes from the remote Git repository Fetching upstream changes from ssh://hudson@002:29418/xxx.git Checking out Revision 45d62ed078309607e0b6a24b842ff33c93f3b740 (feature/WI3076) Cleaning workspace Resetting working tree FATAL: Command "git clean -fdx" returned status code 1: stdout: Removing Source/xxx/zzz/Areas Removing Source/xxx/zzz/Content Removing Source/xxx/zzz/Scripts Removing Source/xxx/zzz/Views stderr: warning: failed to remove Source/xxx/zzz/Areas warning: failed to remove Source/xxx/zzz/Content warning: failed to remove Source/xxx/zzz/Scripts warning: failed to remove Source/xxx/zzz/Views hudson.plugins.git.GitException: Command "git clean -fdx" returned status code 1: stdout: Removing Source/xxx/zzz/Areas Removing Source/xxx/zzz/Content Removing Source/xxx/zzz/Scripts Removing Source/xxx/zzz/Views stderr: warning: failed to remove Source/xxx/zzz/Areas warning: failed to remove Source/xxx/zzz/Content warning: failed to remove Source/xxx/zzz/Scripts warning: failed to remove Source/xxx/zzz/Views at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1086) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1063) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:900) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:910) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clean(CliGitAPIImpl.java:367) at hudson.plugins.git.GitAPI.clean(GitAPI.java:251) at hudson.plugins.git.extensions.impl.CleanCheckout.onCheckoutCompleted(CleanCheckout.java:28) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:890) at hudson.model.AbstractProject.checkout(AbstractProject.java:1415) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Environment: OS: Windows 2008 R2 Java: 1.6.0_26 Jenkins: 1.547 Git client: Newest (1.6.1) Other plugins: All are updated, like Git (2.0.1) Jenkins is running as Windows service, with Local system account Project: Jenkins Priority: Critical Reporter: Hannu Piki This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators.
[JIRA] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
x29a reopened JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing I am reopening this issue because i see the behavior in the current version of xUnit. Please see my comment for further investigation. Thanks! Change By: x29a (14/Jan/14 9:04 AM) 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/groups/opt_out.
[JIRA] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
x29a commented on JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing Unfortunately this seems to still occur on Windows 7 host (java version "1.7.0_17") Jenkins v1.544, xUnit 1.78 The build is configured to run without unittests, so there is nothing to parse for xUnit. The build itself ran just fine, but the raised Exception by xUnit marks it as failed. Config: "xunit@1.78"> *UnitTestU.log true false true false *UnittestG.log true false true false 1 1 3000 Error: Archiving artifacts [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing CppUnit-1.12.1 (default) [xUnit] [INFO] - [CppUnit-1.12.1 (default)] - No test report file(s) were found with the pattern '*UnitTestU.log' relative to 'e:\jenkins\workspace\build' for the testing framework 'CppUnit-1.12.1 (default)'. Did you enter a pattern relative to the correct directory? Did you generate the result report(s) for 'CppUnit-1.12.1 (default)'? [xUnit] [WARNING] - No test reports found for the metric 'CppUnit' with the resolved pattern '*UnitTestU.log'. ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception java.lang.InterruptedException: org.jenkinsci.plugins.xunit.SkipTestException at hudson.FilePath.act(FilePath.java:905) at hudson.FilePath.act(FilePath.java:887) at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:111) at org.jenkinsci.plugins.xunit.XUnitProcessor.performXUnit(XUnitProcessor.java:54) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:88) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.FilePath$TunneledInterruptedException: org.jenkinsci.plugins.xunit.SkipTestException at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2463) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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 hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Caused by: org.jenkinsci.plugins.xunit.SkipTestException at org.jenkinsci.plugins.xunit.service.XUnitTransformer.invoke(XUnitTransformer.java:142) at org.jenkinsci.plugins.xunit.service.XUnitTransformer.invoke(XUnitTransformer.java:17) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2461) ... 10 more Finished: FAILURE Checking the code on github i found the exception beeing thrown in https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/java/org/jenkinsci/plugins/xunit/service/XUnitTransformer.java and the problem seems to be that the exception is inheriting from "InterruptedException" here https://github.com/jenkinsci/xunit-plugin/blob/master/src/main/java/org/jenkinsci/plugins/xunit/SkipTestException.java which jenkins will fail on apperantly :/ 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
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Milosz Sotomski commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Replacing "/bin/echo " works for me to but only for builds thats only checking out project. I stil have mesage in build configuration: Failed to connect to repository : Command "git config --local --remove-section credential.helper" returned status code 255: stdout: stderr: error: could not lock config file .git/config And problem with Git publisher and Pushing results after successful build. Pushing HEAD to branch fix of origin repository ERROR: Failed to push merge to origin repository hudson.plugins.git.GitException: Failed to connect to https://git.farmaprom.pl/root/farmaprom.git (status = 401) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:1601) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:952) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.push(CliGitAPIImpl.java:1109) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.push(CliGitAPIImpl.java:1121) at hudson.plugins.git.GitAPI.push(GitAPI.java:65) at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:226) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Milosz Sotomski edited a comment on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Replacing "/bin/echo " works for me to but only for builds thats only checking out project. I stil have mesage in build configuration: Failed to connect to repository : Command "git config --local --remove-section credential.helper" returned status code 255: stdout: stderr: error: could not lock config file .git/config And problem with Git publisher and Pushing results after successful build. Pushing HEAD to branch fix of origin repository ERROR: Failed to push merge to origin repository hudson.plugins.git.GitException: Failed to connect to https://xxx.repo.org/project.git (status = 401) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:1601) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:952) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.push(CliGitAPIImpl.java:1109) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.push(CliGitAPIImpl.java:1121) at hudson.plugins.git.GitAPI.push(GitAPI.java:65) at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:226) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Alexey Kislin commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) stderr: error: could not lock config file .git/config I have this message too. But only at the configuration page. I think the cause is that current directory is not the workspace of a project, so git cannot find ".git/config" 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/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21370) Addprojectlabel functionality is not available with 1.20 / Extend addprojectlabel with recurse subproject feature.
Christian Bürenheide created JENKINS-21370 Addprojectlabel functionality is not available with 1.20 / Extend addprojectlabel with recurse subproject feature. Issue Type: Bug Assignee: Cletus D'Souza Components: integrity-plugin Created: 14/Jan/14 9:37 AM Description: Hi, with the code changes made on IntegrityCheckpointAction.java in commit dde34906510a9ab528438fe177680c1be1f5d428, the possibility to perform a 'addprojectlabel' after a build has been removed. This functionality was available until integrity-plugin 1.19. For us it was a very useful functionality which we are missing now. In our environment we 1) Make a checkpoint (without label) before the build 2) Add the label to the checkpoint after a successful build. So we only apply labels to successful builds which is important to keep the project histories clear and comprehensible. In my opinion the possibility to set a checkpoint label before the build (which is a new feature) is not enough. We would further like to have the 'addprojectlabel' functionality implemented in a way that it reverses subprojects. I already made the needed code changes in my fork "cbue/integrity-plugin" and will provide a pull request for this issue. Best regards Christian Due Date: 14/Jan/14 12:00 AM Project: Jenkins Priority: Major Reporter: Christian Bürenheide 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/groups/opt_out.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-18605) Cannot get RemoteAgent's ClassID for test type
Avishai Moshka assigned JENKINS-18605 to Avishai Moshka Cannot get RemoteAgent's ClassID for test type Change By: Avishai Moshka (14/Jan/14 9:45 AM) Assignee: Ofir Shaked Avishai Moshka 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/groups/opt_out.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-18605) Cannot get RemoteAgent's ClassID for test type
Avishai Moshka started work on JENKINS-18605 Cannot get RemoteAgent's ClassID for test type Change By: Avishai Moshka (14/Jan/14 9:49 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/groups/opt_out.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-18605) Cannot get RemoteAgent's ClassID for test type
Avishai Moshka commented on JENKINS-18605 Cannot get RemoteAgent's ClassID for test type hi, HP automation plugin does not support executing LoadRunner scenarios from ALM. the documentation will be updated. 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/groups/opt_out.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-18605) Cannot get RemoteAgent's ClassID for test type
Avishai Moshka stopped work on JENKINS-18605 Cannot get RemoteAgent's ClassID for test type Change By: Avishai Moshka (14/Jan/14 9:49 AM) Status: In Progress Open 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/groups/opt_out.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-18605) Cannot get RemoteAgent's ClassID for test type
Avishai Moshka resolved JENKINS-18605 as Not A Defect Cannot get RemoteAgent's ClassID for test type this is not supported. this plugin can run only UFT (Functional tests) from ALM Change By: Avishai Moshka (14/Jan/14 9:53 AM) Status: Open Resolved Fix Version/s: current Resolution: Not A Defect 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Peter Phillips commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Further to my previous comment: The git configuration page runs 'git config --local', which will always require a workspace, but one doesn't exist (or hasn't been initialised at that point). That is why polling doesn't work too, as there is no workspace then either. We could go down the route of requiring an initialised workspace, but that seems like a backwards step as the git client was recently changed to do a ls-remote and therefore not to require a workspace (e.g. see JENKINS-10131). I've created a fork with the config set to system too - see https://github.com/pphillips-techphob/git-client-plugin/tree/config-system. I found that the Windows user that Jenkins is running as doesn't have a user home directory so therefore required that the configuration be stored in git home instead. 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/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-21250) NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+
Henrique Rodrigues commented on JENKINS-21250 NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+ Bruce Edge, I've read (somewhere) that this should be fixed in 1.547, released yesterday. Could you test it please? 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/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-21250) NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+
Hack Kampbjørn commented on JENKINS-21250 NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+ I can confirm that this is fixed in 1.547 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/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-21250) NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+
Norbert Pfistner commented on JENKINS-21250 NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+ I can also confirm that this is fixed in 1.547 Many 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/groups/opt_out.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-18201) Sumbit job with "Execute HP tests *" step crashed with 500 error
Avishai Moshka commented on JENKINS-18201 Sumbit job with "Execute HP tests *" step crashed with 500 error hi, this was fixed on version 2.0.2 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/groups/opt_out.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-18201) Sumbit job with "Execute HP tests *" step crashed with 500 error
Avishai Moshka resolved JENKINS-18201 as Fixed Sumbit job with "Execute HP tests *" step crashed with 500 error Change By: Avishai Moshka (14/Jan/14 11:15 AM) Status: Open Resolved Assignee: Ofir Shaked Avishai Moshka Fix Version/s: current 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/groups/opt_out.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-17776) Add option to save entire results folder, not just report
Avishai Moshka assigned JENKINS-17776 to Avishai Moshka Add option to save entire results folder, not just report Change By: Avishai Moshka (14/Jan/14 11:20 AM) Assignee: Ofir Shaked Avishai Moshka 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/groups/opt_out.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-17776) Add option to save entire results folder, not just report
Avishai Moshka commented on JENKINS-17776 Add option to save entire results folder, not just report hi, can you please share some more info? what is the test type? LoadRunner? UFT/Functional? 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/groups/opt_out.
[JIRA] [core] (JENKINS-21371) Enhance SecurityRealm API to support queries of the group membership
stephenconnolly created JENKINS-21371 Enhance SecurityRealm API to support queries of the group membership Issue Type: New Feature Assignee: Unassigned Components: core Created: 14/Jan/14 11:23 AM Description: It can be useful in the UIs of AuthorizationStrategies to allow the user to see the members of the groups defined external to Jenkins (i.e. defined in the backing SecurityRealm) It is likely that not every security realm will support this operation, but certainly realms such as ActiveDirectory and LDAP should be able to support retrieving this information, so we should provide an API that permits these realms to provide this extra information so that AuthorizationStrategies can enhance the UX Project: Jenkins Priority: Minor Reporter: stephenconnolly 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/groups/opt_out.
[JIRA] [maven] (JENKINS-21372) NPE when releasing all locks
andre klim created JENKINS-21372 NPE when releasing all locks Issue Type: Bug Assignee: Unassigned Components: maven Created: 14/Jan/14 11:31 AM Description: [locks-and-latches] Releasing all the locks [locks-and-latches] All the locks released ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException at java.util.StringTokenizer.(StringTokenizer.java:199) at java.util.StringTokenizer.(StringTokenizer.java:236) at hudson.tasks.MailSender.createEmptyMail(MailSender.java:326) at hudson.tasks.MailSender.createUnstableMail(MailSender.java:186) at hudson.tasks.MailSender.getMail(MailSender.java:160) at hudson.tasks.MailSender.execute(MailSender.java:100) at hudson.maven.reporters.MavenMailer.end(MavenMailer.java:56) at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:103) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:829) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) at hudson.model.Run.execute(Run.java:1678) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Project: Jenkins Priority: Blocker Reporter: andre klim 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/groups/opt_out.
[JIRA] [maven] (JENKINS-21372) NPE when parsing emails for notification when build is unstable and email field does not contain any email
andre klim updated JENKINS-21372 NPE when parsing emails for notification when build is unstable and email field does not contain any email Change By: andre klim (14/Jan/14 11:35 AM) Summary: NPE when releasing all locks parsing emails for notification when build is unstable and email field does not contain any email 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/groups/opt_out.
[JIRA] [core] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
Jürgen Prechtl created JENKINS-21373 Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547 Issue Type: Bug Assignee: Unassigned Components: core, plugin Created: 14/Jan/14 11:36 AM Description: After upgrading Jenkins to version 1.547 it's not possible to connect to a Windows slave annymore. The only log output is: Connecting to Checking if Java exists Java is installed and works. Project: Jenkins Priority: Major Reporter: Jürgen Prechtl 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/groups/opt_out.
[JIRA] [core] (JENKINS-21371) Enhance SecurityRealm API to support queries of the group membership
SCM/JIRA link daemon commented on JENKINS-21371 Enhance SecurityRealm API to support queries of the group membership Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/security/GroupDetails.java core/src/main/java/hudson/security/SecurityRealm.java http://jenkins-ci.org/commit/jenkins/4ace130e3b9c4145cc639eb07032d6cc0a0ea84d Log: Merge pull request #1088 from stephenc/master [FIXED JENKINS-21371] Enhance SecurityRealm API to support queries of the group membership Compare: https://github.com/jenkinsci/jenkins/compare/b01ad4d4b8bf...4ace130e3b9c 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/groups/opt_out.
[JIRA] [core] (JENKINS-21371) Enhance SecurityRealm API to support queries of the group membership
SCM/JIRA link daemon resolved JENKINS-21371 as Fixed Enhance SecurityRealm API to support queries of the group membership Change By: SCM/JIRA link daemon (14/Jan/14 11:49 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/groups/opt_out.
[JIRA] [core] (JENKINS-21371) Enhance SecurityRealm API to support queries of the group membership
SCM/JIRA link daemon commented on JENKINS-21371 Enhance SecurityRealm API to support queries of the group membership Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/security/GroupDetails.java core/src/main/java/hudson/security/SecurityRealm.java http://jenkins-ci.org/commit/jenkins/ec12c07ef51cc38b60ffeb1808c69c155866926e Log: [FIXED JENKINS-21371] Enhance SecurityRealm API to support queries of the group membership 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/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
Daniel Beck commented on JENKINS-20772 'Apply' error screens don't work This wasn't backported completely to the 1.532.2 RC. My improvements are missing, so the error dialog cannot be scrolled and shows an entire Jenkins page with header, sidebar, and everything. 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/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
Alex Ouzounis commented on JENKINS-20935 Provide separate monitoring pages for each slave node Just updated to the Monitoring plugin version 1.49 and all links in the node/monitoring page instead of starting with my defined Jenkins URL (host/jenkins) start with just the host making the links and images broken. Is anyone else seeing the same 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/groups/opt_out.
[JIRA] [ldap] (JENKINS-21374) Add option to remove obsolete 'ROLE_' prefixed groups
Daniel Beck created JENKINS-21374 Add option to remove obsolete 'ROLE_' prefixed groups Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: ldap Created: 14/Jan/14 12:22 PM Description: LDAP plugin duplicates every group membership 'foo' as 'ROLE_FOO'. This should be made optional (or even removed). Project: Jenkins Priority: Minor Reporter: Daniel Beck 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/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-21368) After installation of Promoted Builds Plugin some jobs that are NOT using plugin got FATALs.
Seweryn Habdank-Wojewodzki commented on JENKINS-21368 After installation of Promoted Builds Plugin some jobs that are NOT using plugin got FATALs. It seems plugin collide with job that contains "Trigger/call builds on the other projects". After removal of that build part job is working, but ofcourse that is not desired. And again job DOES NOT contain enabled "Promote builds when...", what makes error very strange. How not enabled feature can collide with other features . 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/groups/opt_out.
[JIRA] [security] (JENKINS-2324) Feature - Set read permission by project for project-based security
Daniel Beck resolved JENKINS-2324 as Fixed Feature - Set read permission by project for project-based security Nathan Nobbe: Permissions cannot be removed on a per-project basis. You need to give everyone 'Overall/Read' globally, and then give them project-specific 'Job/Read' on every project they should have access to. Change By: Daniel Beck (14/Jan/14 12:30 PM) Status: Reopened 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/groups/opt_out.
[JIRA] [matrix] (JENKINS-15464) Matrix-based security -Job cancel privilege not working
Daniel Beck commented on JENKINS-15464 Matrix-based security -Job cancel privilege not working This is just a UI issue. Like 'Administer' implies all other privileges (except those optional ones set on the command line), so does 'Build' imply 'Cancel'. The underlying cause is JENKINS-14713. 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/groups/opt_out.
[JIRA] [tracking-svn] (JENKINS-16340) Can't watch any projects
evernat resolved JENKINS-16340 as Cannot Reproduce Can't watch any projects So resolving as can't reproduce. Thanks Change By: evernat (14/Jan/14 12:35 PM) 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/groups/opt_out.
[JIRA] [core] (JENKINS-12038) Jenkins installs 32 bit JRE on Windows 2008 64 bit (the JRE in the JENKINS_HOME)
evernat resolved JENKINS-12038 as Incomplete Jenkins installs 32 bit JRE on Windows 2008 64 bit (the JRE in the JENKINS_HOME) No response from the reporter, so resolving as incomplete. Please reopen if needed. Change By: evernat (14/Jan/14 12:38 PM) Status: Open Resolved Resolution: Incomplete 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/groups/opt_out.
[JIRA] [plugin] (JENKINS-11871) Cannot access data in dropdownDescriptorSelector for validation
evernat resolved JENKINS-11871 as Incomplete Cannot access data in dropdownDescriptorSelector for validation No response from the reporter, so resolving as incomplete. Please reopen if needed. Change By: evernat (14/Jan/14 12:39 PM) Status: Open Resolved Resolution: Incomplete 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/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
Oleg Nenashev commented on JENKINS-20935 Provide separate monitoring pages for each slave node Yes, this is a known issue. It will be fixed in the next release. See https://github.com/jenkinsci/monitoring-plugin/commit/48469a309e6d235a9ff506f3e57a2586b4e807dc 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/groups/opt_out.
[JIRA] [core] (JENKINS-18911) Views should find all jobs that are "discoverable" OR "read" (currently only "read")
Daniel Beck commented on JENKINS-18911 Views should find all jobs that are "discoverable" OR "read" (currently only "read") This would probably break all list view columns that just assume that accessible jobs' information can be accessed. Discover also does not allow to list jobs anyway, based on its description, so I don't see how this is a bug. Could you please clarify this? This permission grants discover access to jobs. Lower than read permissions, it allows you to redirect anonymous users to the login page when they try to access a job url. Without it they would get a 404 error and wouldnt be able to discover project names. 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/groups/opt_out.
[JIRA] [cli] (JENKINS-16309) CLI errors with Job names containing dashes
evernat commented on JENKINS-16309 CLI errors with Job names containing dashes @Rita Garcia Is it reproduced for you? with a recent Jenkins version? 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/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
Alex Ouzounis
commented on JENKINS-20935
Provide separate monitoring pages for each slave node
thanks!
the problem though is also affecting the links (not only the icons) and the patch provided does not seem to include any fix for the actual links i.e. ${it.monitoringUrl} seems not to include the full Jenkins URL, although I could be easily 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-17900) subversion credentials are not stored in hudson.scm.SubversionSCM.xml
Daniel Beck commented on JENKINS-17900 subversion credentials are not stored in hudson.scm.SubversionSCM.xml Likely resolved with the Subversion plugin 2.0 (currently in beta) which uses Credentials plugin to store credentials. 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/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
Oleg Nenashev commented on JENKINS-20935 Provide separate monitoring pages for each slave node Yes, you are right. I'll submit a fix ASAP 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
SCM/JIRA link daemon commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Code changed in jenkins User: Nicolas De loof Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/7835f8c67f57a5e34dff0347b2667d7348cfc6df Log: Merge pull request #67 from anadimisra/master JENKINS-21016: removed whitespace from /bin/echo argument Compare: https://github.com/jenkinsci/git-client-plugin/compare/f759bca7872a...7835f8c67f57 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/groups/opt_out.
[JIRA] [core] (JENKINS-21371) Enhance SecurityRealm API to support queries of the group membership
dogfood commented on JENKINS-21371 Enhance SecurityRealm API to support queries of the group membership Integrated in jenkins_main_trunk #3167 [FIXED JENKINS-21371] Enhance SecurityRealm API to support queries of the group membership (Revision ec12c07ef51cc38b60ffeb1808c69c155866926e) Result = SUCCESS Stephen Connolly : ec12c07ef51cc38b60ffeb1808c69c155866926e Files : core/src/main/java/hudson/security/SecurityRealm.java core/src/main/java/hudson/security/GroupDetails.java 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/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-21250) NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+
Miquel Martin commented on JENKINS-21250 NullPointerException in AggregatedTestResultPublisher causes Job to fail after upgrade from 1.544 to 1.545+ One more confirmation that it now works from my side, thanks a bunch! 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/groups/opt_out.
[JIRA] [xcode] (JENKINS-21375) XCode 5 needs more parameters to store xcarchive
Daniel Kopp
created JENKINS-21375
XCode 5 needs more parameters to store xcarchive
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
xcode
Created:
14/Jan/14 2:19 PM
Description:
If you use XCode 5 you need to add -archivePath ${WORKSPACE}/YourApp.xcarchive to save the xcarchive. Otherwise non is stored.
Project:
Jenkins
Priority:
Major
Reporter:
Daniel Kopp
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/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
Oleg Nenashev reopened JENKINS-20935 Provide separate monitoring pages for each slave node Change By: Oleg Nenashev (14/Jan/14 2:21 PM) Resolution: Fixed Status: Resolved Reopened Assignee: evernat Oleg Nenashev 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-4021) TFS - unparseable date problem
Mats Taraldsvik commented on JENKINS-4021 TFS - unparseable date problem @Justinas Urbanavicius: Sure, a brute-force solution might be a bad idea. However, the example proves that the dates are parseable. Setting the preferred/correct locale in the Jenkins TFS Plugin's configuration is a viable solution imho, changing the TFS Server configuration is not. 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/groups/opt_out.
[JIRA] [git] (JENKINS-21376) status code 255 error: could not lock config file .git/config: No such file or directory
Guillaume Pfeiffer created JENKINS-21376 status code 255 error: could not lock config file .git/config: No such file or directory Issue Type: Bug Assignee: Nicolas De Loof Attachments: BuildErrorMessage.png, JenkinsErrorMessage.png Components: git Created: 14/Jan/14 3:05 PM Description: Since the last update of the Git plugin with the new credential feature, an error appeared on the project configuration page. "Failed to connect to repository : Command "git config --local credential.helper store --file=\"/tmp/git1652196526881950884.credentials\"" returned status code 255: stdout: stderr: error: could not lock config file .git/config: No such file or directory" I configure the credential with an user authorized to clone and push repository on our platform, and configure project to use it but this error is still present. I attach two file to this Issue, the first is the error message on the configuration page. The second is the build log when the credential feature is up. Before this version, we used .netrc file to set credentials for clone/fetch repository with git on jenkins(This feature still workingfor now). However, this feature of credential gestion by jenkins is very interesting for us. Environment: Scientific Linux 6.3 git 1.8.5.1 Jenkins 1.5.32 Project: Jenkins Priority: Minor Reporter: Guillaume Pfeiffer 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/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
Jesse Glick commented on JENKINS-20772 'Apply' error screens don't work Right, but the most critical fix—showing something in the error dialog—was backported. I think we can live with that, unless the lack of scrolling is making it impossible to see error details. (See https://github.com/jglick/jenkins/compare/printStackTrace-JDK-6507809 for another angle on this.) 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/groups/opt_out.
[JIRA] [warnings] (JENKINS-21377) Java warnings generated by tycho-compiler-jdt 0.19.0 not detected
Uwe Petschke created JENKINS-21377 Java warnings generated by tycho-compiler-jdt 0.19.0 not detected Issue Type: Improvement Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 14/Jan/14 3:16 PM Description: Building Java sources with Maven using org.eclipse.tycho:tycho-compiler-jdt:0.19.0 produces compiler warnings in a slightly different format than older versions: 0.19.0 [WARNING] /path/to/job/job-name/module/src/main/java/com/example/Example.java:[13] something.getOldValue(); ^ The method getOldValue() from the type SomeType is deprecated before 0.19.0 [WARNING] /path/to/job/job-name/module/src/main/java/com/example/Example.java:[13,0] something.getOldValue(); ^ The method getOldValue() from the type SomeType is deprecated The only difference is the specification of the location within the source file: [13] vs. [13,0] The leads to the problem that when using the "Java Compiler (Eclipse)" parser does not detect any warnings. When using the "Java Compiler (javac)" parser instead, the warnings are detected but the message is not extracted. I've already patched the parser and will submit a pull request soon. Project: Jenkins Priority: Major Reporter: Uwe Petschke 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/groups/opt_out.
[JIRA] [jacoco] (JENKINS-16580) Display more than only line coverage in graph
Chris Williams commented on JENKINS-16580 Display more than only line coverage in graph So it seems like this used to be available and was reverted to just lines covered versus lines missed? https://github.com/jenkinsci/jacoco-plugin/commit/ab3f301b4c269dd12e80fcecae73be2ddbdccbca So you basically just need someone to fork and submit a PR that has both versions based on an if condition looking at some configuration value (as well as surfacing that value as a checkbox in jenkins config?) 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/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-21378) Manual trigger of downstream job is disabled if upstream job is UNSTABLE
sheryl pinto created JENKINS-21378 Manual trigger of downstream job is disabled if upstream job is UNSTABLE Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-pipeline Created: 14/Jan/14 3:52 PM Description: The pipeline view doesn't allow manual triggering of downstream jobs if the upstream job is marked as UNSTABLE. The auto-triggering of downstream jobs via the Jenkins Parameterized Trigger plugin works for UNSTABLE parent jobs. Project: Jenkins Priority: Major Reporter: sheryl pinto 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/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-21378) Manual trigger of downstream job is disabled if upstream job is UNSTABLE
sheryl pinto updated JENKINS-21378 Manual trigger of downstream job is disabled if upstream job is UNSTABLE Change By: sheryl pinto (14/Jan/14 3:54 PM) Environment: Jenkins ver. 1.521Build Pipeline plugin 1.4.2 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/groups/opt_out.
[JIRA] [warnings] (JENKINS-21377) Java warnings generated by tycho-compiler-jdt 0.19.0 not detected
Uwe Petschke commented on JENKINS-21377 Java warnings generated by tycho-compiler-jdt 0.19.0 not detected Created pull request: https://github.com/jenkinsci/warnings-plugin/pull/35 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/groups/opt_out.
[JIRA] [bazaar] (JENKINS-18955) Add multiple scm support to Bazaar plugin
Sebastian Messerschmidt commented on JENKINS-18955 Add multiple scm support to Bazaar plugin Any chance this gets into the next stable release? 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-3785) Add option to perform labeling for each TFS build
rodrigolopes commented on JENKINS-3785 Add option to perform labeling for each TFS build Or it could be implemented as a PostBuild action 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/groups/opt_out.
[JIRA] [maven] (JENKINS-21379) Build Aborted when selecting • Incremental build / • Build modules in parallel
kamal kishore created JENKINS-21379 Build Aborted when selecting • Incremental build / • Build modules in parallel Issue Type: Bug Assignee: Unassigned Components: maven Created: 14/Jan/14 4:37 PM Description: Hi There, I am working on a multi-module project. The build/Junit Tests/Sonar time in total is close to 45min. Although it works flawlessly, but the time taken is too much. When I tried to build using below option on Jenkins: • Incremental build - only build changed modules • Build modules in parallel The build gets aborted. Be it build/Junit/Sonar. The Maven version is 3.1.0 and Jenkins Version is 1.526. Could you please help/Suggest. Thanks, Kamal Due Date: 15/Jan/14 12:00 AM Environment: Windows Project: Jenkins Priority: Major Reporter: kamal kishore 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/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-21181) Build pipeline creating stack trace after logging on as non-admin user
Samy Lerari commented on JENKINS-21181 Build pipeline creating stack trace after logging on as non-admin user Got the exact same exception after simutanously upgraded Jenkins to 1.545 and Build Pipeline Plugin to 1.4.2. All non admin users who had only Global Read permission (plus of course some job level permissions) had this exception. I was forced to give them global read+discover permission which resulted on all users seeing all jobs. Corrected the issue by downgrading Build Pipeline Plugin from 1.4.2 to 1.4.1. Switched back to only Global Read permission : users now only see jobs they can interact with (and no longer all of them). Note : This seems to me duplicate of 20993 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/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
Samy Lerari commented on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in Got the exact same exception after simutanously upgraded Jenkins to 1.545 and Build Pipeline Plugin to 1.4.2. All non admin users who had only Global Read permission (plus of course some job level permissions) had this exception. I was forced to give them global read+discover permission which resulted on all users seeing all jobs. Corrected the issue by downgrading Build Pipeline Plugin from 1.4.2 to 1.4.1. Switched back to only Global Read permission : users now only see jobs they can interact with (and no longer all of them). Note : This seems to me duplicate of 21181 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/groups/opt_out.
[JIRA] [core] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
Tom Jones commented on JENKINS-21373 Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547 I'm seeing the same problem. All of my windows slaves are failing with the same problem. The windows slave has the following log message: Exception in thread "main" java.net.SocketTimeoutException: Accept timed out at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method) at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source) at java.net.AbstractPlainSocketImpl.accept(Unknown Source) at java.net.PlainSocketImpl.accept(Unknown Source) at java.net.ServerSocket.implAccept(Unknown Source) at java.net.ServerSocket.accept(Unknown Source) at hudson.remoting.Launcher.runAsTcpServer(Launcher.java:385) at hudson.remoting.Launcher.run(Launcher.java:236) at hudson.remoting.Launcher.main(Launcher.java:192) 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/groups/opt_out.
[JIRA] [core] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
Tom Jones edited a comment on JENKINS-21373 Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547 I'm seeing the same problem. Everything was working before the upgrade (ver. 1.544) but immediately after the upgrade all of my windows slaves are failing with the same problem. The windows slave has the following log message: Exception in thread "main" java.net.SocketTimeoutException: Accept timed out at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method) at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source) at java.net.AbstractPlainSocketImpl.accept(Unknown Source) at java.net.PlainSocketImpl.accept(Unknown Source) at java.net.ServerSocket.implAccept(Unknown Source) at java.net.ServerSocket.accept(Unknown Source) at hudson.remoting.Launcher.runAsTcpServer(Launcher.java:385) at hudson.remoting.Launcher.run(Launcher.java:236) at hudson.remoting.Launcher.main(Launcher.java:192) 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/groups/opt_out.
[JIRA] [core] (JENKINS-20085) Functions.globalIota overflow
Matt Legrand commented on JENKINS-20085 Functions.globalIota overflow A side note: the Script Console fix mentioned above worked nicely for me on Jenkins 1.528. The symptom was a page showing "You must fix POST method..." when starting any job. This started occurring for no obvious reason recently. After doing the fix above, Jenkins behaved correctly once more. 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/groups/opt_out.
