[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Szymon J commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user Now I see that I can choose "Use commit author in changelog" under Additional Behaviour. 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-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Szymon J commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user I am already using the "checkout" syntax: checkout([$class: 'GitSCM', branches: [[name: 'snip']], browser: [$class: 'GithubWeb', repoUrl: 'snip'], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[snip]]) Where can I find the documentation for the available options? 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-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Szymon J commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user It looks like this setting `authorOrCommitter` has been moved back in 2013 to some "Extensions". Where can I find them? Is it 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-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Szymon J edited a comment on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user I can't find that setting in the "Git plugin" section in the /configure page. I only see "user.name", "user.email", "Create new accounts base on author/committer's email". Could you point to where to find that setting? Also, it'd be useful to see how to do this in a Jenkinsfile pipeline. 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-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user
Title: Message Title Szymon J commented on JENKINS-38698 Re: SCM Changelog: Commits, made via github, displayed with "noreply" user I can't find that setting in the "Git plugin" section in the /configure page. I only see "user.name", "user.email", "Create new accounts base on author/committer's email". Could you point to where to find that setting? Also, it'd be useful to see how to do this in a Jenkinsfile pipeline. 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-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title Szymon J commented on JENKINS-41832 Re: master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener() It seems that the problem you are addressing with SyncQueueListener is that of the POSIX `select` or `poll`, which is to monitor a number of items for their readiness. So a blocking queue would not help here. As far as I can tell the only way to wait on a number of java.concurrent.Future is to launch a number of threads each waiting on one Future and updating a synchronized object. http://stackoverflow.com/questions/117690/wait-until-any-of-futuret-is-done 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-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title Szymon J commented on JENKINS-41832 Re: master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener() Created https://github.com/jenkinsci/pubsub-light-module/pull/6 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-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title Szymon J edited a comment on JENKINS-41832 Re: master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener() The bug happens when there is more than one item in the queue and none of the futures is done.1. // queue has 2 items, tryQueue has 0 items2. leftItem = queue.poll() // queue has 1, tryQueue has 03. tryQueue.drainTo(queue) // queue has 1, tryQueue has 04. !isDone => tryQueue.put(leftItem) // queue has 1, tryQueue has 15. leftItem = queue.poll() // queue has 0, tryQueue has 16. tryQueue.drainTo(queue) // queue has 1, tryQueue has 07. !isDone =>tryQueue.put(leftItem) // queue has 1, tryQueue has 1... spin we're back in 4. spinning. 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-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title Szymon J commented on JENKINS-41832 Re: master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener() The bug happens when there is more than one item in the queue and none of the futures is done. 1. // queue has 2 items, tryQueue has 0 items 2. leftItem = queue.poll() // queue has 1, tryQueue has 0 3. tryQueue.drainTo(queue) // queue has 1, tryQueue has 0 4. !isDone => tryQueue.put(leftItem) // queue has 1, tryQueue has 1 5. leftItem = queue.poll() // queue has 0, tryQueue has 1 6. tryQueue.drainTo(queue) // queue has 1, tryQueue has 0 7. !isDone =>tryQueue.put(leftItem) // queue has 1, tryQueue has 1 ... spin 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-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title
Szymon J edited a comment on JENKINS-41832
Re: master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
If I understand the intention of SyncQueueListener, it just has a small bug.{code:java}leftItem = queueTaskLeftPublishQueue.poll(...)if (leftItem!= null) { // FIXME: This is a bug. Don't drain tryLater unless the future is done. tryLaterQueueTaskLeftQueue.drainTo(queueTaskLeftPublishQueue); if (leftItem.getFuture().isDone()) {// ..// TODO: FIXME: This is a good place to drain the tryLater queue publish(...); } else {tryLaterQueueTaskLeftQueue.put(leftItem); }} else { tryLaterQueueTaskLeftQueue.drainTo(queueTaskLeftPublishQueue);}{code}
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-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title
Szymon J commented on JENKINS-41832
Re: master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
If I understand the intention of SyncQueueListener, it just has a small bug.
leftItem = queueTaskLeftPublishQueue.poll(...)
if (leftItem!= null) {
// FIXME: This is a bug. Don't drain tryLater unless the future is done.
tryLaterQueueTaskLeftQueue.drainTo(queueTaskLeftPublishQueue);
if (leftItem.getFuture().isDone()) {
// ..
} else {
tryLaterQueueTaskLeftQueue.put(leftItem);
}
} else {
tryLaterQueueTaskLeftQueue.drainTo(queueTaskLeftPublishQueue);
}
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-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title
Szymon J edited a comment on JENKINS-41832
Re: master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
If I understand the intention of SyncQueueListener, it just has a small bug.{code:java}leftItem = queueTaskLeftPublishQueue.poll(...)if (leftItem!= null) { // FIXME: This is a bug. Don't drain tryLater unless the future is done. tryLaterQueueTaskLeftQueue.drainTo(queueTaskLeftPublishQueue); if (leftItem.getFuture().isDone()) {// .. // TODO: FIXME: This is a good place to drain the tryLater queue } else {tryLaterQueueTaskLeftQueue.put(leftItem); }} else { tryLaterQueueTaskLeftQueue.drainTo(queueTaskLeftPublishQueue);}{code}
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-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title Szymon J commented on JENKINS-41832 Re: master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener() I should explain that the log is heavy in size (10k lines), but the output rate is not that big (few lines per sec). 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-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title
Szymon J edited a comment on JENKINS-41832
Re: master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
This is using pipeline script, one node, three stages. The step in progress was is sh("bazel build ...") This happens in every build.
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-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title
Szymon J commented on JENKINS-41832
Re: master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
This is using pipeline script, one node, three stages. The step in progress was sh("bazel build ...")
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-41832) master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener()
Title: Message Title Szymon J created an issue Jenkins / JENKINS-41832 master uses 100% cpu in jenkinsci.plugins.pubsub.listeners.SyncQueueListener() Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/08 1:22 AM Environment: jenkins 52.0 blueocean 1.0.0-b22 pubsub-light 1.6 OS: ubuntu 16.04 xenial JAVA: openjdk 1.8.0 Priority: Minor Reporter: Szymon J During a build with a heavy log the master pubsub publisher thread has one core pegged at 100% in: org.jenkinsci.plugins.pubsub.listeners.SyncQueueListener$1.run(SyncQueueListener.java:103) Note that no browser is connected to jenkins over HTTP at the time. Add Comment
