[JIRA] (JENKINS-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Title: Message Title
Jesús Benavente commented on JENKINS-53088
Re: Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Hi Roy. I´m sorry but I've got disconneted along time the class UpdateAlmEntityRequest implements the perform method of the GeneralPutBulkRequest class, which calls the getDataBytes method tha include the node Entities StringBuilder builder = new StringBuilder("");
// code placeholder
private byte[] getDataBytes() {
StringBuilder builder = new StringBuilder("");
for (Map values : getFields()) {
builder.append("");
for (String key : values.keySet()) {
builder.append(RestXmlUtils.fieldXml(key, values.get(key)));
}
builder.append("");
}
return builder.append("").toString().getBytes();
}
However, the api rest does not allow that node. It should be
..
//StringBuilder builder = new StringBuilder("");
StringBuilder builder = new StringBuilder("");
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/optou
[JIRA] (JENKINS-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Title: Message Title
Jesús Benavente edited a comment on JENKINS-53088
Re: Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Hi Roy.I´m sorry but I've got disconneted along long timethe class UpdateAlmEntityRequest implements the perform method of the GeneralPutBulkRequest class, which calls the getDataBytes method tha include the node EntitiesStringBuilder builder = new StringBuilder(""); {code:java}// code placeholder private byte[] getDataBytes() {StringBuilder builder = new StringBuilder("");for (Map values : getFields()) {builder.append("");for (String key : values.keySet()) {builder.append(RestXmlUtils.fieldXml(key, values.get(key)));}builder.append("");}return builder.append("").toString().getBytes();}{code} However, the api rest does not allow that node. It should be {code:java}..//StringBuilder builder = new StringBuilder("");StringBuilder builder = new StringBuilder("");{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 "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-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Title: Message Title
Jesús Benavente edited a comment on JENKINS-53088
Re: Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Hi Roy.I´m sorry but I've got disconneted long timethe class UpdateAlmEntityRequest implements the perform method of the GeneralPutBulkRequest class, which calls the getDataBytes method tha include the node Entities node StringBuilder builder = new StringBuilder(""); {code:java}// code placeholder private byte[] getDataBytes() {StringBuilder builder = new StringBuilder("");for (Map values : getFields()) {builder.append("");for (String key : values.keySet()) {builder.append(RestXmlUtils.fieldXml(key, values.get(key)));}builder.append("");}return builder.append("").toString().getBytes();}{code} However, the api rest does not allow that node. It should be {code:java}..//StringBuilder builder = new StringBuilder("");StringBuilder builder = new StringBuilder("");{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 "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-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Title: Message Title
Jesús Benavente edited a comment on JENKINS-53088
Re: Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Hi Roy.I´m sorry but I've got disconneted long timethe class UpdateAlmEntityRequest implements the perform method of the GeneralPutBulkRequest class, which calls the getDataBytes method tha include the Entities node StringBuilder builder = new StringBuilder(""); {code:java}// code placeholder private byte[] getDataBytes() {StringBuilder builder = new StringBuilder("");for (Map values : getFields()) {builder.append("");for (String key : values.keySet()) {builder.append(RestXmlUtils.fieldXml(key, values.get(key)));}builder.append("");}return builder.append("").toString().getBytes();}{code} However, the api rest does not allow that node. {code:java}Error: Response Error: qccore.general-errorBad RequestFailure: Server returned HTTP response code: 400 for URL: Failure: java.io.IOException: Server returned HTTP response code: 400 for URL: http://./qcbin/rest/domains/ISB_GSW/projects/HAR/test-sets/1404 {code} It should be {code:java}..//StringBuilder builder = new StringBuilder("");StringBuilder builder = new StringBuilder("");{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 "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-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Title: Message Title
Jesús Benavente edited a comment on JENKINS-53088
Re: Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Hi Roy.I´m sorry but I've got disconneted long timethe class UpdateAlmEntityRequest implements the perform method of the GeneralPutBulkRequest class, which calls the getDataBytes method tha include the Entities node StringBuilder builder = new StringBuilder(""); {code:java}// code placeholder private byte[] getDataBytes() {StringBuilder builder = new StringBuilder("");for (Map values : getFields()) {builder.append("");for (String key : values.keySet()) {builder.append(RestXmlUtils.fieldXml(key, values.get(key)));}builder.append("");}return builder.append("").toString().getBytes();}{code} However, the api rest does not allow that Entities node. {code:java}Error: Response Error: qccore.general-errorBad RequestFailure: Server returned HTTP response code: 400 for URL: Failure: java.io.IOException: Server returned HTTP response code: 400 for URL: http://./qcbin/rest/domains/ISB_GSW/projects/HAR/test-sets/1404 {code} It should be {code:java}..//StringBuilder builder = new StringBuilder("");StringBuilder builder = new StringBuilder("");{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 "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-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Title: Message Title
Jesús Benavente edited a comment on JENKINS-53088
Re: Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Hi Roy.I´m sorry but I've got disconneted long timethe class UpdateAlmEntityRequest implements the perform method of the GeneralPutBulkRequest class, which calls the getDataBytes method tha include the Entities node StringBuilder builder = new StringBuilder(""); {code:java}// code placeholder private byte[] getDataBytes() {StringBuilder builder = new StringBuilder("");for (Map values : getFields()) {builder.append("");for (String key : values.keySet()) {builder.append(RestXmlUtils.fieldXml(key, values.get(key)));}builder.append("");}return builder.append("").toString().getBytes();}{code} However, the api rest does not allow Entities node. {code:java}Error: Response Error: qccore.general-errorBad RequestFailure: Server returned HTTP response code: 400 for URL: Failure: java.io.IOException: Server returned HTTP response code: 400 for URL: http://./qcbin/rest/domains/ISB_GSW/projects/HAR/test-sets/1404 {code} It should be . It´s ok for me. {code:java}..//StringBuilder builder = new StringBuilder("");StringBuilder builder = new StringBuilder("");{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 "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-34545) Assigning roles is case sensitive, and it shouldn't be
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34545 Assigning roles is case sensitive, and it shouldn't be Change By: Oleg Nenashev Issue Type: Bug New Feature 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-53580) Access denied, user no permission to Full / Read
Title: Message Title Oleg Nenashev closed an issue as Duplicate Jenkins / JENKINS-53580 Access denied, user no permission to Full / Read Change By: Oleg Nenashev Status: Open Closed Resolution: Duplicate 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-53580) Access denied, user no permission to Full / Read
Title: Message Title Oleg Nenashev commented on JENKINS-53580 Re: Access denied, user no permission to Full / Read It duplicates JENKINS-34545 and other issues. It is a known and documented behavior of the plugin, and I do not consider it as a defect. But it is still a nice improvement to add a support of the case-insensitive mode 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-34545) Assigning roles is case sensitive, and it shouldn't be
Title: Message Title Oleg Nenashev commented on JENKINS-34545 Re: Assigning roles is case sensitive, and it shouldn't be https://github.com/jenkinsci/role-strategy-plugin/pull/43 BTW 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-53596) Modify the priority when a build is triggered by a Maven release
Title: Message Title markiewb_merc created an issue Jenkins / JENKINS-53596 Modify the priority when a build is triggered by a Maven release Issue Type: Improvement Assignee: Unassigned Components: prioritysorter-plugin Created: 2018-09-16 11:51 Priority: Major Reporter: markiewb_merc My use-case is to increase the priority of a build if it has been triggered by a Maven release. Release builds on a shared Jenkins server are normally more important than f.e. timer-triggered builds. Please have a look at my pull request at https://github.com/jenkinsci/priority-sorter-plugin/pull/46 . It is very similar to the existing TriggeredByUser implementation. Add Comment
[JIRA] (JENKINS-53597) Plugins used in pipelines are not reported
Title: Message Title Chad Williams created an issue Jenkins / JENKINS-53597 Plugins used in pipelines are not reported Issue Type: Improvement Assignee: Unassigned Components: plugin-usage-plugin Created: 2018-09-16 12:20 Labels: pipeline Priority: Major Reporter: Chad Williams Within an environment where most jobs recently have been migrated to version controlled Jenkinsfiles, I was hoping to use this plugin for cleaning up plugins that dropped out during said migration. I'm aware that the wiki states Plugins used in pipeline scripts would not be listed normally as used by jobs, because they are used dynamically in Jenkinsfiles. However, I was under the impression that not be listed normally as used by jobs implies that they are listed as something else. The wiki should clearly state that currently, plugins used by pipeline builds are not shown _at all*. That being said, it would be be very nice to have pipelines covered such that this plugin can also be of use in modern version-controlled CI setups. I understand that dynamic plugin loading is a difficulty, analyzing past builds of every job would however already be a great step forward.
[JIRA] (JENKINS-50552) Pipeline projects do not trigger libvirt VM snapshot reverts.
Title: Message Title Michael Dirks assigned an issue to Michael Dirks Jenkins / JENKINS-50552 Pipeline projects do not trigger libvirt VM snapshot reverts. Change By: Michael Dirks Assignee: Philipp Bartsch Michael Dirks 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-50552) Pipeline projects do not trigger libvirt VM snapshot reverts.
Title: Message Title Michael Dirks commented on JENKINS-50552 Re: Pipeline projects do not trigger libvirt VM snapshot reverts. Work on a fix for this has begun. I have the plugin listening to the pipeline complete event now, though I don't think I can make the "Before Snapshot" option work with Pipeline projects. 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-50552) Pipeline projects do not trigger libvirt VM snapshot reverts.
Title: Message Title Michael Dirks started work on JENKINS-50552 Change By: Michael Dirks Status: Open In Progress 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-53598) Injection of BITBUCKET_PAYLOAD should be optional
Title: Message Title Oleg Feferman created an issue Jenkins / JENKINS-53598 Injection of BITBUCKET_PAYLOAD should be optional Issue Type: Improvement Assignee: Unassigned Components: bitbucket-plugin Created: 2018-09-16 13:14 Priority: Major Reporter: Oleg Feferman In version 1.1.5 of bitbucket plugin a following change was added: fix JENKINS-32372 Inject the Payload into the build through $BITBUCKET_PAYLOAD The issue with this change is when payload is too big - builds using nunit test runner fail with a following message: System.InvalidOperationException: The environment block used to start a process cannot be longer than 65535 bytes. Your environment block is 68162 bytes long. Remove some environment variables and try again. After we looked into what environment block contains we found out that BITBUCKET_PAYLOAD is the reason for this failure. This can be easily workaround by restarting build manually or with one more simple change but in some complicated scenarios this is not an option
[JIRA] (JENKINS-46097) Milestone can be passed by older build if another build exits early
Title: Message Title Torsten Kleiber commented on JENKINS-46097 Re: Milestone can be passed by older build if another build exits early The mentioned workaround unfortunatly means running in another bug: https://issues.jenkins-ci.org/browse/JENKINS-49447 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-49447) Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input
Title: Message Title Torsten Kleiber commented on JENKINS-49447 Re: Using a milestone before an input will abort older build if there is a failure while the older build wait for a user input The mentioned workaround unfortunatly means running in another bug: https://issues.jenkins-ci.org/browse/JENKINS-46097 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-50552) Pipeline projects do not trigger libvirt VM snapshot reverts.
Title: Message Title Michael Dirks commented on JENKINS-50552 Re: Pipeline projects do not trigger libvirt VM snapshot reverts. Fix is working. Cleaning up, then submitting a PR. 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-53599) CancellationException when starting remoting Kafka agent
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-53599 CancellationException when starting remoting Kafka agent Issue Type: Bug Assignee: Jeff Thompson Components: remoting, remoting-kafka-plugin Created: 2018-09-16 18:42 Priority: Minor Reporter: Pham Vu Tuan SEVERE: Execution exception when launch: SEVERE: Execution exception when launch: java.util.concurrent.CancellationException at java.util.concurrent.FutureTask.report(FutureTask.java:121) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at io.jenkins.plugins.remotingkafka.KafkaComputerLauncher.launch(KafkaComputerLauncher.java:119) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
[JIRA] (JENKINS-53599) CancellationException when starting remoting Kafka agent
Title: Message Title
Pham Vu Tuan updated an issue
Jenkins / JENKINS-53599
CancellationException when starting remoting Kafka agent
Change By:
Pham Vu Tuan
I got this exception when starting Kafka agent with remoting 3.26 {code:java}SEVERE: Execution exception when launch: SEVERE: Execution exception when launch: java.util.concurrent.CancellationException at java.util.concurrent.FutureTask.report(FutureTask.java:121) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at io.jenkins.plugins.remotingkafka.KafkaComputerLauncher.launch(KafkaComputerLauncher.java:119) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) {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 "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsub
[JIRA] (JENKINS-53599) CancellationException when starting remoting Kafka agent
Title: Message Title Pham Vu Tuan assigned an issue to Pham Vu Tuan Jenkins / JENKINS-53599 CancellationException when starting remoting Kafka agent Change By: Pham Vu Tuan Assignee: Jeff Thompson Pham Vu Tuan 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-52995) Make Display URL Provider configurable via JCasC
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52995 Make Display URL Provider configurable via JCasC Change By: Oleg Nenashev Labels: jcasc-compatibility newbie-friendly 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-53576) Configuration-as-Code compatibility
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53576 Configuration-as-Code compatibility Change By: Oleg Nenashev Labels: jcasc-compatibility newbie-friendly 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-41180) "choice" parameter should take array for choices argument
Title: Message Title Craig Rodrigues assigned an issue to Daniel Beck Jenkins / JENKINS-41180 "choice" parameter should take array for choices argument Change By: Craig Rodrigues Assignee: Daniel Beck 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-41180) "choice" parameter should take array for choices argument
Title: Message Title Craig Rodrigues updated JENKINS-41180 Fixed in Jenkins-2.112 Jenkins / JENKINS-41180 "choice" parameter should take array for choices argument Change By: Craig Rodrigues Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41180) "choice" parameter should take array for choices argument
Title: Message Title Craig Rodrigues updated JENKINS-41180 Fixed in https://github.com/jenkinsci/jenkins/commit/6de571632c3873689981c27902ae8269fdf094eb Jenkins / JENKINS-41180 "choice" parameter should take array for choices argument Change By: Craig Rodrigues Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40358) Snippet editor: Invalid code for "choice" parameter/properties
Title: Message Title Craig Rodrigues assigned an issue to Daniel Beck Jenkins / JENKINS-40358 Snippet editor: Invalid code for "choice" parameter/properties Change By: Craig Rodrigues Assignee: Daniel Beck 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-40358) Snippet editor: Invalid code for "choice" parameter/properties
Title: Message Title Craig Rodrigues resolved as Fixed Jenkins / JENKINS-40358 Snippet editor: Invalid code for "choice" parameter/properties Change By: Craig Rodrigues Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53600) I would like to be able to remove Github.com from the API Endpoint option
Title: Message Title Denys Digtiar created an issue Jenkins / JENKINS-53600 I would like to be able to remove Github.com from the API Endpoint option Issue Type: New Feature Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-09-17 03:48 Priority: Minor Reporter: Denys Digtiar As a Jenkins Admin, I would like to be able to limit the Repository scanning to self-hosted Github Enterprise server only Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc
[JIRA] (JENKINS-35524) new ec2 slave is terminated or terminating during launch
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-35524 Re: new ec2 slave is terminated or terminating during launch The same issue happens if you use an AMI based on encrypted snapshot but the AWS profile / credentials set up for the EC2 plugin do not have permission to us this KMS key. This issue is mainly about handling AWS errors to provide a useful feedback. 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-35524) new ec2 slave is terminated or terminating during launch
Title: Message Title Allan BURDAJEWICZ edited a comment on JENKINS-35524 Re: new ec2 slave is terminated or terminating during launch The same issue happens if you use an AMI based on encrypted snapshot but the AWS profile / credentials set up for the EC2 plugin do not have permission to us this KMS key. This issue is mainly caused by AWS specific errors and the problem is mainly about handling AWS errors to provide a useful feedback to the Jenkins administrator . 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-36438) Naginator plugin throws NPE for pipeline jobs
Title: Message Title Deepak KS commented on JENKINS-36438 Re: Naginator plugin throws NPE for pipeline jobs Is there any plans for fix support re-building pipelines? There is no update on this since last two years. This is one of most basic and essential features that should be available such a widely used tool. How come there is no fix for 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-53194) InfluxDB error failed to collect data after updates
Title: Message Title Aleksi Simell updated JENKINS-53194 Fixed with PR 47. Jenkins / JENKINS-53194 InfluxDB error failed to collect data after updates Change By: Aleksi Simell Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53601) Wrong remoting printed version for Kafka agent
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-53601 Wrong remoting printed version for Kafka agent Issue Type: Bug Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-09-17 06:34 Priority: Minor Reporter: Pham Vu Tuan The remoting version was wrong for the plugin, it keeps printing 3.22 although I changed it to different version in POM file. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Jon B commented on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" The repro case here is pretty simple: 1) Create a parallel job (even a job that just does a sleep) 2) Terminate the executor's host while its running It hangs with this error every time. 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-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Jon B commented on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" I don't mean to be dramatic but this is literally the biggest problem in all of Jenkins as far as I can tell. If we lose an ec2 host while an executor is doing parallel work, we badly need for the parallel item to restart on a healthy node. When it just plain hangs, we can't do that and the user experience of hanging is not acceptable. I would recommend elevating the urgency here to the highest level to get this triaged. 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-49707) Pipeline hangs: "The channel is closing down or has closed down"
Title: Message Title Jon B edited a comment on JENKINS-49707 Re: Pipeline hangs: "The channel is closing down or has closed down" I don't mean to be dramatic but this is literally the biggest problem in all of Jenkins as far as I can tell. If we lose an ec2 host while an executor is doing parallel work, we *badly need* for the parallel item to restart on a another healthy node executor . When it just plain hangs, we can't do that and the user experience of hanging is not acceptable.I would recommend elevating the urgency here to the highest level to get this triaged. 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-53602) Dashboard no Chart
Title: Message Title J S created an issue Jenkins / JENKINS-53602 Dashboard no Chart Issue Type: Bug Assignee: Tobias Gruetzmacher Attachments: image-2018-09-17-08-49-12-308.png, image-2018-09-17-08-49-20-442.png Components: dashboard-view-plugin, slack-plugin Created: 2018-09-17 06:50 Environment: Linux RedHat 7 - Jenkins Version : 2.121.3 - Slack Version : 2.3 - Dashboard View : 2.9.11 Priority: Critical Reporter: J S Hello Jenkins Community, I have problems with the Dashboard View plugin of the Graphical Job Statistics since installing Slack plugin. Normally the Test Trend Chart looks like this on the Dashboard: But after installing Slack Plugin (I think), I don't become the Graph Chart anymore but the following message, the problem appears completely reliable. If I edit the Dashboard and Save the chart I could see again. But after a few Minutes I become again the Message "Test Summary Graph" If I Click on the Message I can see the following Stack Trace : java.lang.NullPointerException at jenkins.plugins.slack.webhook.WebhookEndpoint.getUrlName(WebhookEndpoint.java:51) at jenkins.model.Jenkins.getDynamic(Jenkins.java:3663) at java.lang.invoke.VirtualHandle.invokeExact_thunkArchetype_L(VirtualHandle.java:128) at java.lang.invoke.AsTypeHandle.invokeExact_thunkArchetype_X(AsTypeHandle.java:49) at java.lang.invoke.InvokeGenericHandle.invokeExact_thunkArchetype_X(InvokeGene
[JIRA] (JENKINS-53602) Dashboard no Chart
Title: Message Title J S updated an issue Jenkins / JENKINS-53602 Dashboard no Chart Change By: J S Labels: Dashboard Dashboard-View-Plugin Jenkins Jenkins-Bug slack 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.
