[JIRA] (JENKINS-50020) CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage
Title: Message Title
Dominic Hargreaves commented on JENKINS-50020
Re: CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage
Thanks for taking a look! It's possibly worth noting that after this happens a lot we also see a completely unresponsive web interface which forces us to kill jenkins and start up again, accompanied by these log messages:
Mar 01, 2018 1:02:56 PM jenkins.metrics.api.Metrics$HealthChecker execute
WARNING: Some health checks are reporting as unhealthy: [thread-deadlock : [Handling POST /ajaxExecutors from 10.42.2.5 : RequestHandlerThread[#8880] View/ajaxExecutors.jelly locked on java.util.concurrent.locks.ReentrantReadWriteLock$No
nfairSync@3acfc25d (owned by Executor #0 for jenkins-linux-build-slaveb4d1b0 : executing PlaceholderExecutable:ExecutorStepExecution.PlaceholderTask{runId=JOBNAME#1247,label=(linux||linux-fallback||linux-scalable),context=Cp
sStepContext[10:node]:Owner[JOBNAME/1247:JOBNAME #1247],cookie=null,auth=null}):
at sun.misc.Unsafe.park(Native Method)
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.doAcquireShared(AbstractQueuedSynchronizer.java:967)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283)
at java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727)
at hudson.model.Executor.getAsynchronousExecution(Executor.java:646)
at hudson.model.Executor.isDisplayCell(Executor.java:666)
at hudson.model.Computer.getDisplayExecutors(Computer.java:991)
at sun.reflect.GeneratedMethodAccessor1217.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
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:74)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
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.ForEachTag.doTag(ForEachTag.java:150)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at
[JIRA] (JENKINS-36570) Implement pipeline compatibility
Title: Message Title Dominic Hargreaves commented on JENKINS-36570 Re: Implement pipeline compatibility I was probably coming at this from the wrong direction. I can confirm that job groups/priority sorting works on a pipeline job as a whole and that is good enough for us at the moment. 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-36570) Implement pipeline compatibility
Title: Message Title Dominic Hargreaves commented on JENKINS-36570 Re: Implement pipeline compatibility Oleg Nenashev I had a look at https://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin and the only mention of pipeline is a change entry mentioning this ticket. But I can't see anywhere how one would allocated a node in a given job group, which I assume is how this would need to work, any examples at all of it being used in a pipeline script. So given your reference to existing documentation I suspect there's something I'm just not finding from a google search? 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-36570) Implement pipeline compatibility
Title: Message Title Dominic Hargreaves commented on JENKINS-36570 Re: Implement pipeline compatibility I see that this is now merged in, but could anyone say to what extent this is useful in practice, and how to use it, as it wasn't obvious from this issue and the PR 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-35503) Slack plugin reveals integration token
Title: Message Title Dominic Hargreaves updated an issue Jenkins / JENKINS-35503 Slack plugin reveals integration token Change By: Dominic Hargreaves The Slack plugin reveals the integration token in the global configuration. In environments when many people have access to view the global configuration, this presents a security vulnerability since the token gives appears to give access to quite a bit of theSlack instance (though it's not entirely clear where that's configured). 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] [slack-plugin] (JENKINS-35503) Slack plugin reveals integration token
Title: Message Title Dominic Hargreaves created an issue Jenkins / JENKINS-35503 Slack plugin reveals integration token Issue Type: Bug Assignee: Kurt Madel Components: slack-plugin Created: 2016/Jun/09 3:22 PM Priority: Minor Reporter: Dominic Hargreaves The Slack plugin reveals the integration token in the global configuration. In environments when many people have access to view the global configuration, this presents a security vulnerability since the token gives access to the Add Comment
