[JIRA] [plugin] (JENKINS-23916) Adding a plugin to a build job which contains file upload button restricts user to rename the build job
Manoj Pattanaik created JENKINS-23916 Adding a plugin to a build job which contains file upload button restricts user to rename the build job Issue Type: Bug Assignee: Unassigned Components: plugin Created: 22/Jul/14 6:41 AM Description: Jenkins Ver 1.553 I am developing a plugin to which I added a file upload button as shown below: The file upload button works fine as expected. The problem is when I add this plugin to a build job, I am not able to rename the build job. Removing the plugin from the build job only allows me to rename the build job. Environment: System Properties Name ↓ Value awt.toolkit sun.awt.windows.WToolkit executable-war C:\Program Files (x86)\Jenkins\jenkins.war file.encoding Cp1252 file.encoding.pkg sun.io file.separator \ hudson.diyChunking true hudson.lifecycle hudson.lifecycle.WindowsServiceLifecycle java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.awt.windows.WPrinterJob java.class.path C:\Program Files (x86)\Jenkins\jenkins.war java.class.version 51.0 java.endorsed.dirs C:\Program Files (x86)\Jenkins\jre\lib\endorsed java.ext.dirs C:\Program Files (x86)\Jenkins\jre\lib\ext;C:\Windows\Sun\Java\lib\ext java.home C:\Program Files (x86)\Jenkins\jre java.io.tmpdir C:\Windows\TEMP\ java.library.path C:\Program Files (x86)\Jenkins\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files (x86)\CA\SharedComponents\PEC\bin;c:\Program Files (x86)\CA\SC\CAWIN\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files (x86)\CA\SC\Csam\SockAdapter\bin;c:\Program Files (x86)\CA\DSM\bin;c:\Program Files (x86)\CA\SC\CBB\;c:\PROGRA~2\CA\SC\CAM\bin;C:\Program Files (x86)\McAfee\MOVE AV Client\;C:\Program Files\CA\SCM;c:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;c:\Program Files\Microsoft SQL Server\110\Tools\Binn\;c:\Program Files\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;;. java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.7.0_25-b17 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_25 java.vm.info mixed mode java.vm.name Java HotSpot(TM) Client VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 23.25-b01 line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch x86 os.name Windows Server 2008 R2 os.version 6.1 path.separator ; sun.arch.data.model 32 sun.boot.class.path C:\Program Files (x86)\Jenkins\jre\lib\resources.jar;C:\Program Files (x86)\Jenkins\jre\lib\rt.jar;C:\Program Files (x86)\Jenkins\jre\lib\sunrsasign.jar;C:\Program Files (x86)\Jenkins\jre\lib\jsse.jar;C:\Program Files (x86)\Jenkins\jre\lib\jce.jar;C:\Program Files (x86)\Jenkins\jre\lib\charsets.jar;C:\Program Files (x86)\Jenkins\jre\lib\jfr.jar;C:\Program Files (x86)\Jenkins\jre\classes sun.boot.library.path C:\Program Files (x86)\Jenkins\jre\bin sun.cpu.endian little sun.cpu.isalist pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86 sun.desktop windows sun.io.unicode.encoding UnicodeLittle sun.java.command C:\Program Files (x86)\Jenkins\jenkins.war --httpPort=8080 sun.java.launcher SUN_STANDARD sun.jnu.encoding Cp1252 sun.management.compiler HotSpot Client Compiler sun.os.patch.level Service Pack 1 svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistent false user.country US user.dir C:\Program Files (x86)\Jenkins user.home C:\ user.language en user.name user.script user.timezone Asia/Calcutta user.variant
[JIRA] [core] (JENKINS-23914) Invalid element added to in job causing NPE on job load
Craig Ringer commented on JENKINS-23914 Invalid element added to in job causing NPE on job load I wonder if this is related to the way the matrix plugin sets NullSCM for all child projects? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23914) Invalid element added to in job causing NPE on job load
Craig Ringer commented on JENKINS-23914 Invalid element added to in job causing NPE on job load Looking at the git history for the job, I see that whenever this happened the git configuration for the job was also lost, e.g. - "hudson.plugins.git.GitSCM" plugin="git@2.2.2"> -2 - - + "hudson.scm.NullSCM"/> This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8900) allow time limit to be specified for build step
Craig Ringer commented on JENKINS-8900 allow time limit to be specified for build step Domas, generally features get implemented when someone puts in the time to implement them, or funds their implementation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23915) When Jenkins can't read a job, it vanishes from the job-list instead of being replaced with an error marker
Craig Ringer created JENKINS-23915 When Jenkins can't read a job, it vanishes from the job-list instead of being replaced with an error marker Issue Type: Improvement Assignee: Unassigned Components: core Created: 22/Jul/14 5:45 AM Description: As part of JENKINS-23914 I noticed that jobs that Jenkins fails to load completely vanish from the UI. They're still present in jobs/jobname/config.xml, but the only indication they exist in the UI is an error in the log where they failed to load. It would be a usability improvement helpful if, in cases where the job XML was parsed successfully but the job objects couldn't be created, jenkins displayed a "broken" job in the job-list which shows the exception encountered when loading the job when opened. Vanishing jobs aren't fun, especially if you don't know how to fix them by hand. Environment: Jenkins 1.574-SNAPSHOT Project: Jenkins Labels: job corruption usability Priority: Minor Reporter: Craig Ringer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23914) Invalid element added to in job causing NPE on job load
Craig Ringer created JENKINS-23914 Invalid element added to in job causing NPE on job load Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jul/14 5:38 AM Description: On several occasions recently, while editing my matrix jobs, I've noticed that Jenkins has lost the SCM configuration for git polling and replaced it with an invalid entry in the job xml:that causes the job to fail to load when Jenkins is restarted, with: Failed Loading job bdr_linux java.lang.NullPointerException at hudson.model.AbstractProject.onLoad(AbstractProject.java:326) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:496) at hudson.model.Items.load(Items.java:279) at jenkins.model.Jenkins$18.run(Jenkins.java:2599) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:885) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:701) I haven't yet nailed down a way to reproduce this, but it seems to occur most often around when I've also been having issues with configuration elements throwing exceptions on save. The job appears to just "vanish" from the job list, as Jenkins doesn't show broken jobs in the UI at all. To find out what happened I had to go digging in the config XML. I version my configuration XML, so I was able to see the following in the most recent diff for jobs/bdr_linux/config.xml: - - H/5 * * * * - false - + To repair the job, I can revert that hunk, or just delete the invalid null element then re-create the trigger in the UI. So there are a couple of problems here: A null element like that is invalid and should never be written out, as it cannot be consumed; and the trigger configuration is being lost. Environment: Jenkins 1.574-SNAPSHOT (17d9093) Project: Jenkins Labels: configuration corruption job Priority: Major Reporter: Craig Ringer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23786) Permit "Execute shell" jobs to return 2 for "unstable"
Craig Ringer commented on JENKINS-23786 Permit "Execute shell" jobs to return 2 for "unstable" I've updated the pull request with: support for BatchFile too Unit tests and think it's ready to go. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23884) Git/GitHub Enterprise (GHE) SCM Polling creates builds with "No Changes" when there are two similarly named branches present
Mark Waite commented on JENKINS-23884 Git/GitHub Enterprise (GHE) SCM Polling creates builds with "No Changes" when there are two similarly named branches present I've uploaded to google drive in hopes you can download it from there. The zip file contains two plugins. Upload the git client plugin first, then the git plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23907) Jenkins CLI
Daniel Beck commented on JENKINS-23907 Jenkins CLI There do not seem to be any relevant changes between 1.572 and 1.573. Is a warning or error logged by Jenkins when you do that? If so, what is it? Please ensure that this is the jenkins-cli.war matching the running Jenkins instance (download from link on /cli page). Did the file jenkins.autocfg.key change since it worked on 1.572? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-23903) NullPointeException in hudson.maven.Maven3Builder$MavenExecutionListener.sessionEnded
Daniel Beck updated JENKINS-23903 NullPointeException in hudson.maven.Maven3Builder$MavenExecutionListener.sessionEnded Report needs to specify Maven Project plugin versions. Also, is this a regression from an earlier version? Did it ever work? What config changes happened since? Are you able to reproduce this issue in a simpler configuration, maybe one that can be reproduced by others? Change By: Daniel Beck (21/Jul/14 11:36 PM) Component/s: maven Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
dogfood commented on JENKINS-22641 Jenkins no longer kills running processes after job fails Integrated in jenkins_main_trunk #3538 [FIXED JENKINS-22641] FileUtils.readFileToByteArray behavior has changed in the latest version of commons-io. (Revision 410f06adfa798d29118c77ed01c5c02fc207cb02) Add test unit for JENKINS-22641 (Revision 0d4c0cb6b274bfa18c810fcf761e3ad8b27ceb34) JENKINS-22641 Noting merge of #1322. (Revision 14a147eda8eebfd78c1cc53e1d59232d720de6b7) Result = SUCCESS schristou88 : 410f06adfa798d29118c77ed01c5c02fc207cb02 Files : core/src/main/java/hudson/util/ProcessTree.java schristou88 : 0d4c0cb6b274bfa18c810fcf761e3ad8b27ceb34 Files : test/src/test/java/hudson/util/ProcessTreeKillerTest.java Jesse Glick : 14a147eda8eebfd78c1cc53e1d59232d720de6b7 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23913) Unable to change user passwords
Daniel Beck resolved JENKINS-23913 as Not A Defect Unable to change user passwords According to web search, issues of this kind seem to be a OS/Java configuration issue and unrelated to Jenkins. https://hbase.apache.org/book.html#trouble.crypto.HBASE-10132 https://www.liferay.com/community/wiki/-/wiki/Main/Glassfish+tips/pop_up?controlPanelCategory=portlet_36#section-Glassfish+tips-certutil+issue http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6928796 Report needs to show this is a Jenkins problem and not the issue described on the linked web pages. Unfortunately not enough information (e.g. is this a regression in Jenkins, ...) is provided. Change By: Daniel Beck (21/Jul/14 11:31 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19465) OSX Slave hangs while being launched
Erik Purins commented on JENKINS-19465 OSX Slave hangs while being launched When I reconnect on the console to try and work around the issue, the node comes back online (executors available in the left column), but the slave node icon remains blinking as if it is not connected correctly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git fetch and git submodule update commands
Mark Waite edited a comment on JENKINS-20387 Timeout (10min) on git fetch and git submodule update commands There are two different classes of timeout in the plugin. Timeout for fetch is governed by the setting in the UI. Timeout for operations which are not fetch are fixed at 10 minutes, at least in one or more cases I've detected. Since fetch is the primary network operation which may be slow, and non-fetch operations are almost entirely local operations, the timeout setting on fetch has been a reasonable heuristic. Is there any way you can test my theory that the "git submodule" command is blocking on an authentication prompt? For example, can you see if your git server is sending lots of data to the client while that command is blocked? If the server is sending lots of data, then it is not an authentication prompt which is blocking. Are the submodule repositories expected to take a long time to clone (because they are large)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
SCM/JIRA link daemon commented on JENKINS-22641 Jenkins no longer kills running processes after job fails Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/14a147eda8eebfd78c1cc53e1d59232d720de6b7 Log: JENKINS-22641 Noting merge of #1322. Compare: https://github.com/jenkinsci/jenkins/compare/a8756c6c0ddc...14a147eda8ee This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
SCM/JIRA link daemon commented on JENKINS-22641 Jenkins no longer kills running processes after job fails Code changed in jenkins User: christ66 Path: test/src/test/java/hudson/util/ProcessTreeKillerTest.java http://jenkins-ci.org/commit/jenkins/0d4c0cb6b274bfa18c810fcf761e3ad8b27ceb34 Log: Add test unit for JENKINS-22641 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
SCM/JIRA link daemon commented on JENKINS-22641 Jenkins no longer kills running processes after job fails Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/util/ProcessTree.java test/src/test/java/hudson/util/ProcessTreeKillerTest.java http://jenkins-ci.org/commit/jenkins/f03e67a49bf01343635c60e894b9617483a03011 Log: Merge branch 'JENKINS-22641' of github.com:christ66/jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
SCM/JIRA link daemon commented on JENKINS-22641 Jenkins no longer kills running processes after job fails Code changed in jenkins User: christ66 Path: core/src/main/java/hudson/util/ProcessTree.java http://jenkins-ci.org/commit/jenkins/410f06adfa798d29118c77ed01c5c02fc207cb02 Log: [FIXED JENKINS-22641] FileUtils.readFileToByteArray behavior has changed in the latest version of commons-io. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
SCM/JIRA link daemon commented on JENKINS-22641 Jenkins no longer kills running processes after job fails Code changed in jenkins User: christ66 Path: core/src/main/java/hudson/util/ProcessTree.java http://jenkins-ci.org/commit/jenkins/9ac68b92dcc0bc093c7983cdb0aab72342165df4 Log: Merge branch 'JENKINS-22641' of github.com:christ66/jenkins into JENKINS-22641 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
SCM/JIRA link daemon resolved JENKINS-22641 as Fixed Jenkins no longer kills running processes after job fails Change By: SCM/JIRA link daemon (21/Jul/14 10:39 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19465) OSX Slave hangs while being launched
Erik Purins edited a comment on JENKINS-19465 OSX Slave hangs while being launched You would possibly also need to pass '-secret HASH' on the command line to authenticate, where HASH is the secret token for that node. See JENKINS-18342 for a groovy console script to get your node's secret, which would otherwise never display. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19465) OSX Slave hangs while being launched
Erik Purins commented on JENKINS-19465 OSX Slave hangs while being launched You would possibly also need to pass '-secret HASH' on the command line to authenticate, where HASH is the secret token for that node. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23913) Unable to change user passwords
Luke MacNeil created JENKINS-23913 Unable to change user passwords Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 21/Jul/14 10:15 PM Description: Unable to change user passwords. javax.servlet.ServletException: java.security.ProviderException: doFinal() failed at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) 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.doHandl
[JIRA] [repository-connector] (JENKINS-18040) Unable to install repository-connector-plugin
Dominik Bartholdi resolved JENKINS-18040 as Cannot Reproduce Unable to install repository-connector-plugin Change By: Dominik Bartholdi (21/Jul/14 9:03 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23882) Long build startup
dan tran commented on JENKINS-23882 Long build startup long wait happens after jenkins restart. Looks like p4jenks my need to cache to changelog This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
ryangardner commented on JENKINS-20276 Native Library Error after upgrading ssh-agent from 1.3 to 1.4 Same issue with same stack traces as above. Downgrading from 1.4.1 to 1.3 (found here http://mirrors.jenkins-ci.org/plugins/ssh-agent/1.3/ and uploaded manually to my jenkins) fixed the issue. Can something please be done to fix this so that my ssh-agent wont break if someone accidently upgrades the plugin again? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [liquibase-runner] (JENKINS-23912) Changeset order
Keith Collison created JENKINS-23912 Changeset order Issue Type: Bug Assignee: Keith Collison Components: liquibase-runner Created: 21/Jul/14 7:10 PM Description: Changesets should be listed in the order they were executed. Project: Jenkins Priority: Major Reporter: Keith Collison This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Daniel Beck resolved JENKINS-23193 as Not A Defect UI blocked frequently Based on discussion in the comments, this seems to be a JDK 6/7 bug on Windows systems, not a Jenkins issue. Regarding the memory issue on Tomcat, consider asking on the jenkinsci-users list for help. Change By: Daniel Beck (21/Jul/14 7:06 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-23626) Implement "cancel all" action for the Build Queue (like Hudson version 2.2.1)
Daniel Beck commented on JENKINS-23626 Implement "cancel all" action for the Build Queue (like Hudson version 2.2.1) It takes less than ten minutes to set up an environment for this from scratch, so it cannot be that important if that's not possible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23877) With 1.572, long consoles will not display 'full' console while build is still running, only a portion
Daniel Beck resolved JENKINS-23877 as Duplicate With 1.572, long consoles will not display 'full' console while build is still running, only a portion Alright, seems safe to consider this a duplicate. Change By: Daniel Beck (21/Jul/14 6:50 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/d/optout.
[JIRA] [junit] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
dogfood commented on JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds Integrated in jenkins_main_trunk #3535 [FIXED JENKINS-10234] Removed checkpoint from JUnitResultArchiver. (Revision 90ff9f806fcac1a58f4bd40bfcc4ed5273ff116a) Result = SUCCESS Jesse Glick : 90ff9f806fcac1a58f4bd40bfcc4ed5273ff116a Files : changelog.html core/src/main/java/hudson/tasks/junit/JUnitResultArchiver.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23900) API failing on some jobs
Daniel Beck commented on JENKINS-23900 API failing on some jobs To confirm, replace the relevant culprits element from the build whose API doesn't work with the working one's, and Manage Jenkins » Reload Configuration From Disk. Then try again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-23902) Matrix parent takes executor slot and blocks children
Daniel Beck commented on JENKINS-23902 Matrix parent takes executor slot and blocks children Are you using a plugin that changes how the queue or executor assignment work? (When in doubt, post your entire plugin list) Is this happening regularly or just in special circumstances? Can you reproduce the problem on a pristine Jenkins instance? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-16737) java.lang.RuntimeException: No author in changeset null
Mark Waite commented on JENKINS-16737 java.lang.RuntimeException: No author in changeset null That is an interesting combination of observations. Since the problem is intermittent (at least for me), and does not always happen on the same machine, I'm not sure how I would confidently assure that the updating slave.jar was the solution. I will certainly investigate my machines to confirm they are all running the current slave.jar. When I've seen the problem, I was usually able to resolve it by wiping the workspace. A workspace wipe does not touch the changelog.xml file, so I'm a little suspicious that the changelog.xml is not the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh] (JENKINS-23911) Shell command doesn't run in background
VIA Studio created JENKINS-23911 Shell command doesn't run in background Issue Type: Bug Assignee: Unassigned Components: ssh Created: 21/Jul/14 6:25 PM Description: At some point in the recent releases, it seems Jenkins can no longer runs background shell commands correctly. That is, it waits for the job to finish. I have updated to the latest version of Jenkins and the SSH plugin. I have reproduced the problem with the following job: echo 'Jenkins start:' date sh /tmp/test.sh & echo 'Jenkins end:' date This produces the output: + echo 'Jenkins start:' Jenkins start: + date Mon Jul 21 14:20:40 EDT 2014 + sh /tmp/test.sh + echo 'Jenkins end:' Jenkins end: + date Mon Jul 21 14:20:40 EDT 2014 Script end: Mon Jul 21 14:20:50 EDT 2014 The script contains: sleep 10 echo 'Script end:' date Considering this does not work over SSH shell script or a local shell script, my guess would be in the last few releases something changes with the escaping of an ampersand. Environment: Centos 5.10 Project: Jenkins Priority: Minor Reporter: VIA Studio This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-23860) allow for custom flags to be passed to git
Mark Waite commented on JENKINS-23860 allow for custom flags to be passed to git JENKINS-21248 was not rejected as an enhancement request, it was rejected because the author of the enhancement refused to implement it so that the enhancement would be maintainable in future versions. That is the submitter's right, as part of an open source project, but it is also the maintainer's right to reject changes which make the plugin more difficult to maintain. The git plugin and the git client plugin are installed in over 3 Jenkins installations. We're trying to be very careful that changes accepted into the git client plugin and the git plugin will not break those 3+ installations and will be maintainable and extensible for future versions. The tight coupling which would be created between a "command line arguments" field for every git command in the git client plugin and the UI would make the implementation even more tightly attached to the command line git implementation. The JGit implementation (also in the git client plugin) would be unable to adapt to those command line arguments, as would any future alternate implementations (like a libgit2 based implementation). If you'd like to join the efforts to improve the git-client-plugin, you're encouraged to join the development community and submit "pull requests". I'd love to see your proposals, and particularly in submodules we could use many more unit tests to confirm the plugin is behaving as expected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23910) NullPointerException in JUnit tests calling postCredential
dmatag
created JENKINS-23910
NullPointerException in JUnit tests calling postCredential
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
subversion
Created:
21/Jul/14 6:13 PM
Description:
Hi. This code:
DescriptorExtensionList> desc = SubversionSCM.all();
DescriptorImpl ss = (DescriptorImpl) desc.get(DescriptorImpl.class);
StringWriter log = new StringWriter();
PrintWriter logWriter = new PrintWriter(log);
UserProvidedCredential upc =
new UserProvidedCredential(user, password, null,
request.findAncestorObject(AbstractProject.class));
ss.postCredential(url[0], upc, logWriter);
causes:
Caused by: java.lang.NullPointerException
at hudson.scm.SubversionSCM$DescriptorImpl$1.onSuccess(SubversionSCM.java:2249)
at hudson.scm.UserProvidedCredential$AuthenticationManagerImpl.acknowledgeAuthentication(UserProvidedCredential.java:233)
at org.tmatesoft.svn.core.auth.BasicAuthenticationManager.acknowledgeAuthentication(BasicAuthenticationManager.java:56)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:749)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382)
In:
public void postCredential(String url, final UserProvidedCredential upc, PrintWriter logWriter) throws SVNException, IOException {
SVNRepository repository = null;
try {
// the way it works with SVNKit is that
// 1) svnkit calls AuthenticationManager asking for a credential.
//this is when we can see the 'realm', which identifies the user domain.
// 2) DefaultSVNAuthenticationManager returns the username and password we set below
// 3) if the authentication is successful, svnkit calls back acknowledgeAuthentication
//(so we store the password info here)
repository = SVNRepositoryFactory.create(SVNURL.parseURIDecoded(url));
repository.setTunnelProvider( createDefaultSVNOptions() );
AuthenticationManagerImpl authManager = upc.new AuthenticationManagerImpl(logWriter) {
@Override
protected void onSuccess(String realm, Credential cred) {
LOGGER.info("Persisted "+cred+" for "+realm);
credentials.put(realm, cred);
save();
if (upc.inContextOf!=null)
new PerJobCredentialStore(upc.inContextOf).acknowledgeAuthentication(realm,cred);
}
};
authManager.setAuthenticationForced(true);
repository.setAuthenticationManager(authManager);
repository.testConnection();
authManager.checkIfProtocolCompleted();
} finally {
if (repository != null)
repository.closeSession();
}
}
Because:
credentials is null in "credentials.put(realm, cred);" statement.
version 1.54 works fine
Environment:
Jenkins 1.572 and lower
Project:
Jenkins
Priority:
Major
Reporter:
dmatag
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
[JIRA] [junit] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
SCM/JIRA link daemon resolved JENKINS-10234 as Fixed Junit result archiver getting stuck for a long time in concurrent builds Change By: SCM/JIRA link daemon (21/Jul/14 5:47 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
SCM/JIRA link daemon commented on JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/tasks/junit/JUnitResultArchiver.java http://jenkins-ci.org/commit/jenkins/90ff9f806fcac1a58f4bd40bfcc4ed5273ff116a Log: [FIXED JENKINS-10234] Removed checkpoint from JUnitResultArchiver. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23877) With 1.572, long consoles will not display 'full' console while build is still running, only a portion
Jesper Jensen edited a comment on JENKINS-23877 With 1.572, long consoles will not display 'full' console while build is still running, only a portion I disabled timestamper and the console now follows the build as expected. I currently can't get a job to produce the "full log" option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23877) With 1.572, long consoles will not display 'full' console while build is still running, only a portion
Jesper Jensen commented on JENKINS-23877 With 1.572, long consoles will not display 'full' console while build is still running, only a portion I disabled timestamper and the console now follows the build as expected. I currently can't get a job to produce the "full log" options but is trying. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20941) Stored git credentials not used when submodule is updated
Andreas N
commented on JENKINS-20941
Stored git credentials not used when submodule is updated
Still a problem with Git Client plugin in version 1.9.2. Had to downgrade to 1.4.3 to make "git submodule update --init --recursive" work again.
This is on a Windows 7 Jenkins slave using Git from Mingw/MSys and HTTPS as transport protocol. Here's some console output of a build failing to update submodules:
18:04:55 Started by user daff
18:04:55 Building remotely on Windows 7 Build Server in workspace C:\Jenkins\workspace\libfoobar-windows-unstable
18:04:55 > git rev-parse --is-inside-work-tree
18:04:55 Fetching changes from the remote Git repository
18:04:55 > git config remote.origin.url https://git.example.com/quux-libfoobar.git
18:04:55 Fetching upstream changes from https://git.example.com/quux-libfoobar.git
18:04:55 > git --version
18:04:55 using .gitcredentials to set credentials
18:04:55 > git config --local credential.helper store --file=\"C:\Windows\TEMP\git5399135379421883157.credentials\"
18:04:55 > git fetch --tags --progress https://git.example.com/quux-libfoobar.git +refs/heads/*:refs/remotes/origin/*
18:04:56 > git config --local --remove-section credential
18:04:56 > git rev-parse "origin/master^{commit}"
18:04:56 Checking out Revision 4297be25a4ab6367f3061d4a6dbd9752a203ecb5 (origin/master)
18:04:56 > git config core.sparsecheckout
18:04:56 > git checkout -f 4297be25a4ab6367f3061d4a6dbd9752a203ecb5
18:04:56 > git rev-list 4297be25a4ab6367f3061d4a6dbd9752a203ecb5
18:04:56 > git remote
18:04:56 > git submodule init
18:04:57 > git submodule sync
18:04:58 > git config --get remote.origin.url
18:04:58 > git submodule update --init --recursive
18:05:00 FATAL: Command "git submodule update --init --recursive" returned status code 1:
18:05:00 stdout:
18:05:00 stderr: fatal: Authentication failed for 'https://git.example.com/quux-libc.git/'
18:05:00 Unable to fetch in submodule path 'quux-libc'
18:05:00
18:05:00 hudson.plugins.git.GitException: Command "git submodule update --init --recursive" returned status code 1:
18:05:00 stdout:
18:05:00 stderr: fatal: Authentication failed for 'https://git.example.com/quux-libc.git/'
18:05:00 Unable to fetch in submodule path 'quux-libc'
18:05:00
18:05:00 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1406)
18:05:00 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:87)
18:05:00 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$6.execute(CliGitAPIImpl.java:741)
18:05:00 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
18:05:00 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
18:05:00 at hudson.remoting.UserRequest.perform(UserRequest.java:118)
18:05:00 at hudson.remoting.UserRequest.perform(UserRequest.java:48)
18:05:00 at hudson.remoting.Request$2.run(Request.java:328)
18:05:00 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
18:05:00 at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
18:05:00 at java.util.concurrent.FutureTask.run(Unknown Source)
18:05:00 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
18:05:00 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
18:05:00 at hudson.remoting.Engine$1$1.run(Engine.java:63)
18:05:00 at java.lang.Thread.run(Unknown Source)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-23836) NumberFormatException when clicking search button on Global Build Search
Len Isac commented on JENKINS-23836 NumberFormatException when clicking search button on Global Build Search Same issue occurring with global-build-stats version 1.3 in Jenkins ver. 1.554 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [liquibase-runner] (JENKINS-23909) Allow setting of liquibase properties file
Keith Collison started work on JENKINS-23909 Allow setting of liquibase properties file Change By: Keith Collison (21/Jul/14 4:39 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [liquibase-runner] (JENKINS-23909) Allow setting of liquibase properties file
Keith Collison created JENKINS-23909 Allow setting of liquibase properties file Issue Type: New Feature Assignee: Keith Collison Components: liquibase-runner Created: 21/Jul/14 4:38 PM Description: Should be simple text field. The only tricky part is parsing it for relevant fields (the Liquibase API doesn't provide a great way to re-use its routine) Project: Jenkins Priority: Major Reporter: Keith Collison This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-23902) Matrix parent takes executor slot and blocks children
James Howe commented on JENKINS-23902 Matrix parent takes executor slot and blocks children No, but it should be defaulting to "true". Unless that's what changed and the wiki page is out of date? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [liquibase-runner] (JENKINS-23908) Provide way to execute external liquibase
Keith Collison created JENKINS-23908 Provide way to execute external liquibase Issue Type: New Feature Assignee: Keith Collison Components: liquibase-runner Created: 21/Jul/14 4:30 PM Description: In addition to running "embedded" liquibase (inside Jenkin's JVM), plugin can allow user to execute external liquibase. Similar to the Groovy plugin's way of distinguishing "System" execution. I expect some features that are possible in running inside Jenkins's JVM won't be possible when using this option. Project: Jenkins Priority: Major Reporter: Keith Collison This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [liquibase-runner] (JENKINS-23908) Provide way to execute external liquibase
Keith Collison started work on JENKINS-23908 Provide way to execute external liquibase Change By: Keith Collison (21/Jul/14 4:30 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23907) Jenkins CLI
Garron Kramer created JENKINS-23907 Jenkins CLI Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cli Created: 21/Jul/14 4:26 PM Description: root@jenkins-testbed-01:/var/lib/jenkins/jobs# java -jar /var/cache/jenkins/war/WEB-INF/jenkins-cli.jar -i /root/.ssh/jenkins.autocfg.key -s http://localhost:8080/ list-jobs Exception in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:227) at hudson.cli.Connection.readBoolean(Connection.java:93) at hudson.cli.CLI.authenticate(CLI.java:553) at hudson.cli.CLI._main(CLI.java:464) at hudson.cli.CLI.main(CLI.java:382) This worked on 1.572. No longer works on 1.573. Environment: Debian Wheezy x86_64; Project: Jenkins Priority: Major Reporter: Garron Kramer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23884) Git/GitHub Enterprise (GHE) SCM Polling creates builds with "No Changes" when there are two similarly named branches present
M Chon commented on JENKINS-23884 Git/GitHub Enterprise (GHE) SCM Polling creates builds with "No Changes" when there are two similarly named branches present Hi, Mark, Yes, I can test out the 1.10.0 plugin. However, after reading your explanation, I still do not understand why Jenkins triggered build the festivus-dev branch when changes were checked into master, not either festivus-dev branch. Also, builds were triggered even when there was a typo in the branch name. It seems like the existence of the 2nd festivus-dev branch caused Jenkins to completely ignore the branch specifier and trigger all builds regardless of the branch they were configured with. Even if both "jdoe/blah/festivus-dev" and "festivus-dev" , a change checked into "master" should not have triggered a build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
Jesse Glick updated JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds Change By: Jesse Glick (21/Jul/14 4:22 PM) Labels: checkpoint concurrent This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [managed-scripts] (JENKINS-22918) Add option to output executed commands to job console
Jonas Kuepper commented on JENKINS-22918 Add option to output executed commands to job console Hi Dominik, thanks for your answer. so i guess this is not possible, without a major overhaul? somthing like /bin/bash -x managed-scripname.sh is not possible? Thanks anyway Jonas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
Jesse Glick started work on JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds Change By: Jesse Glick (21/Jul/14 4:18 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
Jesse Glick updated JENKINS-10234 Junit result archiver getting stuck for a long time in concurrent builds Change By: Jesse Glick (21/Jul/14 4:18 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
Jesse Glick assigned JENKINS-10234 to Jesse Glick Junit result archiver getting stuck for a long time in concurrent builds Change By: Jesse Glick (21/Jul/14 4:18 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance] (JENKINS-23841) NPE when viewing Parameterized Build Report on Inheritance Job Type
Justin Wagner edited a comment on JENKINS-23841 NPE when viewing Parameterized Build Report on Inheritance Job Type I opened another Issue to track the fact that the inheritance plugin stores inherited parameters in a non-standard way which makes this report non-functional for those job types. JENKINS-23906 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance] (JENKINS-23841) NPE when viewing Parameterized Build Report on Inheritance Job Type
Justin Wagner commented on JENKINS-23841 NPE when viewing Parameterized Build Report on Inheritance Job Type I opened another Issue to track the fact that the inheritance plugin stores inherited parameters in a non-standard way which makes this report non-functional for those job types. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance] (JENKINS-23906) Parameterized Build Report doesn't show any parameters for inheritable job
Justin Wagner created JENKINS-23906 Parameterized Build Report doesn't show any parameters for inheritable job Issue Type: Bug Assignee: Unassigned Components: project-inheritance, simple-parameterized-builds-report Created: 21/Jul/14 3:52 PM Description: When trying to view the parameter report for a job which inherited parameters from it's parent job, the parameterized build report shows that there weren't any parameters for each build. I'm assuming this has to do with the face that the parameters are "inherited" rather than being native to the job. Is there any way we can allow these parameters to show up in this report? Environment: Jenkins Version 1.572 Project Inheritance Plugin Version 1.5.0 Simple Parameterized Build Report Plugin Version 1.3 Project: Jenkins Priority: Major Reporter: Justin Wagner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance] (JENKINS-23841) NPE when viewing Parameterized Build Report on Inheritance Job Type
Justin Wagner resolved JENKINS-23841 as Fixed NPE when viewing Parameterized Build Report on Inheritance Job Type Your recent changes avoid the NPE, which is specifically what I mentioned with this issue, so I'll mark it as resolved. However there must be something fundamentally different in how inheritable jobs get their inheritable parameters than how normal jobs get them. I say this because now the Parameterized Build Report shows up, but it just says that no builds had any parameters. I'm afraid the owners of the Inheritable job plugin aren't very responsive. From the looks of things it was built for an internal need at Intel which it serves well, however there is no driver for them to support it for the general community. I'm just assuming that based on the YouTube video they published for the plugin. Thanks for your quick response! Change By: Justin Wagner (21/Jul/14 3:48 PM) Status: Open Resolved Assignee: Nalin Makar Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-23905) Jenkins Slaves launched with the incorrect environment variables
Monty Byrnes created JENKINS-23905 Jenkins Slaves launched with the incorrect environment variables Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 21/Jul/14 3:42 PM Description: Intermittent error where slaves launch with the incorrect environment variables. Tends to happen when there is a large demand for slaves to launch. Environment variables are set on Jenkins as required but do not seem to be injected to slaves at times causing builds to fail due to incorrect environment. Example: LD_LIBRARY_PATH set on master : /proj/litpadm200/tools/py-3pps-2.0/usr/lib64 Failed Job environment: LD_LIBRARY_PATH : /app/openmotif/2.3.1/lib Environment: 1.89 of plugin used in Jenkins version 1.537 Project: Jenkins Priority: Critical Reporter: Monty Byrnes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core] (JENKINS-23904) SlowRequestCheck= kills UI performance and pegs CPU at 100%
teilo
created JENKINS-23904
SlowRequestCheck= kills UI performance and pegs CPU at 100%
Issue Type:
Bug
Assignee:
Unassigned
Components:
support-core
Created:
21/Jul/14 3:36 PM
Description:
The slow request checker pegs the JDK VM_Thread at 100% cpu as it is in a constant loop grabing thread dumps.
Getting full thread dumps on a largish system (18 slaves, 5 polls, several web requests) every 3 seconds is not a great idea.
There is no way to tune this and the only way to fix this is to uninstall the support core plugin and restart jenkins.
depending on the JDK you may be able to terminate the Slow request thread with the following
import jenkins.util.Timer
import java.util.concurrent.*
def timer = Timer.get()
def tasks = timer.queue.toArray()
def field = FutureTask.class.getDeclaredField("callable")
field.setAccessible(true)
for (task in tasks) {
if (field.get(task).task.class == com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.class) {
println(task.toString() + " <-== SlowRequestChecker")
println(task.cancel(true))
println(timer.queue.remove())
}
}
Once the requestChecker is removed the UI response is near instantanious.
Environment:
2 * E5-2690 (16 real cores, 32 inc hyperthreading)
112 MB RAM
-Xmx24g -Xms16g
Project:
Jenkins
Priority:
Major
Reporter:
teilo
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Andreas Horst commented on JENKINS-10191 JDK selection is hidden even when a JDK is configured As a side note: I can no longer reproduce the Sonar issue since apparently the value of the element in the job configuration differs between a fresh Jenkins installation with only one JDK installation and a Jenkins which had two JDK installations of which one was removed later on. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin
Morten Engelhardt Olsen edited a comment on JENKINS-23901 Job SCM changes are not valid after running plugin Sure. Started by upstream project "as-sdk__verify__master" build number 165 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on # in workspace /home/buildmaster/mcu-production-jenkins/workspace/as-sdk__push__master Deleting project workspace... done Wiping out workspace first. Cloning the remote Git repository Cloning repository ats/atmelstudio_sdk.git > git init /home/buildmaster/mcu-production-jenkins/workspace/as-sdk__push__master Fetching upstream changes from ats/atmelstudio_sdk.git > git --version using GIT_SSH to set credentials > git fetch --tags --progress ats/atmelstudio_sdk.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url ats/atmelstudio_sdk.git > git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url ats/atmelstudio_sdk.git Fetching upstream changes from ats/atmelstudio_sdk.git using GIT_SSH to set credentials > git fetch --tags --progress ats/atmelstudio_sdk.git +refs/heads/*:refs/remotes/origin/* Checking out Revision 5c84374470a94fb05747dcf4b0b03320c032b244 (origin/ready_fix_toolsdirproperty) > git config core.sparsecheckout > git checkout -f 5c84374470a94fb05747dcf4b0b03320c032b244 > git rev-list 3131160c5ae5d5ff738b006a775e5a99b96d0d21 2.0 Checking out integration target branch master and pulling latest changes [as-sdk__push__master] $ git checkout master [as-sdk__push__master] $ git pull origin master Preparing to merge changes in commit 5c84374470a94fb05747dcf4b0b03320c032b244 to integration branch master [as-sdk__push__master] $ git merge -m "Integrated origin/ready_fix_toolsdirproperty" 5c84374470a94fb05747dcf4b0b03320c032b244 --no-ff Updating TSD-3797 Performing pre-verified post build steps [PREINT-SCM] Commiting changes [as-sdk__push__master] $ git push origin master [PREINT-SCM] Deleting development branch [as-sdk__push__master] $ git push origin :ready_fix_toolsdirproperty Triggering a new build of as-sdk__publish__master #11 Collecting metadata... Metadata collection done. Notifying upstream projects of job completion Finished: SUCCESS Also added to trello card with internal link to build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Andreas Horst commented on JENKINS-10191 JDK selection is hidden even when a JDK is configured These are excerpts from some build console outputs. With config.no.jdk.xml: Started by user Andreas Horst Building remotely on lab76 (maven java) in workspace /home/jenkins/workspace/Vire Updating https://sselab.de/lab9/private/svn/vire/trunk/vire at revision '2014-07-21T16:52:50.204 +0200' At revision 156 no change for https://sselab.de/lab9/private/svn/vire/trunk/vire since the previous build Parsing POMs maven31-agent.jar already up to date maven31-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [Vire] $ java -XX:MaxPermSize=512m -Djava.awt.headless=true -cp /home/jenkins/maven31-agent.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/boot/plexus-classworlds-2.5.1.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/conf/logging jenkins.maven3.agent.Maven31Main /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1 /home/jenkins/slave.jar /home/jenkins/maven31-interceptor.jar /home/jenkins/maven3-interceptor-commons.jar 60423 <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f /home/jenkins/workspace/Vire/pom.xml -s /home/jenkins/.m2/settings.vire.xml clean install -e -X Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T18:37:52+01:00) Maven home: /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1 Java version: 1.7.0_55, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.13.0-32-generic", arch: "amd64", family: "unix" [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/conf/settings.xml [DEBUG] Reading user settings from /home/jenkins/.m2/settings.vire.xml [INFO] Scanning for projects... With config.with.jdk.xml: Started by user Andreas Horst Building remotely on lab76 (maven java) in workspace /home/jenkins/workspace/Vire Updating https://sselab.de/lab9/private/svn/vire/trunk/vire at revision '2014-07-21T17:14:44.362 +0200' At revision 156 no change for https://sselab.de/lab9/private/svn/vire/trunk/vire since the previous build Parsing POMs maven31-agent.jar already up to date maven31-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [Vire] $ /home/jenkins/tools/hudson.model.JDK/Java_SE_Development_Kit_7u65/bin/java -XX:MaxPermSize=512m -Djava.awt.headless=true -cp /home/jenkins/maven31-agent.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/boot/plexus-classworlds-2.5.1.jar:/home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/conf/logging jenkins.maven3.agent.Maven31Main /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1 /home/jenkins/slave.jar /home/jenkins/maven31-interceptor.jar /home/jenkins/maven3-interceptor-commons.jar 43246 <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f /home/jenkins/workspace/Vire/pom.xml -s /home/jenkins/.m2/settings.vire.xml clean install -e -X Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T18:37:52+01:00) Maven home: /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1 Java version: 1.7.0_65, vendor: Oracle Corporation Java home: /home/jenkins/tools/hudson.model.JDK/Java_SE_Development_Kit_7u65/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.13.0-32-generic", arch: "amd64", family: "unix" [INFO] Error stacktraces are turned on. [DEBUG] Reading global settings from /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.2.1/conf/settings.xml [DEBUG] Reading user settings from /home/jenkins/.m2/settings.vire.xml [INFO] Scanning for projects... As you can see, the first build is IMHO run with the wrong JDK since the default JDK there is the OS JDK and NOT the single JDK known to Jenkins (which was 1.7.0_u65). Only after selecting the right JDK in the job configuration (which required adding a second JDK installation) the build was executed with the right JDK (second console output). This message is automatically generated by JIRA. If you think it was sent
[JIRA] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin
Morten Engelhardt Olsen commented on JENKINS-23901 Job SCM changes are not valid after running plugin Sure. Started by upstream project "as-sdk__verify__master" build number 165 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on norbuild01vm.corp.atmel.com (Linux amd64-RedHatEnterpriseServer RedHatEnterpriseServer 6.5 RedHat RHEL6 amd64-RedHatEnterpriseServer-6.5 RedHatEnterpriseServer-6.5 amd64) in workspace /home/buildmaster/mcu-production-jenkins/workspace/as-sdk__push__master Deleting project workspace... done Wiping out workspace first. Cloning the remote Git repository Cloning repository ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git > git init /home/buildmaster/mcu-production-jenkins/workspace/as-sdk__push__master Fetching upstream changes from ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git > git --version using GIT_SSH to set credentials buildmaster (ssh-key) > git fetch --tags --progress ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git > git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git Fetching upstream changes from ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git using GIT_SSH to set credentials buildmaster (ssh-key) > git fetch --tags --progress ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git +refs/heads/*:refs/remotes/origin/* Checking out Revision 5c84374470a94fb05747dcf4b0b03320c032b244 (origin/ready_fix_toolsdirproperty) > git config core.sparsecheckout > git checkout -f 5c84374470a94fb05747dcf4b0b03320c032b244 > git rev-list 3131160c5ae5d5ff738b006a775e5a99b96d0d21 2.0 Checking out integration target branch master and pulling latest changes [as-sdk__push__master] $ git checkout master [as-sdk__push__master] $ git pull origin master Preparing to merge changes in commit 5c84374470a94fb05747dcf4b0b03320c032b244 to integration branch master [as-sdk__push__master] $ git merge -m "Integrated origin/ready_fix_toolsdirproperty" 5c84374470a94fb05747dcf4b0b03320c032b244 --no-ff Updating TSD-3797 Performing pre-verified post build steps [PREINT-SCM] Commiting changes [as-sdk__push__master] $ git push origin master [PREINT-SCM] Deleting development branch [as-sdk__push__master] $ git push origin :ready_fix_toolsdirproperty Triggering a new build of as-sdk__publish__master #11 Collecting metadata... Metadata collection done. Notifying upstream projects of job completion Finished: SUCCESS Also added to trello card with internal link to build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin
Morten Engelhardt Olsen edited a comment on JENKINS-23901 Job SCM changes are not valid after running plugin Sure. Started by upstream project "as-sdk__verify__master" build number 165 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on norbuild01vm.corp.atmel.com (Linux amd64-RedHatEnterpriseServer RedHatEnterpriseServer 6.5 RedHat RHEL6 amd64-RedHatEnterpriseServer-6.5 RedHatEnterpriseServer-6.5 amd64) in workspace /home/buildmaster/mcu-production-jenkins/workspace/as-sdk__push__master Deleting project workspace... done Wiping out workspace first. Cloning the remote Git repository Cloning repository ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git > git init /home/buildmaster/mcu-production-jenkins/workspace/as-sdk__push__master Fetching upstream changes from ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git > git --version using GIT_SSH to set credentials buildmaster (ssh-key) > git fetch --tags --progress ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git > git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git Fetching upstream changes from ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git using GIT_SSH to set credentials buildmaster (ssh-key) > git fetch --tags --progress ssh://g...@stash.corp.atmel.com:7999/ats/atmelstudio_sdk.git +refs/heads/*:refs/remotes/origin/* Checking out Revision 5c84374470a94fb05747dcf4b0b03320c032b244 (origin/ready_fix_toolsdirproperty) > git config core.sparsecheckout > git checkout -f 5c84374470a94fb05747dcf4b0b03320c032b244 > git rev-list 3131160c5ae5d5ff738b006a775e5a99b96d0d21 2.0 Checking out integration target branch master and pulling latest changes [as-sdk__push__master] $ git checkout master [as-sdk__push__master] $ git pull origin master Preparing to merge changes in commit 5c84374470a94fb05747dcf4b0b03320c032b244 to integration branch master [as-sdk__push__master] $ git merge -m "Integrated origin/ready_fix_toolsdirproperty" 5c84374470a94fb05747dcf4b0b03320c032b244 --no-ff Updating TSD-3797 Performing pre-verified post build steps [PREINT-SCM] Commiting changes [as-sdk__push__master] $ git push origin master [PREINT-SCM] Deleting development branch [as-sdk__push__master] $ git push origin :ready_fix_toolsdirproperty Triggering a new build of as-sdk__publish__master #11 Collecting metadata... Metadata collection done. Notifying upstream projects of job completion Finished: SUCCESS Also added to trello card with internal link to build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Andreas Horst updated JENKINS-10191 JDK selection is hidden even when a JDK is configured config.no.jdk.xml is a job configuration where only one JDK installation is known to Jenkins (hence no actual value). config.with.jdk.xml is a configuration of the same job but this time an actual JDK (one of two JDKs known to Jenkins) is selected. Change By: Andreas Horst (21/Jul/14 3:18 PM) Attachment: config.no.jdk.xml Attachment: config.with.jdk.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-23860) allow for custom flags to be passed to git
Aaron Simmons commented on JENKINS-23860 allow for custom flags to be passed to git Providing a "command line arguments" field for every command would work. Otherwise the plugin is going to fall further and further behind git's features. If this ticket is wontfix, and tickets like JENKINS-21248 are rejected, what are end users supposed 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/d/optout.
[JIRA] [core] (JENKINS-23903) NullPointeException in hudson.maven.Maven3Builder$MavenExecutionListener.sessionEnded
Fernando Miguelez created JENKINS-23903 NullPointeException in hudson.maven.Maven3Builder$MavenExecutionListener.sessionEnded Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 21/Jul/14 3:13 PM Description: [INFO] Installing /home/appusr/.jenkins/jobs/_BUILD_ARTIFACT/workspace/icm.demo.core.app/target/icm.demo.core.app-0.7-SNAPSHOT/lib/res.jar to /home/appusr/.m2/repository/com/telvent/oip/icm.demo.core.app/0.7-SNAPSHOT/icm.demo.core.app-0.7-SNAPSHOT.jar Notifying upstream projects of job completion Join notifier requires a CauseAction [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 34.069s [INFO] Finished at: Mon Jul 21 16:51:28 CEST 2014 [INFO] Final Memory: 44M/64M [INFO] ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com [ERROR] Internal error: java.lang.NullPointerException -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.NullPointerException at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:117) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:178) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at hudson.maven.Maven3Builder.call(Maven3Builder.java:134) at hudson.maven.Maven3Builder.call(Maven3Builder.java:69) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.NullPointerException at hudson.maven.Maven3Builder$MavenExecutionListener.sessionEnded(Maven3Builder.java:467) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:64) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:170) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) ... 23 more [ERROR] java.lang.NullPointerException at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:100) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:849) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) at hudson.model.Run.execute(Run.java:1732) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) project=hudson.maven.
[JIRA] [jobgenerator] (JENKINS-23390) Custom workspace setting disappears randomly
Peter Mate commented on JENKINS-23390 Custom workspace setting disappears randomly We also have the same problem with Job Generator version 1.22 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23900) API failing on some jobs
Filip Ryborz edited a comment on JENKINS-23900 API failing on some jobs I have added build xml files. I think the problem is with: some_user_name When API works this line looks like: It looks like it happens for builds that have some changes. We poll Synergy and use Synergy plugin to track changes in SW. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23810) Create a based alternative tot he tag
Tom FENNELLY commented on JENKINS-23810 Create a based alternative tot he tag Dev list discussion: https://groups.google.com/forum/?hl=en#!topic/jenkinsci-dev/GOiQdvctBB0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23900) API failing on some jobs
Filip Ryborz edited a comment on JENKINS-23900 API failing on some jobs I have added build xml files. I think the problem is with: some_user_name When API works this line looks like: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23900) API failing on some jobs
Filip Ryborz edited a comment on JENKINS-23900 API failing on some jobs I have added build xml files. I think the problem is with: some_user_name When API works this line looks like: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23842) Wrap icon images in an tag
Tom FENNELLY edited a comment on JENKINS-23842 Wrap icon images in an tag https://github.com/tfennelly/jenkins/compare/JENKINS-23842 This branch also contains a "shim" plugin that can be used by plugins that want to get the benefits of the tag, while remaining backward compatible with older versions of Jenkins. Here's the credentials plugin modified to use the icon shim plugin: https://github.com/jenkinsci/credentials-plugin/compare/icon-tag-shim-test This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Andreas Horst commented on JENKINS-10191 JDK selection is hidden even when a JDK is configured And ambiguity strikes again: 1.7.0_u55 was the OS wide JDK on the slave node while 1.7.0_u65 was the Jenkins "system-wide" configured JDK. Since the job did not specify anything related to a JDK (you cannot select a JDK in a Maven job unless Jenkins has more than one JDK installation) the job used the OS JDK (which IMHO is wrong). It should never fall back to the environment since nobody can guarantee even the existence of a JDK for arbitrary environments. I'll come back with the configuration files in a minute (I'll have to remove the second JDK installation in order to reproduce the original 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/d/optout.
[JIRA] [core] (JENKINS-23900) API failing on some jobs
Filip Ryborz commented on JENKINS-23900 API failing on some jobs I have added buld xml files. I think the problem is with: some_user_name When API works this line looks like: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23900) API failing on some jobs
Filip Ryborz updated JENKINS-23900 API failing on some jobs Change By: Filip Ryborz (21/Jul/14 2:52 PM) Attachment: Jenkins.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin
Lars Kruse commented on JENKINS-23901 Job SCM changes are not valid after running plugin Hi Morten, could you attach the log from build #119, either here or to the Trello card This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin
Lars Kruse updated JENKINS-23901 Job SCM changes are not valid after running plugin Card on JOSRA Pretested Integration roadmap board This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-755) Default JDK meaning in project options is confusing.
Daniel Beck commented on JENKINS-755 Default JDK meaning in project options is confusing. "(System)" or "(System Default)" seem to be appropriate alternative names for the '(Default)' JDK. While not resolving related issues, at least that would be less ambiguous. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin
Lars Kruse updated JENKINS-23901 Job SCM changes are not valid after running plugin Change By: Lars Kruse (21/Jul/14 2:41 PM) Assignee: Alexander Uldall This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Daniel Beck commented on JENKINS-10191 JDK selection is hidden even when a JDK is configured Andreas: Please provide relevant config.xml from the affected jobs at the relevant points in time (as that will contain the JDK configuration even if hidden from UI). Your second job's issue does not appear to be possible if one JDK is configured system-wide. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-23902) Matrix parent takes executor slot and blocks children
Daniel Beck commented on JENKINS-23902 Matrix parent takes executor slot and blocks children Did you set hudson.model.Hudson.flyweightSupport (see https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties )? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23900) API failing on some jobs
Daniel Beck commented on JENKINS-23900 API failing on some jobs Could you provide successful and failing build.xml files? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23193) UI blocked frequently
Saulo Alvarado Mateos commented on JENKINS-23193 UI blocked frequently Two weeks with Tomcat and without problems detected. The only thing we see is memory usage. Although the garbage collector runs and frees up memory very often, the minimum memory usage increases every day and never come down from that value. There are still 200 MB to peak, and we can further increase the maximum memory available. But are we in front of possible memory leaks? Is it necessary to periodically restart Jenkins to restart the minimum use of memory? However I understand that this is a different problem. Currently we use Tomcat 8 running on JDK 1.7. Max memory = 764 MB, Max PermGen 256 MB. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-23902) Matrix parent takes executor slot and blocks children
James Howe created JENKINS-23902 Matrix parent takes executor slot and blocks children Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project Created: 21/Jul/14 1:36 PM Description: Not sure when the behaviour changed, but the parent job used to take an extra "free" slot. Now it's taking an actual slot, which can end up being the only slot that one of its children can use, leading to an effective deadlock. Environment: Jenkins 1.573, matrix-project 1.2 Project: Jenkins Priority: Critical Reporter: James Howe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-16737) java.lang.RuntimeException: No author in changeset null
Heiko Briebrecher commented on JENKINS-16737 java.lang.RuntimeException: No author in changeset null I could sidestep the error by updating the slave.jar on our jenkins slave to the latest version. AFAIK changesets are determined on the slave and then sent to the jenkins master. Occasionally they got truncated at an arbitrary position. The truncated changelog entries are stored in $JENKINS_HOME/jobs/XXX/builds/NNN/changelog.xml and need to be deleted/corrected to prevent further RuntimeExceptions while building or browsing the job history. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23889) Remove Eclipse generate files from source tree
Paul Allen resolved JENKINS-23889 as Fixed Remove Eclipse generate files from source tree Removed the .classpath and .project files from Workshop (never made it into GitHub) Change By: Paul Allen (21/Jul/14 1:25 PM) Status: Open Resolved Assignee: Paul Allen Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-755) Default JDK meaning in project options is confusing.
Andreas Horst commented on JENKINS-755 Default JDK meaning in project options is confusing. I highly vote for fixing this one way or another since - as everybody in here already stated - the ambiguity can cause quite some trouble (see my comment on #10191. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23760) Workspace Name Format cannot contain spaces
Paul Allen resolved JENKINS-23760 as Fixed Workspace Name Format cannot contain spaces Fixed in version 1.0.5 P4 client replaces a space with an underscore (bug in p4java). Change By: Paul Allen (21/Jul/14 1:17 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12550) System default JDK wrongly used if JDK is created first
Andreas Horst commented on JENKINS-12550 System default JDK wrongly used if JDK is created first Please note my comment on #10191. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23760) Workspace Name Format cannot contain spaces
Paul Allen assigned JENKINS-23760 to Paul Allen Workspace Name Format cannot contain spaces Change By: Paul Allen (21/Jul/14 1:14 PM) Assignee: Paul Allen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10191) JDK selection is hidden even when a JDK is configured
Andreas Horst
commented on JENKINS-10191
JDK selection is hidden even when a JDK is configured
Looks like I'm reviving this pretty old one but IMHO it's definitely an important one.
I agree with the reporter because I ran into several issues caused by the "default JDK" assumption:
I created a fresh Jenkins (1.573) installation and configured the current JDK 7 (Java SE DK 1.7.0_u65) in Jenkins. Since one cannot select the JDK to use in (e.g.) Maven jobs I was assuming Jenkins would take the 1.7.0_u65 JDK. I also provided a fresh SSH slave node and ran across the following issues. If Java is not installed on the node, Jenkins copies a pretty old 1.6.0_u45 JDK for execution on the node and also correctly provides the specified 1.7.0_65 JDK for the job's builds. Unfortunately the Sonar post build step which was configured to use the same JDK as the job ("Inherit From Job") tried to use plain "java" which was not present on the slave node machine; the job failed. Selecting the 1.7.0_u65 JDK in the Sonar step configuration fixed this.
In a second scenario I installed a JDK on the SSH slave node such that Jenkins would not use the way too old 1.6.0_u45 JDK. Again the job was "configured" (since only one JDK was configured for Jenkins one cannot select which one to use) to use the "default JDK". Unfortunately the "default JDK" on the slave node was 1.7.0_u55 and NOT the 1.7.0_u65 JDK as specified in Jenkins main configuration. And ON TOP OF that, one has to define a second JDK just to be able to configure the job to use the right one (which it does eventually). Also with an actual selection the Sonar step configuration using "Inherit From Job" does what it is supposed to do.
Long story short; TL;DR:
The "default JDK" assumption is error prone and highly misleading. On a side note: I'd also like to see Jenkins use a more up-to-date JRE than 1.6 on SSH slave nodes if they don't have Java installed.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin
Morten Engelhardt Olsen created JENKINS-23901 Job SCM changes are not valid after running plugin Issue Type: Bug Affects Versions: current Assignee: Alexander Uldall Attachments: jenkins_jira_post.PNG, jenkins_job_trigger.PNG, jira_post_stash.PNG Components: pretested-integration Created: 21/Jul/14 1:06 PM Description: The SCM Changes list is invalidated after the pretest plugin has merged a ready-branch to master. This makes the list for the job and the jira notification contain invalid commit hash links. I guess this is bacause of the squash commit that is used, making the commit on master different than the on that triggered jenkins, in tandem with the deletion of the branch causing stash to not find the commit in the repository. This makes the information presented misleading for users. I would probably propose to either "change" the changes links provided by the git scm plugin to the new, squashed commit, keeping the old list in a separate pane if possible. See attached images for how it looks in our jenkins/jira/stash setup. Project: Jenkins Priority: Major Reporter: Morten Engelhardt Olsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23900) API failing on some jobs
Filip Ryborz created JENKINS-23900 API failing on some jobs Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 21/Jul/14 1:02 PM Description: When I try to use API for some jobs I get an exception. For example: job/NAME/1/api/xml - OK job/NAME/2/api/xml - OK job/NAME/2/api/json - OK job/NAME/3/api/json - FAIL job/NAME/3/api/xml - FAIL Stack trace: javax.servlet.ServletException: java.lang.IllegalArgumentException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) 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) a
[JIRA] [rebuild] (JENKINS-15882) rebuild plugin should not store non-stored password parameter
Walter Kacynski closed JENKINS-15882 as Fixed rebuild plugin should not store non-stored password parameter Change By: Walter Kacynski (21/Jul/14 12:53 PM) 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/d/optout.
[JIRA] [repository-connector] (JENKINS-18040) Unable to install repository-connector-plugin
Anders Båtstrand commented on JENKINS-18040 Unable to install repository-connector-plugin I am no longer on this case, and others also operate our jenkins machine, but I found the following. The issue is gone (the plugin is installed). Other plugins work. The token-macro-plugin is installed. I do not remember the state of the jenkins installation at the time of reporting this bug. I suggest the bug 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/d/optout.
[JIRA] [rebuild] (JENKINS-15882) rebuild plugin should not store non-stored password parameter
Walter Kacynski commented on JENKINS-15882 rebuild plugin should not store non-stored password parameter I've tested this and it works great. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22685) Jenkins cannot restart Windows service
Paul Adams commented on JENKINS-22685 Jenkins cannot restart Windows service I have a similar problem with the 1.554.3 LTS release using the Windows Service, whereby Jenkins does not restart. It just sits there with the message "Please wait while Jenkins is restarting...". I have to manually restart using the Windows Services Manager. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
