[JIRA] (JENKINS-41845) Suppress default pipeline output
Title: Message Title Reinhold Füreder commented on JENKINS-41845 Re: Suppress default pipeline output OK => I dared to file JENKINS-54904 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-54350) Java 11 compatibility: Update JTH to the recent version
Title: Message Title Oleg Nenashev updated JENKINS-54350 It was actually fixed by removing JTH dependency at all: JENKINS-54424 Jenkins / JENKINS-54350 Java 11 compatibility: Update JTH to the recent version Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved 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-54905) Support of Java 11 in Jenkinsfile Runner and Custom WAR Packager
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54905 Support of Java 11 in Jenkinsfile Runner and Custom WAR Packager Issue Type: Epic Assignee: Oleg Nenashev Components: custom-war-packager, jenkinsfile-runner Created: 2018-11-28 08:11 Labels: java11 Priority: Minor Reporter: Oleg Nenashev 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 j
[JIRA] (JENKINS-54905) Support of Java 11 in Jenkinsfile Runner and Custom WAR Packager
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54905 Support of Java 11 in Jenkinsfile Runner and Custom WAR Packager Change By: Oleg Nenashev In order to run Jenkinsfile Runner with Java 11, we need to apply some updates there to enable smooth execution on Java 11.Same with Custom WAR packager, which produces custom JFR images 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-54907) Provide a default JFR Dockerfile for Java 11 images
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-54907 Provide a default JFR Dockerfile for Java 11 images Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-54906) Custom WAR Packager should produce Java 11-compatible JFR images
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-54906 Custom WAR Packager should produce Java 11-compatible JFR images Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-54906) Custom WAR Packager should produce Java 11-compatible JFR images
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54906 Custom WAR Packager should produce Java 11-compatible JFR images Issue Type: New Feature Assignee: Oleg Nenashev Components: custom-war-packager Created: 2018-11-28 08:16 Priority: Minor Reporter: Oleg Nenashev Right now Custom WAR Packager implements a custom build flow for a Jenkinsfile Runner Dockerfile. JAXB libraries are not included into the bundle, and the flags are not set. So the image won't work on Java 11 even if you set a Java 11 base image in CWP settings. Add Comment
[JIRA] (JENKINS-54907) Provide a default JFR Dockerfile for Java 11 images
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54907 Provide a default JFR Dockerfile for Java 11 images Issue Type: New Feature Assignee: Oleg Nenashev Components: jenkinsfile-runner Created: 2018-11-28 08:16 Priority: Minor Reporter: Oleg Nenashev 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-54355) ClassNotFound: java.sql.Date in JDK 11 in Pipeline Utility Steps
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54355 ClassNotFound: java.sql.Date in JDK 11 in Pipeline Utility Steps Change By: Oleg Nenashev Summary: ClassNotFound: java.sql.Date in JDK 11 in Pipeline Utility Steps 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-48509) Push UFT test results to JIRA via Jenkins
Title: Message Title Vidya Hiremath commented on JENKINS-48509 Re: Push UFT test results to JIRA via Jenkins Hi, I also need support on this to append UFT test results to Jira via Jenkins. I am trying to execute UFT test cases using Jenkin as CI tool and repository used here is SVN. I have impediments in pushing UFT test results to Jira via Jenkin. 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-54674) PCT: Add Docker packaging for Java 11
Title: Message Title Oleg Nenashev updated JENKINS-54674 Integrated into the master branch. Unfortnately there was no PCT releases for a long time, so we cannot just release it (CC Raul Arabaolaza). But it's not required for Java 11 needs anyway Jenkins / JENKINS-54674 PCT: Add Docker packaging for Java 11 Change By: Oleg Nenashev Status: In Review 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-54885) Azure VM Plugin: 1: The storage account name already exists. Use a different name.
Title: Message Title Olivier Vernin commented on JENKINS-54885 Re: Azure VM Plugin: 1: The storage account name already exists. Use a different name. Jakub Michalec true it is and with exactly the same issue INFRA-1923 We are affected since yesterday 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-54885) Azure VM Plugin: 1: The storage account name already exists. Use a different name.
Title: Message Title Jie Shen commented on JENKINS-54885 Re: Azure VM Plugin: 1: The storage account name already exists. Use a different name. Jakub Michalec I have no idea about this. I don't have the access to their configuration. 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-54885) Azure VM Plugin: 1: The storage account name already exists. Use a different name.
Title: Message Title Jie Shen commented on JENKINS-54885 Re: Azure VM Plugin: 1: The storage account name already exists. Use a different name. The new version 0.7.5 has just been released and should fix this issue. It may take a little time to syn on Jenkins plugin manager. Sorry for all your inconvenience again. 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-54656) cvs plugin broken - not possible to add new projects
Title: Message Title Torsten Werner updated an issue Jenkins / JENKINS-54656 cvs plugin broken - not possible to add new projects Change By: Torsten Werner Priority: Major Blocker 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-54885) Azure VM Plugin: 1: The storage account name already exists. Use a different name.
Title: Message Title Jack Chen commented on JENKINS-54885 Re: Azure VM Plugin: 1: The storage account name already exists. Use a different name. Thanks for the quick fix Jie Shen ! Any idea what the root cause is ? 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-54656) cvs plugin broken - not possible to add new projects
Title: Message Title Torsten Werner commented on JENKINS-54656 Re: cvs plugin broken - not possible to add new projects I'm watching the same issue. Steps to reproduce: create a new project select CVS for SCM set the required values for CVSROOT, password (if needed), project try to save It is currently impossible to create a new CVS project. It is even impossible to change the source code management. This is a blocker, it is more than critical. I use Jenkins 2.138.2, CVS plugin is the same version like reported: 2.14 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-54885) Azure VM Plugin: 1: The storage account name already exists. Use a different name.
Title: Message Title Jie Shen commented on JENKINS-54885 Re: Azure VM Plugin: 1: The storage account name already exists. Use a different name. Jack Chen, it is caused by inconsistent results from API side. I have created an issue on github repo azure-rest-api-specs . And I think the root cause of this issue may on the service side changes. 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-54908) allow delay of starting new instances
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-54908 allow delay of starting new instances Issue Type: New Feature Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2018-11-28 09:03 Priority: Minor Reporter: Dominik Bartholdi I would like to have an option to configure the ec2 plugin to wait before it starts a new ec2 instance. e.g. If I have an ec2 agent running, then I would like jenkins to wait for X-minutes before it starts an other instance. During this time the already running agent might get available and then there is no need to start a second instance. btw. I'm not sure what I missed, but I'm not able to see the value for instanceCapStr anywhere on the UI... Add Comment
[JIRA] (JENKINS-45930) Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException)
Title: Message Title Joerg Schwaerzler commented on JENKINS-45930 Re: Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException) Ulli Hafner: Thanks for the quick answer. Sounds great 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-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Jose Blas Camacho Taboada started work on JENKINS-49997 Change By: Jose Blas Camacho Taboada 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-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-49997 Jenkins / JENKINS-49997 Pipeline Declarative post unsuccessful block Change By: Jose Blas Camacho Taboada Status: In Progress Review 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-54885) Azure VM Plugin: 1: The storage account name already exists. Use a different name.
Title: Message Title Olivier Vernin commented on JENKINS-54885 Re: Azure VM Plugin: 1: The storage account name already exists. Use a different name. I confirm that the fix is deployed and working on ci.jenkins.io 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-44566) Unable to validate template when specifying existing storage account with custom image URI
Title: Message Title Roni Yessod commented on JENKINS-44566 Re: Unable to validate template when specifying existing storage account with custom image URI Hi, we are suddenly getting the following error: "The storage account name already exists. Use a different name." We haven't change the storage account we use and the custom URL image is located in that storage account. Any ideas on what could be the problem? 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-44566) Unable to validate template when specifying existing storage account with custom image URI
Title: Message Title Roni Yessod reopened an issue Jenkins / JENKINS-44566 Unable to validate template when specifying existing storage account with custom image URI Change By: Roni Yessod Resolution: Fixed Status: Closed Reopened 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-54885) Azure VM Plugin: 1: The storage account name already exists. Use a different name.
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-54885 Azure VM Plugin: 1: The storage account name already exists. Use a different name. Change By: Jie Shen Status: In Progress Resolved Resolution: Fixed Released As: 0.7.5 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-52967) Add support for https storage account
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-52967 Add support for https storage account Change By: Jie Shen Status: In Progress Resolved Resolution: Fixed Released As: 0.7.5 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-54909) Parallel Runner execuable cannot be found on Native OS
Title: Message Title Tamas Florin started work on JENKINS-54909 Change By: Tamas Florin 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-54909) Parallel Runner execuable cannot be found on Native OS
Title: Message Title Tamas Florin created an issue Jenkins / JENKINS-54909 Parallel Runner execuable cannot be found on Native OS Issue Type: Bug Assignee: Tamas Florin Components: hp-application-automation-tools-plugin Created: 2018-11-28 09:50 Environment: Windows OS with any native langage: Russian, Chinese, etc. Priority: Minor Reporter: Tamas Florin steps: 1. create a jenkins job 2. add step "Execute MF tests from file system" 3. build job to run on a node pointing to English OS + UFT in english, run finishes successfully 4. edit job to change node to Native OS + UFT in native language, run failed with error below: could not to find parallel_runner_executable 5. Go to the native node machine itself, run "parallenrunner", runner executable is found actually Add Comment
[JIRA] (JENKINS-54909) Parallel Runner execuable cannot be found on Native OS
Title: Message Title Tamas Florin closed an issue as Fixed Jenkins / JENKINS-54909 Parallel Runner execuable cannot be found on Native OS Change By: Tamas Florin Status: In Progress Closed 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-54909) Parallel Runner execuable cannot be found on Native OS
Title: Message Title Tamas Florin updated an issue Jenkins / JENKINS-54909 Parallel Runner execuable cannot be found on Native OS Change By: Tamas Florin steps:1. create a jenkins job2. add step "Execute MF tests from file system"3. build job to run on a node pointing to English OS + UFT in english, run finishes successfully 4. edit job to change node to Native OS + UFT in native language, run failed with error below: could not to find parallel_runner_executable5. Go to the native node machine itself, run "parallenrunner", runner executable is found actually 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-54909) Parallel Runner execuable cannot be found on Native OS
Title: Message Title Tamas Florin updated an issue Jenkins / JENKINS-54909 Parallel Runner execuable cannot be found on Native OS Change By: Tamas Florin steps Steps to reproduce the issue :1. create a jenkins job2. add step "Execute MF tests from file system"3. build job to run on a node pointing to English OS + UFT in english, run finishes successfully4. edit job to change node to Native OS + UFT in native language, run failed with error below: could not to find parallel_runner_executable5. Go to the native node machine itself, run "parallenrunner", runner executable is found actually 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-54569) java.lang.NullPointerException when upding status in TFS/Team Services
Title: Message Title Bart van der Meulen commented on JENKINS-54569 Re: java.lang.NullPointerException when upding status in TFS/Team Services I use the 'Trigger generic build' action 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-54752) Ansi plugin fails to render formatted console output
Title: Message Title Chiel de K commented on JENKINS-54752 Re: Ansi plugin fails to render formatted console output Same here. Disabling ansicolor make it able to tail th elog again in Jenkins. Without disabling it we can no longer see the complete log... While tailing we get the IndexOutOfBoundsException at a certain moment and when loading the logs of a finished build the logs are clipped. 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-54569) java.lang.NullPointerException when upding status in TFS/Team Services
Title: Message Title Florian Bäuerle commented on JENKINS-54569 Re: java.lang.NullPointerException when upding status in TFS/Team Services Thank you for the information. Apparently I broke your Jenkins due to some misassumptions I made about the plugin's abilities to trigger Jenkins Jobs – sorry. I think I've got a working fix here: https://github.com/mrflow/tfs-plugin/tree/wip/jenkins-54569 But I tested that with a Multibranch Pipeline Job (You seem to use a Freestyle Job) and the Job triggering part of the plugin is pretty messy. So I would kindly like to ask you to test the fix if possible. Building the plugin is possible with (you need maven): mvn package 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-42136) shared-library abstraction causing RejectedExecutionException when running sh() commands
Title: Message Title Carlos Sanchez commented on JENKINS-42136 Re: shared-library abstraction causing RejectedExecutionException when running sh() commands I see RejectedExecutionException when more jobs than "Max connections to Kubernetes API" are running 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-54910) Could not able to Build Azure Function APP using MSBuild Plugin
Title: Message Title sumanthnath gangavarapu created an issue Jenkins / JENKINS-54910 Could not able to Build Azure Function APP using MSBuild Plugin Issue Type: Bug Assignee: Lionel Cabasson Components: msbuild-plugin Created: 2018-11-28 11:21 Priority: Blocker Reporter: sumanthnath gangavarapu I could not able to build azure function app project using MSBuild plugin. Below is the error from console output: : warning MSB4078: The project file "***.csproj" is not supported by MSBuild and cannot be built. Add Comment
[JIRA] (JENKINS-54910) Could not able to Build Azure Function APP using MSBuild Plugin
Title: Message Title sumanthnath gangavarapu commented on JENKINS-54910 Re: Could not able to Build Azure Function APP using MSBuild Plugin Lionel Cabasson Please let me know if you need any further information. This is a blocker for us since one month. Thank you 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-54843) Maven Enforcer Plugin crashes with java.level=11
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54843 Maven Enforcer Plugin crashes with java.level=11 Change By: Baptiste Mathus Labels: java11 java11-compatibility 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Martin Mössner commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher One possible workaround: 1. Go the "Plugin Manager" "Advanced" tab. 2. Without any change press the "submit" button of the "HTTP Proxy Configuration". 3. Go to the "Updates" tab. 4. Press the "Check now" button. Works on our prod- and testsystem (V 2.153). 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-54897) Unexpected error in launching a agent after restart
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54897 Re: Unexpected error in launching a agent after restart Did you see if the plugin retry to connect automatically? if should be because has the default configuration to make it `launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15`, after 15 seconds of the fail it must retry to connect The duplicate messages bothered me, it is like two processes were running at the same time, Which JDK do you use? [11/27/18 16:18:08] [SSH] Opening SSH connection to jenkins-slave.example.com:22. [11/27/18 16:18:29] [SSH] SSH host key matches key in Known Hosts file. Connection will be allowed. [11/27/18 16:18:29] [SSH] SSH host key matches key in Known Hosts file. Connection will be allowed. [11/27/18 16:18:29] [SSH] Authentication successful. [11/27/18 16:18:29] [SSH] Authentication successful. [11/27/18 16:18:29] [SSH] The remote user's environment is: [11/27/18 16:18:29] [SSH] The remote user's environment is: 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Kurt updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Kurt Priority: Blocker Critical 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-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Kurt commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher I can confirm that the workaround does work for us, too. Martin Mössner Good work! How did you figure that out? Have you already checked if the problem re-appears after some time or a Jenkins restart? I can't test that on my side at the moment as I cannot restart Jenkins without coordination. From theses findings, can we conclude, that the issue is related to the proxy credential storage? Anyway, I think that justifies reducing the severity to Critical (it's still possible to obtain new plugins and updates now). 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-54911) Windows Slave disconnects automatically
Title: Message Title Prashant B created an issue Jenkins / JENKINS-54911 Windows Slave disconnects automatically Issue Type: Bug Assignee: Emilio Escobar Components: windows-slaves-plugin Created: 2018-11-28 12:09 Environment: Production Labels: slave Priority: Critical Reporter: Prashant B Hello, We are using Windows Slave to execute powershell scripts. slave is configured using DCOM method (username and password). for last 10 days, windows slave automatically disconnects and reconnects back. due to this running scripts are failing. can someone help me to troubleshoot the issue. Master : Run's on RHEL 7.4 and Version : 2.89.4 Windows Slave : Windows 2016 Event Log: "The Jenkins agent (jenkinsslave-C__jenkins) at C:\jenkins service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly." please do let me know which logs are required,i'll upload them
[JIRA] (JENKINS-54911) Windows Slave disconnects automatically
Title: Message Title Prashant B updated an issue Jenkins / JENKINS-54911 Windows Slave disconnects automatically Change By: Prashant B Attachment: jenkins-slave.err.log Attachment: jenkins-slave.wrapper.log 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-54524) Improper Encoding of Sync Status
Title: Message Title Simon Martineau commented on JENKINS-54524 Re: Improper Encoding of Sync Status Raising the priority as for now my Jenkins instance is completely unusable (see previous comment). 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-54524) Improper Encoding of Sync Status
Title: Message Title Simon Martineau updated an issue Jenkins / JENKINS-54524 Improper Encoding of Sync Status Change By: Simon Martineau 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-54912) TestResult-Section renders imagemap-div's to body
Title: Message Title Sven Appenrodt created an issue Jenkins / JENKINS-54912 TestResult-Section renders imagemap-div's to body Issue Type: Bug Assignee: Timothy Bingaman Attachments: body.PNG, section.PNG Components: sectioned-view-plugin Created: 2018-11-28 12:29 Environment: jenkins 2.153 (windows) plugin version 2.15 chromium webbrowser on ubuntu Priority: Major Reporter: Sven Appenrodt We derrived the SectionenView class in our own plugin to support updates via ajax refresh (used jelly-includes for minimum dependencies). The usecase is: we're showing some results on a monitor hanging on the wall which is connected with a small banana-pi. This one has no cpu power so normal jenkins-site-refresh will cause displaying blank sites for some millies. Using ajax refresh's will prevent this kind of flickering. We know, there are some memleaks mentionen in JENKINS-41100 for which we found some workarounds. But still, after some time the chromium browser crashes while displaying the site. We figured out: the DOM tree is growing larger and larger over the time until the browser is not able to handle it anymore. Reason: the TestResult-Section renders its view to the normal dom-position (see attachted screenshot: section.png) but for the clickable area overlay at the diagram-image is added as div container to the body element (see picture body.png). Problem: using ajax replaces the "section-div" with the new content, but cannot prevent adding additional divs to the body node. And the your plugin will add more... and more.. and more. The behavior is reproducable under e
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Martin Mössner commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher First I've made a change on "no-proxy-hosts". The change itself had nothing to do with proxy functionality, because it was a removement of an old full qualified server. So I was very wondering. Then the problem re-appears again and so I've submitted again (without change) the HTTP Proxy Configuration. I don't know how often it re-appears, but still it's happening... 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-54397) Microfocus Health Analyzer all checks are executed on Master instead of Slave
Title: Message Title Daniel Gront stopped work on JENKINS-54397 Change By: Daniel Gront Status: In Progress Open 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-54397) Microfocus Health Analyzer all checks are executed on Master instead of Slave
Title: Message Title Daniel Gront updated JENKINS-54397 Jenkins / JENKINS-54397 Microfocus Health Analyzer all checks are executed on Master instead of Slave Change By: Daniel Gront 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-54397) Microfocus Health Analyzer all checks are executed on Master instead of Slave
Title: Message Title Daniel Gront updated JENKINS-54397 Jenkins / JENKINS-54397 Microfocus Health Analyzer all checks are executed on Master instead of Slave Change By: Daniel Gront Status: In Review 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-54913) CPS serialization failure - Mysterious serialization errors
Title: Message Title Nicklas Wallgren created an issue Jenkins / JENKINS-54913 CPS serialization failure - Mysterious serialization errors Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-11-28 12:59 Environment: java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_111-8u111-b14-3~14.04.1-b14 workflow-aggregator 2.5 workflow-api 2.33 workflow-basic-steps 2.12 workflow-cps 2.60 workflow-cps-global-lib 2.12 workflow-durable-task-step 2.26 workflow-job 2.29 workflow-multibranch 2.20 workflow-scm-step 2.7 workflow-step-api 2.16 workflow-support 2.22 Priority: Minor Reporter: Nicklas Wallgren I'm getting a serialization error from time to time. com.google.gson.JsonPrimitive [org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860), org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:569), org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65), org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56), org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:50), org.jboss.marshalling.river.RiverObjectOutputStream.writeObjectOverride(RiverObjectOutputStream.java:179), java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344), java.util.HashMap.internalWriteEntries(HashMap.java:1785), java.util.HashMap.writeObject(HashMap.java:1362), sun.reflect.GeneratedMethodAccessor447.invoke(Unknown Source), sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43), java.lang.reflect.Method.invoke(Method.java:498), org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:273), org.jboss.marshalling.rive
[JIRA] (JENKINS-54913) CPS serialization failure - Mysterious serialization errors
Title: Message Title
Nicklas Wallgren updated an issue
Jenkins / JENKINS-54913
CPS serialization failure - Mysterious serialization errors
Change By:
Nicklas Wallgren
I'm getting a serialization error from time to time. {code:java} com.google.gson.JsonPrimitive[org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860), org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:569), org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65), org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56), org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:50), org.jboss.marshalling.river.RiverObjectOutputStream.writeObjectOverride(RiverObjectOutputStream.java:179), java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344), java.util.HashMap.internalWriteEntries(HashMap.java:1785), java.util.HashMap.writeObject(HashMap.java:1362), sun.reflect.GeneratedMethodAccessor447.invoke(Unknown Source), sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43), java.lang.reflect.Method.invoke(Method.java:498), org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:273), org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:976), org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854), org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032), org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988), org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854), org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65), org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56), org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:50), org.jboss.marshalling.river.RiverObjectOutputStream.writeObjectOverride(RiverObjectOutputStream.java:179), java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344), java.util.HashMap.internalWriteEntries(HashMap.java:1785), java.util.HashMap.writeObject(HashMap.java:1362), sun.reflect.GeneratedMethodAccessor447.invoke(Unknown Source), sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43), java.lang.reflect.Method.invoke(Method.java:498), org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:273), org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:976), org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854), org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032), org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988), org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854), org.j
[JIRA] (JENKINS-54700) Findbugs SAXParser not found
Title: Message Title Tomasz Lisowski commented on JENKINS-54700 Re: Findbugs SAXParser not found Downgrading to 1.0.0-beta4 did not solve the problem in my case 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-54914) Purge ATH
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-54914 Purge ATH Issue Type: Epic Assignee: Lucie Votypkova Components: acceptance-test-harness Created: 2018-11-28 13:06 Priority: Minor Reporter: Oliver Gondža 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-54915) Remove no_docker tests now when upstream CI supports docker
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-54915 Remove no_docker tests now when upstream CI supports docker Issue Type: Epic Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2018-11-28 13:08 Priority: Minor Reporter: Oliver Gondža https://github.com/jenkinsci/acceptance-test-harness/tree/master/src/test/java/plugins/no_docker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54915) Remove no_docker tests now when upstream CI supports docker
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-54915 Remove no_docker tests now when upstream CI supports docker Change By: Oliver Gondža Issue Type: Epic Task 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-54916) Collapse trivial tests to meaningful use-cases
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-54916 Collapse trivial tests to meaningful use-cases Issue Type: Task Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2018-11-28 13:10 Priority: Minor Reporter: Oliver Gondža 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-54700) Findbugs SAXParser not found
Title: Message Title Christian Asselmeyer commented on JENKINS-54700 Re: Findbugs SAXParser not found Tomasz Lisowski I also had to downgrade analysis-model-api to 1.0.0-beta13 to get the Warning NG 1.0.0-beta4 working properly. 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-54700) Findbugs SAXParser not found
Title: Message Title Matt Wilson updated an issue Jenkins / JENKINS-54700 Findbugs SAXParser not found Change By: Matt Wilson We've traditionally used the individual plugins (PMD, Findbugs) but came across this when one of our projects moved from Findbugs to Spotbugs. We really like how the report looks and we're keen to use it in place of the older plugins...I've run into some trouble using the Findbugs option on the new plugin. When I try to collect findbugs information I get this:[FindBugs] [ERROR] Parsing of file 'x' failed due to an exception: org.dom4j.DocumentException: Sax error Nested exception: SAX2 driver class org.apache.xerces.parsers.SAXParser not found at edu.umd.cs.findbugs.SortedBugCollection.doReadXML(SortedBugCollection.java:391) at edu.umd.cs.findbugs.SortedBugCollection.doReadXML(SortedBugCollection.java:368) at edu.umd.cs.findbugs.SortedBugCollection.readXML(SortedBugCollection.java:355) at edu.hm.hafner.analysis.parser.FindBugsParser.readXml(FindBugsParser.java:230) at edu.hm.hafner.analysis.parser.FindBugsParser.parse(FindBugsParser.java:175) at edu.hm.hafner.analysis.parser.FindBugsParser.parse(FindBugsParser.java:111) at edu.hm.hafner.analysis.parser.FindBugsParser.parse(FindBugsParser.java:97) at edu.hm.hafner.analysis.IssueParser.parse(IssueParser.java:70) at io.jenkins.plugins.analysis.core.util.FilesScanner.aggregateIssuesOfFile(FilesScanner.java:101) at io.jenkins.plugins.analysis.core.util.FilesScanner.scanFiles(FilesScanner.java:85) at io.jenkins.plugins.analysis.core.util.FilesScanner.invoke(FilesScanner.java:68) at io.jenkins.plugins.analysis.core.util.FilesScanner.invoke(FilesScanner.java:29) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3085) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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)Caused by: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found The strange part is if I copy the findbugs xml files to a different job I don't get the error. The plugin does complain about not being able to find the source but it still process the data and gives me a nice report. I guess the issue is being triggered when the plugin attempts to parse through the source code. just an addition here. I'm seeing the same issue when I try and use spotbugs... I know that isn't a surprise, but I thought I'd post it.[SpotBugs] [ERROR] Parsing of file '...' failed due to an exception: *14:41:22* *14:41:22* org.dom4j.DocumentException: Sax error Nested exception: SAX2 driver class org.apache.xerces.parsers.SAXParser not found*14:41:22* at edu.
[JIRA] (JENKINS-54917) Github pull request builds created but not triggered
Title: Message Title Vincent de Lagabbe created an issue Jenkins / JENKINS-54917 Github pull request builds created but not triggered Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-11-28 13:26 Environment: Jenkins version: 2.138.3 Github branch source plugin version: 2.4.1 Labels: github github-branch-source-plugin pull-request Priority: Minor Reporter: Vincent de Lagabbe I use the github branch source plugin with a github.com hosted organization The organization setup is: Discover branches: "Exclude branches that are also files as PR" Discover pull requests from origin: "Both the current pull request revision and the pull request merged with the current target branch revision" I recursively updates sub modules and checkout over SSH When a PR is created, the two pull request jenkins jobs "PR-head" and "PR-merge" are created, but Jenkins does not start them The "Organization event" log shows messages: > No automatic builds for PR-XX-head > No automatic builds for PR-XX-merge Why are the PRs jobs not built ? Thank you very much
[JIRA] (JENKINS-54885) Azure VM Plugin: 1: The storage account name already exists. Use a different name.
Title: Message Title Peter Salvatore commented on JENKINS-54885 Re: Azure VM Plugin: 1: The storage account name already exists. Use a different name. Upgraded to 0.7.5 and we are back in business. Thank you so much Jie Shen ! 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-54918) Purge machine support in ATH
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-54918 Purge machine support in ATH Issue Type: Task Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2018-11-28 13:47 Priority: Minor Reporter: Oliver Gondža https://github.com/jenkinsci/acceptance-test-harness/tree/master/src/main/java/org/jenkinsci/test/acceptance/machine This should remove a lot of maven dependencies including jclouds Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-s
[JIRA] (JENKINS-49778) If one stage in the pipeline fails, all the states are marked/color with the same status color
Title: Message Title Costin Caraivan closed an issue as Duplicate Jenkins / JENKINS-49778 If one stage in the pipeline fails, all the states are marked/color with the same status color Change By: Costin Caraivan 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-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-54919
Newly defined parameters aren't available in Declarative agent configuration on first build
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-11-28 13:53
Priority:
Major
Reporter:
Andrew Bayer
This is similar to both JENKINS-40574 and JENKINS-43911 (well, how JENKINS-43911 would behave from 1.2 onward - previously it was just that environment was evaluated after agent during execution) - parameters is evaluated at the beginning of the Declarative runtime, but agent is populated before that, at the very start of execution. So if params.FOO already exists when the build starts, then agent { label params.FOO }}} will work fine, but if it's a new parameter (like, say, on first build of a branch), {{params.FOO's value there will end up as null. A workaround for now is to do label "${params.FOO ?: 'whatever-the-default-value-should-be'}", but I'll work on a better solution.
Add Comment
[JIRA] (JENKINS-26313) Workflow script fails if CPS-transformed methods are called from constructors
Title: Message Title Yngvar Kristiansen commented on JENKINS-26313 Re: Workflow script fails if CPS-transformed methods are called from constructors Is there any way of putting a nice error message in the jenkins log? It took some time to figure this out. In fact, all of my @NonCps-related problems have been time consuming, especially when you have never heard of it before. 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-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title Shahin Kordasti commented on JENKINS-41497 Re: Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries I am confused as to what the "fix" is. I enabled the setting "Dont trigger build a build on commit notifications" for all our Jenkins jobs and they still get triggered whenever the global library SCM has a commit and this keeps happening after the first time. Do I need to remove the global library and re-add it again for this to work? 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-45966) " 'Jenkinsfile' not found" due to race condition w/ webhooks and the GH Contents API
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-45966 " 'Jenkinsfile' not found" due to race condition w/ webhooks and the GH Contents API Change By: Josh Soref *The Symptom:*When using an enterprise GHE that is running slow (or I imagine, with a very fast jenkins instance, maybe even on production GH), a check for a Jenkinsfile in the branch events will say that one was not found, even though there is a Jenkinsfile in the PR's origin branch, and in the target branch. This seems to happen if you "slam" GH by creating a commit, branch, and PR all in one go (which people do with automated commits). *What I think is the cause:*As far as I can tell, GitHubSCMProbe is relying on the contents API to determine if a new branch or PR has a Jenkinsfile. When building merge PRs, it uses the merge refs with the contents API, but the merge refs aren't actually ready yet when GH sends out it's its webhooks. To prove this, I spun up a ruby sinatra app that listens for a PR webhook and immediately calls back to GH with the contents API. This reliably fails to find a ref (returns "No commit found for the ref"), unless you put a short sleep between when it receives the webhook, and when it calls out for content. You can find that here: [https://github.com/SpencerMalone/test-repo] if you want to play with it yourself. This is probably something that GH needs to fix, so I've sent them a support ticket, but just incase they are unable to, or in case it takes an exceedingly long time, I've opened this. I think in cases where we get a ref not found from the contents API while responding to branch events, there should be a short delay + retry. Add Comment
[JIRA] (JENKINS-50220) Wrong link target for pipeline syntax link in pipeline jobs
Title: Message Title Torsten Werner commented on JENKINS-50220 Re: Wrong link target for pipeline syntax link in pipeline jobs It is fixed. The link is working again. 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-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title Andrew Bayer started work on JENKINS-54919 Change By: Andrew Bayer 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-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title Andrew Bayer commented on JENKINS-54919 Re: Newly defined parameters aren't available in Declarative agent configuration on first build PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/301 - let's see if it doesn't regress anything else... 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-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title Andrew Bayer updated JENKINS-54919 Jenkins / JENKINS-54919 Newly defined parameters aren't available in Declarative agent configuration on first build Change By: Andrew Bayer Status: In Progress Review 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-54688) Operating System informations are anonymized
Title: Message Title Francisco Fernández updated JENKINS-54688 Jenkins / JENKINS-54688 Operating System informations are anonymized Change By: Francisco Fernández Status: In Review Resolved Resolution: Fixed Released As: support-core-2.52 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-54920) Refactor AboutJenkins class
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-54920 Refactor AboutJenkins class Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2018-11-28 14:55 Priority: Minor Reporter: Josh Soref The AboutJenkins class is huge (>1000 lines) and coverage in AboutJenkinsTest consists of a single function mayBeDateSmokes. I'm trying to improve the output of the AboutJenkins code, and potentially improve the sanitization. But in order to do that (and not be laughed at by my colleagues), I need to be able to write tests for the pieces of code I'm changing. As is, AboutJenkins isn't practically testable in small units because everything is hidden in private class or private static. I understand that people may have pending pull requests (they should get them merged) and they may have code which depends on minute details of how this code works. If they care, they should get their changes merged and then help write tests documenting their expectations which would make it easier for future contributors to understand the constraints the code lives with when they write changes. Add Comment
[JIRA] (JENKINS-54920) Refactor AboutJenkins class
Title: Message Title Josh Soref commented on JENKINS-54920 Re: Refactor AboutJenkins class For reference, my current proposal is here: https://github.com/jsoref/support-core-plugin/tree/refactor I won't make a PR for it until jenkinsci/support-core-plugin#155 is merged 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-54882) Websphere Deploy Plugin Error ADMC0016E
Title: Message Title Hernan Tavella commented on JENKINS-54882 Re: Websphere Deploy Plugin Error ADMC0016E I changed the port to 8879 that seems to be the correct because now i can get the avaibles targets when i hit the button in the plug in config. But now i have a new error : Artifact is being deployed to virtual host: default_host Deploying 'AApp' to IBM WebSphere Application Server Error deploying to IBM WebSphere Application Server: Failed to install artifact: Failure uploading archive to server Performing rollback of 'AApp' WARNING: Artifact doesn't exist rollback repository Build step 'Deploy To IBM WebSphere Application Server' changed build result to FAILURE Finished: FAILURE 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-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Stephen Morley commented on JENKINS-54654 Re: A recent update breaks builds by escaping slashes to percent signs in workspace paths Jesse Glick that might explain why the setting was not updated but why is it not valid to reference a directory outside of the JENKINS_HOME. Personally I don't like keeping active data sets in the "Program Files (x86)" directory. This has worked for over 5 years now and suddenly it fails. (Turns out we also have a problem with some utility which is not working with the spaces in the path name so our builds are broken using this form but without it Jenkins just chokes). 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-32250) Multi-branch projects do not support Dashboard views
Title: Message Title Tomasz Lisowski commented on JENKINS-32250 Re: Multi-branch projects do not support Dashboard views Is there any workaround for this issue? 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-54921) can not release connection
Title: Message Title
Sylvia Xie created an issue
Jenkins / JENKINS-54921
can not release connection
Issue Type:
Bug
Assignee:
Karl-Heinz Marbaise
Components:
java-client-api
Created:
2018-11-28 15:33
Priority:
Minor
Reporter:
Sylvia Xie
public InputStream getFile(URI path) throws IOException { HttpGet getMethod = new HttpGet(path); HttpResponse response = client.execute(getMethod, localContext); jenkinsVersion = ResponseUtils.getJenkinsVersion(response); httpResponseValidator.validateResponse(response); return new RequestReleasingInputStream(response.getEntity().getContent(), getMethod); } when invoke getFile method and occur exception at validateResponse(), connetions cannot be released
Add Comment
[JIRA] (JENKINS-54922) Generated markdown should work in MacDown.app
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-54922
Generated markdown should work in MacDown.app
Issue Type:
Bug
Assignee:
Emilio Escobar
Components:
support-core-plugin
Created:
2018-11-28 15:50
Priority:
Minor
Reporter:
Josh Soref
Currently the generated Markdown doesn't do a good enough job of escaping {} characters and the sanitizer loves to generate {} which means that labels and node names have a tendency to generate partially italicized content when rendered in at least MacDown and potentially many other renderers. Sample raw content:
* computer_reliable_bulletin (`user_junior_process.slaves.DumbSlave`)
- Description:_Java 8_
- Executors: 1
- Remote FS root: `/home/jenkins`
- Labels: label_transparent_court label_religious_blood pipeline view_medieval_corn label_mutual_violation label_related_favourite label_easy_insurance
Rendered as:
computer reliable bulletin (user_junior_process.slaves.DumbSlave)
Description: Java 8
Executors: 1
Remote FS root: /home/jenkins
Labels: label_transparent_court label_religious_blood pipeline view_medieval_corn label_mutual_violation label_related_favourite label_easy_insurance
[JIRA] (JENKINS-54849) SVN_REVISION and/or SVN_REVISION_X not being set
Title: Message Title Alex Earl commented on JENKINS-54849 Re: SVN_REVISION and/or SVN_REVISION_X not being set These issues look related 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-54922) Generated markdown should work in MacDown.app
Title: Message Title Josh Soref commented on JENKINS-54922 Re: Generated markdown should work in MacDown.app jenkinsci/support-core-plugin#155 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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Fernando Nasser commented on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
Another option: def status = sh(returnStatus: true, returnStdout: true, returnStderr: true, script: "git merge --no-edit $branches") Would return a Map, which can be seen as { 'rc': , 'stdout': , 'stderr': } A compromise would be to have both stderr and stdout together (easy to capture?) { 'rc': , 'output': } P.S.: The 'returnStderr' does not exist yet, I'll file a JIRA for it as it is useful independently.
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-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title John Hill commented on JENKINS-41497 Re: Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries This is a pretty significant issue. We've removed our Global Pipeline Library config, restarted jenkins and it's still triggering events 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-52860) Remove dependency on Build Flow
Title: Message Title Tim Jacomb updated JENKINS-52860 merged https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/91 Jenkins / JENKINS-52860 Remove dependency on Build Flow Change By: Tim Jacomb 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-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title John Hill updated an issue Jenkins / JENKINS-41497 Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries Change By: John Hill Comment: This is a pretty significant issue. We've removed our Global Pipeline Library config, restarted jenkins and it's still triggering events 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-54871) "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven
Title: Message Title Brad DeWindt commented on JENKINS-54871 Re: "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven Valentin, Thanks for the quick response. I was able to fix my issue by adding tuning the JVM arguments as suggested: "-Dgatling.compilerJvmArgs="-Xmx512m" My test now runs without any issue. Thanks again! Brad 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-54871) "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven
Title: Message Title Brad DeWindt edited a comment on JENKINS-54871 Re: "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven Valentin,Thanks for the quick response. I was able to fix my this issue by adding tuning the JVM arguments as suggested:"-Dgatling.compilerJvmArgs="-Xmx512m"My test now runs without any issue.Thanks again!Brad 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-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Andrew Bayer updated JENKINS-49997 This'll be in 1.3.4. Jenkins / JENKINS-49997 Pipeline Declarative post unsuccessful block Change By: Andrew Bayer Status: In Review 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-54923) Spawning processes from build on windows server
Title: Message Title Sampath Kumar Kokkiripati created an issue Jenkins / JENKINS-54923 Spawning processes from build on windows server Issue Type: Bug Assignee: Lionel Cabasson Components: msbuild-plugin Created: 2018-11-28 17:38 Environment: Windows Priority: Major Reporter: Sampath Kumar Kokkiripati I am currently experiencing this issue on windows server Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure [Office365connector] No webhooks to notify Finished: FAILURE Add Comment
[JIRA] (JENKINS-54923) Spawning processes from build on windows server
Title: Message Title Sampath Kumar Kokkiripati updated an issue Jenkins / JENKINS-54923 Spawning processes from build on windows server Change By: Sampath Kumar Kokkiripati I am currently experiencing this issue on Jenkins running on windows server Process leaked file descriptors. See [https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors] for more information Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure [Office365connector] No webhooks to notify Finished: FAILURE [Jenkins ver. 2.143|https://jenkins.io/] 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-54923) Spawning processes from build on windows server
Title: Message Title Sampath Kumar Kokkiripati updated an issue Jenkins / JENKINS-54923 Spawning processes from build on windows server Change By: Sampath Kumar Kokkiripati I am currently experiencing this issue on Jenkins running on windows server Process leaked file descriptors. See [https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors] for more informationBuild step 'Build a Visual Studio project or solution using MSBuild' marked build as failure[Office365connector] No webhooks to notifyFinished: FAILURE 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-53184) Plugins and Core versions are redacted when they have 4 groups of digits
Title: Message Title Josh Soref commented on JENKINS-53184 Re: Plugins and Core versions are redacted when they have 4 groups of digits I think AboutContent could just add/remove the plugin versions as it goes. I might look into doing 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-49577) delete bundle has no confirmation
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-49577 delete bundle has no confirmation Change By: Josh Soref Summary: delete bundle has no comfirmation confirmation 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-54923) Spawning processes from build on windows server
Title: Message Title Sampath Kumar Kokkiripati updated an issue Jenkins / JENKINS-54923 Spawning processes from build on windows server Change By: Sampath Kumar Kokkiripati * I am currently experiencing this issue on Jenkins running on windows server * It is killing my job in middle without executing the next build step and job is finishing with the failure message. Process leaked file descriptors. See [https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors] for more information Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure [Office365connector] No webhooks to notify * Finished: FAILURE * * [Jenkins ver. 2.143|https://jenkins.io/] * 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-54923) Spawning processes from build on windows server
Title: Message Title Sampath Kumar Kokkiripati updated an issue Jenkins / JENKINS-54923 Spawning processes from build on windows server Change By: Sampath Kumar Kokkiripati *I am currently experiencing this issue on Jenkins running on windows server* I'm currently using M.S. Build Script for build and deployment. It is killing my job in middle without executing the next build step and job is finishing with the following failure message. Process leaked file descriptors. See [https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors] for more information Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure [Office365connector] No webhooks to notify *Finished: FAILURE**[Jenkins ver. 2.143|https://jenkins.io/]* 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-54924) Script Runs In Script Console But Not Job DSL
Title: Message Title
Ben Moseley created an issue
Jenkins / JENKINS-54924
Script Runs In Script Console But Not Job DSL
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2018-11-28 17:51
Priority:
Minor
Reporter:
Ben Moseley
Related to JENKINS-28701 The following script executes just fine in script console, but the import throws an error in job console output. I looked at a ticket with an almost identical name, but I don't fully grasp how to solve the problem. I got the base script from another user and made some minor modifications to make it fit the intended purpose:
import hudson.plugins.shelveproject.ShelveProjectTaskdef daysBack=45;
Jenkins.instance.getAllItems(AbstractProject.class).each{ it->
def lastBuild=it.getLastBuild()
if(it.name.startsWith("BuildThor") || it.name.startsWith("IntTestThor")){
if(lastBuild != null){
def back = Calendar.getInstance()
back.set(Calendar.DAY_OF_YEAR,back.get(Calendar.DAY_OF_YEAR)-daysBack)
if (lastBuild.getTime().compareTo(back.getTime()) < 0) {
println it.name + " was built over " + daysBack + " days ago: " + lastBuild.getTime()
if (it instanceof AbstractProject){
println " *PROJECT SHELVED THIS ITERATION*"
def spt= new ShelveProjectTask(it)
Hudson.getInstance().getQueue().schedule(spt , 0 );
}
}
}
else{
println it.name + " was not shelved this iteration."
}
}
}
ERROR
[JIRA] (JENKINS-44042) jnlp slave ConnectionRefusalException None of the protocols were accepted
Title: Message Title Nirav Patel commented on JENKINS-44042 Re: jnlp slave ConnectionRefusalException None of the protocols were accepted fyi, i saw this issue when my jenkins hosts' (my mac) IP changed. I updated kubernetes cloud config's jenkins host and tunnel host ip and that fixed it for me. 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-44042) jnlp slave ConnectionRefusalException None of the protocols were accepted
Title: Message Title Nirav Patel edited a comment on JENKINS-44042 Re: jnlp slave ConnectionRefusalException None of the protocols were accepted fyi, i saw this issue when my jenkins hosts' (my mac) IP changed. I updated kubernetes cloud config's jenkins host and tunnel host ip and that fixed it for me. It also happens if IPs are pointing to some other jenkins home from which you haven't submitted original job. 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.
