[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-23914) Invalid null/ element added to triggers/ in job causing NPE on job load
Craig Ringer commented on JENKINS-23914 Invalid null/ element added to triggers/ 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. - scm class="hudson.plugins.git.GitSCM" plugin="git@2.2.2" -configVersion2/configVersion - - /scm + scm class="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-23914) Invalid null/ element added to triggers/ in job causing NPE on job load
Craig Ringer commented on JENKINS-23914 Invalid null/ element added to triggers/ 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] [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: f:entry input type="file" size="40" jsonAware="yes"/ /f:entry 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
[JIRA] [promoted-builds] (JENKINS-22094) Promoted builds not picking up injected env settings as of 2.17 (2.15 is ok)
podskalsky commented on JENKINS-22094 Promoted builds not picking up injected env settings as of 2.17 (2.15 is ok) I would also need to have the defined environment variables from the https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin running he in the promoted additional build actions (shell). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23917) Protocol deadlock while uploading artifacts from ppc64
Craig Ringer updated JENKINS-23917 Protocol deadlock while uploading artifacts from ppc64 Change By: Craig Ringer (22/Jul/14 7:18 AM) Summary: Protocoldeadlockwhileuploadingartifacts fromppc64 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23917) Protocol deadlock while uploading artifacts
Craig Ringer created JENKINS-23917 Protocol deadlock while uploading artifacts Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jul/14 7:17 AM Description: I've encountered an ssh2 channel protocol issue when a ppc64 slave communicates with an x64 master. Most operations, like sending build logs, work fine. When the time comes to upload artifacts at the end of the build the build stalls indefinitely at: Archiving artifacts If I get stack dumps of slave and master using jstack, I see the master waiting to read from the slave: "Channel reader thread: Fedora16-ppc64-Power7-osuosl-karman" prio=10 tid=0x038c2800 nid=0x6de7 in Object.wait() [0x7f825ef8b000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on 0xbf5802e0 (a com.trilead.ssh2.channel.Channel) at java.lang.Object.wait(Object.java:502) at com.trilead.ssh2.channel.FifoBuffer.read(FifoBuffer.java:212) - locked 0xbf5802e0 (a com.trilead.ssh2.channel.Channel) at com.trilead.ssh2.channel.Channel$Output.read(Channel.java:127) at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:946) - locked 0xbf5802e0 (a com.trilead.ssh2.channel.Channel) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:67) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:93) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) and the slave is waiting for data from the master: "Channel reader thread: channel" prio=10 tid=0x0fff940fedd0 nid=0x558e runnable [0x0fff6dc6d000] java.lang.Thread.State: RUNNABLE at java.io.FileInputStream.readBytes(Native Method) at java.io.FileInputStream.read(FileInputStream.java:236) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read(BufferedInputStream.java:254) - locked 0x0fff78ba9f98 (a java.io.BufferedInputStream) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:67) at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:93) at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) of course I can't get those dumps at exactly the same moment, even if that were meaningful with network latencies and buffering, but repeated runs never show any other state for either thread. tshark shows that there's some SSH chatter going on: 0.00 SLAVE - MASTER SSH 126 Encrypted response packet len=60 0.176121 MASTER - SLAVE SSH 94 Encrypted request packet len=28 0.176151 SLAVE - MASTER TCP 66 ssh 37501 [ACK] Seq=61 Ack=29 Win=707 Len=0 TSval=4141397874 TSecr=2808266826 but it should well be low level ssh keepalives or similar, as it's at precise 5 second intervals with nothing much else happening. There are three master-slave ssh connections, so it's not guaranteed that it's even the one associated with the stuck channel. My first thought is endianness. I don't really know how to begin debugging this issue, though.
[JIRA] [core] (JENKINS-23917) Protocol deadlock while uploading artifacts from ppc64
Craig Ringer commented on JENKINS-23917 Protocol deadlock while uploading artifacts from ppc64 I'm going to re-test with a simplified build and a single executor configured. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23917) Protocol deadlock while uploading artifacts from ppc64
Craig Ringer commented on JENKINS-23917 Protocol deadlock while uploading artifacts from ppc64 Interestingly, archiving worked with a trivial configuration - a dd command to create a dummy file and a trivial archiving command to copy it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3] (JENKINS-23918) S3 plugin: Storage class and bucket region selection disabled, GovCloud selected by default
Craig Ringer created JENKINS-23918 S3 plugin: Storage class and bucket region selection disabled, GovCloud selected by default Issue Type: Bug Assignee: Michael Watt Components: s3 Created: 22/Jul/14 7:37 AM Description: Since s3-plugin 0.6, I've noticed that when adding a new "Archive artifacts to S3" post-build task the new "Storage Class" and "Bucket Region" pulldowns are initially empty. When the job configuration is saved then re-opened, the pulldowns are populated. Storage Class has defaulted to "Standard" and "Bucket Region" has defaulted to "GovCloud". This will result in errors about the access key being unknown because GovCloud has a completely isolated authentication setup with different IAM, keys, etc. This is a regression since 0.5. Environment: s3-plugin 0.7-SNAPSHOT; also observed in 0.6. Jenkins 1.574-snapshot, also observed in 1.572. Google Chrome. Project: Jenkins Labels: regression 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] [s3] (JENKINS-23918) S3 plugin: Storage class and bucket region selection disabled, GovCloud selected by default
Craig Ringer updated JENKINS-23918 S3 plugin: Storage class and bucket region selection disabled, GovCloud selected by default Change By: Craig Ringer (22/Jul/14 7:41 AM) Description: Sinces3-plugin0.6,IvenoticedthatwhenaddinganewArchiveartifactstoS3post-buildtaskthenewStorageClassandBucketRegionpulldownsareinitiallyempty.Whenthejobconfigurationissavedthenre-opened,thepulldownsarepopulated.StorageClasshasdefaultedtoStandardandBucketRegionhasdefaultedtoGovCloud.ThiswillresultinerrorsabouttheaccesskeybeingunknownbecauseGovCloudhasacompletelyisolatedauthenticationsetupwithdifferentIAM,keys,etc. Aftereditingasecondtimetocorrecttheconfigthepluginworksasnormal.Theproblemalsoaffectsconfigurationsupgradedfrom0.5. Thisisaregressionsince0.5. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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 It looks like culprits is not the culprit in this case. It seems that API fails on changelog.xml. I have attached the file. When I leave it empty like: ?xml version="1.0" encoding="UTF-8"? log /log then API works fine. Interesting thing is that I have 7 builds triggered by SCM change and only 3 builds with changelog in them? I'm using synergy plugin 1.7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-23827) Puppet-lint regex matching too much
Jon Skarpeteig commented on JENKINS-23827 Puppet-lint regex matching too much Suggested regex fix: ^\s*(^:+)0-9+)^:+)(?:WARNING)|(?:ERROR)):\s*(.*)$ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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%
Kohsuke Kawaguchi commented on JENKINS-23904 SlowRequestCheck= kills UI performance and pegs CPU at 100% I see. We'll split this off to a separate plugin so that it can be removed entirely. I wonder using ThreadMXBean.getThreadInfo() that specifies thread IDs explicitly would reduce the overhead. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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%
SCM/JIRA link daemon resolved JENKINS-23904 as Fixed SlowRequestCheck= kills UI performance and pegs CPU at 100% Change By: SCM/JIRA link daemon (22/Jul/14 8:42 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core] (JENKINS-23904) SlowRequestCheck= kills UI performance and pegs CPU at 100%
SCM/JIRA link daemon commented on JENKINS-23904 SlowRequestCheck= kills UI performance and pegs CPU at 100% Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/jenkins/support/slowrequest/SlowRequestChecker.java http://jenkins-ci.org/commit/support-core-plugin/1499fe2b79a556e7988801c792c49fc15d379d58 Log: FIXED JENKINS-23904 SlowRequestCheck= kills UI performance and pegs CPU at 100% Made the timings for this configurable by a system property Only collect thread dump if there is a slow request This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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%
SCM/JIRA link daemon commented on JENKINS-23904 SlowRequestCheck= kills UI performance and pegs CPU at 100% Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/jenkins/support/slowrequest/SlowRequestChecker.java src/main/java/com/cloudbees/jenkins/support/slowrequest/SlowRequestFilter.java http://jenkins-ci.org/commit/support-core-plugin/8c8df7ae0977af0f31324906d4f43764f03846fc Log: FIXED JENKINS-23904 SlowRequestCheck= kills UI performance and pegs CPU at 100% Provide a means to completely disable the slow request checker both at startup and in a running Jenkins Compare: https://github.com/jenkinsci/support-core-plugin/compare/2b43d350f9a3...8c8df7ae0977 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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 updated JENKINS-23902 Matrix parent takes executor slot and blocks children Yeah, it could be a few plugins actually. I'll see what I can reproduce with. Change By: James Howe (22/Jul/14 8:51 AM) Environment: Jenkins1.573,matrix-project1.2 ,prioritysorter2.8,throttle-concurrents1.8.3 Component/s: prioritysorter Component/s: throttle-concurrents This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [next-executions] (JENKINS-23919) show also for poll SCM triggers
Michael Keppler created JENKINS-23919 show also for poll SCM triggers Issue Type: Improvement Assignee: Unassigned Components: next-executions Created: 22/Jul/14 9:00 AM Description: The list of next executions contains all projects that are configured using the "build periodically" trigger. In contrast to that, projects using the "Poll SCM" trigger are not displayed, although they are using the same mechanism to schedule builds, they just may skip such a scheduled build if there are no changes. That's why to me it seems reasonable to also list projects using "Poll SCM". Project: Jenkins Priority: Major Reporter: Michael Keppler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-23827) Puppet-lint regex matching too much
Ulli Hafner commented on JENKINS-23827 Puppet-lint regex matching too much Can you please wrap your regexp with the noformat tag? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-23827) Puppet-lint regex matching too much
Ulli Hafner
updated JENKINS-23827
Puppet-lint regex matching too much
Change By:
Ulli Hafner
(22/Jul/14 9:16 AM)
Description:
Warningsregex:
{noformat}
^\s*([^:]+):([0-9]+):([^:]+):([^:]+):\s*(.*)$
{noformat}
resultsinfalsepositives.Runningacceptancetests,outputsthefollowingwhichismatched:
{noformat}
Ubuntuubuntu-server-1404-x64executedin0.14secondslocalhost$scp/var/lib/jenkins/jobs/puppet-bind/workspaceubuntu-server-1404-x64:/etc/puppet/modules/bind{}ubuntu-server-1404-x6413:48:01$envPATH=/usr/bin:/opt/puppet-git-repos/hiera/bin:${PATH}RUBYLIB=/opt/puppet-git-repos/hiera/lib:/opt/puppet-git-repos/hiera-puppet/lib:${RUBYLIB}facterosfamilyDebian
{noformat}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [warnings] (JENKINS-23827) Puppet-lint regex matching too much
Jon Skarpeteig commented on JENKINS-23827 Puppet-lint regex matching too much https://github.com/jenkinsci/warnings-plugin/pull/40 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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%
stephenconnolly commented on JENKINS-23904 SlowRequestCheck= kills UI performance and pegs CPU at 100% @Kohsuke It would seem our paths crossed... If you want to try the thread ID specific version too that could help further This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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%
stephenconnolly commented on JENKINS-23904 SlowRequestCheck= kills UI performance and pegs CPU at 100% FYI the root cause of the issue as I see it is that the thread dump was eager not lazy... you had a check to lazy load the thread dump but you were eagerly fetching it up front. I removed the eager fetch in 1499fe2b79a556e7988801c792c49fc15d379d58 I am unsure that we need to spin off to a separate 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] [clearcase-ucm] (JENKINS-23920) The '' Special character not handled with describe (case 11500)
Mads Nielsen created JENKINS-23920 The Special character not handled with describe (case 11500) Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm Created: 22/Jul/14 9:24 AM Project: Jenkins Priority: Minor Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [memory-map] (JENKINS-23734) Memory map plugin does not allow to enter absolute or relative path
Mads Nielsen commented on JENKINS-23734 Memory map plugin does not allow to enter absolute or relative path I am pretty sure the the plugin works with relative paths. The ant pattern given starts from the current workspace and scans down and sideways. As stated we need to see what pattern that is specified in the job configuration to determine if that is indeed not the case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core] (JENKINS-23904) SlowRequestCheck= kills UI performance and pegs CPU at 100%
stephenconnolly commented on JENKINS-23904 SlowRequestCheck= kills UI performance and pegs CPU at 100% https://github.com/jenkinsci/support-core-plugin/tree/slow-request-alt-strategy is an additional change that could perhaps help. I also note that deadlock analysis etc is missing if you use the thread specific getThreadInfo() so I am unsure if that is a good idea or not to drop from the slow request checker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23921) new divs layout doesn't work with IE8
podskalsky created JENKINS-23921 new divs layout doesnt work with IE8 Issue Type: Bug Assignee: Unassigned Components: core, gui Created: 22/Jul/14 9:44 AM Description: The new layout using divs is not running at IE8. All boxes(menues,tables,...) are below each other and some fields are not visible. Project: Jenkins Priority: Critical Reporter: podskalsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mantis] (JENKINS-23922) Regexp works only if one group exists.
Alex Ouzounis created JENKINS-23922 Regexp works only if one group exists. Issue Type: Bug Assignee: sogabe Components: mantis Created: 22/Jul/14 10:18 AM Description: The issue at hand is that Updater.java line 134: id = Integer.parseInt(matcher.group(1)); always goes for the first group. When using a pattern like: ((issues?):?(\s*(,|and)?\s*(\d+))+) parsing fails. It would be welcome to be able to define the _expression_ of the group the user wishes the matcher to match or define the group number. Project: Jenkins Priority: Major Reporter: Alex Ouzounis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [websphere-deployer] (JENKINS-23923) WebSphere Deployer : Connection Failed due to SocketException
kamwai wong created JENKINS-23923 WebSphere Deployer : Connection Failed due to SocketException Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: websphere-deployer Created: 22/Jul/14 10:24 AM Description: I have follow the instructions to install the certs copy the wasadmin files, also I have copy the IBM JDK libraries (ibmjgssprovider.jar and all ibm*.jar ) to Jenkins\plugins\websphere-deployer\WEB-INF\lib and I have the below error .. please help . Connection failed: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host 10.100.51.193 at port 8885. at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:529) at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.connect(WebSphereDeploymentService.java:234) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin$DescriptorImpl.doTestConnection(WebSphereDeployerPlugin.java:325) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) 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$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.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
[JIRA] [parameterized-remote-trigger] (JENKINS-22231) Allow parameterized remote trigger to be a post-build action
Richard Pijnenburg commented on JENKINS-22231 Allow parameterized remote trigger to be a post-build action Hi, Any news on this? Would love to have it as post build action. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/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
Daniel Beck updated JENKINS-23915 When Jenkins cant read a job, it vanishes from the job-list instead of being replaced with an error marker An administrative monitor (the messages on the top of "Manage Jenkins") pointing out unloadable data would probably be a better solution. Creating "proxy" items in the hierarchy would on one hand make permissions handling difficult (should everyone with read permission to the real thing have read permissions to the error message item?), and wouldn't be visible enough on large instances. Change By: Daniel Beck (22/Jul/14 11:16 AM) Issue Type: Improvement NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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 null/ element added to triggers/ in job causing NPE on job load
Daniel Beck updated JENKINS-23914 Invalid null/ element added to triggers/ in job causing NPE on job load Change By: Daniel Beck (22/Jul/14 11:16 AM) Labels: configurationcorruptionjob xstream This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23921) new divs layout doesn't work with IE8
Daniel Beck updated JENKINS-23921 new divs layout doesnt work with IE8 Assigning to Tom as he's mentioned work needs to be done for IE8 compatibility before in comments to JENKINS-23779. Reducing priority as the software is no longer supported by the vendor, and all Windows versions still supported allow at least IE9 (with the exception of Server 2003). Change By: Daniel Beck (22/Jul/14 11:19 AM) Assignee: TomFENNELLY Priority: Critical Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23921) new divs layout doesn't work with IE8
Tom FENNELLY commented on JENKINS-23921 new divs layout doesnt work with IE8 Ahhh... thanks Daniel Is there an official browser support matrix defined for 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-11200) Renaming a job does not rename the workspace on slaves
Andreas Horst commented on JENKINS-11200 Renaming a job does not rename the workspace on slaves Reproducible on 1.573 (not tested job deletion; only renaming). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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 It looks like there is some kind of a problem with XML tags. Tags that are suggested by Jenkins wiki: changelog changeset version=xxx /changeset /changelog Format used by the plugin: log logentry revision=xxx /logentry /log When I change logentry to changeset everything is OK. Interesting is that SynergyChangeLogParser works OK and I can view changes on Jenkins web page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle] (JENKINS-19941) Gradle Plugin: Add Support For Downstream Dependencies
ASD commented on JENKINS-19941 Gradle Plugin: Add Support For Downstream Dependencies Thanks Christian for implementing this. It will really help. Some notes about how we are using Jenkins fwiw: 1 - All of our projects are "free-style software projects." With the Jenkins Gradle plugin installed, this provides an optional Gradle "Build Step" for any project. We add this build step to each project. Within this build step would be a good place to provide a checkbox that says "Automatically build downstream dependencies". This way the support would be optional. 2 - Our projects are multi-module. In the root-level build.gradle we have a version number defined. In the sub projects we apply from ../build.gradle and depend on compile: $coords + 'artifact' + $ver. ($coords and $ver being defined in ../build.gradle). I don't think this should affect the plugin though since you are getting the dependency information directly from Gradle which correctly resolves the variables for the artifact. 3 - All of our dependencies are resolved using the gradle maven plugin from an artifact repository (Nexus). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mantis] (JENKINS-23922) Regexp works only if one group exists.
Alex Ouzounis resolved JENKINS-23922 as Wont Fix Regexp works only if one group exists. No need to fix anything, just make sure you define your other groups as uncaptured by appending ?: Change By: Alex Ouzounis (22/Jul/14 2:07 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mantis] (JENKINS-23922) Regexp works only if one group exists.
Alex Ouzounis commented on JENKINS-23922 Regexp works only if one group exists. I can get around the issue by defined uncaptured groups like so: iIssues?:?(?:\s*(?:,|and)?\s*(\d+))+ As you can see the only matching group is (\d+) which gets correctly captured. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mantis] (JENKINS-23922) Regexp works only if one group exists.
Alex Ouzounis assigned JENKINS-23922 to Alex Ouzounis Regexp works only if one group exists. Change By: Alex Ouzounis (22/Jul/14 2:06 PM) Assignee: sogabe AlexOuzounis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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 null/ element added to triggers/ in job causing NPE on job load
Craig Ringer updated JENKINS-23914 Invalid null/ element added to triggers/ in job causing NPE on job load bdr_linux_config.xml: config file for current working build. See prior comment for details. bdr_linux_broken_config.xml: config file last time I noticed it break. Change By: Craig Ringer (22/Jul/14 2:24 PM) Attachment: bdr_linux_config.xml Attachment: bdr_linux_broken_config.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] [core] (JENKINS-23914) Invalid null/ element added to triggers/ in job causing NPE on job load
Craig Ringer commented on JENKINS-23914 Invalid null/ element added to triggers/ in job causing NPE on job load Daniel, I've only edited them via the web UI, with the exception of repairing the null/ breakage the two times it's occurred. The job I've observed the issue with gets edited quite frequently. I've only noticed this problem a couple of times. Until recently I've always been in a rush when working on it so unfortunately I didn't note all the details. I'll attach the current config.xml . The version attached, the latest working version, has the build-timeout plugin enabled, but I only just installed that so it can be ignored for this purpose. Similarly, the s3-plugin in the config.xml is version s3@0.7-SNAPSHOT (because I've fixed a couple of bugs since 0.6), but I've seen the issue with 0.6 too. The config.xml is unedited. There's nothing secret in there, it's for an open source project anyway. I'll also attach the config.xml from the most recent time I noticed it break. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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 commented on JENKINS-23915 When Jenkins cant read a job, it vanishes from the job-list instead of being replaced with an error marker Good point. In the mean time, hopefully people searching for "jenkins job vanished" will find this and know to look in the jenkins error log. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ownership] (JENKINS-23926) Job Ownership not available if VCS fails
Hubert Grzeskowiak created JENKINS-23926 Job Ownership not available if VCS fails Issue Type: Bug Assignee: Oleg Nenashev Components: ownership Created: 22/Jul/14 2:57 PM Description: If VCS checkout/update fails, you can't send emails to job owners since the variables are not injected. Can I somehow set a default, e.g. an admin, and let every job override it? Project: Jenkins Priority: Minor Reporter: Hubert Grzeskowiak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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 null/ element added to triggers/ in job causing NPE on job load
Craig Ringer commented on JENKINS-23914 Invalid null/ element added to triggers/ in job causing NPE on job load I know this is frustratingly vague, by the way. I've cranked the log levels up and will be watching for it happening again. I'm pretty sure it's occurred as a result of exceptions being thrown during configuration save, but beyond that can't be too sure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ownership] (JENKINS-23926) Job Ownership not available if VCS fails
Hubert Grzeskowiak updated JENKINS-23926 Job Ownership not available if VCS fails Change By: Hubert Grzeskowiak (22/Jul/14 3:04 PM) Description: IfVCScheckout/updatefails,youcantsendemailstojobownerssincethevariablesarenotinjected.CanIsomehowsetadefault,e.g.anadmin,andleteveryjoboverrideit? Thatwouldmakeforaniceworkaroundincaseitsnotpossibletoinjectthevariablesatthestartofabuild(beforecodeischeckedout). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-23927) Parameterized trigger should be able to optionally retry failed blocked builds
abayer created JENKINS-23927 Parameterized trigger should be able to optionally retry failed blocked builds Issue Type: Improvement Assignee: abayer Components: parameterized-trigger Created: 22/Jul/14 3:32 PM Description: If you've got a long chain of blocking parameterized trigger builds and one fails for known transient reasons, it'd be really nice if that build could automatically be re-run in place, without interrupting the full chain. This shouldn't be enabled by default, obviously, and should have a limited number of retries. It should determine whether to rebuild by looking for a pattern in the build log, like the Naginator plugin. Basically, I'm saying let's integrate Naginator-style behavior into the parameterized trigger plugin. Project: Jenkins Priority: Major Reporter: abayer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-23275) ScmSyncConfiguration NullPointerException on postCredential
Roger Sillito commented on JENKINS-23275 ScmSyncConfiguration NullPointerException on postCredential I'm getting a different error trace at the point where I've entered my SCM url in the config sreen. My version are: Jenkins ver. 1.561 - 1.573 SCM Sync Configuration Plugin: 0.0.7.5 Credentials Plugin: 1.15 Subversion Plug-in: 2.4.1 I've followed the troubleshooting steps (https://wiki.jenkins-ci.org/display/JENKINS/ScmSyncConfig+Troubleshootings) and can get a test jenkins job to update from the svn repository. Stack trace javax.servlet.ServletException: java.lang.NullPointerException 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.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.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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:79) 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
[JIRA] [scm-sync-configuration] (JENKINS-23275) ScmSyncConfiguration NullPointerException on postCredential
Roger Sillito edited a comment on JENKINS-23275 ScmSyncConfiguration NullPointerException on postCredential I'm getting a different error trace at the point where I've entered my SCM url in the config sreen. My version are: Jenkins ver. 1.573 SCM Sync Configuration Plugin: 0.0.7.5 Credentials Plugin: 1.15 Subversion Plug-in: 2.4.1 I've followed the troubleshooting steps (https://wiki.jenkins-ci.org/display/JENKINS/ScmSyncConfig+Troubleshootings) and can get a test jenkins job to update from the svn repository. The repo is hosted on a separate machine secured using TLS. Stack trace javax.servlet.ServletException: java.lang.NullPointerException 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.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.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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:79) 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)
[JIRA] [scm-sync-configuration] (JENKINS-23275) ScmSyncConfiguration NullPointerException on postCredential
Roger Sillito edited a comment on JENKINS-23275 ScmSyncConfiguration NullPointerException on postCredential I'm getting a different error trace at the point where I've entered my SCM url in the config sreen, however it sounds like a similar issue to the above so I'll post here. My versions are: Jenkins ver. 1.573 SCM Sync Configuration Plugin: 0.0.7.5 Credentials Plugin: 1.15 Subversion Plug-in: 2.4.1 I've followed the troubleshooting steps (https://wiki.jenkins-ci.org/display/JENKINS/ScmSyncConfig+Troubleshootings) and can get a test jenkins job to update from the svn repository. The repo is hosted on a separate machine secured using TLS. Stack trace javax.servlet.ServletException: java.lang.NullPointerException 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.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.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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:79) 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
[JIRA] [git] (JENKINS-20389) Merge commits trigger uneccessary builds when Include/Exclude regions are defined
Trey Duskin commented on JENKINS-20389 Merge commits trigger uneccessary builds when Include/Exclude regions are defined Any update on this issue? Or, if anyone has a workaround, would you mind posting it here? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-23275) ScmSyncConfiguration NullPointerException on postCredential
Roger Sillito edited a comment on JENKINS-23275 ScmSyncConfiguration NullPointerException on postCredential I'm getting a different error trace at the point where I've entered my SCM url in the config sreen. My version are: Jenkins ver. 1.573 SCM Sync Configuration Plugin: 0.0.7.5 Credentials Plugin: 1.15 Subversion Plug-in: 2.4.1 I've followed the troubleshooting steps (https://wiki.jenkins-ci.org/display/JENKINS/ScmSyncConfig+Troubleshootings) and can get a test jenkins job to update from the svn repository. Stack trace javax.servlet.ServletException: java.lang.NullPointerException 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.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.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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:79) 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
[JIRA] [core] (JENKINS-23917) Protocol deadlock while uploading artifacts from ppc64
Craig Ringer commented on JENKINS-23917 Protocol deadlock while uploading artifacts from ppc64 I've been able to reproduce this with a trivial job and after limiting the node to a single executor. It is not consistently reproducible, it's somewhat random. I suspect it's dependent on the input being archived (10MB of randomly generated data), but it could also be just plain random. I'll attach the config.xml and thread dumps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23917) Protocol deadlock while uploading artifacts from ppc64
Craig Ringer commented on JENKINS-23917 Protocol deadlock while uploading artifacts from ppc64 If it is helpful, I can provision access to the build worker for anyone interested in this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23917) Protocol deadlock while uploading artifacts from ppc64
Craig Ringer updated JENKINS-23917 Protocol deadlock while uploading artifacts from ppc64 Build log is: Started by user Craig Ringer [EnvInject] - Loading node environment variables. Building remotely on fedora16-ppc64-Power7-osuosl-karman (ppc64 fedora16 ppc linux fedora) in workspace /home/jenkins/workspace/ppctest [ppctest] $ /bin/sh -xe /tmp/hudson9160124340407748260.sh + dd if=/dev/urandom of=dummy.out bs=1M count=10 10+0 records in 10+0 records out 10485760 bytes (10 MB) copied, 0.604488 s, 17.3 MB/s Archiving artifacts At the time the master stack was taken there was another build running. I'll see if I can capture another once it's idle. Change By: Craig Ringer (22/Jul/14 3:53 PM) Attachment: config.xml Attachment: jenkins-master-stack.txt Attachment: jenkins-slave-stack.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23928) Duration reported in API does not include time spent in queue.
Xavier Shay created JENKINS-23928 Duration reported in API does not include time spent in queue. Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jul/14 4:17 PM Description: The value reported at /job/jobname/api/json?tree=buildsduration does not include time spent waiting for an available worker. I can't find another attribute that has this information in it. This is important to me because I care about the total time someone is spent waiting for a build, not just the actual execution. Thanks, Xavier (P.S. http://javadoc.jenkins-ci.org/hudson/model/Run.html#getDuration() is not clear whether the return value includes queue time or not.) Jenkins ver. 1.532.2 Project: Jenkins Priority: Major Reporter: Xavier Shay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23929) Cannot use 'WORKSPACE' variable when creating custom workspace to *modify* the auto-generated workspace
Phil Rutherford
created JENKINS-23929
Cannot use WORKSPACE variable when creating custom workspace to *modify* the auto-generated workspace
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
22/Jul/14 4:19 PM
Description:
In short: We need to have "${WORKSPACE}_${Branch}" as the custom workspace where this simply adds the branch name (a parameter) to the existing auto-created workspace. This doesn't work as the auto-generated WORKSPACE variable has not been created yet as far as I can tell. Please can it be created before the attempt to resolve the workspace and if the "${WORKSPACE}" variable is detected in the declaration then the code follows the same path as for auto-generated workspaces?
This is not the same as using say EXECUTOR_NUMBER in the workspace name in the custom workspace declaration as the auto-generated workspace uses the currently running 'instance' number of a job (where the node has multiple executors) so if you have restricted the number of instances of a job (e.g. "Throttle Concurrent Builds" plugin) then you only get up to the number of allowed instances of workspaces to be created. This is important as our workspaces are very big and consume lots of disk space - SSDs for speed, so space is relatively costly - and we have multiple branches which multiplies up this number even further!
The reason for needing to modify the workspace comes from the Perforce plugin which has useful utility parameters 'P4CLEANWORKSPACE' and 'P4QUICKCLEANWORKSPACE'. However our branches exist within the same workspace directory so if these options are used then they completely blow away any other branch than the one specified. The obvious solution is to modify the workspace (as in the first paragraph above) but without the ability to modify the existing workspace we run into space issues.
Hope I have made a somewhat complex issue clear . I have tried various workarounds (which feel more like hacks), none of which worked, but the best solution really is as described in this report I think. And this would be a useful addition to Jenkins anyway.
Unless anyone can think of a way of doing this?
Project:
Jenkins
Priority:
Major
Reporter:
Phil Rutherford
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ownership] (JENKINS-23926) Job Ownership not available if VCS fails
Oleg Nenashev commented on JENKINS-23926 Job Ownership not available if VCS fails Hello Hubert, As a workaround, you could use Token Macro in Mail-Ext plugin. See wiki for available macro descriptions. Macros correctly define owners on any build stage. Best regards, Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-build-times] (JENKINS-23930) Define timescale in Build Times graph
Ahmed Osman created JENKINS-23930 Define timescale in Build Times graph Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: project-build-times Created: 22/Jul/14 4:30 PM Description: Presently when the chart is rendered it displays the build times in an unknown time scale, it appears to be ms. It would be preferable to at least define this in minutes or even provide an option to select the time scale. Additionally would like the time scale to be visible within the rendered chart. Environment: CentOs 6.5 x64 / Chrome Project: Jenkins Labels: plugin Priority: Minor Reporter: Ahmed Osman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23917) Protocol deadlock while uploading artifacts from ppc64
Craig Ringer updated JENKINS-23917 Protocol deadlock while uploading artifacts from ppc64 Master at idle Change By: Craig Ringer (22/Jul/14 4:32 PM) Attachment: jenkins-master-idle-stack.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23875) Ability to pass reference repo recursively
Mark Waite commented on JENKINS-23875 Ability to pass reference repo recursively I had considered this type of enhancement but was not sure how to present it in a user interface. Currently, the repository has "Additional Behaviours" which includes the "Advanced clone" section that includes the location of the reference repository. That is a single location for the entire job. With submodules, the reference repository probably needs to be specified for each submodule as a separate repository, with no promise that there is any pattern between the location of the primary repository and the location of the submodule repositories. Are you using "reference repository location by convention" for your submodule reference repository definitions, or is there some more sophisticated way to do it that I've not understood? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23322) FATAL: java.io.IOException: Remote call on Machine Name failed
Mark Waite closed JENKINS-23322 as Cannot Reproduce FATAL: java.io.IOException: Remote call on Machine Name failed Change By: Mark Waite (22/Jul/14 4:36 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] [git] (JENKINS-23322) FATAL: java.io.IOException: Remote call on Machine Name failed
Mark Waite resolved JENKINS-23322 as Cannot Reproduce FATAL: java.io.IOException: Remote call on Machine Name failed After one month without any response to the request for more information, I'm closing this bug as "Cannot Reproduce" Change By: Mark Waite (22/Jul/14 4:36 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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: test/src/test/java/hudson/util/ProcessTreeKillerTest.java http://jenkins-ci.org/commit/jenkins/0f3574bbc109935e37bbd473c2a9e7b7625e3ced Log: Merge branch 'JENKINS-22641' of github.com:christ66/jenkins Compare: https://github.com/jenkinsci/jenkins/compare/37c5bc2fd861...0f3574bbc109 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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
SCM/JIRA link daemon commented on JENKINS-23912 Changeset order Code changed in jenkins User: keith Path: src/main/java/org/jenkinsci/plugins/liquibase/builder/ExecutedChangesetAction.java src/main/resources/org/jenkinsci/plugins/liquibase/builder/ExecutedChangesetAction/index.jelly src/main/resources/org/jenkinsci/plugins/liquibase/builder/ExecutedChangesetAction/summary.jelly http://jenkins-ci.org/commit/liquibase-runner-plugin/4087cbcfa3425af7b3b4a009eb52ee10c61c5a7f Log: Fix for JENKINS-23912 changeset order now preserved Compare: https://github.com/jenkinsci/liquibase-runner-plugin/compare/b3a9ae4d2986...4087cbcfa342 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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
SCM/JIRA link daemon commented on JENKINS-23909 Allow setting of liquibase properties file Code changed in jenkins User: keith Path: pom.xml src/main/java/org/jenkinsci/plugins/liquibase/builder/BuildChangeExecListener.java src/main/java/org/jenkinsci/plugins/liquibase/builder/CliOption.java src/main/java/org/jenkinsci/plugins/liquibase/builder/LiquibaseBuilder.java src/main/java/org/jenkinsci/plugins/liquibase/builder/LiquibaseProperty.java src/main/java/org/jenkinsci/plugins/liquibase/common/PropertiesParser.java src/main/resources/org/jenkinsci/plugins/liquibase/builder/LiquibaseBuilder/config.jelly http://jenkins-ci.org/commit/liquibase-runner-plugin/9ec1399f303bc37d0182839947a21fca317b810f Log: JENKINS-23909 - Allow setting of liquibase properties file introduced use of properties object to do so. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [configure-job-column] (JENKINS-23931) Error on Project Save
Curtis Salisbury created JENKINS-23931 Error on Project Save Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: configure-job-column Created: 22/Jul/14 5:42 PM Description: When I try to save a job configuration, I am getting the following errors: javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize hudson.model.Project#buildWrappers for class hudson.model.FreeStyleProject 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.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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
[JIRA] [core] (JENKINS-23921) new divs layout doesn't work with IE8
Daniel Beck commented on JENKINS-23921 new divs layout doesnt work with IE8 No. It's time though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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
Daniel Beck commented on JENKINS-23915 When Jenkins cant read a job, it vanishes from the job-list instead of being replaced with an error marker Did you check Manage Jenkins, or Manage Jenkins » Manage Old Data to see whether this exists already? Most loading errors should already appear at least in Old Data... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21518) Error while using SSH credentials to fetch git repository.
matt urbanski commented on JENKINS-21518 Error while using SSH credentials to fetch git repository. I have seen this when a slave is using two sets of ssh credentials at the same time. In my case it was the ssh-agent plugin and the git plugin conflicting. As soon as I got rid of one of them, everything worked again. YMMV. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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 a link to the wiki page you mentioned? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [toolenv] (JENKINS-23932) Parameter definition for tool selection
Jesse Glick created JENKINS-23932 Parameter definition for tool selection Issue Type: New Feature Assignee: Unassigned Components: toolenv Created: 22/Jul/14 6:26 PM Description: When the choice of a tool should be parameterized, it would be nice to have a ParameterDefinition where you can pick a ToolInstallation subclass and then select a tool of that kind. The ParameterValue could define environment variables for the name of the tool and its home. Possible the same could be done for a matrix Axis. Project: Jenkins Labels: parameter Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [thinBackup] (JENKINS-23377) cron driven backups never happen
Lars Thorup commented on JENKINS-23377 cron driven backups never happen I see the same issue. Version: CentOS release 6.5 Jenkins ver. 1.572 Let me know if there is more information you need. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [thinBackup] (JENKINS-23377) cron driven backups never happen
Lars Thorup edited a comment on JENKINS-23377 cron driven backups never happen I see the same issue. Version: CentOS release 6.5 Jenkins ver. 1.572 ThinBackup 1.7.4 Let me know if there is more information you need. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-16376) BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?
m_broida commented on JENKINS-16376 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE? This is not fixed in 1.542. We're waiting for this fix before we upgrade. Changelog does not show this issue (or any of the duplicated/related issues) have ever been incorporated/released. When will this fix be incorporated? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-23894) P4PASSWD has additional quotation when passing to MAC system, and it failed.
Haiqing Zhang assigned JENKINS-23894 to Haiqing Zhang P4PASSWD has additional quotation when passing to MAC system, and it failed. Change By: Haiqing Zhang (22/Jul/14 7:28 PM) Assignee: HaiqingZhang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-16376) BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?
Alex Earl commented on JENKINS-16376 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE? What do you mean 1.542? This is a bug against email-ext, not core. Email-ext does not have a version 1.542. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-23894) P4PASSWD has additional quotation when passing to MAC system, and it failed.
Haiqing Zhang started work on JENKINS-23894 P4PASSWD has additional quotation when passing to MAC system, and it failed. Change By: Haiqing Zhang (22/Jul/14 7:30 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-23894) P4PASSWD has additional quotation when passing to MAC system, and it failed.
Haiqing Zhang resolved JENKINS-23894 as Not A Defect P4PASSWD has additional quotation when passing to MAC system, and it failed. Change By: Haiqing Zhang (22/Jul/14 7:30 PM) Status: InProgress Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-23894) P4PASSWD has additional quotation when passing to MAC system, and it failed.
Haiqing Zhang closed JENKINS-23894 as Not A Defect P4PASSWD has additional quotation when passing to MAC system, and it failed. Change By: Haiqing Zhang (22/Jul/14 7:30 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] [build-pipeline] (JENKINS-23363) View tabs not visible or accessible after Build Pipeline plugin update to version 1.4.3
Akira Yamamoto commented on JENKINS-23363 View tabs not visible or accessible after Build Pipeline plugin update to version 1.4.3 I updated to Jenkins 1.570. Now it works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [metrics] (JENKINS-23933) Expose build successful/unstable/failed metrics as histogram
Mirko Friedenhagen created JENKINS-23933 Expose build successful/unstable/failed metrics as histogram Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: metrics Created: 22/Jul/14 8:01 PM Description: We are running a couple of Jenkins masters. We have run into problems because nodes are not able to access vital systems like our internal Maven repository or our SCM, sometimes because the hosts were down or because of new VLAN settings or firewalls between nodes or even because of configuration changes. In these cases the number of failing builds is increasing immediately. It would be nice if the metrics plugin could provide histograms of successful, unstable and failed builds, so we can react more promptly. Project: Jenkins Priority: Major Reporter: Mirko Friedenhagen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23929) Cannot use 'WORKSPACE' variable when creating custom workspace to *modify* the auto-generated workspace
Daniel Beck
commented on JENKINS-23929
Cannot use WORKSPACE variable when creating custom workspace to *modify* the auto-generated workspace
The workspace is specified relative to the node root directory, by default equivalent to
workspace/${JOB_NAME}
(depending on the value of the Java system property hudson.model.Slave.workspaceRoot). Did you try
workspace/${JOB_NAME}_${Branch}
?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-23928) Duration reported in API does not include time spent in queue.
Daniel Beck resolved JENKINS-23928 as Not A Defect Duration reported in API does not include time spent in queue. This is by design. Unexpected downtime of a node would completely kill your duration statistics otherwise. To get load related statistics, try /load-statistics (also per node, per label). For the time spent in the queue per build, try using the Metrics plugin, it adds an action to builds that shows wait time, build time, and total time. May even expose this on the API. Change By: Daniel Beck (22/Jul/14 8:27 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23917) Protocol deadlock while uploading artifacts from ppc64
Daniel Beck updated JENKINS-23917 Protocol deadlock while uploading artifacts from ppc64 Change By: Daniel Beck (22/Jul/14 8:31 PM) Labels: archivingartifactdeadlock remoting slavesshunix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [radiatorview] (JENKINS-23924) New div layout breaks Radiator view
Daniel Beck updated JENKINS-23924 New div layout breaks Radiator view Change By: Daniel Beck (22/Jul/14 8:30 PM) 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-23928) Duration reported in API does not include time spent in queue.
Xavier Shay commented on JENKINS-23928 Duration reported in API does not include time spent in queue. Unexpected downtime of a node would completely kill your duration statistics otherwise. That's desirable for end-user metrics - doesn't matter why someone is waiting. Thanks for your suggestions! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23887) View Full Build Flow does not correctly order build steps
Arun Thomas updated JENKINS-23887 View Full Build Flow does not correctly order build steps Change By: Arun Thomas (22/Jul/14 8:48 PM) Priority: Minor Trivial This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle] (JENKINS-19941) Gradle Plugin: Add Support For Downstream Dependencies
Gregory Boissinot commented on JENKINS-19941 Gradle Plugin: Add Support For Downstream Dependencies In my opinion, looking for mapping jobs from Gradle dependencies and trigger a build for matching jobs is a wrong way. Gradle plugin must not be in charge of this schenario. It has to be delegated to another component with a in-memory graph. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [lastfailureversioncolumn] (JENKINS-23885) Time duration missing for inheritance projects
Arun Thomas updated JENKINS-23885 Time duration missing for inheritance projects Change By: Arun Thomas (22/Jul/14 8:51 PM) Priority: Trivial Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jenkins-multijob-plugin] (JENKINS-16950) Can't remove sort of phases in multijob project
chris doughty commented on JENKINS-16950 Cant remove sort of phases in multijob project A couple of ways to temporarily work around the issue, although both ugly: 1.) Is to add a ? at the end of the URL like: https://hostname.com/job/JOBNAME/? However any future sorting requires a new ? be appended to undo the sorting, and removing the question marks will result in sorting returning again. 2.) Start a new browser tab and the sorting should be reset in the new tab (tested with Firefox v30.0) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jenkins-multijob-plugin] (JENKINS-16950) Can't remove sort of phases in multijob project
chris doughty edited a comment on JENKINS-16950 Cant remove sort of phases in multijob project A couple of ways to temporarily work around the issue, although both ugly: 1.) Is to add a ? at the end of the URL like: https://hostname.com/job/JOBNAME/? However any future sorting requires a new ? be appended to undo the sorting, and removing the question marks will result in sorting returning again. 2.) Start a new browser tab and the sorting should be reset in the new tab (tested with Firefox v30.0) Jenkins ver. 1.571 / MultiJob ver. 1.13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-16376) BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?
m_broida commented on JENKINS-16376 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE? Sorry. I reached this issue from a different issue and thought it was still against Jenkins itself. I meant Jenkins version 1.542. I see from the email-ext changelog that version 2.37 has this fix in it. We're using 2.36, so an update should fix this for us. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-23934) Jenkins variables evaluation is missing
Jiri Holy
created JENKINS-23934
Jenkins variables evaluation is missing
Issue Type:
Bug
Assignee:
Manuel Carrasco
Components:
performance-plugin
Created:
22/Jul/14 11:57 PM
Description:
Jenkins variables are not evaluated in input fields.
E.g.: if you try to reference report file as "result_${BUILD_NUMBER}.xml" then it will search for that exact filename, not "result_345.xml" or whatever.
Project:
Jenkins
Priority:
Major
Reporter:
Jiri Holy
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ec2] (JENKINS-23935) Allow tags for all instances in an EC2 cloud configuration
Craig Ringer created JENKINS-23935 Allow tags for all instances in an EC2 cloud configuration Issue Type: New Feature Assignee: Francis Upton Components: ec2 Created: 23/Jul/14 12:09 AM Description: For cost and instance management it would be extremely useful to be able to configure a set of tags that apply to all instances. Right now, if you want to add, say, a BillingCategory tag, you have to add it to each individual instance type. With lots of instance types that adds up. Time permitting I'll have a go at implementing this, I just wanted to put the idea out there. Project: Jenkins Labels: ec2 tags 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-23915) When Jenkins can't read a job, it vanishes from the job-list instead of being replaced with an error marker
Craig Ringer commented on JENKINS-23915 When Jenkins cant read a job, it vanishes from the job-list instead of being replaced with an error marker I looked in there when getting the exception above from the logs. I don't recall the red-highlighted message about old/unreadable data appearing then. If I get the chance to restart the node I'll try intentionally breaking a build XML and seeing if it shows up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23917) Protocol deadlock while uploading artifacts from ppc64
Craig Ringer edited a comment on JENKINS-23917 Protocol deadlock while uploading artifacts from ppc64 Attached a jstack for the master at idle except for the stuck connection. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode] (JENKINS-17184) Allow setting a custom timeout when unlocking the keychain
Antek Baranski started work on JENKINS-17184 Allow setting a custom timeout when unlocking the keychain Change By: Antek Baranski (23/Jul/14 1:09 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode] (JENKINS-17184) Allow setting a custom timeout when unlocking the keychain
Antek Baranski resolved JENKINS-17184 as Fixed Allow setting a custom timeout when unlocking the keychain https://github.com/jenkinsci/xcode-plugin/pull/47 Change By: Antek Baranski (23/Jul/14 1:09 AM) Status: InProgress Resolved Assignee: AntekBaranski 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.
