[JIRA] (JENKINS-38484) Using test stability publisher in a Pipeline build will hang
Title: Message Title kutzi commented on JENKINS-38484 Re: Using test stability publisher in a Pipeline build will hang I'm not sure, but I think you cannot do a release without being a maintainer. Please go forward and request becoming an maintainer for this project, if you like to. Thank you for your work on this issue! 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-38484) Using test stability publisher in a Pipeline build will hang
Title: Message Title kutzi commented on JENKINS-38484 Re: Using test stability publisher in a Pipeline build will hang Yes, +1 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-38484) Using test stability publisher in a Pipeline build will hang
Title: Message Title kutzi commented on JENKINS-38484 Re: Using test stability publisher in a Pipeline build will hang Yes, by all means. Do it if you have the appropriate permissions in Github and so. If not, let me know, so I can assist you. Sorry for not reacting earlier. 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-35336) SSH agent not starting because file not created
Title: Message Title kutzi commented on JENKINS-35336 Re: SSH agent not starting because file not created We get occasionally the same problem on our build nodes. Would be good if the error message could have some more details - e.g. what's actually the path of the file trying to be created. BTW: in our case it was an issue of no more inodes available on the node, so we just had to delete some workspaces on it. 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-50818) CLONE - Activity/branches for some pipelines fail to load with no errormessage
Title: Message Title kutzi created an issue Jenkins / JENKINS-50818 CLONE - Activity/branches for some pipelines fail to load with no errormessage Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-04-16 08:56 Environment: Windows Priority: Major Reporter: kutzi I have three multibranch pipelines, two with few branches and few builds, and one with many branches and many builds (but not that ** many). The two with few branches work fine, but for the one with many branches, the "activity" and "branches" fail to load while showing a "loading" message forever. The script log from my browser says Error fetching page TypeError: Cannot read property 'toLowerCase' of undefined at TimeHarmonizerUtil.getI18nTitle (blueocean-core-js.js:64082) at LiveStatusIndicator.render (blueocean-core-js.js:63371) at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext (jenkins-design-language.js:48404) at ReactCompositeComponentWrapper._renderValidatedComponent (jenkins-design-language.js:48427) at ReactCompositeComponentWrapper.performInitialMount (jenkins-design-language.js:47967) at ReactCompositeComponentWrapper.mountComponent (jenkins-design-language.js:47863) at Object.mountComponent (jenkins-design-language.js:54203) at ReactCompositeComponentWrapper.performInitialMount (jenkins-design-language.js:47976) at ReactCompositeComponentWrapper.mountComponent (jenkins-design-language.js:47863) at Object.mountComponent (jenkins-design-language.js:54203) at ReactDOMComponent.mountChildren (jenkins-design-language.js:53165) at ReactDOMComponent._createInitial
[JIRA] (JENKINS-50818) Activity/branches for some pipelines fail to load with no errormessage
Title: Message Title kutzi updated an issue Jenkins / JENKINS-50818 Activity/branches for some pipelines fail to load with no errormessage Change By: kutzi Summary: CLONE - Activity/branches for some pipelines fail to load with no errormessage 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-50818) Activity/branches for some pipelines fail to load with no errormessage
Title: Message Title
kutzi updated an issue
Jenkins / JENKINS-50818
Activity/branches for some pipelines fail to load with no errormessage
Change By:
kutzi
I have three multibranch pipelines, two with few branches and few builds, and one with many branches and many builds started seeing this after updating to Blue Ocean 1.5.0 ( but not _that_ ** many) Jenkins 2 . The two with few 107.2)Some projects/ branches work fine , but while for other only the one with many branches header bars are rendered , but no builds. No error msg in the "activity" and "branches" fail to load while showing a "loading" message forever UI . The script log from my browser says This error in the JS console: {code: java _javascript_ } VM640 blueocean-core-js.js:58091 Error fetching page TypeError: Cannot read property 'toLowerCase' of undefinedat TimeHarmonizerUtil.getI18nTitle ( VM640 blueocean-core-js.js: 64082 54181 )at LiveStatusIndicator.render ( VM640 blueocean-core-js.js: 63371 53477 )at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext ( VM639 jenkins-design-language.js: 48404 49621 )at ReactCompositeComponentWrapper._renderValidatedComponent ( VM639 jenkins-design-language.js: 48427 49644 )at ReactCompositeComponentWrapper.performInitialMount ( VM639 jenkins-design-language.js: 47967 49184 )at ReactCompositeComponentWrapper.mountComponent ( VM639 jenkins-design-language.js: 47863 49080 )at Object.mountComponent ( VM639 jenkins-design-language.js: 54203 55420 )at ReactCompositeComponentWrapper.performInitialMount ( VM639 jenkins-design-language.js: 47976 49193 )at ReactCompositeComponentWrapper.mountComponent ( VM639 jenkins-design-language.js: 47863 49080 )at Object.mountComponent ( VM639 jenkins-design-language.js: 54203 55420 )at ReactDOMComponent.mountChildren ( VM639 jenkins-design-language.js: 53165 54382 )at ReactDOMComponent._createInitialChildren ( VM639 jenkins-design-language.js: 49291 50508 )at ReactDOMComponent.mountComponent ( VM639 jenkins-design-language.js: 49110 50327 )at Object.mountComponent ( VM639 jenkins-design-language.js: 54203 55420 )at ReactDOMComponent.mountChildren ( VM639 jenkins-design-language.js: 53165 54382 )at ReactDOMComponent._createInitialChildren ( VM639 jenkins-design-language.js: 49291 50508 )at ReactDOMComponent.mountComponent ( VM639 jenkins-design-language.js: 49110 50327 )at Object.mountComponent ( VM639 jenkins-design-language.js: 54203 55420 )at ReactCompositeComponentWrapper.performInitialMount ( VM639 jenkins-design-language.js: 47976 49193 )at ReactCompositeComponentWrapper.mountComponent ( VM639 jenkins-design-language.js: 47863 49080 )at Object.mountComponent ( VM639 jenkins-design-language.js: 54203 55420 )at ReactCompositeComponentWrapper.performInitialMount ( VM639 jenkins-design-language.js: 47976 49193 ) {code}
[JIRA] (JENKINS-50820) Rebuild button gone in Blue Ocean UI
Title: Message Title kutzi created an issue Jenkins / JENKINS-50820 Rebuild button gone in Blue Ocean UI Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-04-16 09:47 Priority: Minor Reporter: kutzi After update to Jenkins 2.107.2 (from 2.89.4) most (but not all!) rebuild buttons are gone from the Blue Ocean UI (rebuild links in the classic UI are still there). No error msg. I couldn't yet find out the pattern why the rebuild button is still there for some builds, but not anymore for others. This happened with blue ocean plugin 1.4.2. In the mean time I've upgraded to 1.5.0, but this issue still persists. Add Comment
[JIRA] (JENKINS-50820) Rerun button gone in Blue Ocean UI
Title: Message Title kutzi updated an issue Jenkins / JENKINS-50820 Rerun button gone in Blue Ocean UI Change By: kutzi Summary: Rebuild Rerun button gone in Blue Ocean 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title kutzi updated an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: kutzi Attachment: deadlock.txt 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title kutzi commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads I did already update to workflow-cps 2.5.2, but then tomorrow got a new deadlock. See attachment deadlock.txt 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title kutzi edited a comment on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads I did already update to workflow-cps 2.5.2, but then tomorrow this morning got a new deadlock. See attachment [^deadlock.txt] 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-49774) NPE in Autofavorite plugin
Title: Message Title
kutzi created an issue
Jenkins / JENKINS-49774
NPE in Autofavorite plugin
Issue Type:
Bug
Assignee:
James Dumay
Components:
blueocean-autofavorite-plugin
Created:
2018-02-27 15:29
Priority:
Major
Reporter:
kutzi
The autofavorite plugin has failed pipeline builds in several occasions. I didn't find a pattern yet, but restarting the build seemed to help. Pull request #2 opened http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-2Connecting to ... http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-3Checking out git ... http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-21 > git config core.sparsecheckout # timeout=10 http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-22 > git checkout -f 035d5953f1344f13cf12b9d62c6d661a69e2a6c2 http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-23 > git merge 01419d665c6de32d37d75c5a85f0aeedf86d7403 # timeout=10 http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-24 > git rev-parse HEAD^{commit} # timeout=10 http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-25Merge succeeded, producing 035d5953f1344f13cf12b9d62c6d661a69e2a6c2 http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-26Checking out Revision 035d5953f1344f13cf12b9d62c6d661a69e2a6c2 (PR-2) http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-27
[JIRA] (JENKINS-49774) NPE in Autofavorite plugin
Title: Message Title
kutzi updated an issue
Jenkins / JENKINS-49774
NPE in Autofavorite plugin
Change By:
kutzi
{{ The autofavorite plugin has failed pipeline builds in several occasions. I didn't find a pattern yet, but restarting the build seemed to help.}} {{ Pull request #2 opened [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-2] Connecting to ... [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-3] Checking out git ... @script to read Jenkinsfile [|http://jenkins-master Cloning the remote Git repository . swat . ham . sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-21] > git config core.sparsecheckout # timeout=10 [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-22] > git checkout -f 035d5953f1344f13cf12b9d62c6d661a69e2a6c2 [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-23] > git merge 01419d665c6de32d37d75c5a85f0aeedf86d7403 # timeout=10 [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-24] > git rev-parse HEAD^\{commit} # timeout=10 [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-25]Merge succeeded, producing 035d5953f1344f13cf12b9d62c6d661a69e2a6c2 [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-26]Checking out Revision 035d5953f1344f13cf12b9d62c6d661a69e2a6c2 (PR-2) [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-27] > git config core.sparsecheckout # timeout=10 [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-28] > git checkout -f 035d5953f1344f13cf12b9d62c6d661a69e2a6c2 [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-29] Commit message: "check" [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-30] First time build. Skipping changelog. [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-31] [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-32] GitHub has been notified of this commit’s build result [|http://jenkins-master.swat.ham.sg-cloud.co.uk/blue/organizations/jenkins/Website%20GH%20Orga%2Fcara-jobs/detail/PR-2/1/pipeline#log-33] [|
[JIRA] (JENKINS-49774) NPE in Autofavorite plugin
Title: Message Title
kutzi updated an issue
Jenkins / JENKINS-49774
NPE in Autofavorite plugin
Change By:
kutzi
The autofavorite plugin has failed pipeline builds in several occasions. I didn't find a pattern yet, but restarting the build seemed to help.}} {{ Pull request #2 openedConnecting to ...Checking out git ...@script to read JenkinsfileCloning the remote Git repository...Commit message: "check"First time build. Skipping changelog.GitHub has been notified of this commit’s build resultjava.lang.NullPointerException at io.jenkins.blueocean.autofavorite.FavoritingScmListener.onCheckout(FavoritingScmListener.java:109) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:127) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:143) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:120) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:271) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE }}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49774) NPE in Autofavorite plugin
Title: Message Title kutzi commented on JENKINS-49774 Re: NPE in Autofavorite plugin Sorry, I don't see that error anymore and the build logs of the builds, where it happened, are already gone. You can close the issue if you like to and I'll reopen it if I encounter the issue, again. 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-38609) Shared libraries root to be specified in the PATH field
Title: Message Title kutzi commented on JENKINS-38609 Re: Shared libraries root to be specified in the PATH field I know that this has been closed as Won't Do, but I want to share an additional use case where this might be useful to have. We like to have testing code and the code for the shared library related to the tests close together - i.e. in one repo. The directory structure looks like this e.g. src/main/java/ src/main/resources/ src/test/java/ and so on. If I add now the shared library to this it's like this src/ vars/ I.e. it 'taints' the global directory structure of the project I'd rather more like it to be something like this: src/pipeline/groovy src/pipeline/vars 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-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title
kutzi commented on JENKINS-28822
Re: Can't distinguish between durable task abort and failure in workflow plugin
I guess this is also the reason for JENKINS-43339, isn't it? This is IMO a big issue as it makes to post { aborted {} } section in declarative pipelines largely unusable. In fact, I've not seen a single occasion when aborted worked as expected. For me the failure section is always triggered instead.
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-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title
kutzi edited a comment on JENKINS-28822
Re: Can't distinguish between durable task abort and failure in workflow plugin
I guess this is also the reason for JENKINS-43339, isn't it?This is IMO a big issue as it makes to post the _post { aborted {} } _ section in declarative pipelines largely unusable. In fact, I've not seen a single occasion when _aborted_ worked as expected. For me the _failure_ section is always triggered instead.
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-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title
kutzi edited a comment on JENKINS-28822
Re: Can't distinguish between durable task abort and failure in workflow plugin
I guess this is also the reason for JENKINS-43339, isn't it?This is IMO a big issue as it makes the _post { aborted {} }_ section in declarative pipelines largely unusable. In fact, I've not seen a single occasion when _aborted_ worked as expected - when manually aborting a build . For me Then the _failure_ section is always triggered instead.
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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title kutzi updated an issue Jenkins / JENKINS-54073 "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Change By: kutzi Attachment: threaddump_jenkins-54073.txt 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title kutzi commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps I think I've experienced the same issue. CPU dropped to normal levels after downgrade to 2.25 I've attached a thread dump 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title kutzi commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Sam Van Oort what are FlowNodes? Jesse Glick I've already downgraded the plugin, again, and cannot get the info you requested, anymore. As this is a production-critical instance, I won't be able to set up a test case with the new plugin version in a short timeframe. 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-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title kutzi commented on JENKINS-55427 Re: Blue Ocean display of sequential stages in parallel stages is flaky Any update on this? It didn't become any better with the latest BlueOcean updates. It's IMO basically unusable as long as the build is running. For one because you sometimes cannot select the later branches: wherever I click, always the steps for the 1st branch are displayed - even it the other branch is displayed as selected in the UI. For 2nd, even if you manage to select a different branch, often the logs display switches to a different branch, if that branch gets new log updates 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-56639) when viewing a pipeline in blue ocean, please stop auto opening console log of failed step
Title: Message Title kutzi commented on JENKINS-56639 Re: when viewing a pipeline in blue ocean, please stop auto opening console log of failed step Yes, please! This is so annoying. 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-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title kutzi created an issue Jenkins / JENKINS-55427 Blue Ocean display of sequential stages in parallel stages is flaky Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-01-07 15:01 Environment: BlueOcean 1.10.1 Priority: Minor Reporter: kutzi 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.
[JIRA] (JENKINS-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title kutzi updated an issue Jenkins / JENKINS-55427 Blue Ocean display of sequential stages in parallel stages is flaky Change By: kutzi When there are sequential stages in a parallel stage then the display of them is often not correct and very inconsistent - i.e. sometimes the display changes even from one build to the next.This seems to apply only to running builds. As soon as the build is completed the stages are displayed correctly.Note: this seems to be related to JENKINS-55320, but that one is about BlueOcean 1.9 and scripted stages. This one is about declarative stages. 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-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title kutzi updated an issue Jenkins / JENKINS-55427 Blue Ocean display of sequential stages in parallel stages is flaky Change By: kutzi Attachment: Screenshot from 2019-01-07 15-57-37.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title kutzi commented on JENKINS-55427 Re: Blue Ocean display of sequential stages in parallel stages is flaky E.g. in one build the stage 'Integration Tests' was showing the sequential stages of the stage 'IWG | DBG'. See 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-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title kutzi commented on JENKINS-55427 Re: Blue Ocean display of sequential stages in parallel stages is flaky In other instances the sequential stages are correctly mapped to the parallel stages, but the sequential steps in 'IWG | DBG' are shown grey all the time, even if they are already finished. 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-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title
kutzi updated an issue
Jenkins / JENKINS-55427
Blue Ocean display of sequential stages in parallel stages is flaky
Change By:
kutzi
When there are sequential stages in a parallel stage then the display of them is often not correct and very inconsistent - i.e. sometimes the display changes even from one build to the next.This seems to apply only to running builds. As soon as the build is completed the stages are displayed correctly.Note: this seems to be related to JENKINS-55320, but that one is about BlueOcean 1.9 and scripted stages. This one is about declarative stages. This is the relevant part of my Jenkinsfile:{code:java}stage("Run Tests") {parallel {stage("Acceptance Tests") {steps {...}}}stage("Integration Tests") {steps {}}stage("IWG | DBG") {stages {stage("IWG Tests") {steps {...}}stage("DBG Tests") {steps {...}}}}stage("Payment Acceptance Tests") {steps {...}}} {code}
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 "Jenkin
[JIRA] (JENKINS-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title
kutzi updated an issue
Jenkins / JENKINS-55427
Blue Ocean display of sequential stages in parallel stages is flaky
Change By:
kutzi
When there are sequential stages in a parallel stage then the display of them is often not correct and very inconsistent - i.e. sometimes the display changes even from one build to the next. This seems to apply only to running builds. As soon as the build is completed the stages are displayed correctly.Note: this seems to be related to JENKINS-55320, but that one is about BlueOcean 1.9 and scripted stages. This one is about declarative stages. This is the relevant part of my Jenkinsfile:{code:java}stage("Run Tests") {parallel {stage("Acceptance Tests") {steps {...}} } stage("Integration Tests") {steps {}}stage("IWG | DBG") {stages {stage("IWG Tests") {steps {...}}stage("DBG Tests") {steps {...}}}}stage("Payment Acceptance Tests") {steps {...}}} } {code}
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
[JIRA] (JENKINS-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title
kutzi updated an issue
Jenkins / JENKINS-55427
Blue Ocean display of sequential stages in parallel stages is flaky
Change By:
kutzi
When there are sequential stages in a parallel stage then the display of them is often not correct and very inconsistent - i.e. sometimes the display changes even from one build to the next. This seems to apply only to running builds. As soon as the build is completed the stages are displayed correctly.Note: this seems to be related to JENKINS-55320, but that one is about BlueOcean 1.9 and scripted stages. This one is about declarative stages and BlueOcean 1 . 10.1 This is the relevant part of my Jenkinsfile:{code:java}stage("Run Tests") {parallel {stage("Acceptance Tests") {steps {...}}stage("Integration Tests") {steps {}}stage("IWG | DBG") {stages {stage("IWG Tests") {steps { ...}}stage("DBG Tests") {steps { ...}}}}stage("Payment Acceptance Tests") {steps {...}}}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title kutzi updated an issue Jenkins / JENKINS-55427 Blue Ocean display of sequential stages in parallel stages is flaky Change By: kutzi Attachment: Screenshot from 2019-01-07 16-22-29.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title kutzi edited a comment on JENKINS-55427 Re: Blue Ocean display of sequential stages in parallel stages is flaky In other instances the sequential stages are correctly mapped to the parallel stages, but the sequential steps in 'IWG | DBG' are shown grey all the time, even if they are already finished. !Screenshot from 2019-01-07 16-22-29.png|thumbnail! 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-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title kutzi commented on JENKINS-55427 Re: Blue Ocean display of sequential stages in parallel stages is flaky Also clicking on these grey-but-already-finished stages is often - but not always - not possible. 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-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title kutzi edited a comment on JENKINS-55427 Re: Blue Ocean display of sequential stages in parallel stages is flaky Also clicking on click-selecting these grey-but-already-finished stages is often - but not always - not possible. 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-55427) Blue Ocean display of sequential stages in parallel stages is flaky
Title: Message Title kutzi updated an issue Jenkins / JENKINS-55427 Blue Ocean display of sequential stages in parallel stages is flaky Change By: kutzi Priority: Minor Major 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-55476) unsuccessful block is triggered for successful runs
Title: Message Title
kutzi created an issue
Jenkins / JENKINS-55476
unsuccessful block is triggered for successful runs
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2019-01-09 12:52
Environment:
pipeline-model-api plugin 1.3.4 Jenkins 2.150.1
Priority:
Critical
Reporter:
kutzi
The post-unsuccessful block of my declarative pipeline is triggered even if the build is successful! Excerpt from my Jenkinsfile
pipeline {
stages { ... }
post {
always { ... }
success { ... }
unsuccessful {
script {
echo "Build results: ${currentBuild.result} - ${currentBuild.currentResult}"
...
}
}
}
}
And I can see `Build results: SUCCESS - SUCCESS` in the pipeline output - and the other steps of the unsuccessful block executed as well, of course
[JIRA] (JENKINS-51745) Wrong elapsed time showing in blueocean
Title: Message Title kutzi commented on JENKINS-51745 Re: Wrong elapsed time showing in blueocean Actually, both are often shown wrong for me: duration of single steps and duration for the whole pipeline. And it's always that the shown time is to long. 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-48859) BlueOcean API parallel node duration in ms incorrect in declarative pipeline
Title: Message Title kutzi commented on JENKINS-48859 Re: BlueOcean API parallel node duration in ms incorrect in declarative pipeline Is there any update on this? 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-55540) IRC client crashes sending long messages
Title: Message Title kutzi assigned an issue to Unassigned Jenkins / JENKINS-55540 IRC client crashes sending long messages Change By: kutzi Assignee: kutzi 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-51745) Wrong elapsed time showing in blueocean
Title: Message Title kutzi commented on JENKINS-51745 Re: Wrong elapsed time showing in blueocean No progress on this? Really a shame, the times shown in Blue Ocean are useless without this being fixed 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-51745) Wrong elapsed time showing in blueocean
Title: Message Title kutzi updated an issue Jenkins / JENKINS-51745 Wrong elapsed time showing in blueocean Change By: kutzi Sprint: Blue Ocean - Candidates, Blue Ocean - 1.6 - beta 4 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-53295) error log should be collapsed by default too
Title: Message Title kutzi commented on JENKINS-53295 Re: error log should be collapsed by default too Yes, please! There are many annoying things in the way blue ocean is showing/following the logs, but this is one of the most disturbing ones. Another use case: browsing through the previous few failed builds and trying to looks into the artifacts where more info (e.g. log files) is stored. On every build blue ocean is 1st scrolling down to show the end of the failed step log and I have to manually scroll up, again, to get to the artifacts tab. 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-37891) Build Failure Analyzer: output of tests not escaped on build results page
Title: Message Title kutzi updated an issue Jenkins / JENKINS-37891 Build Failure Analyzer: output of tests not escaped on build results page Change By: kutzi Environment: Jenkins ver. 1. 625 651 . 2 1 Build Failure Analyzer 1. 13 15 . 3 0 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-37891) Build Failure Analyzer: output of tests not escaped on build results page
Title: Message Title kutzi created an issue Jenkins / JENKINS-37891 Build Failure Analyzer: output of tests not escaped on build results page Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2016/Sep/01 1:26 PM Environment: Jenkins ver. 1.625.2 Build Failure Analyzer 1.13.3 Labels: jenkins plugins Priority: Minor Reporter: kutzi As you hover over the right-side of "Indication_1", a down-arrow appears. If you click on the arrow, a contextMenu XHR request fires in the background. Unfortunately, they all seem to fail with a 404 "not found" response. Error message on Web debugger console: prototype.js:1585 POST http://jenkins/job/job_name/build_number/consoleFull/contextMenu 404 (Not Found) I believe it is because of invalid URL for contextMenu; consoleFull/contextMenu. Context menus for others work with JSON, however, consoleFull/contextMenu just redirects to the build page, also hard to expect any contextMenu from console output. Just in case it has been probably caused from old version of plug-in, please let me know. Otherwise, I recommend that the URL for down-arrow menu should be modified for proper purposes, for example a selection for highlighted (claimed) lines for the build log indication.
[JIRA] (JENKINS-37891) Build Failure Analyzer: output of tests not escaped on build results page
Title: Message Title kutzi updated an issue Jenkins / JENKINS-37891 Build Failure Analyzer: output of tests not escaped on build results page Change By: kutzi Labels: jenkins plugins 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-37891) Build Failure Analyzer: output of tests not escaped on build results page
Title: Message Title kutzi updated an issue Jenkins / JENKINS-37891 Build Failure Analyzer: output of tests not escaped on build results page Change By: kutzi As you hover over We had the right-side of "Indication_1", a down-arrow appears. If you click 'Treat failed test cases' checkbox enabled and so test outputs are written on the arrow, a contextMenu XHR request fires in the background build page . Unfortunately, they all seem to fail with a 404 "not found" response. Error message on Web debugger console: prototype.js:1585 POST http://jenkins/job/job_name/build_number/consoleFull/contextMenu 404 (Not Found)I believe it is because In one of invalid URL for contextMenu; consoleFull/contextMenu those case the test output contained HTML source - which wasn't escaped and so used as part of the page DOM . Context menus for others work with JSON, however, consoleFull/contextMenu just redirects to As this was an overly blocking the build whole page, also hard to expect any contextMenu from console output this was kind of annoying . Just in case it has been probably caused from old version of plug-in, please let me know I've now updated to 1 . Otherwise 17.0 , I recommend that the URL but still not better for down-arrow menu should be modified for proper purposes, for example a selection for highlighted (claimed) lines for the build log indication existing builds . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37891) Build Failure Analyzer: output of tests not escaped on build results page
Title: Message Title kutzi commented on JENKINS-37891 Re: Build Failure Analyzer: output of tests not escaped on build results page That was part of the test output org.openqa.selenium.WebDriverException: Element is not clickable at point (161.9499969482422, 437.41668701171875). Other element would receive the click: 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-38283) jabber-plugin does not list out pipeline jobs
Title: Message Title kutzi commented on JENKINS-38283 Re: jabber-plugin does not list out pipeline jobs I haven't had the time to familiarise myself with the pipeline plugin and it may take some time for me to work on this - given my priorities have somewhat shifted away from Jenkins. So if you really want something to happen here: a Pull Request would be welcome! 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-39459) Unable to delete project in Jenkins
Title: Message Title kutzi assigned an issue to Unassigned Jenkins / JENKINS-39459 Unable to delete project in Jenkins Change By: kutzi Assignee: kutzi 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-39459) Unable to delete project in Jenkins
Title: Message Title kutzi commented on JENKINS-39459 Re: Unable to delete project in Jenkins BTW: this seems much better suited as an usage question on the Jenkins user mailing list. It seems like 'just' a lock on the changelog.xml file by some other process 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-39459) Unable to delete project in Jenkins
Title: Message Title kutzi commented on JENKINS-39459 Re: Unable to delete project in Jenkins Why was this assigned to the downstream-ext plugin? Doesn't seem to be related to that plugin at all. 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-39459) Unable to delete project in Jenkins
Title: Message Title kutzi updated an issue Jenkins / JENKINS-39459 Unable to delete project in Jenkins Change By: kutzi Priority: Major Minor 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-39459) Unable to delete project in Jenkins
Title: Message Title kutzi updated an issue Jenkins / JENKINS-39459 Unable to delete project in Jenkins Change By: kutzi Component/s: core Component/s: downstream-ext-plugin 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] [ircbot-plugin] (JENKINS-35179) IRC Bot does not take commands
Title: Message Title kutzi updated an issue Jenkins / JENKINS-35179 IRC Bot does not take commands Change By: kutzi As requested in https://issues.jenkins-ci.org/browse/JENKINS-15765 : bq. Since this issue is old I am closing it. Try using the latest release. If it is still an issue in the latest release then file a new issue and link back to this one.It still happens with 2.2; can't test newer versions because there are no packages. Still, 2.2 is much younger than the referenced bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-35179) IRC Bot does not take commands
Title: Message Title kutzi commented on JENKINS-35179 Re: IRC Bot does not take commands Hi, what is the version of the IRCBot and the instant-messaging plugin you're using? What is exactly the error and how can I reproduce it - i.e. does it depend on the github-oauth plugin as in the original issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-31660) StackOverflowError when maximum number of builds archived
Title: Message Title kutzi updated an issue Jenkins / JENKINS-31660 StackOverflowError when maximum number of builds archived Change By: kutzi Component/s: junit-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-31660) StackOverflowError when maximum number of builds archived
Title: Message Title kutzi updated an issue Jenkins / JENKINS-31660 StackOverflowError when maximum number of builds archived Change By: kutzi URL: https://bugzilla.mozilla.org/show_bug.cgi?id=1186835 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-31660) StackOverflowError when maximum number of builds archived
Title: Message Title kutzi commented on JENKINS-31660 Re: StackOverflowError when maximum number of builds archived I wonder what is happening when you view the test results on this job even with test-stability disabled. This looks like a bug in the junit-plugin itself, which is probably only triggered by test-stability, because it is 'looking' at the test results, and the error would also happen when you look at the results manually. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-31660) StackOverflowError when maximum number of builds archived
Title: Message Title kutzi commented on JENKINS-31660 Re: StackOverflowError when maximum number of builds archived Is there a way for the plugin to detect this scenario and make the -Xss suggestion to the user? I don't think that is a feasible approach. Changing the -Xss size should be only a last resort when all other things fail and - if there is really an indefinite loop and not only the large number of jobs is the problem - it wouldn't even solve anything at all. It would be great if you could make the jenkins builds folder of the job available, if it's possible. E.g. if it doesn't contain any sensitive data. So we could try to reproduce this problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-24902) Jenkins's security is not applied for IM user
Title: Message Title kutzi commented on JENKINS-24902 Re: Jenkins's security is not applied for IM user As I said before, I think that trusting that if someone has a user name on some remote system (the IM server) also means that he/she has the same username in Jenkins, has the big potential for security issues Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
Title: Message Title kutzi commented on JENKINS-28175 Re: config change deadlock Jenkins when pircx.shutdown() is invoked Hi Leon, I tried to build a version of the plugin with PircBotX 2.1-SNAPSHOT, but 2.1-SNAPSHOT doesn't seem to be available in any standard Maven repository. Can you tell me which Maven repository I need to use? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-stability-plugin] (JENKINS-29251) Exclude skipped tests from the failed count
Title: Message Title kutzi commented on JENKINS-29251 Re: Exclude skipped tests from the failed count 15 + 3 would be 18 failures, so that doesn't add up. The logic of the plugin should be to leave the test history completely unchanged if the test was skipped (which makes sense IMO). So neither the failed cound nor the total count is changed by it. Does that match your observation: i.e. do you have 17 failures in the last 22 build where this test actually did run? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-29494) IRC plug-in throws org.acegisecurity.userdetails.UsernameNotFoundException during onMessage
Title: Message Title kutzi commented on JENKINS-29494 Re: IRC plug-in throws org.acegisecurity.userdetails.UsernameNotFoundException during onMessage Just remove the 'Jenkins Username' from the global plugin configuration. It's only needed when you have a secured Jenkins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
Title: Message Title kutzi commented on JENKINS-28175 Re: config change deadlock Jenkins when pircx.shutdown() is invoked @thelq: can you release PircBotX 2.1, so I can create a release of the Jenkins plugin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
Title: Message Title kutzi edited a comment on JENKINS-28175 Re: config change deadlock Jenkins when pircx.shutdown() is invoked @ [~ thelq ] : can you release PircBotX 2.1, so I can create a release of the Jenkins plugin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-30314) Unable to connect using Jabber plugin (bad-request)
Title: Message Title kutzi commented on JENKINS-30314 Re: Unable to connect using Jabber plugin (bad-request) Which Jabber server are you trying to connect to? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-10742) Send HTML jabber messages
kutzi commented on JENKINS-10742 Send HTML jabber messages Maybe we could start as a 1st step and change the BotCommands to return the current plain-text messages and the model data. Would still mean lot of changes in the Jabber plugin (fork), but at least a bit code reuse. In regards to templating: do yourself a favor and use something different than Jelly (e.g. Freemarker). Surely, Jelly is in widespread use in Jenkins, but it's a pita to use IMHO. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
kutzi commented on JENKINS-28175 config change deadlock Jenkins when pircx.shutdown() is invoked Quite difficult to reproduce this. Seems only to happen when the channel mode is stale while PircBot is shut down. And stale mode seem only to happen, when the server returns something for mode, what Pircbot cannot parse. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
kutzi commented on JENKINS-28175 config change deadlock Jenkins when pircx.shutdown() is invoked Opened an issue against PircBotX: https://code.google.com/p/pircbotx/issues/detail?id=240 Not sure if the issue persists in PircBotX 2.x as a lot has changed there. Trying to update to PircBotX 2.0.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-22042) IRCBot disconnects after long idle
kutzi commented on JENKINS-22042 IRCBot disconnects after long idle That is: for the error that Herman is reporting. Alexej's error might be a completely different one. No way to be sure until he clarifies what it means that the bot 'dies' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-22042) IRCBot disconnects after long idle
kutzi commented on JENKINS-22042 IRCBot disconnects after long idle Herman, on further thoughts your issue seems to be pretty different from the originally reported issue - disconnecting and hanging on notifications is actually a totally different thing. Isn't it actually what you reported in JENKINS-26491? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-22042) IRCBot disconnects after long idle
kutzi commented on JENKINS-22042 IRCBot disconnects after long idle @urras: as you changed this to Critical: can you provide more information. I.e. how to reproduce, error entries in log file etc? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
kutzi commented on JENKINS-28175 config change deadlock Jenkins when pircx.shutdown() is invoked I've create a plugin build which uses PircBotX 2.0.1 which should fix the issue. Would be great, if you could test it, before I build a new release: https://dl.dropboxusercontent.com/u/25863594/ircbot.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-28169) Jabber plugin fails to establish legacy SSL connection, when the Jabber server does not respond on plain communication
kutzi commented on JENKINS-28169 Jabber plugin fails to establish legacy SSL connection, when the Jabber server does not respond on plain communication Fixed in v1.35 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-28208) Crash with J9 1.6
Title: Message Title kutzi commented on JENKINS-28208 Re: Crash with J9 1.6 The Wiki clearly states that Java 7 is required: https://wiki.jenkins-ci.org/display/JENKINS/Jabber+Plugin There's no way around this as the underlying xmpp library require 1.7 itself. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-28208) Jabber plugin doesn't rund with Java 6 (Crash with J9 1.6)
Title: Message Title kutzi resolved as Not A Defect Jenkins / JENKINS-28208 Jabber plugin doesn't rund with Java 6 (Crash with J9 1.6) Change By: kutzi Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-28208) Jabber plugin doesn't rund with Java 6 (Crash with J9 1.6)
Title: Message Title kutzi updated an issue Jenkins / JENKINS-28208 Jabber plugin doesn't rund with Java 6 (Crash with J9 1.6) Change By: kutzi Summary: Jabber plugin doesn't rund with Java 6 ( Crash with J9 1.6 ) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-28208) Jabber plugin doesn't rund with Java 6 (Crash with J9 1.6)
Title: Message Title kutzi reopened an issue Ups, sorry. Thought this was abnout the jabber-plugin Jenkins / JENKINS-28208 Jabber plugin doesn't rund with Java 6 (Crash with J9 1.6) Change By: kutzi Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-28208) Crash with J9 1.6
Title: Message Title kutzi edited a comment on JENKINS-28208 Re: Crash with J9 1.6 - - The Wiki clearly states that Java 7 is required: https://wiki.jenkins-ci.org/display/JENKINS/Jabber+Plugin- - -There's no way around this as the underlying xmpp library require 1.7 itself.- Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-28208) Crash with J9 1.6
Title: Message Title kutzi updated an issue Jenkins / JENKINS-28208 Crash with J9 1.6 Change By: kutzi Summary: Jabber plugin doesn't rund with Java 6 ( Crash with J9 1.6 ) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-28208) Crash with J9 1.6
Title: Message Title kutzi edited a comment on JENKINS-28208 Re: Crash with J9 1.6 - The Wiki clearly states that Java 7 is required: https://wiki.jenkins-ci.org/display/JENKINS/Jabber+Plugin - - There's no way around this as the underlying xmpp library require 1.7 itself. - Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-28208) Crash with J9 1.6
Title: Message Title kutzi edited a comment on JENKINS-28208 Re: Crash with J9 1.6 --The Wiki clearly states that Java 7 is required: https://wiki.jenkins - ci.org/display/JENKINS/Jabber+Plugin - - -There's no way around this as the underlying xmpp library require 1.7 itself.- Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-28208) Crash with J9 1.6
Title: Message Title kutzi commented on JENKINS-28208 Re: Crash with J9 1.6 What does stop you from running Jenkins with a 1.7 VM? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-28208) Crash with J9 1.6
Title: Message Title kutzi commented on JENKINS-28208 Re: Crash with J9 1.6 Will see, what I can do. Anyway there are serious talks going on to raise the requirements for Jenkins itself to Java 1.7. So you won't have any luck running Jenkins with 1.6 for much longer. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-28208) Crash with J9 1.6
Title: Message Title kutzi commented on JENKINS-28208 Re: Crash with J9 1.6 I've now documented it for the plugin, too. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-28208) Crash with J9 1.6
Title: Message Title kutzi resolved as Won't Fix Jenkins / JENKINS-28208 Crash with J9 1.6 Change By: kutzi Status: Reopened Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging-plugin] (JENKINS-24902) Jenkins's security is not applied for IM user
Title: Message Title kutzi commented on JENKINS-24902 Re: Jenkins's security is not applied for IM user It would under circumstances be pretty easy to get admin rights to Jenkins by registering an admin_ IM user for example. There are probably a couple of other thinkable attack vectors if we would simply trust the passed IM user credentials. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title kutzi commented on JENKINS-28626 Re: IRC notification results in need to restart Jenkins Please provide the full stack trace Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title
kutzi commented on JENKINS-28626
Re: IRC notification results in need to restart Jenkins
Yes, that looks like a bug in the IRC plugin, but I fail to see how the plugin caused Jenkins to shut down. The order in the log file is, that there's an info that the JVM is shutting down ('INFO: JVM is terminating. Shutting down Winstone') and only after that the irc plugin logs an exception.
Do you have additional logs which show how the irc plugin causes the Jenkins shutdown and/or do you have instructions on how to reproduce the issue?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title kutzi commented on JENKINS-28626 Re: IRC notification results in need to restart Jenkins Seems like this is a bug in PircBotX 1.9 which was fixed in 2.0 (see changelog: https://code.google.com/p/pircbotx/wiki/ChangeLog) You might want to try the unreleased version of the IRC plugin which already uses PircBotx 2.0 https://dl.dropboxusercontent.com/u/25863594/ircbot.hpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
Title: Message Title kutzi commented on JENKINS-28175 Re: config change deadlock Jenkins when pircx.shutdown() is invoked Antoine, any chance you can try the unreleased IRC plugin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title kutzi commented on JENKINS-28626 Re: IRC notification results in need to restart Jenkins You can configure different notification styles (normal, short, ...) as far as I remember. On top of that there is currently no possibility to configure it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28626) IRC notification results in need to restart Jenkins
Title: Message Title kutzi commented on JENKINS-28626 Re: IRC notification results in need to restart Jenkins Can you confirm, that it was really the IRC plugin which lead to Jenkins shutdown? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
Title: Message Title kutzi commented on JENKINS-28175 Re: config change deadlock Jenkins when pircx.shutdown() is invoked Sorry, I missed the last updates here. Leon Blakey: since you did already the needed changes on your fork: can you update your fork to use the released version 2.1 and open a pull request? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10763) Definition of the terms Stable/Unstable/Failed; Successful/Unsuccessful and so on
Title: Message Title kutzi commented on JENKINS-10763 Re: Definition of the terms Stable/Unstable/Failed; Successful/Unsuccessful and so on KY Lee: I had already mentioned that page in https://groups.google.com/forum/?hl=de#!topic/jenkinsci-dev/2rMdYX3WMwo and why I think that it is not enough. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [downstream-ext-plugin] (JENKINS-30789) New condition: Downstream build result
Title: Message Title kutzi edited a comment on JENKINS-30789 Re: New condition: Downstream build result Can you elaborate on how this should exactly work (e.g.: should it be base own based on the result of the *previous* downstream build?) and what is the usecase for this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [downstream-ext-plugin] (JENKINS-30789) New condition: Downstream build result
Title: Message Title kutzi commented on JENKINS-30789 Re: New condition: Downstream build result Can you elaborate on how this should exactly work (e.g.: should it be base own the result of the previous downstream build?) and what is the usecase for this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
