[JIRA] (JENKINS-38276) Increase size of text area for pipeline script code
Title: Message Title
Christian Höltje commented on JENKINS-38276
Re: Increase size of text area for pipeline script code
Even better: The ui-resizable-handle actually works! This CSS makes it available (with horrible colors!):
.ui-resizable-handle {
position: absolute;
bottom: 0;
background-color: #1f7313;
width: 100%;
height: 10px;
cursor: row-resize;
opacity: 0.1;
}
.ui-resizable-handle:hover {
opacity: 0.6;
}
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.174439.1474032648000.2939.1582180320798%40Atlassian.JIRA.
[JIRA] (JENKINS-38276) Increase size of text area for pipeline script code
Title: Message Title
Christian Höltje commented on JENKINS-38276
Re: Increase size of text area for pipeline script code
This CSS fixes it. The link to the pipeline syntax can get messy, but better than not having resize.
.ace_editor {
resize:vertical; overflow:auto !important;
}
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.174439.1474032648000.2899.1582176300918%40Atlassian.JIRA.
[JIRA] (JENKINS-60852) Support Code Climate format
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-60852 Support Code Climate format Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-01-23 21:53 Priority: Minor Reporter: Christian Höltje For the mission to support everything... The Code Climate Schema is used by some tools that only otherwise support custom formats (cough reek cough). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60851) Support TAP protocol
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-60851 Support TAP protocol Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-01-23 21:49 Priority: Minor Reporter: Christian Höltje I would suggest supporting the Test Anything Protocol (AKA "TAP") as a format. It's used by a bunch of smaller specialty linters and testers like bash, perl, and fish. There is a standalone TAP plugin but it would make sense to add it into WNG. Add Comment
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Christian Höltje commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Doing some googling... The has_recent_activity=1 cookie seems to be coming from GitHub. I suspect that the cookie parser being used by Jenkins is broken. 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.198903.1556022985000.15523.1563465120902%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Christian Höltje commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page I have the same issue. To reproduce: Goto $JENKINS_URL/manage Goto $JENKINS_URL/configureSecurity Press "Reload" or click the "Configure Global Security" and you get a traceback saying anonymous doesn't have the right permissions. If you get the "Retry with POST" page and you look at the networking console, you'll see that it actually re-logged you in by visiting github and coming back. That's why the POST got converted to a GET. As above, I get these log entries everytime: Jul 18, 2019 11:20:33 AM hudson.util.Secret toString WARNING: Use of toString() on hudson.util.Secret from java.lang.String.valueOf(String.java:2994). Prefer getPlainText() or getEncryptedValue() depending your needs. see https://jenkins.io/redirect/hudson.util.Secret/ Jul 18, 2019 11:20:34 AM org.apache.http.client.protocol.ResponseProcessCookies processCookies WARNING: Invalid cookie header: "Set-Cookie: has_recent_activity=1; path=/; expires=Thu, 18 Jul 2019 16:20:34 -". Invalid 'expires' attribute: Thu, 18 Jul 2019 16:20:34 - This is the full traceback mentioned above: org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/war/WEB-INF/lib/jenkins-core-2.176.2.jar!/lib/layout/view.jelly:39:20: anonymous is missing the Overall/Administer permission at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) 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:120) 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:120) at org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:276) at org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92) at com.sun.proxy.$Proxy108.layout(Unknown Source) at lib.LayoutTagLib$layout.call(Unknown Source) at hudson.security.GlobalSecurityConfiguration.index.run(index.groovy:15) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:74) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:62) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.ScriptInvoker.execute(ScriptInvoker.java:56) at org.kohsuke.stapler.jelly.ScriptInvoker.execute(ScriptInvoker.java:43) at
[JIRA] (JENKINS-56996) null permission lookup when pull-request's origin repo/branch is deleted on github
Title: Message Title Christian Höltje commented on JENKINS-56996 Re: null permission lookup when pull-request's origin repo/branch is deleted on github So, the issue is that the updating of all PRs stops, not that this one PR doesn't refresh (which is understandable). Is that correct? The scanning for the entire organization folder (and down) stops, nothing new gets added or removed. 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-56996) null permission lookup when pull-request's origin repo/branch is deleted on github
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-56996 null permission lookup when pull-request's origin repo/branch is deleted on github Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-04-12 20:55 Environment: Jenkins 2.164.1 git: 4.0.0-rc git-client: 3.0.0-rc git-server: 1.7 github: 1.29.4 github-api: 1.95 github-branch-source: 2.4.5 github-oauth: 0.31 github-pr-coverage-status: 2.0.0 pipeline-github: 2.5 pipeline-github-lib: 1.0 Priority: Major Reporter: Christian Höltje We use GitHub Organizations to manage our jobs. We found a bug where if a pull request has its source repository/branch deleted (e.g. it was a personal fork and that personal fork was deleted) then that repository stops updating from github. Here is the log from the "Scan Repository Log': Checking pull request #154 ERROR: [Fri Apr 12 16:39:29 EDT 2019] Could not fetch branches from source org.jenkinsci.plugins.github_branch_source.GitHubSCMNavigator::https://github.example.com/api/v3::robert-continuous-delivery::howard java.io.FileNotFoundException: https://github.example.com/api/v3/repos/robert-continuous-delivery/howard/collaborators/null/permission at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:625)
[JIRA] (JENKINS-34019) ANSIColor plugin leaks format onto next line's timestamp
Title: Message Title Christian Höltje commented on JENKINS-34019 Re: ANSIColor plugin leaks format onto next line's timestamp We have an issue where [0m (aka setaf 0) is being printed to the screen at the end of a line with color and timestamps. This messes up the color for all future lines, though the timestamps themselves are okay. 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-24387) Support parsing output of $(tput sgr0)
Title: Message Title Christian Höltje commented on JENKINS-24387 Re: Support parsing output of $(tput sgr0) Hmm... My issue may be JENKINS-34019 instead. [0m (setaf 0) is not the same as [m (setgr0). 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-24387) Support parsing output of $(tput sgr0)
Title: Message Title
Christian Höltje edited a comment on JENKINS-24387
Re: Support parsing output of $(tput sgr0)
Since adding [PR #132|https://github.com/jenkinsci/ansicolor-plugin/pull/132] this issue now becomes very important because each line isn't reset.Now colors are bleeding into other lines.A good example is Cucumber, where text that was previously default/reset becomes red after an error. You can see {{[ 0 0m }} in the output of the error message.
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-24387) Support parsing output of $(tput sgr0)
Title: Message Title
Christian Höltje edited a comment on JENKINS-24387
Re: Support parsing output of $(tput sgr0)
Since adding [PR #132|https://github.com/jenkinsci/ansicolor-plugin/pull/132] this issue now becomes very important because each line isn't reset.Now colors are bleeding into other lines.A good example is Cucumber, where text that was previously default/reset becomes red after an error. You can see {{[0}} in the output of the error message.
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-24387) Support parsing output of $(tput sgr0)
Title: Message Title Christian Höltje commented on JENKINS-24387 Re: Support parsing output of $(tput sgr0) Since adding PR #132 this issue now becomes very important because each line isn't reset. Now colors are bleeding into other lines. A good example is Cucumber, where text that was previously default/reset becomes red after an error. 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-44231) Safely pass args to sh step
Title: Message Title
Christian Höltje commented on JENKINS-44231
Re: Safely pass args to sh step
Michael Slattery That isn't sufficient for all cases, alas. It will work for pure ascii (I think). Depending on the locale, there are many other things that'll cause problems. That's why I use withEnv(){ ... } as a work around until we can pass an array to {{sh.}}
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-52921) Impossible to make a build from bitbucket
Title: Message Title Christian Höltje closed an issue as Not A Defect Check your network. It is unable to reach bitbucket.org. Closing. Jenkins / JENKINS-52921 Impossible to make a build from bitbucket Change By: Christian Höltje Status: Open Closed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53095) publishHTML() doesn't work with directories named 'class'
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-53095 publishHTML() doesn't work with directories named 'class' Change By: Christian Höltje Summary: publishHTML() doesn't work with paths that contain directories named 'class' Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-53095) publishHTML() doesn't work with paths that contain 'class'
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-53095 publishHTML() doesn't work with paths that contain 'class' Issue Type: Bug Assignee: Richard Bywater Components: htmlpublisher-plugin Created: 2018-08-17 13:10 Priority: Minor Reporter: Christian Höltje When using publishHTML() for anything that has class directories, anything in those directories will not work from Jenkins; they show up as 404. Example: The URL https://JENKINS_URL/job/MYJOB/Documentation/class/src/manifest.js~Manifest.html returns a 404 error. This was noted by the esdoc folks and (incorrectly?) attributed to being a Jetty problem. Add Comment
[JIRA] (JENKINS-51426) make autobundle generation period configurable from UI
Title: Message Title Christian Höltje commented on JENKINS-51426 Re: make autobundle generation period configurable from UI It would be nice if this was a UI option instead of a system property. It's hard to know what all system properties are supported (and it can change depending on plugins). Config options in the UI are much more straight-forward. 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-51428) Scripts not permitted error when using createReviewRequests()
Title: Message Title
Christian Höltje updated an issue
Jenkins / JENKINS-51428
Scripts not permitted error when using createReviewRequests()
Change By:
Christian Höltje
When using {{createReviewRequests}} I get:{noformat}Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.jenkinsci.plugins.pipeline.github.PullRequestGroovyObject createReviewRequests java.lang.String java.lang.String).{noformat}
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-51428) Scripts not permitted error when using createReviewRequests()
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-51428 Scripts not permitted error when using createReviewRequests() Issue Type: Bug Assignee: Aaron Whiteside Components: pipeline-github-plugin Created: 2018-05-18 17:00 Environment: Jenkins 2.107.3 pipeline-github-2.0 pipeline-github-lib-1.0 Priority: Minor Reporter: Christian Höltje When using createReviewRequests I get: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.jenkinsci.plugins.pipeline.github.PullRequestGroovyObject createReviewRequests java.lang.String java.lang.String). Add Comment
[JIRA] (JENKINS-51426) support core makes systems with performance problems worse
Title: Message Title Christian Höltje commented on JENKINS-51426 Re: support core makes systems with performance problems worse cc: David Schott 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-51426) support core makes systems with performance problems worse
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-51426 support core makes systems with performance problems worse Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2018-05-18 14:15 Priority: Major Reporter: Christian Höltje Our system had the bug JENKINS-49745 which creates an obscene amount of Log entries by default in Jenkins. The sheer number of log entries were negatively impacting the system (large amounts of memory and disk io were being used). The support core plugin ended up actually making the system unusable when it built its support bundles (zip files) every half hour, eventually killing the system altogether. I would propose two things: Add a configuration option to turn off the automatic building of support bundles. Have support core be smart enough to not try building bundles when the system is under pressure (and put up a banner on $JENKINS_URL/manage to showing bundles were skipped) Add Comment
[JIRA] (JENKINS-42611) Could not initialize class EventDispatcherFactory
Title: Message Title Christian Höltje commented on JENKINS-42611 Re: Could not initialize class EventDispatcherFactory Yeah Tom FENNELLY hasn't been around a while. 1.16 has been pending for more than a year. 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM Since I didn't see this problem in Blue Ocean 1.4.2 but I'm seeing it in 1.5.0 I went looking for changes in Blue Ocean that may have triggered this problem... I found PR #1667 by Vivek Pandey. It was to fix JENKINS-48820. I doubt it caused this problem, but maybe it made it worse? 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-51057 EventDispatcher and ConcurrentLinkedQueue ate my JVM Change By: Christian Höltje Labels: leak memory memory-leak 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title
Christian Höltje commented on JENKINS-51057
Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM
I finally got VirtualVM working reasonably well (using lots of RAM and a RAM Disk for temp files). I found that there are 0 instances of org.jenkinsci.plugins.ssegateway.EventHistoryStore and 0 instances of org.jenkinsci.plugins.ssegateway.sse.EventDispatcher. Is it possible that the Retry objects are not being reclaimed by GC? When I look at the objects in VirtualVM the Retry object has a reference (item) to a ConcurrentLinkedQueue$Node object. The Node object has a reference (item) to the Retry object plus a reference to the next {{Node} in the queue.
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-50348) Why does "Pipeline: Groovy" require "Support Core"?
Title: Message Title Christian Höltje commented on JENKINS-50348 Re: Why does "Pipeline: Groovy" require "Support Core"? I was able to remove support-core by stopping Jenkins, removing the support-core directory and .jpi files from $JENKINS_HOME/plugins. This still doesn't explain why the Web UI is incorrectly marking it as "required" by "Pipeline: Groovy". 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM I managed to use jvirtualvm to look at the .hprof from the initial comment and it was our friend EventDispatcher$Retry and $ConcurrentLinkedQueue$Node using up 90% of the memory. 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM Looking in $JENKINS_HOME/logs/sse-events/ I see 16 .json files in jobs and 108 .json files in pipeline. And they change frequently (e.g. they are now, a minute later, 6 and 54). Is there another place I can look at why there are some many Retry objects? 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM This morning: Class Size (Kb) % size Instances % instances Source org.jenkinsci.plugins.ssegateway.sse.EventDispatcher$Retry 283,979 5 9,087,330 10 java.util.concurrent.ConcurrentLinkedQueue$Node 214,241 4 9,140,981 10 Is there a way I can find out what's in the queues to track what's causing the Retry to happen? Add Comment
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM Some more events from our logs: May 03, 2018 1:36:00 PM FINE org.jenkinsci.plugins.ssegateway.sse.EventDispatcher doDispatch Error dispatching event to SSE channel. Write failed. May 03, 2018 1:36:36 PM FINE org.jenkinsci.plugins.ssegateway.sse.EventDispatcher doDispatch Error dispatching event to SSE channel. Write failed. May 03, 2018 1:36:39 PM FINE org.jenkinsci.plugins.ssegateway.sse.EventDispatcher processRetries Error dispatching retry event to SSE channel. Write failed. Dispatcher jenkins-blueocean-core-js-1525286577663-o9g92 (1006446612). May 03, 2018 1:36:39 PM FINE org.jenkinsci.plugins.ssegateway.sse.EventDispatcher processRetries Error dispatching retry event to SSE channel. Write failed. Dispatcher jenkins-blueocean-core-js-1525286577663-o9g92 (1006446612). May 03, 2018 1:36:39 PM FINE org.jenkinsci.plugins.ssegateway.sse.EventDispatcher processRetries Error dispatching retry event to SSE channel. Write failed. Dispatcher jenkins-blueocean-core-js-1525286577663-o9g92 (1006446612). 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
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM I got further when using the non-alpine openjdk image. Still doesn't build, but it is due to tests failing. $ docker run --rm -it -v maven-repo:/root/.m2 -v $PWD:/src:rw -w /src maven:3-jdk-8 mvn verify ... Results : Failed tests: org.jenkinsci.plugins.ssegateway.EventHistoryStoreTest.test_autoDeleteOnExpire(org.jenkinsci.plugins.ssegateway.EventHistoryStoreTest) Run 1: EventHistoryStoreTest.test_autoDeleteOnExpire:119 expected:<100> but was:<50> Run 2: EventHistoryStoreTest.test_autoDeleteOnExpire:119 expected:<100> but was:<50> Run 3: EventHistoryStoreTest.test_autoDeleteOnExpire:119 expected:<100> but was:<50> Run 4: EventHistoryStoreTest.test_autoDeleteOnExpire:119 expected:<100> but was:<50> Run 5: EventHistoryStoreTest.test_autoDeleteOnExpire:119 expected:<100> but was:<50> org.jenkinsci.plugins.ssegateway.EventHistoryStoreTest.test_delete_stale_events(org.jenkinsci.plugins.ssegateway.EventHistoryStoreTest) Run 1: EventHistoryStoreTest.test_delete_stale_events:69 Run 2: EventHistoryStoreTest.test_delete_stale_events:69 Run 3: EventHistoryStoreTest.test_delete_stale_events:69 Run 4: EventHistoryStoreTest.test_delete_stale_events:69 Run 5: EventHistoryStoreTest.test_delete_stale_events:69 Tests run: 12, Failures: 2, Errors: 0, Skipped: 0 ... [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project sse-gateway: There are test failures. ... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM There are a lot of changes/improvements in sse-gateway (mostly by R. Tyler Croy) since 1.15 was released (back in Jan 16th, 2017). In the logs, I see a commit titled message leaks which sounds interesting. I tried compiling the master branch and I get errors: $ docker run --rm -it -v maven-repo:/root/.m2 -v $PWD:/src:rw -w /src maven:3-jdk-8-alpine mvn verify ... [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.0:npm (npm install) on project sse-gateway: Failed to run task: 'npm install' failed. java.io.IOException: Cannot run program "/src/node/node" (in directory "/src"): error=2, No such file or directory -> [Help 1] 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM And now its at: Class Size (Kb) % size Instances % instances Source org.jenkinsci.plugins.ssegateway.sse.EventDispatcher$Retry 105,174 3 3,365,570 4 java.util.concurrent.ConcurrentLinkedQueue$Node 79,051 2 3,372,854 4 Add Comment
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM In our logs, we're see messages like: May 02, 2018 1:04:41 PM WARNING org.jenkinsci.plugins.ssegateway.sse.EventDispatcher unsubscribe Invalid SSE unsubscribe configuration. No active subscription matching filter: May 02, 2018 1:04:41 PM WARNING org.jenkinsci.plugins.ssegateway.sse.EventDispatcher unsubscribe Invalid SSE unsubscribe configuration. No active subscription matching filter: May 02, 2018 1:04:41 PM WARNING org.jenkinsci.plugins.ssegateway.sse.EventDispatcher unsubscribe Invalid SSE unsubscribe configuration. No active subscription matching filter: May 02, 2018 1:04:41 PM WARNING org.jenkinsci.plugins.ssegateway.sse.EventDispatcher unsubscribe Invalid SSE unsubscribe configuration. No active subscription matching filter: Could that be related? 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title
Christian Höltje edited a comment on JENKINS-51057
Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM
Our Jenkins server has been up 23 hours and we're already seeing large numbers of the EventDispacher objects: || Class|| Size (Kb)|| % size|| Instances|| % instances|| Source|||[ int[]|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=int]|1,056,446|26|868,075|1| ||[char[]|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=char]|447,243|11|2,837,232|4| ||[java.lang.Object[]|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=java.lang.Object]|250,560|6|4,813,216|7| ||[java.lang.StackTraceElement|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=java.lang.StackTraceElement]|239,176|6|7,653,653|11| ||[byte[]|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=byte]|165,917|4|581,581|0| ||[java.lang.String|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=java.lang.String]|146,722|3|6,260,161|9| ||[ org.jenkinsci.plugins.ssegateway.sse.EventDispatcher$Retry|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=org.jenkinsci.plugins.ssegateway.sse.EventDispatcher$Retry]|96,964|2|3,102,853|4| ||[java.util.concurrent.ConcurrentLinkedQueue$Node|https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=java.util.concurrent.ConcurrentLinkedQueue$Node]|73,163|1|3,121,633|4| | It isn't a problem (yet) but this is alarming. Our other, Jenkins server has no references to {{EventDispatcher$Retry}} in the memory histogram, even when expanding details.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM Our Jenkins server has been up 23 hours and we're already seeing large numbers of the EventDispacher objects: Class Size (Kb) % size Instances % instances Source [int[] https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=int] 1,056,446 26 868,075 1 [char[] https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=char] 447,243 11 2,837,232 4 [java.lang.Object[] https://ghenkins.bigdatalab.ibm.com/monitoring?part=source=java.lang.Object] 250,560 6 4,813,216 7 java.lang.StackTraceElement 239,176 6
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-51057 EventDispatcher and ConcurrentLinkedQueue ate my JVM Issue Type: Bug Assignee: Tom FENNELLY Components: sse-gateway-plugin Created: 2018-05-01 19:36 Environment: Jenkins 2.107.2 ace-editor-1.1 analysis-core-1.95 ansicolor-0.5.2 ant-1.8 antisamy-markup-formatter-1.5 apache-httpcomponents-client-4-api-4.5.3-2.1 artifactory-2.15.1 authentication-tokens-1.3 badge-1.4 blueocean-1.5.0 blueocean-autofavorite-1.2.2 blueocean-bitbucket-pipeline-1.5.0 blueocean-commons-1.5.0 blueocean-config-1.5.0 blueocean-core-js-1.5.0 blueocean-dashboard-1.5.0 blueocean-display-url-2.2.0 blueocean-events-1.5.0 blueocean-git-pipeline-1.5.0 blueocean-github-pipeline-1.5.0 blueocean-i18n-1.5.0 blueocean-jira-1.5.0 blueocean-jwt-1.5.0 blueocean-personalization-1.5.0 blueocean-pipeline-api-impl-1.5.0 blueocean-pipeline-editor-1.5.0 blueocean-pipeline-scm-api-1.5.0 blueocean-rest-1.5.0 blueocean-rest-impl-1.5.0 blueocean-web-1.5.0 bouncycastle-api-2.16.2 branch-api-2.0.19 build-timeout-1.19 build-user-vars-plugin-1.5 buildtriggerbadge-2.9 checkstyle-3.50 cli-commander-0.3 cloudbees-bitbucket-branch-source-2.2.10 cloudbees-folder-6.4 clover-4.9.0 cobertura-1.12 command-launcher-1.2 conditional-buildstep-1.3.6 config-file-provider-2.18 copyartifact-1.39.1 credentials-2.1.16 credentials-binding-1.16 cucumber-reports-3.16.0 cvs-2.14 dashboard-view-2.9.11 display-url-api-2.2.0 docker-commons-1.11 docker-workflow-1.15.1 durable-task-1.22 email-ext-2.62 embeddable-build-status-1.9 envinject-2.1.5 envinject-api-1.5 extended-read-permission-2.0 external-monitor-job-1.7 favorite-2.3.1 findbugs-4.72 git-3.8.0 git-client-2.7.1 git-server-1.7 github-1.29.0 github-api-1.90 github-branch-source-2.3.3 github-oauth-0.29 gradle-1.28 groovy-2.0 groovy-postbuild-2.4 handlebars-1.1.1 handy-uri-templates-2-api-2.1.6-1.0 htmlpublisher-1.16 http_request-1.8.22 ibm-application-security-1.1.2 icon-shim-2.0.3 ivy-1.28 jackson2-api-2.8.11.1 jacoco-3.0.1 javadoc-1.4 jenkins-design-language-1.5.0 jira-2.5.1 job-dsl-1.69 jquery-detached-1.2.1 jsch-0.1.54.2 junit-1.24 ldap-1.20 lockable-resources-2.2 mailer-1.21 mapdb-api-1.0.9.0 matrix-auth-2.2 matrix-project-1.13 maven-plugin-3.1.2 mercurial-2.3 metrics-3.1.2.11 metrics-graphite-3.0.0 modernstatus-1.2 momentjs-1.1.1 monitoring-1.72.0 pam-auth-1.3 parameterized-trigger-2.35.2 pegdown-formatter-1.3 performance-3.8 pipeline-build-step-2.7 pipeline-github-2.0 pipeline-github-lib-1.0 pipeline-graph-analysis-1.6
[JIRA] (JENKINS-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title Christian Höltje commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found I've read through a bunch of them. This is obviously a kind of error that can exist/be-caused-by many plugins. That's why it should be fixed in Core across the board. 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title
Christian Höltje edited a comment on JENKINS-50867
Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
It is running in a docker container, so it isn't in an app server. It's using the war directly:{code}java $JAVA_OPTS -jar /usr/share/jenkins/jenkins.war $JENKINS_OPTS "$@"{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-50875) multiple jobDSL() pipeline steps destroys all but the last
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-50875 multiple jobDSL() pipeline steps destroys all but the last Change By: Christian Höltje Summary: multiple jobDSL() pipeline steps clobber each other. destroys all but the last 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-50875) multiple jobDSL() pipeline steps clobber each other.
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-50875 multiple jobDSL() pipeline steps clobber each other. Change By: Christian Höltje Priority: Minor Major 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title Christian Höltje commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found Here are the flags passed: -Djava.awt.headless=true -Xms4g -Xmx4g -Dhudson.model.LoadStatistics.clock=3000 -Dhudson.model.LoadStatistics.decay=0.0 -Dhudson.slaves.NodeProvisioner.recurrencePeriod=3000 -Dhudson.slaves.NodeProvisioner.MARGIN=99 -Dhudson.slaves.NodeProvisioner.MARGIN0=0.99 -Dhudson.slaves.NodeProvisioner.MARGIN_DECAY=0.0 -XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent -XX:+ParallelRefProcEnabled -XX:+UseStringDeduplication -XX:+UnlockDiagnosticVMOptions -XX:G1SummarizeRSetStatsPeriod=1 -Xloggc:/tmp/gc-%t.log -XX:NumberOfGCLogFiles=5 -XX:+UseGCLogFileRotation -XX:GCLogFileSize=20m -DexecutableWar.jetty.sessionIdCookieName=HYBORIA 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title Christian Höltje commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found It is running in a docker container, so it isn't in an app server. 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title Christian Höltje commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found I was able to be reproduced 100% until I made the system properties change. I'm afraid to clear that system properties because this is a production system that really can't afford anymore down time. It started as an intermediate thing, but became higher and higher probability until yesterday when it was 100%. 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title Christian Höltje edited a comment on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found I was able to be reproduced reproduce it 100% until I made the system properties change.I'm afraid to clear that system properties property because this is a production system that really can't afford anymore down time.It started as an intermediate thing, but became higher and higher probability until yesterday when it was 100%. 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-50875) multiple jobDSL() pipeline steps clobber each other.
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-50875 multiple jobDSL() pipeline steps clobber each other. Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-04-18 19:48 Environment: Jenkins 2.89.4 ace-editor-1.1 ansicolor-0.5.2 ant-1.8 antisamy-markup-formatter-1.5 apache-httpcomponents-client-4-api-4.5.3-2.1 artifactory-2.15.1 authentication-tokens-1.3 badge-1.2 blueocean-1.4.2 blueocean-autofavorite-1.2.2 blueocean-bitbucket-pipeline-1.4.2 blueocean-commons-1.4.2 blueocean-config-1.4.2 blueocean-core-js-1.4.2 blueocean-dashboard-1.4.2 blueocean-display-url-2.2.0 blueocean-events-1.4.2 blueocean-git-pipeline-1.4.2 blueocean-github-pipeline-1.4.2 blueocean-i18n-1.4.2 blueocean-jira-1.4.2 blueocean-jwt-1.4.2 blueocean-personalization-1.4.2 blueocean-pipeline-api-impl-1.4.2 blueocean-pipeline-editor-1.4.2 blueocean-pipeline-scm-api-1.4.2 blueocean-rest-1.4.2 blueocean-rest-impl-1.4.2 blueocean-web-1.4.2 bouncycastle-api-2.16.2 branch-api-2.0.18 build-keeper-plugin-1.3 build-pipeline-plugin-1.5.8 buildtriggerbadge-2.9 cli-commander-0.3 cloudbees-bitbucket-branch-source-2.2.10 cloudbees-folder-6.4 command-launcher-1.2 conditional-buildstep-1.3.6 config-file-provider-2.18 copyartifact-1.39.1 credentials-2.1.16 credentials-binding-1.16 cucumber-reports-3.15.0 cvs-2.14 display-url-api-2.2.0 docker-commons-1.11 docker-java-api-3.0.14 docker-plugin-1.1.3 docker-workflow-1.15.1 durable-task-1.22 email-ext-2.62 extended-read-permission-2.0 extensible-choice-parameter-1.5.0 external-monitor-job-1.7 favorite-2.3.1 ghprb-1.40.0 git-3.8.0 git-client-2.7.1 git-server-1.7 github-1.29.0 github-api-1.90 github-branch-source-2.3.3 github-oauth-0.29 gradle-1.28 groovy-postbuild-2.4 handlebars-1.1.1 handy-uri-templates-2-api-2.1.6-1.0 htmlpublisher-1.15 http_request-1.8.22 ibm-ucdeploy-publisher-1.2.7 icon-shim-2.0.3 ivy-1.28 jackson2-api-2.8.11.1 jacoco-3.0.1 javadoc-1.4 jenkins-design-language-1.4.2 jira-2.5 job-dsl-1.68 jobConfigHistory-2.18 jquery-1.12.4-0 jquery-detached-1.2.1 jsch-0.1.54.2 junit-1.24 kubernetes-1.5 kubernetes-credentials-0.3.1 label-linked-jobs-5.1.2 ldap-1.20 lockable-resources-2.2 mailer-1.21 mapdb-api-1.0.9.0 mask-passwords-2.11.0 matrix-auth-2.2 matrix-project-1.12 maven-plugin-3.1.2 mercurial-2.3 metrics-3.1.2.11 momentjs-1.1.1 monitoring-1.71.0 next-build-number-1.5 pam-auth-1.3 parameterized-trigger-2.35.2 pegdown-formatter-1.3 performance-3.6 pipeline-build-step-2.7 pipeline-github-lib-1.0 pipeline-graph-analysis-1.6
[JIRA] (JENKINS-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-50867 SAX2 driver class org.apache.xerces.parsers.SAXParser not found Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-04-18 15:53 Environment: Jenkins 2.89.4 ace-editor-1.1 ansicolor-0.5.2 ant-1.8 antisamy-markup-formatter-1.5 apache-httpcomponents-client-4-api-4.5.3-2.1 artifactory-2.15.1 authentication-tokens-1.3 badge-1.2 blueocean-1.4.2 blueocean-autofavorite-1.2.2 blueocean-bitbucket-pipeline-1.4.2 blueocean-commons-1.4.2 blueocean-config-1.4.2 blueocean-core-js-1.4.2 blueocean-dashboard-1.4.2 blueocean-display-url-2.2.0 blueocean-events-1.4.2 blueocean-git-pipeline-1.4.2 blueocean-github-pipeline-1.4.2 blueocean-i18n-1.4.2 blueocean-jira-1.4.2 blueocean-jwt-1.4.2 blueocean-personalization-1.4.2 blueocean-pipeline-api-impl-1.4.2 blueocean-pipeline-editor-1.4.2 blueocean-pipeline-scm-api-1.4.2 blueocean-rest-1.4.2 blueocean-rest-impl-1.4.2 blueocean-web-1.4.2 bouncycastle-api-2.16.2 branch-api-2.0.18 build-keeper-plugin-1.3 build-pipeline-plugin-1.5.8 buildtriggerbadge-2.9 cli-commander-0.3 cloudbees-bitbucket-branch-source-2.2.10 cloudbees-folder-6.4 command-launcher-1.2 conditional-buildstep-1.3.6 config-file-provider-2.18 copyartifact-1.39.1 credentials-2.1.16 credentials-binding-1.16 cucumber-reports-3.15.0 cvs-2.14 display-url-api-2.2.0 docker-commons-1.11 docker-java-api-3.0.14 docker-plugin-1.1.3 docker-workflow-1.15.1 durable-task-1.22 email-ext-2.62 extended-read-permission-2.0 extensible-choice-parameter-1.5.0 external-monitor-job-1.7 favorite-2.3.1 ghprb-1.40.0 git-3.8.0 git-client-2.7.1 git-server-1.7 github-1.29.0 github-api-1.90 github-branch-source-2.3.3 github-oauth-0.29 gradle-1.28 groovy-postbuild-2.4 handlebars-1.1.1 handy-uri-templates-2-api-2.1.6-1.0 htmlpublisher-1.15 http_request-1.8.22 ibm-ucdeploy-publisher-1.2.7 icon-shim-2.0.3 ivy-1.28 jackson2-api-2.8.11.1 jacoco-3.0.1 javadoc-1.4 jenkins-design-language-1.4.2 jira-2.5 job-dsl-1.68 jobConfigHistory-2.18 jquery-1.12.4-0 jquery-detached-1.2.1 jsch-0.1.54.2 junit-1.24 kubernetes-1.5 kubernetes-credentials-0.3.1 label-linked-jobs-5.1.2 ldap-1.20 lockable-resources-2.2 mailer-1.21 mapdb-api-1.0.9.0 mask-passwords-2.11.0 matrix-auth-2.2 matrix-project-1.12 maven-plugin-3.1.2 mercurial-2.3 metrics-3.1.2.11 momentjs-1.1.1 monitoring-1.71.0 next-build-number-1.5 pam-auth-1.3 parameterized-trigger-2.35.2 pegdown-formatter-1.3 performance-3.6 pipeline-build-step-2.7 pipeline-github-lib-1.0 pipeline-graph-analysis-1.6
[JIRA] (JENKINS-50348) Why does "Pipeline: Groovy" require "Support Core"?
Title: Message Title Christian Höltje commented on JENKINS-50348 Re: Why does "Pipeline: Groovy" require "Support Core"? If it is optional, why can I not uncheck the box next to support-core to disable it? Maybe the bug is that "optional" items cannot be disabled in the plugin manager? 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-45120) GitHub plugin doesn't automatically add webhooks to GitHub for Pipeline job
Title: Message Title Christian Höltje commented on JENKINS-45120 Re: GitHub plugin doesn't automatically add webhooks to GitHub for Pipeline job It looks like the pipeline jobs (flow-definitions) don't understand that the github repository is inside the section of the config. On my system it keeps trying to manage a hook on https://github.com/foo/bar when the project I'm working on is in https://github.com/foo/barbaz. It is driving me nuts. 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-50348) Why does "Pipeline: Groovy" require "Support Core"?
Title: Message Title Christian Höltje commented on JENKINS-50348 Re: Why does "Pipeline: Groovy" require "Support Core"? Jesse Glick Is there any reason you set Support Core as required (instead of optional) in JENKINS-31840 or was it an accident? 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-50348) Why does "Pipeline: Groovy" require "Support Core"?
Title: Message Title Christian Höltje commented on JENKINS-50348 Re: Why does "Pipeline: Groovy" require "Support Core"? It looks like it was added for the issue JENKINS-31840. I'm not sure why it is required and not optional, though. 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-50348) Why does "Pipeline: Groovy" require "Support Core"?
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-50348 Why does "Pipeline: Groovy" require "Support Core"? Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-03-22 19:54 Environment: Pipeline:Groovy version 2.45 Priority: Minor Reporter: Christian Höltje Why does the "Pipeline: Groovy" plugin (part of workflow-cps) require the "Support Core" plugin? Usually "Support Core" is optional. I ask because "Support Core" can kill performance on a system if the system is very busy and generates a lot of logging information. Add Comment
[JIRA] (JENKINS-50179) parallel step with failFast set to false, parallel branch 'foo' kills other parallel branch 'bar' when foo times-out.
Title: Message Title Christian Höltje commented on JENKINS-50179 Re: parallel step with failFast set to false, parallel branch 'foo' kills other parallel branch 'bar' when foo times-out. I have a theory: timeouts are usually implemented via asking the OS to send a SIGALRM at some point in the future (e.g. setitimer() or alarm()). The problem with signals is that they effect all the (Java) threads in a process. If each parallel sub-executor have their own error and timeout handlers, then a SIGALRM will kill them all. 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-50179) parallel step with failFast set to false, parallel branch 'foo' kills other parallel branch 'bar' when foo times-out.
Title: Message Title
Christian Höltje commented on JENKINS-50179
Re: parallel step with failFast set to false, parallel branch 'foo' kills other parallel branch 'bar' when foo times-out.
It fails the same way with the declarative pipeline's parallel stages.
pipeline {
agent any
environment {
TERM = "xterm-256color"
}
options {
timestamps()
timeout(time: 3, unit: 'MINUTES')
ansiColor('xterm')
}
stages {
stage('Setup'){
failFast false
parallel {
stage('foo') {
steps {
script {
try {
timeout(time: 3, unit: 'SECONDS') {
try {
sh "sleep 90"
} catch(ex) {
echo "NARF foo inside: ${ex}"
throw ex
} finally {
echo "NARF foo inside finally"
}
}
} catch(ex) {
echo "NARF foo outside: ${ex}"
throw ex
} finally {
echo "NARF foo outside finally"
}
echo "Done with foo"
}
}
}
stage('bar') {
steps {
script {
try {
sh "sleep 10"
} catch(ex) {
echo "NARF bar: ${ex}"
throw ex
} finally {
echo "NARF bar finally"
}
echo "Done with bar"
}
}
}
}
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49749) progress-bar isn't showing an estimate
Title: Message Title Christian Höltje commented on JENKINS-49749 Re: progress-bar isn't showing an estimate I figured it was a duplicate, but I couldn't find any. Probably because I didn't use the right term(s). 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-49745) Too many CrumbFilter log entries per second
Title: Message Title
Christian Höltje edited a comment on JENKINS-49745
Re: Too many CrumbFilter log entries per second
I'm glad my extra research helped identify the culprit (dashboard-view).I'm not familiar enough with Jelly to know exactly what's going on but it looks like some of the problems are:* It doesn't check the return value (or {{try}}/{{catch}} if done that way) in case there is an error (e.g. a 403). This means there is nothing to bounce the page to the login page (if it requires auth) or refetch a CSRF token. * It fetches everything, even if only some items are needed.* This stuff, if everything is needed, could be returned as a single struct. * Did I miss anything? I'm not familiar with how the CSRF stuff is implemented in Jenkins. It also seems wrong that if the permission for Jenkins are such that anyone (anonymous) can view a URL, then {{GET}} requests for that URL shouldn't need a CSRF token and should never raise a 403.
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-49745) Too many CrumbFilter log entries per second
Title: Message Title Christian Höltje commented on JENKINS-49745 Re: Too many CrumbFilter log entries per second I'm glad my extra research helped identify the culprit (dashboard-view). I'm not familiar enough with Jelly to know exactly what's going on but it looks like some of the problems are: It doesn't check the return value (or try/catch if done that way) in case there is an error (e.g. a 403). It fetches everything, even if only some items are needed. This stuff, if everything is needed, could be returned as a single struct. It also seems wrong that if the permission for Jenkins are such that anyone (anonymous) can view a URL, then GET requests for that URL shouldn't need a CSRF token and should never raise a 403. 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-49749) progress-bar isn't showing an estimate
Title: Message Title Christian Höltje edited a comment on JENKINS-49749 Re: progress-bar isn't showing an estimate It may be the case that the part that does the estimation is broken Possibly related? https://groups . The progress bar on the build page is only showing the striped-progress bar (the one it uses when it doesn't know what the duration is) google . This is on a build that has a very consistent run time of 16 minutes. com/forum/#!topic/jenkinsci-users/BdKmRrkjir4 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-49749) progress-bar isn't showing an estimate
Title: Message Title
Christian Höltje updated an issue
Jenkins / JENKINS-49749
progress-bar isn't showing an estimate
Change By:
Christian Höltje
Comment:
Also, the CSS rules for the {{progress-unknown.gif}} or {{progress-unknown-red.gif}} isn't working. I think it needs a {{td}} at the end of the selectors:https://github.com/jenkinsci/jenkins/blob/master/war/src/main/webapp/css/style.css#L1601andhttps://github.com/jenkinsci/jenkins/blob/master/war/src/main/webapp/css/style.css#L1617
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-49749) progress-bar isn't showing an estimate
Title: Message Title
Christian Höltje updated an issue
Jenkins / JENKINS-49749
progress-bar isn't showing an estimate
Change By:
Christian Höltje
The progress bars for builds inside the "Build Executor Status" sidebar are missing all (or nearly all) showing unknown progress . I don't see any errors in It is as if the _javascript_ console estimating is broken . The HTML looks like this:{noformat} {noformat}I find the {{class=unknown}} suspicious.
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-49749) progress-bar isn't showing an estimate
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-49749 progress-bar isn't showing an estimate Change By: Christian Höltje Comment: I filed a fix for the CSS here: https://github.com/jenkinsci/jenkins/pull/3314But there is still a problem with _most_ of my builds having no progress meter (e.g. they are unknown). 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-49749) progress-bar isn't showing an estimate
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-49749 progress-bar isn't showing an estimate Change By: Christian Höltje Summary: progress-bar isn't shown anymore showing an estimate 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-49749) progress-bar isn't shown anymore
Title: Message Title Christian Höltje commented on JENKINS-49749 Re: progress-bar isn't shown anymore I filed a fix for the CSS here: https://github.com/jenkinsci/jenkins/pull/3314 But there is still a problem with most of my builds having no progress meter (e.g. they are unknown). 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-49749) progress-bar isn't shown anymore
Title: Message Title Christian Höltje commented on JENKINS-49749 Re: progress-bar isn't shown anymore Also, the CSS rules for the progress-unknown.gif or progress-unknown-red.gif isn't working. I think it needs a td at the end of the selectors: https://github.com/jenkinsci/jenkins/blob/master/war/src/main/webapp/css/style.css#L1601 and https://github.com/jenkinsci/jenkins/blob/master/war/src/main/webapp/css/style.css#L1617 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-49749) progress-bar isn't shown anymore
Title: Message Title Christian Höltje commented on JENKINS-49749 Re: progress-bar isn't shown anymore It may be the case that the part that does the estimation is broken. The progress bar on the build page is only showing the striped-progress bar (the one it uses when it doesn't know what the duration is). This is on a build that has a very consistent run time of 16 minutes. 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-49749) progress-bar isn't shown anymore
Title: Message Title
Christian Höltje updated an issue
Jenkins / JENKINS-49749
progress-bar isn't shown anymore
Change By:
Christian Höltje
The progress bars for builds inside the "Build Executor Status" sidebar are missing.I don't see any errors in the _javascript_ console.The HTML looks like this:{noformat}watson-engagement-advisor/job/conversation-vault/job/ develop/244/console" class="progress-bar " title="Started 1 hr 27 min ago Estimated remaining time: N/A"> {noformat}I find the {{class=unknown}} suspicious.
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-49749) progress-bar isn't shown anymore
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-49749 progress-bar isn't shown anymore Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-02-26 16:20 Environment: Jenkins 2.89.4 ace-editor: 1.1 analysis-core: 1.94 ansicolor: 0.5.2 antisamy-markup-formatter: 1.5 ant: 1.8 apache-httpcomponents-client-4-api: 4.5.3-2.1 artifactory: 2.14.0 authentication-tokens: 1.3 blueocean-autofavorite: 1.2.1 blueocean-bitbucket-pipeline: 1.4.2 blueocean-commons: 1.4.2 blueocean-config: 1.4.2 blueocean-core-js: 1.4.2 blueocean-dashboard: 1.4.2 blueocean-display-url: 2.2.0 blueocean-events: 1.4.2 blueocean-github-pipeline: 1.4.2 blueocean-git-pipeline: 1.4.2 blueocean-i18n: 1.4.2 blueocean-jira: 1.4.2 blueocean-jwt: 1.4.2 blueocean: 1.4.2 blueocean-personalization: 1.4.2 blueocean-pipeline-api-impl: 1.4.2 blueocean-pipeline-editor: 1.4.2 blueocean-pipeline-scm-api: 1.4.2 blueocean-rest-impl: 1.4.2 blueocean-rest: 1.4.2 blueocean-web: 1.4.2 bouncycastle-api: 2.16.2 branch-api: 2.0.18 build-timeout: 1.19 buildtriggerbadge: 2.9 build-user-vars-plugin: 1.5 checkstyle: 3.50 cli-commander: 0.3 cloudbees-bitbucket-branch-source: 2.2.10 cloudbees-folder: 6.3 command-launcher: 1.2 conditional-buildstep: 1.3.6 config-file-provider: 2.17 copyartifact: 1.39 credentials-binding: 1.15 credentials: 2.1.16 cucumber-reports: 3.14.0 cvs: 2.13 dashboard-view: 2.9.11 display-url-api: 2.2.0 docker-commons: 1.11 docker-workflow: 1.15.1 durable-task: 1.18 email-ext: 2.61 embeddable-build-status: 1.9 envinject-api: 1.5 envinject: 2.1.5 extended-read-permission: 2.0 external-monitor-job: 1.7 favorite: 2.3.1 findbugs: 4.72 git-client: 2.7.1 github-api: 1.90 github-branch-source: 2.3.2 github: 1.29.0 github-oauth: 0.29 git: 3.7.0 git-server: 1.7 gradle: 1.28 groovy: 2.0 groovy-postbuild: 2.3.1 handlebars: 1.1.1 handy-uri-templates-2-api: 2.1.6-1.0 htmlpublisher: 1.14 icon-shim: 2.0.3 ivy: 1.28 jackson2-api: 2.8.11.1 jacoco: 3.0.1 javadoc: 1.4 jenkins-design-language: 1.4.2 jira: 2.5.1 job-dsl: 1.68 jquery-detached: 1.2.1 jsch: 0.1.54.2 junit: 1.24 ldap: 1.20 lockable-resources: 2.1 mailer: 1.20 mapdb-api: 1.0.9.0 matrix-auth: 2.2 matrix-project: 1.12 maven-plugin: 3.1 mercurial: 2.2 metrics-graphite: 3.0.0 metrics: 3.1.2.10 modernstatus: 1.2 momentjs: 1.1.1 monitoring: 1.71.0 pam-auth: 1.3 parameterized-trigger: 2.35.2 pegdown-formatter: 1.3 performance: 3.5 pipeline-build-step: 2.7 pipeline-github-lib: 1.0 pipeline-graph-analysis: 1.6 pipeline-input-step: 2.8 pipeline-maven: 3.3.2
[JIRA] (JENKINS-49745) Too many CrumbFilter log entries per second
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-49745 Too many CrumbFilter log entries per second Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-02-26 15:24 Environment: Jenkins 2.89.4 Priority: Major Reporter: Christian Höltje The hudson.security.csrf.CrumbFilter generates so many log entries it causes parts of Jenkins to stall until the rate of log messages slows down. 2018-02-24 05:17:10.406+ [id=20011] WARNING hudson.security.csrf.CrumbFilter#doFilter: Found invalid crumb 418a20cb74b577eaae393aa8ac0e. Will check remaining parameters for a valid one... 2018-02-24 05:17:10.406+ [id=20011] WARNING hudson.security.csrf.CrumbFilter#doFilter: No valid crumb was included in request for /$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getOnlineSlaves by joecool. Returning 403. The amount of these logs was causing my Jenkins to stop working: The executors were not being released by jobs (even after they were done running) until the log entry could be written. I checked through the logs and all the entries I have are for these URLs (there could be more, due to the logs rolling so quick): /$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getDisconnectedSlaves /$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getOfflineSlaves
[JIRA] (JENKINS-40344) Leaving a page open past session expiry fills the logs on the master with "Found invalid crumb" warnings
Title: Message Title
Christian Höltje edited a comment on JENKINS-40344
Re: Leaving a page open past session expiry fills the logs on the master with "Found invalid crumb" warnings
This isn't really fixed. I have had to resort to changing the log levels (the URL /log/levels) to prevent it from logging.I'm seeing things like this (from the support logs, because it was more informative):{noformat}2018-02-24 05:17:10.406+ [id=20011] WARNING hudson.security.csrf.CrumbFilter#doFilter: Found invalid crumb 418a20cb74b577eaae393aa8ac0e. Will check remaining parameters for a valid one... 2018-02-24 05:17:10.406+ [id=20011] WARNING hudson.security.csrf.CrumbFilter#doFilter: No valid crumb was included in request for /$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getOnlineSlaves by joecool. Returning 403.{noformat} The amount of these logs was causing my Jenkins to stop working: The executors were not being released by jobs (even after they were done running) until the log entry could be written.I checked through the logs and all the entries I have are for these URLs (there could be more, due to the logs rolling so quick): * {{/$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getDisconnectedSlaves}} * {{/$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getOfflineSlaves}} * {{/$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getOnlineSlaves}} * {{/$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getRunningJobs}} * {{/$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getSlaves}} * {{/$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getTasksInQueue}}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-40344) Leaving a page open past session expiry fills the logs on the master with "Found invalid crumb" warnings
Title: Message Title Christian Höltje commented on JENKINS-40344 Re: Leaving a page open past session expiry fills the logs on the master with "Found invalid crumb" warnings The Jenkins version is 2.89.4. I'll open a new ticket for my case. Thanks! 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-49729) Deleted jobs and builds look the same as everything else
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-49729 Deleted jobs and builds look the same as everything else Change By: Christian Höltje Labels: ui UI UX usability 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-49729) Deleted jobs and builds look the same as everything else
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-49729 Deleted jobs and builds look the same as everything else Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-02-25 03:44 Environment: Jenkins ver. 2.89.4 github-branch-source 2.3.2 Priority: Minor Reporter: Christian Höltje When using the GitHub Organization Folder; if a branch or repository is scheduled to be deleted, there is no visual indication when visiting a sub-page. Example: Set the Org Folder's configuration "Days to keep old items" under "Discard old items" to 1 or higher (I use 4 days) In GitHub create a branch with a Jenkinsfile Wait for it to be built. Once built, delete the branch. In the repository page in Jenkins, it'll show the branch as being struck-through to mark it as pending deletion. Click on the branch. Note how the page (which is for the branch job that will be deleted) looks identical to a page that isn't going to be deleted. Click on the build Note how it is also doesn't show that is is about to be deleted. I would expect that there would be some indicator on the job, build, or console page that the repository, branch, or build is going to be deleted. I have spent hours, multiple times, trying to figure out where the "replay" link went or where build "21" went away, when it was actually not 21 but was PR #1,
[JIRA] (JENKINS-49729) Deleted jobs and builds look the same as everything else
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-49729 Deleted jobs and builds look the same as everything else Change By: Christian Höltje Labels: ui 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-42681) "Replay" editor should be resizable
Title: Message Title Christian Höltje commented on JENKINS-42681 Re: "Replay" editor should be resizable I believe the replay editor is actually the ACE editor. Is this a global ACE editor problem? Or just here? 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-35801) Replay of a run with modified Jenkinsfile
Title: Message Title Christian Höltje commented on JENKINS-35801 Re: Replay of a run with modified Jenkinsfile Isn't this done as the "replay" link on a given build? Or did I misunderstand something? 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-40344) Leaving a page open past session expiry fills the logs on the master with "Found invalid crumb" warnings
Title: Message Title Christian Höltje reopened an issue Jenkins / JENKINS-40344 Leaving a page open past session expiry fills the logs on the master with "Found invalid crumb" warnings Change By: Christian Höltje Resolution: Fixed Status: Resolved Reopened 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-40344) Leaving a page open past session expiry fills the logs on the master with "Found invalid crumb" warnings
Title: Message Title Christian Höltje commented on JENKINS-40344 Re: Leaving a page open past session expiry fills the logs on the master with "Found invalid crumb" warnings This isn't really fixed. I have had to resort to changing the log levels (the URL /log/levels) to prevent it from logging. I'm seeing things like this (from the support logs, because it was more informative): 2018-02-24 05:17:10.406+ [id=20011] WARNING hudson.security.csrf.CrumbFilter#doFilter: Found invalid crumb 418a20cb74b577eaae393aa8ac0e. Will check remaining parameters for a valid one... 2018-02-24 05:17:10.406+ [id=20011] WARNING hudson.security.csrf.CrumbFilter#doFilter: No valid crumb was included in request for /$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getOnlineSlaves by joecool. Returning 403. The amount of these logs was causing my Jenkins to stop working: The executors were not being released by jobs (even after they were done running) until the log entry could be written. I checked through the logs and all the entries I have are for these URLs (there could be more, due to the logs rolling so quick): /$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getDisconnectedSlaves /$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getOfflineSlaves /$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getOnlineSlaves /$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getRunningJobs /$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getSlaves /$stapler/bound/419618ba-22aa-4afb-8528-b112a604cce9/getTasksInQueue Add Comment
[JIRA] (JENKINS-46068) Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)
Title: Message Title Christian Höltje commented on JENKINS-46068 Re: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) Under the covers, the Github Organization Folder should be tracking the repository ID (a number) instead of the name of the repository. 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-37845) GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with
Title: Message Title Christian Höltje commented on JENKINS-37845 Re: GitHub plugin build-on-push for Pipeline job is hard/unpredictable to work with With GitHub Branch Source v2.0.4 I'm not seeing it either 1) create the hook (if missing), even on first index/scan, nor 2) do I see it update hooks. At the moment, I'm manually creating the webhooks with the events: push, repository, and pull-request (see JENKINS-39025 for why). I've tried new GitHub Org Folders, editing existing GH Org Folders, etc. and it never seems to register the webhook anymore. 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-39025) Pull request from forks are not build
Title: Message Title Christian Höltje commented on JENKINS-39025 Re: Pull request from forks are not build I think correct events are: push, repository, and pull-request But I'm not positive, because it seems like the GitHub Org. Folder no longer creates/updates hooks anymore; possibly due to the transition from a separate plugin? 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-42421) BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985'
Title: Message Title Christian Höltje commented on JENKINS-42421 Re: BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985' The permissions problem I was having is due to the command line jar not having being able to get GitHub Orgs/Teams because there are no cached credentials. 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-42280) Nullpointer on BasicSSHUserPrivateKey passphrase
Title: Message Title Christian Höltje commented on JENKINS-42280 Re: Nullpointer on BasicSSHUserPrivateKey passphrase This is important for automating credentials management via tools like Chef and Puppet. See https://github.com/chef-cookbooks/jenkins/issues/561 for an example of the impact. 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-42643) Conditional application of triggers in Declarative
Title: Message Title Christian Höltje commented on JENKINS-42643 Re: Conditional application of triggers in Declarative ❤️ Maybe allow with to work anyplace? Or at least most places? e.g. the properties section (or options or whatever it is called) as well as inside a stage? 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-37220) Job DSL analogue of multibranch projects & organization folders
Title: Message Title
Christian Höltje commented on JENKINS-37220
Re: Job DSL analogue of multibranch projects & organization folders
Use case:
Joe creates a GitHub Org Folder. His repos foo and bar are scanned and picked up because they have a Jenkinsfile in each.
foo is a huge repository (2gb) and he only wants the last 10 commits when building (a shallow clone with depth 10) and without any tags.
bar uses lots of submodules, but isn't big. He wants the submodule extensions turned on and to use the GitHub Org credentials.
This could be done by allow adding extensions at the GitHub Org Folder level, but that would mean forcing all builds to have a depth of 10, no tags, and submodules turned on. This could cause people to split the GitHub Orgs up just to accommodate Jenkins (which may not be possible, if they are paying for the Orgs, etc.) An idea is we could change the scm from an Object to the list form (I don't know what it is called) that looks like [$class:GitSCM, extensions: ... ] I have some code I run in a trusted pipeline via the src/ directory that almost does this...
class ScmEditablizer {
static def makeScmEditable(scm, env) {
Integer i
def branches = []
for (i = 0; i < scm.branches.size(); i++) {
def it = scm.branches.get(i)
branches.add([name: it.getName()])
}
def userRemoteConfigs = []
for (i = 0; i < scm.userRemoteConfigs.size(); i++) {
def it = scm.userRemoteConfigs.get(i)
userRemoteConfigs.add([
name: it.getName(),
url: it.getUrl(),
credentialsId: it.getCredentialsId(),
refspec: it.getRefspec()
])
}
return [ $class: 'GitSCM', extensions: [], branches: branches, userRemoteConfigs: userRemoteConfigs ]
}
}
But this doesn't work because the extensions are missing and it doesn't understand Pull Requests (I don't know why exactly). This allows getting an "editable" scm object that can have extensions, etc. added to it.
Add Comment
[JIRA] (JENKINS-42681) "Replay" editor should be resizable
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-42681 "Replay" editor should be resizable Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2017/Mar/10 7:28 PM Priority: Minor Reporter: Christian Höltje The "Replay" pipeline editor is rather small (15 lines). It would be nice if this was bigger and/or resizable. Possibly related to JENKINS-31585 though that's for the editor in configure I think. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-42643) when/if doesn't work in trigger
Title: Message Title
Christian Höltje created an issue
Jenkins / JENKINS-42643
when/if doesn't work in trigger
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Mar/09 10:00 PM
Priority:
Minor
Reporter:
Christian Höltje
I want to be able to use trigger with cron but only for the master branch. if and when both don't work in the trigger context. Here is what I expected to work:
if (env.BRANCH == 'master') {
trigger { cron('@daily') }
}
Add Comment
[JIRA] (JENKINS-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well I think getting and storing an OAuth token is desirable on login. This is how (for example) iPhone apps work. This could have other uses, such as using that token for Replays (instead of the Org token). 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-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well I think getting and storing an OAuth token is desirable on login. This is how (for example) iPhone apps work. This could have other uses, such as using that token for Replays (instead of the Org token). 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-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well I think getting and storing an OAuth token is desirable on login. This is how (for example) iPhone apps work. This could have other uses, such as using that token for Replays (instead of the Org token). 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-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well I think getting and storing an OAuth token is desirable on login. This is how (for example) iPhone apps work. This could have other uses, such as using that token for Replays (instead of the Org token). 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-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well Oh! I understand now. It also explains the permissions problem I was having with the Jenkins CLI when I discovered JENKINS-42421 That being said, there are other uses for the SSH public keys, including the Jenkins-hosted git server for the workflow pipeline, etc. So this may still be useful. 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-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well Oh! I understand now. It also explains the permissions problem I was having with the Jenkins CLI when I discovered JENKINS-42421 That being said, there are other uses for the SSH public keys, including the Jenkins-hosted git server for the workflow pipeline, etc. So this may still be useful. 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-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well Oh! I understand now. It also explains the permissions problem I was having with the Jenkins CLI when I discovered JENKINS-42421 That being said, there are other uses for the SSH public keys, including the Jenkins-hosted git server for the workflow pipeline, etc. So this may still be useful. 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-42421) BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985'
Title: Message Title Christian Höltje commented on JENKINS-42421 Re: BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985' Huh. I didn't know about /whoAmI 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-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well I didn't explain it well. Sorry. Let me try again: On login, fetch the public ssh keys stored in github (under https://github.com/settings/keys ) and put them into the user's profile in Jenkins automaticall (https://jenkins.example.com/user/USERNAME/ ). That shouldn't require any caching or anything. This is to facilitate using the `jenkins-cli.jar` and other things that talk to Jenkins via ssh. 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-42421) BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985'
Title: Message Title Christian Höltje commented on JENKINS-42421 Re: BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985' This may possibly be related to JENKINS-34835 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-42421) BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985'
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-42421 BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985' Issue Type: Bug Assignee: Sam Gleske Components: github-oauth-plugin Created: 2017/Mar/01 9:49 PM Environment: github-oauth-plugin 0.25 Priority: Major Reporter: Christian Höltje Before, team names would show up. Now they show as `org.kohsuke.github.GHTeam@e004985`. Example: Given the github org 'foo' with the team 'bar', the Organization would show up in my /user/ page as foo*bar. Now, it shows up as foo*org.kohsuke.github.GHTeam@e004985. This is breaking permissions, since I cannot give permissions to teams! Add Comment
[JIRA] (JENKINS-42416) Metrics should include Pipeline "node()" sections.
Title: Message Title
Christian Höltje updated an issue
Jenkins / JENKINS-42416
Metrics should include Pipeline "node()" sections.
Change By:
Christian Höltje
Please update the Plugin to support Jenkins Pipelines.The {{jenkins.job}} items don't reflect {{node() }} parts of Pipeline builds.Also, the { {jenkins . node . XXX . builds` _(timer) }} } parts of items don't show Pipeline builds either .I don ' t mind that m not sure adding pipeline metrics to those builds is correct , but there should be a some way to get information about info on the {{node() { pipeline builds . .. }}} calls. In addition, I think (but am not sure) the {{jenkins.queue}} doesn isn 't seem to be counting pipelines right either.
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
[JIRA] (JENKINS-42416) Metrics should include Pipeline "node()" sections.
Title: Message Title
Christian Höltje created an issue
Jenkins / JENKINS-42416
Metrics should include Pipeline "node()" sections.
Issue Type:
Bug
Assignee:
Unassigned
Components:
metrics-plugin
Created:
2017/Mar/01 7:56 PM
Environment:
Metrics Plugin 3.1.2.9
Priority:
Minor
Reporter:
Christian Höltje
Please update the Plugin to support Jenkins Pipelines. The jenkins.job items don't reflect {{node() { ... }}} parts of Pipeline builds. I don't mind that, but there should be a way to get information about the {{node() { ... } }} calls. In addition, the jenkins.queue doesn't seem to be counting pipelines right either.
Add Comment
