[JIRA] [gerrit-trigger] (JENKINS-10709) multiple builds are triggered for one change in Gerrit
Vlad Aginsky commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit We still suffer from this. Is there any progress? I would like to be a beta tester if this can 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/groups/opt_out.
[JIRA] [fitnesse] (JENKINS-11860) user.dir system property from master (linux) being pulled across to slave (windows)
evernat resolved JENKINS-11860 as Incomplete user.dir system property from master (linux) being pulled across to slave (windows) No response from the reporter, so resolving as incomplete. Change By: evernat (13/Jan/14 8:21 AM) 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] [subversion] (JENKINS-12401) Loosing top level directory when tagging multiple modules.
evernat resolved JENKINS-12401 as Incomplete Loosing top level directory when tagging multiple modules. No response from the reporter, so resolving as incomplete. Change By: evernat (13/Jan/14 8:22 AM) 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] [klockwork] (JENKINS-12394) Publish Klocwork test result report
evernat resolved JENKINS-12394 as Incomplete Publish Klocwork test result report No response from the reporter, so resolving as incomplete. Change By: evernat (13/Jan/14 8:22 AM) 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] [core] (JENKINS-12285) All projects have quiet periods at build time even if quiet period function is turned off in the job.
evernat resolved JENKINS-12285 as Incomplete All projects have quiet periods at build time even if quiet period function is turned off in the job. No response from the reporter, so resolving as incomplete. Change By: evernat (13/Jan/14 8:25 AM) 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] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Vinson Lee reopened JENKINS-21137 git fetch does not have support for --progress option in 1.7.x version of git client binary Change By: Vinson Lee (13/Jan/14 8:25 AM) Resolution: WontFix 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] [hudsontrayapp] (JENKINS-12249) Lost all the hudson configurations after Tomcat restart
evernat resolved JENKINS-12249 as Incomplete Lost all the hudson configurations after Tomcat restart No response from the reporter, so resolving as incomplete. Change By: evernat (13/Jan/14 8:26 AM) 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] [repository] (JENKINS-12304) Intermittent problems when downloading files from the everything Jenkins maven repository
evernat resolved JENKINS-12304 as Incomplete Intermittent problems when downloading files from the everything Jenkins maven repository No response from the reporter, so resolving as incomplete. Change By: evernat (13/Jan/14 8:28 AM) 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] [log-parser] (JENKINS-12085) Failed to parse console log
evernat resolved JENKINS-12085 as Incomplete Failed to parse console log No response from the reporter, so resolving as incomplete. Change By: evernat (13/Jan/14 8:27 AM) 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] [fitnesse] (JENKINS-11860) user.dir system property from master (linux) being pulled across to slave (windows)
Ashok Manji closed JENKINS-11860 as Incomplete user.dir system property from master (linux) being pulled across to slave (windows) This is not a problem for me anymore. Not using this anymore. Closing. Change By: Ashok Manji (13/Jan/14 8:35 AM) Status: Resolved Closed 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] [flexible-publish] (JENKINS-21345) Filter action list on matrix jobs
WH created JENKINS-21345 Filter action list on matrix jobs Issue Type: Improvement Assignee: bap Components: flexible-publish Created: 13/Jan/14 8:51 AM Description: For a matrix job you can add flexible publisher as post build action. Afeter that you can choose the wanted action of the flexible publisher. Unfortunately all existing post build actions are listed there, including those which don't support matrix jobs, e.g. "Perform subversion tagging on successful build" of the Subversion tagging plugin. Improvement: For matrix jobs filter out actions in flexible publishers action list, that don't support matrix builds. Environment: Jenkins LTS 1.532.1 Flexible publisher plugin 0.12 Jenkins Subversion Tagging Plugin 1.16 Project: Jenkins Priority: Major Reporter: WH 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 ?)
Anadi Misra commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Hi! I upgraded to latest Jenkins version and to the latest version of Git client plugin i.e. 1.6.1; no luck. Started by an SCM change EnvInject - Loading node environment variables. Building in workspace /apps/ci/.jenkins/home/jobs/CI-Test/workspace Fetching changes from the remote Git repository Fetching upstream changes from https://github.com/mycompany/mygitrepo.git using .gitcredentials to set credentials FATAL: Failed to fetch from https://github.com/mycompany/mygitrepo.git hudson.plugins.git.GitException: Failed to fetch from https://github.com/mycompany/mygitrepo.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:625) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:847) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:872) 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.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress https://github.com/mycompany/mygitrepo.git +refs/heads/master:refs/remotes/origin/master" returned status code 128: stdout: stderr: error: cannot run /bin/echo : No such file or directory fatal: could not read Username for 'https://github.com': Input/output error at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1086) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:968) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:71) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:197) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:623) ... 10 more I request we make this a blocker considering the fact we cannot proceed with builds at all so long this issue exists. 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] [testflight] (JENKINS-20504) Add ability to specify a file as build notes
Frieder Bluemle commented on JENKINS-20504 Add ability to specify a file as build notes That is a great suggestion. I would also love to see 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] [testflight] (JENKINS-20503) Appending changlog says no changes if a build failed
Ricardo Ruiz commented on JENKINS-20503 Appending changlog says no changes if a build failed Thanks Dale, but that is too complex. The plugin should do it using something like CHANGES_SINCE_LAST_SUCCESS. Perhaps this plugin is not maintained anymore by the author, I don't know. 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] [gerrit-trigger] (JENKINS-20098) GitClient.getRepository deprecated and broken
rsandell commented on JENKINS-20098 GitClient.getRepository deprecated and broken There is a beta version of 2.11 released since a bit over a month back. If you don't dare to run the beta then there is a special 2.10 branch with this fix in https://github.com/jenkinsci/gerrit-trigger-plugin/tree/git-client-fix 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] [gerrit-trigger] (JENKINS-20098) GitClient.getRepository deprecated and broken
kevincai commented on JENKINS-20098 GitClient.getRepository deprecated and broken I have to run with the beta version, and so far it looks good. Thanks1 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] [gerrit-trigger] (JENKINS-20098) GitClient.getRepository deprecated and broken
kevincai edited a comment on JENKINS-20098 GitClient.getRepository deprecated and broken I have to run with the beta version, and so far it looks good. 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] [svn-tag] (JENKINS-9683) Support matrix projects
WH updated JENKINS-9683 Support matrix projects Change By: WH (13/Jan/14 9:34 AM) Summary: Tagginga Support matrix project projects Issue Type: Bug Improvement Assignee: k2nakamura RenjithV Environment: Jenkins LTS 1. 411, 532.1Jenkins SubversionTaggingPlugin1. 14 16 Description: Whentaggingamatrixprojectwithtwoslavesonanaxis,eachbuild triestotag tags thesourcecode. Thefirstbuildsuccessfullydeletes Thisisveryanoying,because the existingtagandcreatesanewtag sourcecodeistaggedmultipletimes . Thesecondbuildfails Subsequentjobshave todeletetheexistingtagand createsatrunkfolderinsidetheexistingtag createitagain . Consoleoutputofthefirstbuild Improvement : Startedbyupstreamprojecttest Supportmatrix build number6Buildingremotelyonslave1Checkingoutafreshworkspacebecausetheresnoworkspaceat/tmp/jenkins_slave1/workspace/test/label/slave1Cleaningworkspace/tmp/jenkins_slave1/workspace/test/label/slave1Checkingoutsvn+ssh://user@server/repo/test/trunkAUabc.txtAtrevision238nochangeforsvn+ssh://user@server/repo/test/trunksince inthatway,thatin the previousbuildmoduleLocation:Remote-svn+ssh://user@server/repo/test/trunkTagBaseURL:svn+ssh://user@server/repo/test/tags/myTag.Deleteoldtagsvn+ssh://user@server/repo/test/tags/myTag.TaggedasRevision240Notifyingupstreamprojectsof job completionFinished:SUCCESSConsoleoutputof configurationonecanchoosewhether the secondbuild:Startedbyupstreamprojecttestbuildnumber6Buildingremotelyonslave2Checkingoutafreshworkspacebecausetheresnoworkspaceat/tmp/jenkins_slave2/workspace/test/label/slave2Cleaningworkspace/tmp/jenkins_slave2/workspace/test/label/slave2Checkingoutsvn+ssh://user@server/repo/test/trunkAUabc matrixparentjoborthematrixchildjobswilldothetagging . txt Atrevision238 nochangeforsvn+ssh://user@server/repo/test/trunksince Thiscouldbeimplementedsimilarto the previousbuildmoduleLocation:Remote email - svn+ssh://user@server/repo/test/trunkTagBaseURL:svn+ssh://user@server/repo/test/tags/myTag extplugin . Therewasnooldtagatsvn+ssh://user@server/repo/test/tags/myTag.TaggedasRevision241NotifyingupstreamprojectsofjobcompletionFinished:SUCCESSSubversionlogsays:239Deleted/test/tags/myTagOldtagdeletedbyJenkinsbuild:jenkins-label=slave1240Added/test/tags/myTag(Copyfrompath/test/trunk)TaggedbyJenkinsbuild:jenkins-label=slave1241Added/test/tags/myTag/trunk(Copyfrompath/test/trunk)TaggedbyJenkinsbuild:jenkins-labe-=slave2 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] [testflight] (JENKINS-20503) Appending changlog says no changes if a build failed
Ricardo Ruiz edited a comment on JENKINS-20503 Appending changlog says no changes if a build failed Thanks Dale, but that is too complex. The plugin should do it using something like CHANGES_SINCE_LAST_SUCCESS. Perhaps this plugin is not maintained anymore by the author, I don't know. I sent an email to the author, let's wait. 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-12870) Disk usage disabled when job configuration is edited, comes later back magically
Grégory Joseph commented on JENKINS-12870 Disk usage disabled when job configuration is edited, comes later back magically I still see the side-effect described here, except the history entry appears as "added" by me, not the SYSTEM user. 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
Grégory Joseph commented on JENKINS-20176 Disk usage plugin write job config.xml after every build i have 0.23 installed and still see this happening. 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-12870) Disk usage disabled when job configuration is edited, comes later back magically
Grégory Joseph edited a comment on JENKINS-12870 Disk usage disabled when job configuration is edited, comes later back magically I still see the side-effect described here, except the history entry appears as "added" by me, not the SYSTEM user. edit: hmm, i'm probably suffering from JENKINS-20176, sorry. Issues might benefit from being linked. 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] [cppcheck] (JENKINS-21346) Not working with cppcheck 1.63
rggjan created JENKINS-21346 Not working with cppcheck 1.63 Issue Type: Bug Assignee: Gregory Boissinot Components: cppcheck Created: 13/Jan/14 9:52 AM Description: Running the cppcheck plugin on a report generated with cppcheck 1.63 (current stable version) gives the following error: Cppcheck Starting the cppcheck analysis. Cppcheck Processing 1 files with the pattern 'cppcheck.xml'. Cppcheck Parsing throws exceptions. org.jenkinsci.plugins.cppcheck.model.Error cannot be cast to org.jenkinsci.plugins.cppcheck.model.Results Build step 'Publish Cppcheck results' changed build result to FAILURE Build step 'Publish Cppcheck results' marked build as failure It works fine with cppcheck 1.62 Project: Jenkins Priority: Blocker Reporter: rggjan 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] [prioritysorter] (JENKINS-21313) Anonymous users can configure and delete PrioritySorter JobGroups
Daniel Beck commented on JENKINS-21313 Anonymous users can configure and delete PrioritySorter JobGroups Is there a reason global configuration doesn't require Administer permission? 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 ?)
Stefan Braun updated JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Change By: Stefan Braun (13/Jan/14 10:24 AM) Priority: Major Blocker 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] [junit] (JENKINS-21347) Jenkins failes with Incorrect XML attributes for test results
Khayrat Glende created JENKINS-21347 Jenkins failes with Incorrect XML attributes for test results Issue Type: Bug Assignee: Unassigned Components: junit Created: 13/Jan/14 10:25 AM Description: Upgraded from 1.526 to 1.544 (no 1.546 due to JENKINS-21250). I'm using the current maven-surefire-plugin. The tests passed but recording the tests failed with: [INFO] . SUCCESS [19.130s] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 5 minutes [INFO] Finished at: Mon Jan 13 10:24:58 CET 2014 [INFO] Final Memory: 120M/495M [INFO] Recording test results Incorrect XML attributes for test results found in **/target/surefire-reports/*.xml Build step 'Publish JUnit test result report' changed build result to FAILURE Project: Jenkins Priority: Major Reporter: Khayrat Glende 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] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here
Alexis Morelle commented on JENKINS-19693 Build Number field expect positive number, so it is impossible to use named builds here What you are referencing is only the display name, in background, Jenkins still reference the build by its number. There's a method in the core to retrieve a build by its number but not by its display name, finding a match may be less efficient then. 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-18935) Make Subversion plugin support Subversion 1.8
Jeebitesh Kalantri commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +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/groups/opt_out.
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
vbier commented on JENKINS-13253 Slave connection reset issues since 1.456 As of today, we also have this problem. Builds have not run for a while, and the only thing we changed in the meantime was moving the master installation from a physical server to a virtual machine. We have been running 1.509.4, and after the error appeared I upgraded to 1.532.1, but this did not change anything. I enabled log level FINE for hudson.remoting, but that does not really give any obvious additional information. I include it here in case you can figure out anything from it: Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Jens Hirschfeld commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21348) Remove Maven Plugin dependency
Daniel Beck created JENKINS-21348 Remove Maven Plugin dependency Issue Type: Improvement Assignee: Alex Earl Components: email-ext Created: 13/Jan/14 10:36 AM Description: It makes no sense for a universal plugin like email-ext to have a mandatory Maven Integration plugin dependency. We don't have Maven 2/3 jobs, I don't allow users to create Maven 2/3 jobs, yet I need the plugin for email-ext. Please implement any Maven project integration in a way that allows that dependency to be removed or made optional. Project: Jenkins Priority: Major 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] [git-client] (JENKINS-20251) git ignores no proxy settings
Nicolas De Loof resolved JENKINS-20251 as Fixed git ignores no proxy settings Change By: Nicolas De Loof (13/Jan/14 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here
Igor Kostenko commented on JENKINS-19693 Build Number field expect positive number, so it is impossible to use named builds here Yes, I understand that build number still could be used. Idea was to make life easier - when you have many different jobs with different build numbers it is easy to make a mistake when you getting specific artifacts from there, using the same name everywhere is more convenient. 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-13253) Slave connection reset issues since 1.456
vbier edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 As of today, we also have this problem. Builds have not run for a while, and the only thing we changed in the meantime was moving the master installation from a physical server to a virtual machine. We have been running 1.509.4, and after the error appeared I upgraded to 1.532.1, but this did not change anything. I enabled log level FINE for hudson.remoting, but that does not really give any obvious additional information. I include it here in case you can figure out anything from it: Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
vbier edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 As of today, we also have this problem. Builds have not run for a while, and the only thing we changed in the meantime was moving the master installation from a physical server to a virtual machine. We have been running 1.509.4, and after the error appeared I upgraded to 1.532.1, but this did not change anything. I enabled log level FINE for hudson.remoting, but that does not really give any obvious additional information. I include it here in case you can figure out anything from it: Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE
[JIRA] [nested-view] (JENKINS-21349) Cannot configure jobs within a nested view with quote character in their name
Frédéric Barrau created JENKINS-21349 Cannot configure jobs within a nested view with quote character in their name Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: CO-PROD-Patch Config [Jenkins] - Google Chrome.png Components: nested-view Created: 13/Jan/14 10:51 AM Description: I've created a nested view whose name contains a quote character ( ' ). Then, when accessing jobs from within this view and configuring it, the configure page hangs with the "loading" layer (see screenshot joined). Tried to escape the quote with a \ with no luck. Environment: Any browser Project: Jenkins Priority: Major Reporter: Frédéric Barrau 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] [prioritysorter] (JENKINS-21313) Anonymous users can configure and delete PrioritySorter JobGroups
mwebber commented on JENKINS-21313 Anonymous users can configure and delete PrioritySorter JobGroups @Magnus: I'm also considering defining custom permissions for this do you think that would make sense Yes it does. It a user can edit a job configuration, it might be good to have a separate permission for whether ot not they can edit the priority. @Daniel: Is there a reason global configuration doesn't require Administer permission? I think the reason is historic. Magnus is going to fix this, I think. 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] [nested-view] (JENKINS-21349) Cannot configure jobs within a nested view with quote character in view's name
Frédéric Barrau updated JENKINS-21349 Cannot configure jobs within a nested view with quote character in views name Change By: Frédéric Barrau (13/Jan/14 10:52 AM) Summary: Cannotconfigurejobswithinanestedviewwithquotecharacterin their views name 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-13253) Slave connection reset issues since 1.456
vbier edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 As of today, we also have this problem. Builds have not run for a while, and the only thing we changed in the meantime was moving the master installation from a physical server to a virtual machine. We have been running 1.509.4, and after the error appeared I upgraded to 1.532.1, but this did not change anything. I enabled log level FINE for hudson.remoting, but that does not really give any obvious additional information. I include it here in case you can figure out anything from it: Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
vbier edited a comment on JENKINS-13253 Slave connection reset issues since 1.456 As of today, we also have this problem. Builds have not run for a while, and the only thing we changed in the meantime was moving the master installation from a physical server to a virtual machine. We have been running 1.509.4, and after the error appeared I upgraded to 1.532.1, but this did not change anything. I enabled log level FINE for hudson.remoting, but that does not really give any obvious additional information. I include it here in case you can figure out anything from it: Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,38) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,628) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,155) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,2) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,157) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Send Pipe.Ack(20,158) Jan 13, 2014 11:04:00 AM FINE hudson.remoting.Channel Received Pipe.Chunk(20,158) Jan 13, 2014 11:04:00 AM FINE
[JIRA] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here
Alexis Morelle commented on JENKINS-19693 Build Number field expect positive number, so it is impossible to use named builds here It's just that you could give the same display name to two existing builds and also name one with a number while there's already a build with that number. Do you think it's fair enough to give priority to numbers (i.e. it's a number so we look for it not as a display name) than look for named builds (and then permalinks)? 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-8317) Matrix jobs with custom workspaces should be able to share the root with no axis-specific subtree
Emil Styrke commented on JENKINS-8317 Matrix jobs with custom workspaces should be able to share the root with no axis-specific subtree This seems to be only part of the solution. I'm using the "Clone workspace" plugin to populate the workspace, and even when setting the directory for sub-builds to ".", each sub-build (as well as the main build) will unpack the workspace (to the same location). There seems to be no way to specify that the sub-builds should ignore the SCM step altogether. 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] [buildgraph-view] (JENKINS-19470) Build Graph not displaying
Ireneusz Makowski commented on JENKINS-19470 Build Graph not displaying I have the same issue here. My configuration is Jenkins 1.532.1, BuildFlow 0.10, BuildGraphView 1.1.1, Jenkins Parameterized Trigger plugin 2.22 It seems that after restart of Jenkins Graph is missing 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] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here
Igor Kostenko commented on JENKINS-19693 Build Number field expect positive number, so it is impossible to use named builds here Yes, it is fair and it is consistent with jeninks url behavior, if you specifying number in http://jenkins/job/job/build/ you will get build by number (and will get an error if you used a number for display name and there is no job with such number). I guess it would be better if just number in display name will be prohibited to avoid confusion and inconsistent behavior. 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] [jobconfighistory] (JENKINS-20511) hudson.maven.MavenBuild MissingFieldException: No field 'targetType' found in class 'hudson.plugins.jobConfigHistory.JobConfigBadgeAction'
Konrad Windszus commented on JENKINS-20511 hudson.maven.MavenBuild MissingFieldException: No field targetType found in class hudson.plugins.jobConfigHistory.JobConfigBadgeAction I do see the issue on Jenkins LTS 1.532.1 with Job Configuration History Plugin 2.5. Every time a new build is triggered on Maven Jobs there is a new entry added to the Unreadable data warnings. 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] [reverse-proxy-auth] (JENKINS-21304) NPE - Reverse Proxy Authentication
Benjamin Urban commented on JENKINS-21304 NPE - Reverse Proxy Authentication Same here. 1.0.1 is working fine, but 1.2 to 1.3.1 produce the following NPE: Jan 10, 2014 10:56:38 AM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: java.lang.NullPointerException at org.eclipse.jetty.util.StringUtil.getBytes(StringUtil.java:378) at org.eclipse.jetty.io.ByteArrayBuffer.init(ByteArrayBuffer.java:81) at org.eclipse.jetty.io.ByteArrayBuffer$CaseInsensitive.init(ByteArrayBuffer.java:424) at org.eclipse.jetty.io.BufferCache$CachedBuffer.init(BufferCache.java:134) at org.eclipse.jetty.io.BufferCache.lookup(BufferCache.java:101) at org.eclipse.jetty.http.HttpFields.getField(HttpFields.java:402) at org.eclipse.jetty.http.HttpFields.getStringField(HttpFields.java:431) at org.eclipse.jetty.server.Request.getHeader(Request.java:605) at org.jenkinsci.plugins.reverse_proxy_auth.ReverseProxySecurityRealm$1.doFilter(ReverseProxySecurityRealm.java:324) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) 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] [reverse-proxy-auth] (JENKINS-21304) NPE - Reverse Proxy Authentication
Benjamin Urban edited a comment on JENKINS-21304 NPE - Reverse Proxy Authentication Same here. 1.0.1 is working fine, but 1.2 to 1.3.1 produce the following NPE: Jan 10, 2014 10:56:38 AM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: java.lang.NullPointerException at org.eclipse.jetty.util.StringUtil.getBytes(StringUtil.java:378) at org.eclipse.jetty.io.ByteArrayBuffer.init(ByteArrayBuffer.java:81) at org.eclipse.jetty.io.ByteArrayBuffer$CaseInsensitive.init(ByteArrayBuffer.java:424) at org.eclipse.jetty.io.BufferCache$CachedBuffer.init(BufferCache.java:134) at org.eclipse.jetty.io.BufferCache.lookup(BufferCache.java:101) at org.eclipse.jetty.http.HttpFields.getField(HttpFields.java:402) at org.eclipse.jetty.http.HttpFields.getStringField(HttpFields.java:431) at org.eclipse.jetty.server.Request.getHeader(Request.java:605) at org.jenkinsci.plugins.reverse_proxy_auth.ReverseProxySecurityRealm$1.doFilter(ReverseProxySecurityRealm.java:324) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Environment here is: Ubuntu 13.10 (x86_64), Jenkins 1.546 and 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] [integrity-plugin] (JENKINS-21350) NullPointerException during checkout on variant projects where the original project has been moved.
Christian Bürenheide created JENKINS-21350 NullPointerException during checkout on variant projects where the original project has been moved. Issue Type: Bug Affects Versions: current Assignee: Cletus DSouza Components: integrity-plugin Created: 13/Jan/14 1:10 PM Description: For some of our components, Jenkins build fails with the following error message in the console log: Preparing to execute si projectinfo for #p=d:/MKS/PlatformA/ProductA.pj#d=dev_(Rel7.8)#s=ComponentA/ModuleA/project.pj Preparing to execute pre-build si checkpoint for #p=d:/MKS/PlatformA/ProductA.pj#d=dev_(Rel7.8)#s=ComponentA/ModuleA/project.pj Successfully executed pre-build checkpoint for project #p=d:/MKS/PlatformA/ProductA.pj#d=dev_(Rel7.8)#s=ComponentA/ModuleA/project.pj, new revision is 1.115 Preparing to execute si viewproject for #p=d:/MKS/PlatformA/ProductA.pj#d=dev_(Rel7.8)#s=ComponentA/ModuleA/project.pj#forceJump=#b=1.115 Checkout directory is /jenkins/mks/dev_Rel7.8/ComponentA/ModuleA A clean copy is requested; deleting contents of /jenkins/mks/dev_Rel7.8/ComponentA/ModuleA Populating clean workspace... FATAL: null java.lang.NullPointerException at hudson.scm.IntegrityCheckoutTask.invoke(IntegrityCheckoutTask.java:277) at hudson.scm.IntegrityCheckoutTask.invoke(IntegrityCheckoutTask.java:24) at hudson.FilePath.act(FilePath.java:914) at hudson.FilePath.act(FilePath.java:887) at hudson.scm.IntegritySCM.checkout(IntegritySCM.java:790) 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) The build fails under those circumstances: The affected integrity project is a variant (development path) project. The original project of that variant project has been moved. In this case, the module d:/MKS/PlatformA/OldComponent/ModuleA (MKS project name: d:/MKS/PlatformA/OldComponent/ModuleA/ModuleA.pj) has been moved to d:/MKS/PlatformA/ComponentA/ModuleA (new MKS project name: d:/MKS/PlatformA/ComponentA/ModuleA/project.pj) Problem analysis: The code line at hudson.scm.IntegrityCheckoutTask.invoke(IntegrityCheckoutTask.java:277) accesses the configuration path of a member in a prepared member list structure, which is null: String configPath = memberInfo.get(CM_PROJECT.CONFIG_PATH).toString(); The main cause seems to be speciality in integrity with the si projectinfo (this is the way currently implemented in the integrity plugin): si projectinfo --project="d:/MKS/PlatformA/ComponentA/ModuleA/project.pj" --projectRevision="1.116" Result: Build Project Name: d:/MKS/PlatformA/OldComponent/ModuleA/ModuleA.pj Server: ... Configuration Path: #p=d:/MKS/PlatformA/ProductA.pj#d=dev_(Rel7.8)#s=ComponentA/ModuleA/project.pj#forceJump=#b=1.116 ... Here we get back the old project name (which was valid before the move). But when we execute project info using the configuration path we get the new project name as a result: si projectinfo --project="#p=d:/MKS/PlatformA/ProductA.pj#d=dev_(Rel7.8)#s=ComponentA/ModuleA/project.pj#forceJump=#b=1.114" Result: Build Project Name: d:/MKS/PlatformA/ComponentA/ModuleA/project.pj Server: ... Configuration Path: #p=d:/MKS/PlatformA/ProductA.pj#d=dev_(Rel7.8)#s=ComponentA/ModuleA/project.pj#forceJump=#b=1.114 Revision: 1.114 ... The problem is that during IntegrityCMProject.parseProject(), where the project including it's members is parsed, the project name that comes with the member infos is matched against that name (using HashtableString, String pjConfigHash) to find out the configuration path for each member. Here the
[JIRA] [integrity-plugin] (JENKINS-21351) Groovy expressions for post build action Integrity Checkin / Configuration name not supported
Christian Bürenheide created JENKINS-21351 Groovy expressions for post build action Integrity Checkin / Configuration name not supported Issue Type: Improvement Affects Versions: current Assignee: Cletus DSouza Components: integrity-plugin Created: 13/Jan/14 1:19 PM Description: In the SCM section of the job config page, the integrity-plugin now supports Groovy expressions for the Configuration Name property. But in the post build action "Integrity checkin", the same property does not accept Groovy expressions. I would like to provide a pull request for that issue. Best regards Due Date: 13/Jan/14 12:00 AM Project: Jenkins Priority: Minor 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] [prioritysorter] (JENKINS-21314) Stack trace displayed on web page when attempting to configure PrioritySorter plugin
mwebber commented on JENKINS-21314 Stack trace displayed on web page when attempting to configure PrioritySorter plugin After editing the invalid XML by hand and restarting, the stack trace is no longer generated. 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] [mercurial] (JENKINS-17632) Please add an option for uncompressed cloning
Anatoly Bubenkov commented on JENKINS-17632 Please add an option for uncompressed cloning important thing for using --uncompressed is that you need same permissions are for push, which is rare case 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] [active-directory] (JENKINS-18884) Seperate Permission for People View to close Security Hole with AD Plugin
ikedam commented on JENKINS-18884 Seperate Permission for People View to close Security Hole with AD Plugin Notes for customization: Links to people list (/asynchPeople, /people) are available at: core/src/main/resources/hudson/model/User/sidepanel.jelly core/src/main/resources/hudson/model/View/AsynchPeople/index.jelly core/src/main/resources/hudson/model/View/People/index.jelly core/src/main/resources/hudson/model/View/sidepanel.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/index.jelly (in blurb) Methods providing people list to views are: hudson.model.View#getAsynchPeople() hudson.model.View#getPeople() Models of people are: hudson.model.View.People hudson.model.View.AsynchPeople (subclass of jenkins.util.ProgressiveRendering) 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] [active-directory] (JENKINS-18884) Seperate Permission for People View to close Security Hole with AD Plugin
ikedam edited a comment on JENKINS-18884 Seperate Permission for People View to close Security Hole with AD Plugin Notes for customization: Links to people list (/asynchPeople, /people) are available at: core/src/main/resources/hudson/model/User/sidepanel.jelly core/src/main/resources/hudson/model/View/AsynchPeople/index.jelly core/src/main/resources/hudson/model/View/People/index.jelly core/src/main/resources/hudson/model/View/sidepanel.jelly core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/index.jelly (in blurb) Methods providing people list to views are: jenkins.model.Jenkins#getAsynchPeople() jenkins.model.Jenkins#getPeople() hudson.model.View#getAsynchPeople() hudson.model.View#getPeople() Models of people are: hudson.model.View.People hudson.model.View.AsynchPeople (subclass of jenkins.util.ProgressiveRendering) 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] [gerrit-trigger] (JENKINS-10709) multiple builds are triggered for one change in Gerrit
Hugo Ares commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit Vlad, have you tried the latest 2.11 beta(2.11.0-beta-4)? 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-18464) Build Pipeline and Join plugin do not play nicely together
Michael Weinrich commented on JENKINS-18464 Build Pipeline and Join plugin do not play nicely together I would like to help fixing this issue, but I'm totally new to Jenkins development (yet I used it for quite some time now). I tried to write a unit test to illustrate the problem (see https://github.com/InterNations/build-pipeline-plugin/compare/join-trigger-fix), however I'm stuck there. Is there anything I can do to accelerate the fix for this issue? I might even get some bounty for the fix (of not for me but for the one fixing it ) If anyone is interested, I would ask for details on that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21151) multiple-scms plugin conflict [checkin]
Christian Bürenheide commented on JENKINS-21151 multiple-scms plugin conflict [checkin] Hi! With the code changes made on IntegrityCheckpointAction.java for this issue, the possibility to perform a 'addprojectlabel' after a build has been removed. This functionality was available until integrity-plugin 1.19. Is this a bug or a feature? For us it was a very useful functionality. 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. So, can you give some information why the feature has been removed? Thanks a lot for your help! Best regards Christian 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-18464) Build Pipeline and Join plugin do not play nicely together
Michael Weinrich edited a comment on JENKINS-18464 Build Pipeline and Join plugin do not play nicely together I would like to help fixing this issue, but I'm totally new to Jenkins development (yet I used it for quite some time now). I tried to write a unit test to illustrate the problem (see https://github.com/InterNations/build-pipeline-plugin/compare/join-trigger-fix), however I'm stuck there. Is there anything I can do to accelerate the fix for this issue? I might even get some bounty for the fix (of course not for me but for the one fixing it ) If anyone is interested, I would ask for details on that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-4021) TFS - unparseable date problem
Mats Taraldsvik commented on JENKINS-4021 TFS - unparseable date problem I looked at this error a while ago, and the best solution I could come up with, was to try parsing the date with all locales on the system. This could be a pretty safe fallback, with optional user configurable locale in the TFS plugin configuration settings. Look at this ideone snippet where I took the current date parsing function and modified it to the proposed behaviour: http://ideone.com/VPqO8e I hope this can be implemented, and solve this bug in most cases (but some might have to configure the locale explicitly). 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 ?)
Chris Yorkston commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I am experiencing the same problem when setting up a build plan on Jenkins using git. I have Jenkins installed on an EC2 instance. Failed to connect to repository : Command "git config --local credential.helper store --file=\"/tmp/git1036220241480036003.credentials\"" returned status code 255: stdout: stderr: error: could not lock config file .git/config: No such file or directory 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 ?)
Tamas Papp commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Polling is also broken. 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-19179) Matrix sub-jobs get disabled
Jesse Glick commented on JENKINS-19179 Matrix sub-jobs get disabled As noted in this QA the workaround is to browse to configure on the matrix configuration and uncheck Disabled. Clearly one bug is that a matrix configuration got disabled somehow, i.e. the MatrixConfiguration.disabled field was set. How? The next bug is that configure (and configSubmit) are even available on matrix configurations (albeit without a sidebar link), when there does not seem to be any intent for these config.xml files to be individually configurable. (The configure page shows all sorts of options, such as SCMs, which are definitely not supposed to be allowed on configurations.) These URLs should presumably be blocked. The config.xml URL is also available; in GET mode this might be OK, but a POST to it is probably also bad. Then there is the problem that despite the fact that MatrixConfiguration.supportsMakeDisabled is false, so no UI button appears to explicitly enable or disable the project, isDisabled is not overridden to unconditionally return true. 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 ?)
Adrian Smith commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I'm sure the developers would appreciate more clues than "Polling is also broken" ! There are solutions to these problems in the thread. This is an open source project. Perhaps you could try and provide answers. It's really not that hard to build the plugin and fix it yourself. 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-20128) HTTP two-way remoting does not work (jenkins-cli.jar without JNLP)
Jesse Glick assigned JENKINS-20128 to Kohsuke Kawaguchi HTTP two-way remoting does not work (jenkins-cli.jar without JNLP) What was the actual cause of the regression? JENKINS-18366? Change By: Jesse Glick (13/Jan/14 3:02 PM) Assignee: KohsukeKawaguchi 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-20128) HTTP two-way remoting does not work (jenkins-cli.jar without JNLP)
Peter van Dijk commented on JENKINS-20128 HTTP two-way remoting does not work (jenkins-cli.jar without JNLP) Yes - see git bisect mention in an earlier comment. 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-21136) ArrayOutOfBounds on almost any admin function - Mac OS X 10.9.1 Jenkins 1.544
Jesse Glick resolved JENKINS-21136 as Duplicate ArrayOutOfBounds on almost any admin function - Mac OS X 10.9.1 Jenkins 1.544 Change By: Jesse Glick (13/Jan/14 3:09 PM) Status: Open Resolved Resolution: Duplicate 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-18537) java.lang.ArrayIndexOutOfBoundsException when trying to save data
Jesse Glick updated JENKINS-18537 java.lang.ArrayIndexOutOfBoundsException when trying to save data Change By: Jesse Glick (13/Jan/14 3:10 PM) Labels: exception jenkins xstream 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-18537) ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6
Jesse Glick updated JENKINS-18537 ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6 Change By: Jesse Glick (13/Jan/14 3:11 PM) Labels: exception jdk xstream 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
Justinas Urbanavicius commented on JENKINS-4021 TFS - unparseable date problem I personally don't agree that implementing a heuristic parser is a good idea, it most likely will create more problems than solve. User set locale in configuration sounds as a better and more simple solution. 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-18537) ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6
Jesse Glick updated JENKINS-18537 ArrayIndexOutOfBoundsException during Jenkins.doConfigSubmit; need XStream 1.4.6 Change By: Jesse Glick (13/Jan/14 3:11 PM) Summary: java ArrayIndexOutOfBoundsExceptionduringJenkins . lang doConfigSubmit;needXStream1 . ArrayIndexOutOfBoundsExceptionwhentryingtosavedata 4.6 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] [email-ext] (JENKINS-21348) Remove Maven Plugin dependency
Alex Earl commented on JENKINS-21348 Remove Maven Plugin dependency At this point, this is kind of a low priority. The Maven stuff is somewhat ingrained in the plugin right now. It was implemented before I took the plugin over, and while I don't necessarily like the dependency, since the maven-plugin is bundled with core, I don't think its a huge deal right now. 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
Justinas Urbanavicius edited a comment on JENKINS-4021 TFS - unparseable date problem I personally don't agree that implementing a heuristic parser is a good idea, it most likely will create more problems than solve. User set locale in configuration sounds as a better and more simple solution. In some cases, then your build system is set up on a different environment, you might not even have the same locales, like building on Linux for example. 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-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Jesse Glick commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows If you can find a command which can be run as the Jenkins user which detects whether the fsutil command needs be run (as an administrator), file an RFE for Jenkins to warn you of this, most simply via a console warning but ideally using an AdministrativeMonitor. (Even better would be for Jenkins to offer to run it after you supply an administrator login, using the Windows equivalent of sudo if there is such a thing.) 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 ?)
Adrian Smith commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) search for my name above and you see fixes for both of these errors. 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 ?)
Tamas Papp commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I'm sure the developers would appreciate more clues than "Polling is also broken" ! Actually I would like to see, whether the developers are able to reproduce these issues. There are solutions to these problems in the thread. This is an open source project. Perhaps you could try and provide answers. It's really not that hard to build the plugin and fix it yourself. If I was able to fix, I would certainly do. I don't see any solution in this thread. Here is a summary: git (client) plugin doesn't work with http(s) based repositories. Polling also seems to be broken. There are various error messages, they probably depend on the system and environment. Eg. setting up the repository on the job configuration page: Failed to connect to repository : Command "git config --local credential.helper store --file=\"/tmp/git3436741386766728464.credentials\"" returned status code 255: stdout: stderr: error: could not lock config file .git/config: No such file or directory build a job manually: Fetching changes from the remote Git repository Fetching upstream changes from https://git.fooodomain.com/git/baar/connect.git using .gitcredentials to set credentials FATAL: Failed to fetch from https://git.fooodomain.com/git/baar/connect.git hudson.plugins.git.GitException: Failed to fetch from https://git.fooodomain.com/git/baar/connect.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:625) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:847) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:872) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) 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) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress https://git.fooodomain.com/git/baar/connect.git +refs/heads/:refs/remotes/origin/" returned status code 128: stdout: stderr: error: cannot run /bin/echo : No such file or directory fatal: could not read Username for 'https://git.fooodomain.com': No such device or address at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1109) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:991) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:71) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:220) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) 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.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) It's easy to reproduce: get the latest version of jenkins and git/git client plugins setup a central credential for the git server setup a job with https repository URL run a build and check the console output 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
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Tamas Papp commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I thought that changes were already applied. Thanks, I'll try 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] [cli] (JENKINS-12629) Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate
Daniel Beck commented on JENKINS-12629 Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate Does not seem to be in 1.532.x, so should probably be backported to 1.532.2, as it's effectively a regression from 1.509.4. 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 ?)
Ron L commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Not everyone has the experience, nor time to troubleshoot this issue on their own. I personally have spent the past 2 weeks trying to resolve this issue without any success. Adrian Smith, I have seen your fix above, but what worries me is that you mention that you guess it'll break on Windows systems. Unfortunately, this is what keeps me from applying this fix myself. Understandably, this is an open source project, but there are far more talented developers with experience in the entire stack that can apply a more reliable fix. 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-15799) loosing matrix sub builds
Sven Appenrodt commented on JENKINS-15799 loosing matrix sub builds Upgraded to Jenkins version 1.539 several days (or months ago). LogRotation is set to X days and Y builds and another job is set to Y builds only. Problem does not occur anymore on both machines. Please can anyone confirm 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] [prioritysorter] (JENKINS-21352) Add Specific Permissions for managing priorities
Magnus Sandberg created JENKINS-21352 Add Specific Permissions for managing priorities Issue Type: New Feature Assignee: Magnus Sandberg Components: prioritysorter Created: 13/Jan/14 4:24 PM Description: Add Specific Permissions for managing priorities, one for the global page and one for managing priority on Jobs. Project: Jenkins Priority: Major Reporter: Magnus Sandberg 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] [prioritysorter] (JENKINS-21313) Anonymous users can configure and delete PrioritySorter JobGroups
Magnus Sandberg closed JENKINS-21313 as Not A Defect Anonymous users can configure and delete PrioritySorter JobGroups Change By: Magnus Sandberg (13/Jan/14 4:28 PM) Status: Open Closed Resolution: NotADefect 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-21353) Cannot delete workspace
D Quigg created JENKINS-21353 Cannot delete workspace Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Jan/14 4:35 PM Description: (Note: Assigned to 'core' component only because I don't know correct component) I'm seeing the same behavior described in JENKINS-19994 but I'm using SVN. Our environment: Master: Jenkins 1.509.1 running on Debian 6.0 Our slave: Win2003 64-bit The slave VM does auto-login and has a startup script that executes; "C:\Program Files\Java\jre6\bin\javaws.exe" http://OurJenkins/computer/OurSlave/slave-agent.jnlp" This works fine. Sometimes, there is an error during SVN checkout like; begin console Deleting project workspace... done Cleaning local Directory ./OurProj Checking out http://OurSvn/OurRepo/trunk/OurProj at revision '2014-01-12T18:53:11.137 -0800' AOurProj snip ERROR: Failed to check out http://OurSvn/OurRepo/trunk/OurProj/SomeDir org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /OurRepo/!svn/vcc/default failed end console After the above checkout failure, subsequent job runs are failing immediately. begin console Deleting project workspace... Cannot delete workspace: java.io.IOException: Unable to delete C:\opt\hudson\workspace\OurJob\SomeDir\MKL\em64t\lib\.svn\tmp\text-base\mkl_core.lib.svn-base ERROR: Cannot delete workspace: java.io.IOException: Unable to delete C:\opt\hudson\workspace\OurJob\SomeDir\MKL\em64t\lib\.svn\tmp\text-base\mkl_core.lib.svn-base end console This will happen as many times as you want to press the 'build' button... After several occurrences of this error, *** I manually deleted the entire $WORKSPACE directory ***. However, the problem still occurs. After reading JENKINS-19994, I started up ProcessExplorer and did 'Find|Find Handle or DLL...' and searched for 'mkl_core'. Sure enough there was a 'javaws.exe' process found. Killing that process (by clicking the 'X' in 'Jenkins slave agent' window) and restarting the Jenkins client resolves the issue. My understanding is that Windows will not delete (or say it deleted) a file if that file is in use. It will always complain until the file is released. This suggests to me that the javaws.exe process is reporting a false positive saying it is using a file when this is not actually the case. So, I don't think this is a Git specific issue as described in JENKINS-19994, but rather a more widely reaching issue. (Unless there is copy-and-paste code between SVN and Git modules). We seem to get SVN checkout errors fairly frequently (which may be a different issue either in Jenkins or our environment) so being able to avoid the "one problem means you're forever stuck" would be nice. Environment: Windows slave - Linux master Project: Jenkins Priority: Major Reporter: D Quigg 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] [publish-over-cifs] (JENKINS-21354) Disable having Clean remote option available in UI
Jurica Krizanic created JENKINS-21354 Disable having Clean remote option available in UI Issue Type: New Feature Affects Versions: current Assignee: bap Components: publish-over-cifs Created: 13/Jan/14 4:44 PM Description: Is it possible to disable having the Clean remote option available in the UI? I believe that lots of users want to protect from unintentionally turning the Clean remote option on, and deleting the remote directory unintentionally. Such an action can be expensive, so it would be useful to have a new feature which provides disabling this option! Project: Jenkins Labels: clean, remote Priority: Major Reporter: Jurica Krizanic 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-20327) javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 241320200000
mwebber commented on JENKINS-20327 javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 24132020 I got this problem in 1.547 when I edited a large view that was constructed using the Sectioned View plugin. I have a lot of jobs, and the way the edit form is constructed means that I hit up against the limit. This didn't use to happen - at what point was the limit introduced? I am about to try the -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500 option to see if that works. 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] [reverse-proxy-auth] (JENKINS-21304) NPE - Reverse Proxy Authentication
Sylvain Veyrié commented on JENKINS-21304 NPE - Reverse Proxy Authentication I have the same as Benjamin, that may to not be the same NPE than Martin and than Ireneusz (lots of NPE out there). After reverse proxy auth plugin upgrade (from 1.0.1 to 1.3.1) and restart, Jenkins always gives: java.lang.NullPointerException at org.eclipse.jetty.util.StringUtil.getBytes(StringUtil.java:383) at org.eclipse.jetty.io.ByteArrayBuffer.init(ByteArrayBuffer.java:81) at org.eclipse.jetty.io.ByteArrayBuffer$CaseInsensitive.init(ByteArrayBuffer.java:424) at org.eclipse.jetty.io.BufferCache$CachedBuffer.init(BufferCache.java:134) at org.eclipse.jetty.io.BufferCache.lookup(BufferCache.java:101) at org.eclipse.jetty.http.HttpFields.getField(HttpFields.java:402) at org.eclipse.jetty.http.HttpFields.getStringField(HttpFields.java:431) at org.eclipse.jetty.server.Request.getHeader(Request.java:605) at org.jenkinsci.plugins.reverse_proxy_auth.ReverseProxySecurityRealm$1.doFilter(ReverseProxySecurityRealm.java:366) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Debian wheezy Jenkins 1.545 Revert to 1.0.1 solves the problem. BTW, I don't know how to find the Groovy line where the error is, using the line number printed in the stacktrace. 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 ?)
Adrian Smith commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) yes, point taken. There is probably some middle ground. One of the benefits of Open Source is that ultimately you can fix it yourself. You can raise the priority all you like, but it's just best efforts from other enthusiastic people that gets us fantastic products like Jenkins that are free! 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-20327) javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 241320200000
mwebber commented on JENKINS-20327 javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 24132020 Adding -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500 option to the Jenkins startup options does indeed fix this problem for 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] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
Ricardo Junior edited a comment on JENKINS-20276 Native Library Error after upgrading ssh-agent from 1.3 to 1.4 Same here. OS: Linux lxkstst1 2.6.32-431.1.2.el6.x86_64 #1 SMP Sun Nov 24 09:37:37 EST 2013 x86_64 x86_64 x86_64 GNU/Linux JVM: java version "1.6.0_45" Java(TM) SE Runtime Environment (build 1.6.0_45-b06) Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode) Log: Started by user anonymous Building in workspace /var/lib/jenkins/workspace/Diretórios ssh-agent Using credentials ansible (Chave Ansible HMP) ssh-agent Looking for ssh-agent implementation... ssh-agent Java/JNR ssh-agent ssh-agent FATAL: Could not find a suitable ssh-agent provider ssh-agent Diagnostic report ssh-agent * Java/JNR ssh-agent ssh-agent java.lang.UnsatisfiedLinkError: /lib/libc.so.6: wrong ELF class: ELFCLASS32 ssh-agent at jnr.ffi.provider.jffi.NativeLibrary.loadNativeLibraries(NativeLibrary.java:87) ssh-agent at jnr.ffi.provider.jffi.NativeLibrary.getNativeLibraries(NativeLibrary.java:70) ssh-agent at jnr.ffi.provider.jffi.NativeLibrary.getSymbolAddress(NativeLibrary.java:49) ssh-agent at jnr.ffi.provider.jffi.NativeLibrary.findSymbolAddress(NativeLibrary.java:59) ssh-agent at jnr.ffi.provider.jffi.AsmLibraryLoader.generateInterfaceImpl(AsmLibraryLoader.java:125) ssh-agent at jnr.ffi.provider.jffi.AsmLibraryLoader.loadLibrary(AsmLibraryLoader.java:63) ssh-agent at jnr.ffi.provider.jffi.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:43) ssh-agent at jnr.ffi.LibraryLoader.load(LibraryLoader.java:228) ssh-agent at jnr.ffi.Library.loadLibrary(Library.java:123) ssh-agent at jnr.ffi.Library.loadLibrary(Library.java:80) ssh-agent at jnr.unixsocket.Native$LibC.clinit(Native.java:40) ssh-agent at jnr.unixsocket.Native.libsocket(Native.java:60) ssh-agent at jnr.unixsocket.Native.socket(Native.java:68) ssh-agent at jnr.unixsocket.UnixServerSocketChannel.init(UnixServerSocketChannel.java:38) ssh-agent at jnr.unixsocket.UnixServerSocket.init(UnixServerSocket.java:29) ssh-agent at jnr.unixsocket.UnixServerSocketChannel.open(UnixServerSocketChannel.java:48) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.AgentServer.start(AgentServer.java:67) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.init(JNRRemoteAgent.java:64) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:54) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:35) ssh-agent at hudson.remoting.LocalChannel.call(LocalChannel.java:45) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentFactory.start(JNRRemoteAgentFactory.java:61) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.init(SSHAgentBuildWrapper.java:211) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:123) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:93) ssh-agent at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:78) ssh-agent at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) ssh-agent at hudson.model.Run.execute(Run.java:1678) ssh-agent at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) ssh-agent at hudson.model.ResourceController.execute(ResourceController.java:88) ssh-agent at hudson.model.Executor.run(Executor.java:231) FATAL: ssh-agent Unable to start agent hudson.util.IOException2: ssh-agent Unable to start agent at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:130) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:93) at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:78) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) 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) Caused by: java.lang.RuntimeException: ssh-agent Could not find a suitable ssh-agent provider. at
[JIRA] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
Ricardo Junior commented on JENKINS-20276 Native Library Error after upgrading ssh-agent from 1.3 to 1.4 Same here. tarted by user anonymous Building in workspace /var/lib/jenkins/workspace/Diretórios ssh-agent Using credentials ansible (Chave Ansible HMP) ssh-agent Looking for ssh-agent implementation... ssh-agent Java/JNR ssh-agent ssh-agent FATAL: Could not find a suitable ssh-agent provider ssh-agent Diagnostic report ssh-agent * Java/JNR ssh-agent ssh-agent java.lang.UnsatisfiedLinkError: /lib/libc.so.6: wrong ELF class: ELFCLASS32 ssh-agent at jnr.ffi.provider.jffi.NativeLibrary.loadNativeLibraries(NativeLibrary.java:87) ssh-agent at jnr.ffi.provider.jffi.NativeLibrary.getNativeLibraries(NativeLibrary.java:70) ssh-agent at jnr.ffi.provider.jffi.NativeLibrary.getSymbolAddress(NativeLibrary.java:49) ssh-agent at jnr.ffi.provider.jffi.NativeLibrary.findSymbolAddress(NativeLibrary.java:59) ssh-agent at jnr.ffi.provider.jffi.AsmLibraryLoader.generateInterfaceImpl(AsmLibraryLoader.java:125) ssh-agent at jnr.ffi.provider.jffi.AsmLibraryLoader.loadLibrary(AsmLibraryLoader.java:63) ssh-agent at jnr.ffi.provider.jffi.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:43) ssh-agent at jnr.ffi.LibraryLoader.load(LibraryLoader.java:228) ssh-agent at jnr.ffi.Library.loadLibrary(Library.java:123) ssh-agent at jnr.ffi.Library.loadLibrary(Library.java:80) ssh-agent at jnr.unixsocket.Native$LibC.clinit(Native.java:40) ssh-agent at jnr.unixsocket.Native.libsocket(Native.java:60) ssh-agent at jnr.unixsocket.Native.socket(Native.java:68) ssh-agent at jnr.unixsocket.UnixServerSocketChannel.init(UnixServerSocketChannel.java:38) ssh-agent at jnr.unixsocket.UnixServerSocket.init(UnixServerSocket.java:29) ssh-agent at jnr.unixsocket.UnixServerSocketChannel.open(UnixServerSocketChannel.java:48) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.AgentServer.start(AgentServer.java:67) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.init(JNRRemoteAgent.java:64) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:54) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:35) ssh-agent at hudson.remoting.LocalChannel.call(LocalChannel.java:45) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentFactory.start(JNRRemoteAgentFactory.java:61) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.init(SSHAgentBuildWrapper.java:211) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:123) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:93) ssh-agent at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:78) ssh-agent at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) ssh-agent at hudson.model.Run.execute(Run.java:1678) ssh-agent at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) ssh-agent at hudson.model.ResourceController.execute(ResourceController.java:88) ssh-agent at hudson.model.Executor.run(Executor.java:231) FATAL: ssh-agent Unable to start agent hudson.util.IOException2: ssh-agent Unable to start agent at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:130) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:93) at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:78) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) 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) Caused by: java.lang.RuntimeException: ssh-agent Could not find a suitable ssh-agent provider. at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.init(SSHAgentBuildWrapper.java:229) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:123) ... 7 more
[JIRA] [build-flow] (JENKINS-21355) Build flow jobs do not respect throttling rules
Michael Rose created JENKINS-21355 Build flow jobs do not respect throttling rules Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow, throttle-concurrents Created: 13/Jan/14 5:49 PM Description: Steps to reproduce: 1. Create a build-flow projectA 2. Setup projectA to allow concurrent builds, but configure throttling so only one build is allowed per node 3. Manually trigger multiple builds of projectA Notice that Jenkins chooses the same node for each build-flow build in a projectA. I may be wrong, but it seems that Jenkins will only choose a different node if the build-flow job is for a different project. In my case: projectA syncs source code to a local workspace on nodeA projectA orchestrates a parametrized build, passing nodeA as a parameter to ensure the build is done on the same node that the source code was sync'd on The build job has a throttle rule that only allows one build per node so even though two build-flow jobs are running on the same node, one build still has to wait for the other. I like that flyweight jobs are excluded from the normal throttle rules, but it would be nice if users could create rules specifically for flyweight jobs; or some way to configure build-flow jobs to not use the same node for each job Project: Jenkins Priority: Major Reporter: Michael Rose 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-20998) Add Timestamp to Workspace View
Chris Bush updated JENKINS-20998 Add Timestamp to Workspace View Where timestamps should go. See comment #2 Change By: Chris Bush (13/Jan/14 5:58 PM) Attachment: workspaceview.png 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-20998) Add Timestamp to Workspace View
Chris Bush edited a comment on JENKINS-20998 Add Timestamp to Workspace View See the attached screenshot for where I'm talking about. On the workspace page, next to each file it should have a timestamp. 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] [active-directory] (JENKINS-18884) Seperate Permission for People View to close Security Hole with AD Plugin
Daniel Beck commented on JENKINS-18884 Seperate Permission for People View to close Security Hole with AD Plugin Possible workaround: Hide Jenkins behind a reverse proxy (e.g. Apache). Configure it to listen only on the 127.0.0.1 interface (--httpListenAddress=127.0.0.1). Forbid access to people/asynchPeople URLs. Those links will then result in 403 Forbidden. Sample Apache httpd.conf excerpt, assuming reverse proxy and Jenkins are running on the same host, Jenkins on port 8080, Apache on port 80: VirtualHost *:80 RewriteEngine On ServerName jenkins.example.org # change to actual server name RewriteRule /asynchPeople/ - [F] RewriteRule /people/ - [F] ProxyPass / http://localhost:8080/ ProxyPassReverse / http://localhost:8080/ ProxyRequests Off /VirtualHost Of course, this simple pattern will prohibit access to e.g. the job named 'people' as well. Haven't tested this with all possible Jenkins URLs, making sure it works for those is left as an exercise to the reader This should keep at least most of the users out, even if it's likely not a 100% solution. 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] [prioritysorter] (JENKINS-21352) Add Specific Permissions for managing priorities
Daniel Beck commented on JENKINS-21352 Add Specific Permissions for managing priorities I understand that not everyone with Job/Configure should be able to edit their job's priority. But why introduce a permission for global job permissions independent from Overall/Administer? What's the use case for not being an admin but wanting to change global job priority 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] [delivery-pipeline] (JENKINS-20717) Add pipelines to view dymacally with regexp
Patrik Boström resolved JENKINS-20717 as Fixed Add pipelines to view dymacally with regexp Merged to master Change By: Patrik Boström (13/Jan/14 7:00 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/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21352) Add Specific Permissions for managing priorities
Magnus Sandberg commented on JENKINS-21352 Add Specific Permissions for managing priorities Well, I might be wrong but I can see the use-case where someone is allowed to tweak the Priority Setup (ie assigning priorities to groups of Jobs) but they are not allowed to change Jenkins main configuration. This permission should however not be confused with managing the basic setup of the Plugin on the main configuration page, that is for Administer to do. 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-12629) Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate
SCM/JIRA link daemon commented on JENKINS-12629 Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate Code changed in jenkins User: Stephen Connolly Path: cli/src/main/java/hudson/cli/NoCheckTrustManager.java http://jenkins-ci.org/commit/jenkins/867a35523c2f6cf7a88e1ddb11c471652c7df5a9 Log: FIXED JENKINS-12629 Using jenkins-cli connecting to HTTPS port fails due to hostname mismatch in certificate. NoCheckTrustManager needed to implement X509TrustManager not just plain TrustManager (cherry picked from commit 0ab79882978292f3751be8e0acf5ae7edb0751f1) Compare: https://github.com/jenkinsci/jenkins/compare/de78db8d6ba0...867a35523c2f 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-17614) Jenkins triggers builds on SCM changes although not configured
Grigoriy Milman commented on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured We have the same issue with Jenkins ver. 1.547. We updated from 1.535 to the 1.546 and suddenly this issue appeared. We are using PTC plugin, and for all build jobs each time when a polling happened the new build is triggered, polling log tells that there is so many changes found, but SCM tells that there is no changes! See attached screens 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-17614) Jenkins triggers builds on SCM changes although not configured
Grigoriy Milman updated JENKINS-17614 Jenkins triggers builds on SCM changes although not configured Change By: Grigoriy Milman (13/Jan/14 7:57 PM) Attachment: view1.JPG Attachment: View2.JPG 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-17614) Jenkins triggers builds on SCM changes although not configured
Grigoriy Milman edited a comment on JENKINS-17614 Jenkins triggers builds on SCM changes although not configured We have the same issue with Jenkins ver. 1.547. We updated from 1.535 to the 1.546 and suddenly this issue appeared. We are using PTC plugin, and for all build jobs each time when a polling happened the new build is triggered, polling log tells that there is so many changes found, but SCM tells that there is no changes! See attached pictures - noticed that here "No changes" and SCM change log tells that This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21356) Add support for using JobProperty to join a Job to a JobGroup
Magnus Sandberg created JENKINS-21356 Add support for using JobProperty to join a Job to a JobGroup Issue Type: Improvement Assignee: Magnus Sandberg Components: prioritysorter Created: 13/Jan/14 8:10 PM Description: Rather than using top down grouping using Views also support bottom up grouping by using a JobProperty. Also optionally support groping by FolderProperty from cloudbees-folders Project: Jenkins Priority: Major Reporter: Magnus Sandberg 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.
