[JIRA] (JENKINS-20718) Add Documentation and help for startup-trigger-plugin
Title: Message Title Danny Staple commented on JENKINS-20718 Re: Add Documentation and help for startup-trigger-plugin No - go ahead. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20718) Add Documentation and help for startup-trigger-plugin
Title: Message Title Danny Staple edited a comment on JENKINS-20718 Re: Add Documentation and help for startup-trigger-plugin No objections - go ahead. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [logaction] (JENKINS-30219) Failed to rotate log, looks to have already been deleted
Title: Message Title Danny Staple updated an issue Jenkins / JENKINS-30219 Failed to rotate log, looks to have already been deleted Change By: Danny Staple Environment: Jenkins 1.609.2Java 1.8.0.45 Also Seen: Jenkins 1.580.1, Java 1.6.0_25-b06 on tomcat. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [nodelabelparameter-plugin] (JENKINS-26905) NodeLabelParameter plugin is missing VALUE for parameter in API
Danny Staple created JENKINS-26905 NodeLabelParameter plugin is missing VALUE for parameter in API Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin Created: 11/Feb/15 4:54 PM Description: When a build has completed with a nodelabel parameter, querying the builds API, in teh parameters list, the NodeLabel parameters have a NAME but no VALUE. Environment: Jenkins-1.580.1, Nodelabelparameter plugin 1.5.1 Project: Jenkins Priority: Major Reporter: Danny Staple This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25845) Node startup log should contain a timestamp
Danny Staple created JENKINS-25845 Node startup log should contain a timestamp Issue Type: Bug Assignee: Unassigned Components: core Created: 01/Dec/14 2:14 PM Description: When starting a windows slave with difficulties, debugging would be easier if there were timestamps on the log output from "manage jenkins"nodelog. Otherwise it is hard to tell that anything new has happened when pressing "launch slave agent" when slave agent troubles (like the DCOM issue) are encountered. Environment: Jenkins 1.580.1 LTS on Fedora, Windows Slave Project: Jenkins Priority: Minor Reporter: Danny Staple This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-25711) Default stylesheet has queued builds overlapping job and configure page
Danny Staple
created JENKINS-25711
Default stylesheet has queued builds overlapping job and configure page
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
20/Nov/14 3:22 PM
Description:
The job page and its child pages are overlapped by a queued build. The finished and running builds descriptions are set to 200px, and never overlap.
However, the HTML for the queued builds is very different:
using a float right for the stop button instead of a td, not have a div to include the parameters which are shown where the desc is on building/built runs.
We have used the simple theme plugin to add the following CSS to make it work for now:
#side-panel, #buildHistory, tr.build-row {
word-wrap: break-word;
}
.build-row.transitive td:nth-child(2) {
max-width: 200px !important;
}
Major because it makes the configure page impossible to work on if there are queued builds and the text overlaps it.
Environment:
Tomcat6, FC15, Jenkins 1.580.1.
Project:
Jenkins
Priority:
Major
Reporter:
Danny Staple
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-25711) Default stylesheet has queued builds overlapping job and configure page
Danny Staple
updated JENKINS-25711
Default stylesheet has queued builds overlapping job and configure page
Change By:
Danny Staple
(20/Nov/14 3:38 PM)
Description:
Thejobpageanditschildpagesareoverlappedbyaqueuedbuild.Thefinishedandrunningbuildsdescriptionsaresetto200px,andneveroverlap.However,theHTMLforthequeuedbuildsisverydifferent:usingafloatrightforthestopbuttoninsteadofatd,nothaveadivtoincludetheparameterswhichareshownwherethedescisonbuilding/builtruns.WehaveusedthesimplethemeplugintoaddthefollowingCSStomakeitworkfornow:
{code}
#side-panel,#buildHistory,tr.build-row{word-wrap:break-word;}.build-row.transitivetd:nth-child(2){max-width:200px!important;}
{code}
Majorbecauseitmakestheconfigurepageimpossibletoworkoniftherearequeuedbuildsandthetextoverlapsit.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [disk-usage-plugin] (JENKINS-22224) one job configuration change results in three Job Config History entries
Danny Staple commented on JENKINS-4 one job configuration change results in three Job Config History entries We are seeing a general problem here - some of the plugins appear (parameterizedTrigger, ThrottleConcurrentbuilds, NodeLabel, ExtendedChoice are current suspects) to do this too - we are now having as many as 8 (!!) saves in the config. For some plugins, it seems that when there is no change, they save a no-diff config. Almost as if each is doing their own save in order. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-10912) Browser/JS memory leak in dashboard
Danny Staple
commented on JENKINS-10912
Browser/JS memory leak in dashboard
I've seen this here too.
The partial fix with innerHtml (which is the same as this stack overflow thing here: http://stackoverflow.com/a/3785323/490188) perhaps plus Douglas Crockford's purge method might mitigate this.
My simpler and brute force fix is a GreaseMonkey script:
if(location.pathname.indexOf('config') == -1) {
//Reload every hour
window.setTimeout(function() {location.reload()}, 1000 * 60 * 60)
}
Which will do for some of our extreme feedback monitors, or accidentally leaving it open overnight in a browser tab.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-24639) ExtendedChoiceParameter not supported in Jenkins CLI (ssh)
Danny Staple created JENKINS-24639 ExtendedChoiceParameter not supported in Jenkins CLI (ssh) Issue Type: Bug Assignee: vimil Components: cli, extended-choice-parameter Created: 09/Sep/14 10:27 AM Description: If I attempt to start a parameterized build via the Jenkins CLI via SSH with an extended choice parameter I get the following message: CLI parameter submission is not supported for the class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition type. Please file a bug report for this I am able to start them by clicking build, and via url with wget. How I ran this: ssh -o ServerAliveInterval=10 -p 9200 hudsonmaster1 build -s test_job -p URL="" -p FOR_CHECK_DEVEL=true -p PLATFORM=x86 -p TEST_SET=main_functional_set -p BRANCH=devel The platform parameter is an extended choice param. Environment: Jenkins 1.554.1 Project: Jenkins Priority: Major Reporter: Danny Staple This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20815) Show Failed Status While the Build is Still In Progress
Danny Staple commented on JENKINS-20815 Show Failed Status While the Build is Still In Progress In our case - there was a build.xml there. The log is being updated. I cannot confirm the executor list status as we have found the cause of the multiple slave instances using the workspace (they should have been using different filesystems but one set were misconfigured), and eliminating this stopped this issue appearing in our system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20815) Show Failed Status While the Build is Still In Progress
Danny Staple commented on JENKINS-20815 Show Failed Status While the Build is Still In Progress we are seeing this in our system now - on a master/slave both on linux, and free-style software project both with and without concurreny, on version 1.554.1. THe job appars to continue on the slave, complete and mark the status as passed later. This appeared to be caused by a hiccup that left us with 2 slave instances pointing at the same workspace. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-13135) Very large console logs will cause Jenkins to crash or behave erratically
Danny Staple commented on JENKINS-13135 Very large console logs will cause Jenkins to crash or behave erratically We no longer reproduce this as we worked around it by redirecting the output somewhere. It is far less likely we will see it as we've internalised this as a standard thing - we only allow small bits of glue code output to the main log, and archive the redirected output. Where there are non-concurrent jobs, this also means it can be observed in the workspace. Where we allow concurrent jobs and slave node labels, we have placed apache servers pointing at the workspace directories so we can easily view the in progress logs, and write the link to them out in the main console log when it starts 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] [subversion] (JENKINS-626) permanent url for svn revision of a build
Danny Staple commented on JENKINS-626 permanent url for svn revision of a build How does this now work since the "primitive XPath result sets now forbidden"? I can query without "text()" and have the surrounding XML - but that requires additional SED or other transformation to de-xml it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Danny Staple commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Ok - I've found something on this today. If you have very "chatty" jobs on the slaves which output a lot of console data, try to log/redirect it to a file - they aren't necessarily the root cause, but make it more prone. If a job is running, but quiet, you can unplug a slave network cable for a few seconds, put it back in and things will pretty much continue as before. However- a slave running a chatty job will die with an io error almost immediately. If you can redirect to file, you may see a big reduction in these. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [startup-trigger-plugin] (JENKINS-20718) Documentation and help for startup-trigger-plugin missing
Danny Staple created JENKINS-20718 Documentation and help for startup-trigger-plugin missing Issue Type: Improvement Affects Versions: current Assignee: ashlux Components: startup-trigger-plugin Created: 22/Nov/13 10:37 AM Description: There is no documentation for this - no help for the plugin control in the job and no readme on the github folder. It would be great to have some simple docs on its usage, and covering things like what happens with a job not tied to slave node, or when tied to multiple nodes. Useful documentation here (sifted from the comments): "This plugin requires a jenkins restart (it will not work using install without restart)." "A tickbox will appear in the trigger section of each job, tick this to trigger it when the node starts". "When a job is tied to node labels with multiple nodes, it will be triggered when each node is started" (not sure about this - but the correct logic could be put here) Project: Jenkins Priority: Minor Reporter: Danny Staple This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [startup-trigger-plugin] (JENKINS-20718) Add Documentation and help for startup-trigger-plugin
Danny Staple updated JENKINS-20718 Add Documentation and help for startup-trigger-plugin Change By: Danny Staple (22/Nov/13 10:55 AM) Summary: Add Documentationandhelpforstartup-trigger-plugin missing This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10537) java.net.SocketTimeoutException: Read timed out
Danny Staple commented on JENKINS-10537 java.net.SocketTimeoutException: Read timed out We are seeing this regularly now in our jenkins setup - ad it causes the slaves to be ejected mid job - killing dozens of tests. We've yet to find the root cause of this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Danny Staple commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours I've not had a moment to try out 1.502 - so cannot confirm this. However - we do not use the active directory plugin in our installation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Danny Staple updated JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Change By: Danny Staple (14/Feb/13 10:03 AM) Environment: DebianSqueezeonLinuxqa012.6.26-2-vserver-amd64#1SMPTueJan2506:09:17UTC2011x86_64GNU/LinuxMacOSX 10.7.3x86_64 FC13,Tomcat6,Jenkins1.480.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Danny Staple commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours We are having the same issue here with Tomcat too - or at least the same symptoms, on the current LTS version of Jenkins running on Fc13, Linux, x86_64. Browsers are accepting cookies - this is seen by all users. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14828) Rebuild plugin crashes when used in conjuction with Extended Choice Parameter
Danny Staple commented on JENKINS-14828 Rebuild plugin crashes when used in conjuction with Extended Choice Parameter The issue is currently still present - but: If you start the build from the UI - the view shows the parameter without a box (as a label, not a text widget), and rebuild will result in the above error. If you start the build via a build.properties file - the view shows the parameter with a box (a text widget), and rebuild will work. This is using rebuild plugin 0.23, and Jenkins ver. 1.480.2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14828) Rebuild plugin crashes when used in conjuction with Extended Choice Parameter
Danny Staple edited a comment on JENKINS-14828 Rebuild plugin crashes when used in conjuction with Extended Choice Parameter The issue is currently still present - but: If you start the build from the UI - the view shows the parameter without a box (as a label, not a text widget), and rebuild will result in the above error. If you start the build via a build.properties file - the view shows the parameter with a box (a text widget), and rebuild will work. This is using extended choice plugin 0.23, and Jenkins ver. 1.480.2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14828) Rebuild plugin crashes when used in conjuction with Extended Choice Parameter
Danny Staple edited a comment on JENKINS-14828 Rebuild plugin crashes when used in conjuction with Extended Choice Parameter The issue is currently still present - but: If you start the build from the UI - the view shows the parameter without a box (as a label, not a text widget), and rebuild will result in the above error. If you start the build via a build.properties file - the view shows the parameter with a box (a text widget), and rebuild will work. This is using extended choice plugin 0.23, rebuilder 1.14, and Jenkins ver. 1.480.2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16109) Slave hung archiving artifacts
Danny Staple
created JENKINS-16109
Slave hung archiving artifacts
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Attachments:
jarstack.log
Components:
core
Created:
12/Dec/12 5:30 PM
Description:
With some artifacts archived on this server, it can get stuck archiving them - seems to be indefinitely (we waited a few hours before killing it, have seen it a few time).
The issue is intermittent.
A log has been attached. It looks like it is getting stuck zipping stuff up to send it over.
{code()}
"pool-1-thread-1293" prio=10 tid=0xabe07800 nid=0x2238 runnable 0xadb7d000
java.lang.Thread.State: RUNNABLE
at java.util.zip.Deflater.deflateBytes(Native Method)
at java.util.zip.Deflater.deflate(Deflater.java:306)
locked 0xeb0d0ac0 (a java.util.zip.ZStreamRef)
at java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:159)
at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:118)
at java.util.zip.GZIPOutputStream.write(GZIPOutputStream.java:72)
locked 0xeb0d0a40 (a java.util.zip.GZIPOutputStream)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
Environment:
Jenkins 1.447.2
OS: Linux $ lsb_release -a
LSB Version: :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID: RedHatEnterpriseServer
Description: Red Hat Enterprise Linux Server release 6.1 (Santiago)
Release: 6.1
Codename: Santiago
SSH Slave:
Slave.jar version: 2.11
[12/12/12 17:11:04] [SSH] java -version returned 1.6.0_22.
Project:
Jenkins
Priority:
Critical
Reporter:
Danny Staple
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16109) Slave hung archiving artifacts
Danny Staple
updated JENKINS-16109
Slave hung archiving artifacts
Change By:
Danny Staple
(12/Dec/12 5:32 PM)
Description:
Withsomeartifactsarchivedonthisserver,itcangetstuckarchivingthem-seemstobeindefinitely(wewaitedafewhoursbeforekillingit,haveseenitafewtime).Theissueisintermittent.Aloghasbeenattached.Itlookslikeitisgettingstuckzippingstuffuptosenditover.{
{{
code}
pool-1-thread-1293prio=10tid=0xabe07800nid=0x2238runnable[0xadb7d000]java.lang.Thread.State:RUNNABLEatjava.util.zip.Deflater.deflateBytes(NativeMethod)atjava.util.zip.Deflater.deflate(Deflater.java:306)-locked0xeb0d0ac0(ajava.util.zip.ZStreamRef)atjava.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:159)atjava.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:118)atjava.util.zip.GZIPOutputStream.write(GZIPOutputStream.java:72)-locked0xeb0d0a40(ajava.util.zip.GZIPOutputStream)atjava.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
{code
}
}}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16109) Slave hung archiving artifacts
Danny Staple
updated JENKINS-16109
Slave hung archiving artifacts
Change By:
Danny Staple
(12/Dec/12 5:31 PM)
Description:
Withsomeartifactsarchivedonthisserver,itcangetstuckarchivingthem-seemstobeindefinitely(wewaitedafewhoursbeforekillingit,haveseenitafewtime).Theissueisintermittent.Aloghasbeenattached.Itlookslikeitisgettingstuckzippingstuffuptosenditover.{
code()}
{{
pool-1-thread-1293prio=10tid=0xabe07800nid=0x2238runnable[0xadb7d000]java.lang.Thread.State:RUNNABLEatjava.util.zip.Deflater.deflateBytes(NativeMethod)atjava.util.zip.Deflater.deflate(Deflater.java:306)-locked0xeb0d0ac0(ajava.util.zip.ZStreamRef)atjava.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:159)atjava.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:118)atjava.util.zip.GZIPOutputStream.write(GZIPOutputStream.java:72)-locked0xeb0d0a40(ajava.util.zip.GZIPOutputStream)atjava.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
{code
}
}}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16109) Slave hung archiving artifacts
Danny Staple commented on JENKINS-16109 Slave hung archiving artifacts Possibly similar (although not sure we were hitting this from multiple threads): http://www.serkey.com/java-help-using-gzipoutputstream-but-never-end-bftb6t.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16109) Slave hung archiving artifacts
Danny Staple commented on JENKINS-16109 Slave hung archiving artifacts I am trying to determine if this really is locking up somewhere - just tracing through the code and versions to find stuff. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15955) Tree query support with config.xml
Danny Staple created JENKINS-15955 Tree query support with config.xml Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 28/Nov/12 3:31 PM Description: Could an enhancement be made so that tree query can be made into the config.xml data - for example if wanting to query the scm branchspec on a selection of jobs. Project: Jenkins Priority: Minor Reporter: Danny Staple This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7162) specifying a cli parameter causes unspecified parameters to be blank
Danny Staple commented on JENKINS-7162 specifying a cli parameter causes unspecified parameters to be blank This also affects the SSH cli access. #JENKINS-11691 looks like a duplicate of this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7162) specifying a cli parameter causes unspecified parameters to be blank
Danny Staple updated JENKINS-7162 specifying a cli parameter causes unspecified parameters to be blank Change By: Danny Staple (02/Aug/12 3:03 PM) Component/s: parameters Component/s: ssh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7162) specifying a cli parameter causes unspecified parameters to be blank
Danny Staple edited a comment on JENKINS-7162 specifying a cli parameter causes unspecified parameters to be blank Oh and the dogfood comment about integrating a patch is most certainly not mcrooney's patch. As mcrooney mentions - it is a completely different patch for #JENKINS-7261. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13135) Very large console logs will cause Jenkins to crash or behave erratically
Danny Staple created JENKINS-13135:
--
Summary: Very large console logs will cause Jenkins to crash or
behave erratically
Key: JENKINS-13135
URL: https://issues.jenkins-ci.org/browse/JENKINS-13135
Project: Jenkins
Issue Type: Bug
Components: core
Environment: Linux, FC13
Java: Java(TM) SE Runtime Environment, 1.6.0_21-b06
JVM:Java HotSpot(TM) 64-Bit Server VM, 17.0-b16, mixed mode
Server: Apache Tomcat/6.0.20
JVM arguments: -Xms1024m
-Xmx4096m
-Dhudson.model.WorkspaceCleanupThread.disabled=true
-Dcatalina.base=/usr/share/tomcat6
-Dcatalina.home=/usr/share/tomcat6
-Djava.endorsed.dirs=
-Djava.io.tmpdir=/var/cache/tomcat6/temp
-Djava.util.logging.config.file=/usr/share/tomcat6/conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
Reporter: Danny Staple
When console logs are exceptionally large (due to user parameters we've had a
3Gb log go through at some point), and somebody tries to view this log, Jenkins
will throw an exception there, and may also deny allocations to other threads -
side effects being disconnected slave nodes, jobs failing to finish up
correctly.
Exception from catalina log:
{code()}
Mar 16, 2012 4:45:30 PM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: item.why. Reason:
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor321.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at
org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at
org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at
org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at
org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at
org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
at
org.apache.commons.jelly.expression.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)
at
org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsString(ExpressionSupport.java:46)
at
org.apache.commons.jelly.expression.CompositeExpression.evaluateAsString(CompositeExpression.java:256)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.buildAttributes(ReallyStaticTagLibrary.java:111)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:95)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at
org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at
org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
[JIRA] (JENKINS-11539) GIT plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-11539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159837#comment-159837 ] Danny Staple commented on JENKINS-11539: Have you tried clearing this workspace and rerunning the job? GIT plugin -- Key: JENKINS-11539 URL: https://issues.jenkins-ci.org/browse/JENKINS-11539 Project: Jenkins Issue Type: Bug Environment: Jenkins-Git plugin, Windows Server 2003 SP2, IIS v6.0 Reporter: Murali Srinivasan I have configured Jenkins to generate builds for the GIT repository in Windows Server. My Jenkins job is configured to Poll the repository continuously and trigger build if any change is found in the repository. The issue is Jenkins job triggers automatically even there is no change in the repository. When I checked the polling log it printed the following message Started on Oct 27, 2011 9:45:54 AM Using strategy: Default [poll] Last Build : #289 [poll] Last Built Revision: Revision 7fd9fb8139dd0c449a0382b505c7857c8634f33f (origin/Prod_dev) Workspace has a .git repository, but it appears to be corrupt. No Git repository yet, an initial checkout is required Done. Took 11 sec Changes found -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
