[JIRA] (JENKINS-56118) Splunk plugin not sending all console to Splunk
Title: Message Title Ted Xiao commented on JENKINS-56118 Re: Splunk plugin not sending all console to Splunk can you try latest 1.9.2 which can send pipeline jobs without sendSplunkConsoleLog step if global option is checked in configure page Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197553.1550045124000.16836.1587716040173%40Atlassian.JIRA.
[JIRA] (JENKINS-58050) sh commands and result set not being published in logs->Splunk
Title: Message Title Ted Xiao updated JENKINS-58050 Jenkins / JENKINS-58050 sh commands and result set not being published in logs->Splunk Change By: Ted Xiao Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200071.156078065.16834.1587715860380%40Atlassian.JIRA.
[JIRA] (JENKINS-61452) Illegal base64 character in FileLogStorage$1.writeHtmlTo(FileLogStorage.java:203)
Title: Message Title Ted Xiao commented on JENKINS-61452 Re: Illegal base64 character in FileLogStorage$1.writeHtmlTo(FileLogStorage.java:203) The console page will go back to normal if the job completes, either normally or aborted. probably a caching bug in the FileLogStorage Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205131.1584010672000.6328.1584028860118%40Atlassian.JIRA.
[JIRA] (JENKINS-61452) Illegal base64 character in FileLogStorage$1.writeHtmlTo(FileLogStorage.java:203)
Title: Message Title Ted Xiao created an issue Jenkins / JENKINS-61452 Illegal base64 character in FileLogStorage$1.writeHtmlTo(FileLogStorage.java:203) Issue Type: Bug Assignee: Unassigned Components: workflow-api-plugin Created: 2020-03-12 10:57 Environment: workflow-api-plugin 2.36 Priority: Critical Reporter: Ted Xiao sporadic console error java.lang.IllegalArgumentException: Illegal base64 character 5b at java.util.Base64$Decoder.decode0(Base64.java:714) at java.util.Base64$Decoder.decode(Base64.java:526) at hudson.util.UnbufferedBase64InputStream.read(UnbufferedBase64InputStream.java:41) at hudson.util.UnbufferedBase64InputStream.read(UnbufferedBase64InputStream.java:53) at java.io.DataInputStream.readFully(DataInputStream.java:195) at java.io.DataInputStream.readFully(DataInputStream.java:169) at hudson.console.ConsoleNote.readFrom(ConsoleNote.java:248) at hudson.console.ConsoleAnnotationOutputStream.eol(ConsoleAnnotationOutputStream.java:111) at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56) at java.io.FilterOutputStream.write(FilterOutputStream.java:77) at org.jenkinsci.plugins.workflow.log.FileLogStorage$1$1.write(FileLogStorage.java:238) at java.io.FilterOutputStream.write(FilterOutputStream.java:125) at org.apache.commons.io.output.ProxyOutputStream.write(ProxyOutputStream.java:89) at org.kohsuke.stapler.framework.io.LargeText$HeadMark.moveTo(LargeText.java:314) at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(Lar
[JIRA] (JENKINS-42178) pipeline as code/multi branch pipeline jobs events
Title: Message Title Ted Xiao updated JENKINS-42178 Jenkins / JENKINS-42178 pipeline as code/multi branch pipeline jobs events Change By: Ted Xiao Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179060.1487521772000.6197.1584010080292%40Atlassian.JIRA.
[JIRA] (JENKINS-60758) Is there a way to override indexes in metadata.properties to use custom index ?
Title: Message Title Ted Xiao commented on JENKINS-60758 Re: Is there a way to override indexes in metadata.properties to use custom index ? It is documented on https://plugins.jenkins.io/splunk-devops Configure Metadata section Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204018.1578990862000.8445.1579078981348%40Atlassian.JIRA.
[JIRA] (JENKINS-60758) Is there a way to override indexes in metadata.properties to use custom index ?
Title: Message Title Ted Xiao updated JENKINS-60758 Jenkins / JENKINS-60758 Is there a way to override indexes in metadata.properties to use custom index ? Change By: Ted Xiao Status: Open Fixed but Unreleased Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204018.1578990862000.8447.1579078981886%40Atlassian.JIRA.
[JIRA] (JENKINS-60334) The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing
Title: Message Title Ted Xiao commented on JENKINS-60334 Re: The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing https://wiki.jenkins.io/display/JENKINS/Splunk+plugin+for+Jenkins For Splunk version 6.5 or later, it is recommended to use the plugin's default config For Splunk 6.3.x or 6.4.x, please adjust the default sourcetype to json:jenkins:old (please remove it if Splunk get upgraded to latest version otherwise data will be extracted twice) custom metadata is for advanced users who build app themself, you do not need it. please move the custom metadata Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203346.1575115143000.6062.1576128720556%40Atlassian.JIRA.
[JIRA] (JENKINS-60334) The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing
Title: Message Title Ted Xiao updated JENKINS-60334 Jenkins / JENKINS-60334 The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing Change By: Ted Xiao Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203346.1575115143000.6066.1576128720744%40Atlassian.JIRA.
[JIRA] (JENKINS-60334) The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing
Title: Message Title
Ted Xiao edited a comment on JENKINS-60334
Re: The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing
https://wiki.jenkins.io/display/JENKINS/Splunk+plugin+for+JenkinsFor Splunk version 6.5 or later, it is recommended to use the plugin's{color:red} default config{color}For Splunk 6.3.x or 6.4.x, please adjust the default sourcetype to json:jenkins:old (please remove it if Splunk get upgraded to latest version otherwise data will be extracted twice)custom metadata is for advanced users who build app themself, you do not need it. please move remove the custom metadata <
/td>
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203346.1575115143000.6068.1576128720862%40Atlassian.JIRA.
[JIRA] (JENKINS-60334) The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing
Title: Message Title Ted Xiao updated JENKINS-60334 Jenkins / JENKINS-60334 The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing Change By: Ted Xiao Status: Open Fixed but Unreleased Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203346.1575115143000.6064.1576128720595%40Atlassian.JIRA.
[JIRA] (JENKINS-56377) console log hangs in web browser after upgrade
Title: Message Title
Ted commented on JENKINS-56377
Re: console log hangs in web browser after upgrade
I think it is because the _javascript_ function which loops each line and appended parallel label https://github.com/jenkinsci/workflow-job-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/workflow/job/console/NewNodeConsoleNote/script.js#L21-L42 It can be reproduced by a generating lots of lines in parallel step, such as
def genText(lines){
(1..lines).each{
println "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur interdum fringilla interdum"
}
return true
}
parallel "branch-1" : { genText(2) },
"branch-2": { genText(2)}
The consoleFull is very slow and firefox complaining about the js Jesse Glick does it make sense to generate the label in backend(Jenkins side) ?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197963.1551669398000.2014.1575617520129%40Atlassian.JIRA.
[JIRA] (JENKINS-60334) The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing
Title: Message Title Ted commented on JENKINS-60334 Re: The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing If you are not a developer and you just want to try it out, please use the update center to download https://jenkins.io/doc/book/managing/plugins/ The simplest and most common way of installing plugins is through the Manage Jenkins > Manage Plugins view, available to administrators of a Jenkins environment. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203346.1575115143000.11375.1575390420238%40Atlassian.JIRA.
[JIRA] (JENKINS-59504) Credentials shown in plaintext in Splunk Console Output
Title: Message Title Ted updated JENKINS-59504 Jenkins / JENKINS-59504 Credentials shown in plaintext in Splunk Console Output Change By: Ted Status: Open Fixed but Unreleased Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202126.1569317096000.6576.1569577140356%40Atlassian.JIRA.
[JIRA] (JENKINS-59504) Credentials shown in plaintext in Splunk Console Output
Title: Message Title Ted commented on JENKINS-59504 Re: Credentials shown in plaintext in Splunk Console Output I would recommend scripted pipeline for such cases Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202126.1569317096000.6565.1569576720124%40Atlassian.JIRA.
[JIRA] (JENKINS-59504) Credentials shown in plaintext in Splunk Console Output
Title: Message Title
Ted commented on JENKINS-59504
Re: Credentials shown in plaintext in Splunk Console Output
If you click the "pipeline steps" on job build page, you will find out something like this The step env step executed first before sendSplunkConsoleLog
environment {
userAndPass = credentials('5d407101-23e0-43e7-83b6-badfdd189698')
}
And because sendSplunkConsoleLog is wrapped inside the scope, it sees the clear text instead of masked ones, just like other steps inside withCredentials such as
withCredentials([usernameColonPassword(credentialsId: '5d407101-23e0-43e7-83b6-badfdd189698', variable: 'abc')]) {
// sh step sees the clear text actually
sh "echo $abc > /tmp/abc.txt"
}
I think it is specific to declarative pipeline design: environment step has higher order. In the contract, we can control the order of execution in scripted pipeline, such as
sendSplunkConsoleLog {
node {
echo "testing console log"
withCredentials([usernameColonPassword(credentialsId: 'blah', variable: 'abc')]) {
echo abc
sh "echo $abc"
echo "hello there"
}
echo "done"
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451
[JIRA] (JENKINS-59504) Credentials shown in plaintext in Splunk Console Output
Title: Message Title Ted updated an issue Jenkins / JENKINS-59504 Credentials shown in plaintext in Splunk Console Output Change By: Ted Attachment: Screen Shot 2019-09-27 at 5.17.58 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202126.1569317096000.6561.1569576180256%40Atlassian.JIRA.
[JIRA] (JENKINS-58866) Splunk plugin not sending json files
Title: Message Title Ted updated JENKINS-58866 Jenkins / JENKINS-58866 Splunk plugin not sending json files Change By: Ted Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201183.1565289754000.5977.1566293340759%40Atlassian.JIRA.
[JIRA] (JENKINS-58866) Splunk plugin not sending json files
Title: Message Title Ted updated JENKINS-58866 Jenkins / JENKINS-58866 Splunk plugin not sending json files Change By: Ted Status: Open Fixed but Unreleased Resolution: Fixed Released As: 1.8.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201183.1565289754000.5975.1566293340734%40Atlassian.JIRA.
[JIRA] (JENKINS-58866) Splunk plugin not sending json files
Title: Message Title Ted commented on JENKINS-58866 Re: Splunk plugin not sending json files it will be fixed by https://github.com/jenkinsci/splunk-devops-plugin/pull/8 you can use https://repo.jenkins-ci.org/snapshots/com/splunk/splunkins/splunk-devops/1.8.1-SNAPSHOT/splunk-devops-1.8.1-20190815.162126-1.hpi for testing Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201183.1565289754000.3552.1565886420142%40Atlassian.JIRA.
[JIRA] (JENKINS-58866) Splunk plugin not sending json files
Title: Message Title Ted commented on JENKINS-58866 Re: Splunk plugin not sending json files could you please add below conf to $SPLUNK_HOME/etc/system/local/limits.conf [http_input] # max request content length, bytes max_content_length = 1000 1.7.2 will send json file in single request instead of line by line so it can be parsed correctly, I guess your splunk http event collector discarded the input for length limit Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201183.1565289754000.11372.1565362440145%40Atlassian.JIRA.
[JIRA] (JENKINS-58050) sh commands and result set not being published in logs->Splunk
Title: Message Title Ted commented on JENKINS-58050 Re: sh commands and result set not being published in logs->Splunk I can not reproduce, please make sure pipeline related plugins get updated to latest version, e.g. https://plugins.jenkins.io/workflow-job https://plugins.jenkins.io/workflow-support Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200071.156078065.2189.1560846780178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57836) Customize metadata information for only some jobs
Title: Message Title Ted updated JENKINS-57836 Jenkins / JENKINS-57836 Customize metadata information for only some jobs Change By: Ted Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199794.1559644291000.22081.1559751600245%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57836) Customize metadata information for only some jobs
Title: Message Title Ted commented on JENKINS-57836 Re: Customize metadata information for only some jobs https://wiki.jenkins.io/display/JENKINS/Splunk+Plugin+for+Jenkins please check section 3: Customize The Job Data Sent to Splunk Jenkins->Configure System->Splunk for Jenkins Configuration->Advanced ->Customize Event Processing Command There is an example in FAQ about collect info of upstream/downstream, I think you can reference that one for usage Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199794.1559644291000.22079.1559751600219%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57586) TaskListenerDecorator's close method is not called
Title: Message Title Ted commented on JENKINS-57586 Re: TaskListenerDecorator's close method is not called Sorry for the trouble. Seems TaskListenerDecorator was added via https://issues.jenkins-ci.org/browse/JENKINS-45693 , Jesse Glick would you mind taking a look? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199504.1558458028000.10849.1558677480113%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57586) TaskListenerDecorator's close method is not called
Title: Message Title Ted commented on JENKINS-57586 Re: TaskListenerDecorator's close method is not called Oleg Nenashev is the behavior expected? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199504.1558458028000.9941.1558613160043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Ted closed an issue as Fixed Jenkins / JENKINS-50993 Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled Change By: Ted Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190218.1524652389000.9938.1558612980364%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Ted updated JENKINS-50993 fixed in splunk-devops 1.7.1 Jenkins / JENKINS-50993 Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled Change By: Ted Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190218.1524652389000.9932.1558612921014%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Ted updated JENKINS-50993 Jenkins / JENKINS-50993 Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled Change By: Ted Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190218.1524652389000.9934.1558612921052%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57586) TaskListenerDecorator's close method is not called
Title: Message Title Ted created an issue Jenkins / JENKINS-57586 TaskListenerDecorator's close method is not called Issue Type: Bug Assignee: Unassigned Attachments: update_test.patch Components: workflow-job-plugin Created: 2019-05-21 17:00 Priority: Minor Reporter: Ted master branch workflow-job-2.33 SNAPSHOT, test case attached (diff file) close method is not called in the pipeline lifecycle, I would like to leverage the close method to release resources used in TaskListenerDecorator, any suggestions ? Add Comment
[JIRA] (JENKINS-54208) Groovy compilation error in Splunk Plugin Extension
Title: Message Title Ted updated JENKINS-54208 Jenkins / JENKINS-54208 Groovy compilation error in Splunk Plugin Extension Change By: Ted Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194845.154031305.5531.1558371780281%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54208) Groovy compilation error in Splunk Plugin Extension
Title: Message Title
Ted commented on JENKINS-54208
Re: Groovy compilation error in Splunk Plugin Extension
pls refer https://plugins.jenkins.io/splunk-devops-extend for declarative syntax
#declarative pipeline
pipeline {
agent any
options {
timeout(time: 1, unit: 'HOURS')
sendSplunkConsoleLog()
}
stages {
stage('Example') {
steps {
echo 'Hello World'
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194845.154031305.5529.1558371780251%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57410) Splunk Plugin Causing threadlock When Testing Connections
Title: Message Title Ted updated JENKINS-57410 Jenkins / JENKINS-57410 Splunk Plugin Causing threadlock When Testing Connections Change By: Ted Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199215.1557526135000.5527.1558371060931%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57410) Splunk Plugin Causing threadlock When Testing Connections
Title: Message Title Ted updated JENKINS-57410 fixed in 1.7.2 Jenkins / JENKINS-57410 Splunk Plugin Causing threadlock When Testing Connections Change By: Ted Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199215.1557526135000.5523.1558371060420%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55192) Being able to add a custom log file would be a really great feature
Title: Message Title Ted commented on JENKINS-55192 Re: Being able to add a custom log file would be a really great feature If the files are out of workspace, please use splunk forwarder to send logs files (e.g. /var/log/*) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55192) Being able to add a custom log file would be a really great feature
Title: Message Title Ted commented on JENKINS-55192 Re: Being able to add a custom log file would be a really great feature There is a post action for sending files located in workspace Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55192) Being able to add a custom log file would be a really great feature
Title: Message Title Ted updated an issue Jenkins / JENKINS-55192 Being able to add a custom log file would be a really great feature Change By: Ted Attachment: Screen Shot 2018-12-14 at 11.02.10 AM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54710) GitException was not retried in shared libraries fetcher
Title: Message Title Ted created an issue Jenkins / JENKINS-54710 GitException was not retried in shared libraries fetcher Issue Type: Bug Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2018-11-20 05:29 Priority: Minor Reporter: Ted https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/libs/SCMSourceRetriever.java#L129 GitException is not subclass of IOException org.eclipse.jgit.errors.NoRemoteRepositoryException: X: fatal: remote error: Server busy Bitbucket is currently under heavy load and is not able to service your request. Please wait briefly and try your request again. at org.eclipse.jgit.transport.TransportGitSsh.cleanNotFound(TransportGitSsh.java:209) at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.(TransportGitSsh.java:290) at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:162) at org.eclipse.jgit.api.LsRemoteCommand.execute(LsRemoteCommand.java:198) Caused: org.eclipse.jgit.api.errors.TransportException: X: fatal: remote error: Server busy Bitbucket is currently under heavy load and is not able to service your request. Please wait briefly and try your request again. at org.eclipse.jgit.api.LsRemoteCommand.execute(LsRemoteCommand.java:221) at org.eclipse.jgit.api.LsRemoteCommand.call(LsRemoteCommand.java:159) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getRemoteReferences(JGitAPIImpl.java:787) Caused: hudson.plugins.git.GitException at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getRemoteReferences(JGitAPIImpl.java:801) at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:708) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:598) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRe
[JIRA] (JENKINS-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Ted commented on JENKINS-50993 Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled Sam Van Oort could you shed some lights on the issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title
Ted edited a comment on JENKINS-50993
Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
LogActionImpl does exist in workflow xml1) The log link is missing if called by {color:red}runs?fullStages=true{color}&_=15252542918482) The log link can be retrieved via individual rest api, such as /job/debug/job/stage_view_debug/ 9 7 /execution/node/15/wfapi/describe!Screen Shot 2018-05-02 at 3.06.03 PM.png!The xml is{code}more 15.xml1415org.jenkinsci.plugins.workflow.steps.EchoStep 1525244349821 UTF-8message Sample Pipeline for Testtrue {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title
Ted edited a comment on JENKINS-50993
Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
LogActionImpl does exist in workflow xml1) The log link is missing although LogActionImpl is in xml if called by {color:red}runs?fullStages=true{color}&_=1525254291848 2) The log link can be retrieved via individual rest api, such as /job/debug/job/stage_view_debug/9/execution/node/15/wfapi/describe !Screen Shot 2018-05-02 at 3.06.03 PM.png!The xml is{code}more 15.xml1415org.jenkinsci.plugins.workflow.steps.EchoStep 1525244349821 UTF-8message Sample Pipeline for Testtrue {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Ted updated an issue Jenkins / JENKINS-50993 Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled Change By: Ted Comment: per the code https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/src/main/java/com/cloudbees/workflow/rest/external/AtomFlowNodeExt.java#L57I guess node.getAction may have caching issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Ted commented on JENKINS-50993 Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled per the code https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/src/main/java/com/cloudbees/workflow/rest/external/AtomFlowNodeExt.java#L57 I guess node.getAction may have caching issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Ted commented on JENKINS-50993 Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled log link is missing although LogActionImpl is in xml The xml is more 15.xml "workflow-support@2.18"> "cps.n.StepAtomNode" plugin="workflow-cps@2.45"> 14 15 org.jenkinsci.plugins.workflow.steps.EchoStep "workflow-api@2.25"> 1525244349821 UTF-8 "workflow-cps@2.45"> "linked-hash-map"> message Sample Pipeline for Test true Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title Ted updated an issue Jenkins / JENKINS-50993 Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled Change By: Ted Attachment: Screen Shot 2018-05-02 at 3.06.03 PM.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title
Ted commented on JENKINS-50993
Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
I think it is related to state view caching. the ID.log is created on disk and can be viewed by "pipeline steps" (flowGraphTable) -> Select step -> Select Log The stage view log only works if 1) rename the job to another folder using the same name 2) restart jenkins What "sendSplunkConsoleLog" does is
@Override
public boolean start() throws Exception {
//refer to WithContextStep implementation
StepContext context = getContext();
Run run = context.get(Run.class);
ConsoleLogFilter filter = BodyInvoker.mergeConsoleLogFilters(context.get(ConsoleLogFilter.class), new TeeConsoleLogFilter(run));
context.newBodyInvoker().withContext(filter).withCallback(BodyExecutionCallback.wrap(context)).start();
return false;
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-42178) pipeline as code/multi branch pipeline jobs events
Title: Message Title
Ted commented on JENKINS-42178
Re: pipeline as code/multi branch pipeline jobs events
pipeline support is provided by a separate plugin splunk-devops-extend, stage is supported out of box(no additional configure is required), but currently stage information is not showed on the app , you have to get it from jenkins_statistics index Sample
index=jenkins_statistics event_tag=job_event job_name=* stages
{
"build_number": 2,
"build_url": "job/blah/2/",
"event_tag": "job_event",
"job_duration": 2123.701,
"job_name": "job/blah/",
"job_result": "SUCCESS",
"job_started_at": "2017-02-17T18:55:02Z",
"job_type": "Pipeline",
"label": "master",
"node": "(master)",
"queue_id": 7059,
"queue_time": 0.069,
"scm": "git",
"stages": [
{
"duration": 47.503,
"id": "23",
"name": "Clone Repo",
"pause_duration": 0.0,
"start_time": 1487358141,
"status": "SUCCESS"
},
{
"duration": 960.245,
"id": "115",
"name": "Static Analysis",
"pause_duration": 0.0,
"start_time": 1487358357,
"status": "SUCCESS"
},
{
"duration": 22.6,
"id": "273",
"name": "Negative API tests",
"pause_duration": 0.0,
"start_time": 1487359317,
"status": "SUCCESS"
}
],
"test_summary": {
"duration": 0.0,
"failures": 0,
"passes": 0,
"skips": 0,
"total": 0
},
"trigger_by": "Branch indexing",
"type": "completed",
"upstream": "",
"user": "anonymous"
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39452) build blocked , looks related to com.splunk.splunkjenkins.utils.LogConsumer
Title: Message Title Ted edited a comment on JENKINS-39452 Re: build blocked , looks related to com.splunk.splunkjenkins.utils.LogConsumer LogConsumer is running on non-blocking mode, the log shows the network between Jenkins master and Splunk server is not stable, and connection was reset (the plugin will resend the data, not a issue) . I don't have detail background about Issue, just my 2 cents based on my Jenkins admin experience:Maybe the connection between the Jenkins master and Slave(job was running on) was also got reset, the job will hang for 30 minutes until socket timeout.refer to https://github.com/jenkinsci/remoting/blob/remoting-2.56/src/main/java/hudson/remoting/Engine.java#L391 (jenkins 1.658 shipped with slave.jar v2.56) 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-39452) build blocked , looks related to com.splunk.splunkjenkins.utils.LogConsumer
Title: Message Title Ted commented on JENKINS-39452 Re: build blocked , looks related to com.splunk.splunkjenkins.utils.LogConsumer LogConsumer is running on non-blocking mode, the log shows the network between Jenkins master and Splunk server is not stable, and connection was reset. I don't have detail background about Issue, just my 2 cents based on my Jenkins admin experience: Maybe the connection between the Jenkins master and Slave(job was running on) was also got reset, the job will hang for 30 minutes until socket timeout. refer to https://github.com/jenkinsci/remoting/blob/remoting-2.56/src/main/java/hudson/remoting/Engine.java#L391 (jenkins 1.658 shipped with slave.jar v2.56) 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] [core] (JENKINS-31768) dead lock while removing computer
Title: Message Title Ted created an issue Jenkins / JENKINS-31768 dead lock while removing computer Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Nov/15 9:11 AM Environment: jenkins v1.634 Priority: Critical Reporter: Ted "Handling POST /configSubmit from 10.160.255.74 : RequestHandlerThread17137": waiting for ownable synchronizer 0x7f3a5d901708, (a java.util.concurrent.locks.ReentrantLock$NonfairSync), which is held by "Computer.threadPoolForRemoting 31767" "Computer.threadPoolForRemoting 31767": waiting to lock monitor 0x7f38ce077bc8 (object 0x7f3a7c8a10c8, a hudson.plugins.ec2.EC2Computer), which is held by "Handling POST /configSubmit from 10.160.255.74 : RequestHandlerThread17137" "Handling POST /configSubmit from 10.160.255.74 : RequestHandlerThread17137": at sun.misc.Unsafe.park(Native Method) parking to wait for <0x7f3a5d901708> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) at java.util.concurrent.locks.AbstractQue
[JIRA] [core] (JENKINS-31253) Lock contention on jenkins.model.Nodes.removeNode
Title: Message Title Ted commented on JENKINS-31253 Re: Lock contention on jenkins.model.Nodes.removeNode The trick part is the whole stack trace didn't show which thread is holding the lock, maybe the lock is held in java native code? I tried to take thread dumps on serval servers at different times, no luck to find the lock holder. 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] [core] (JENKINS-31253) Lock contention on jenkins.model.Nodes.removeNode
Title: Message Title Ted commented on JENKINS-31253 Re: Lock contention on jenkins.model.Nodes.removeNode workaround by pull quest https://github.com/jenkinsci/jenkins/pull/1895 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] [core] (JENKINS-31253) Lock contention on jenkins.model.Nodes.removeNode
Title: Message Title Ted edited a comment on JENKINS-31253 Re: Lock contention on jenkins.model.Nodes.removeNode 100+ threads compete for getting the queue lock, that make the system throughput low stack trace on[ http://pastebin.com/iJaeUmJj] By the way, we are running jenkins 1.634 on jdk java version "1.8.0_45"Java(TM) SE Runtime Environment (build 1.8.0_45-b14)Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode) 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] [core] (JENKINS-31253) Lock contention on jenkins.model.Nodes.removeNode
Title: Message Title Ted commented on JENKINS-31253 Re: Lock contention on jenkins.model.Nodes.removeNode 100+ threads compete for getting the queue lock, that make the system throughput low stack trace on[ http://pastebin.com/iJaeUmJj] 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] [core] (JENKINS-31253) Lock contention on jenkins.model.Nodes.removeNode
Title: Message Title Ted commented on JENKINS-31253 Re: Lock contention on jenkins.model.Nodes.removeNode submitted pull request https://github.com/jenkinsci/jenkins/pull/1893 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] [core] (JENKINS-31253) Lock contention on jenkins.model.Nodes.removeNode
Title: Message Title Ted created an issue Jenkins / JENKINS-31253 Lock contention on jenkins.model.Nodes.removeNode Issue Type: Bug Assignee: Unassigned Components: core Created: 29/Oct/15 10:09 AM Priority: Critical Reporter: Ted We run CI on cloud and the slaves are terminated after one time use, and new slaves are also created on demand. When the slaves number reaches 200 and the throuhput is very slow, and the stacktrace shows over 100 locks parking for java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) parking to wait for <0x7fd6f216d708> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199) at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209) at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285) at hudson.model.Queue._withLock(Queue.java:1291) at hudson.model.Queue.withLock(Queue.java:1176) at jenkins.model.Nodes.removeNode(Nodes.java:193) at jenkins.model.Jenkins.removeNode(Jenkins.java:1751) at hudson.plugins.ec2.EC2OndemandSlave.terminate(EC2OndemandSlave.java:72) at hudson.plugins.ec2.EC2O
[JIRA] [ec2-plugin] (JENKINS-4995) Support windows AMI's in EC2 plugin
Title: Message Title Ted edited a comment on JENKINS-4995 Re: Support windows AMI's in EC2 plugin For those who want to use other local accounts except Administrator, please adjust windows registry `` reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f `` 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] [ec2-plugin] (JENKINS-4995) Support windows AMI's in EC2 plugin
Title: Message Title Ted commented on JENKINS-4995 Re: Support windows AMI's in EC2 plugin For those who want to use other local accounts except Administrator, please adjust windows registry `` reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f `` 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] [ec2-plugin] (JENKINS-4995) Support windows AMI's in EC2 plugin
Title: Message Title Ted commented on JENKINS-4995 Re: Support windows AMI's in EC2 plugin I added NTLM with SPNEGO by pull request https://github.com/jenkinsci/ec2-plugin/pull/165, please check it out. To test, you should enable ssl on WinRM and have a working Administrator account, and `Use HTTPS` is also enabled in the plugin 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] [ec2-plugin] (JENKINS-23787) EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline"
Title: Message Title
ted shaw edited a comment on JENKINS-23787
Re: EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline"
I think the commit https://github.com/jenkinsci/ec2-plugin/commit/c9d69a5da8c9be094701d4c191ba7b1d06c200c9 breaks plugin, user can not launch multiple instances for same AMI since DescribeInstancesRequest returns all instances instead of stopped instances, and no instances can be launched if there is any running culprit below line was removeddiFilters.add(new Filter("instance-state-name").withValues(InstanceStateName.Stopped.toString(), InstanceStateName.Stopping.toString()));
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] [ec2-plugin] (JENKINS-23787) EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline"
Title: Message Title
ted shaw commented on JENKINS-23787
Re: EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline"
I think the commit https://github.com/jenkinsci/ec2-plugin/commit/c9d69a5da8c9be094701d4c191ba7b1d06c200c9 breaks plugin, user can not launch multiple instances for same AMI since DescribeInstancesRequest returns all instances instead of stopped instances, and no instances can be launched if there is any running culprit below line was removed diFilters.add(new Filter("instance-state-name").withValues(InstanceStateName.Stopped.toString(), InstanceStateName.Stopping.toString()));
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.
