[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title MANJU GL updated an issue Jenkins / JENKINS-53073 HPLauncher Throws Error (HP PlugIn) Change By: MANJU GL Attachment: image-2019-12-16-13-34-05-450.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193067.1534441884000.8027.1576483500346%40Atlassian.JIRA.
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title MANJU GL updated an issue Jenkins / JENKINS-53073 HPLauncher Throws Error (HP PlugIn) Change By: MANJU GL Attachment: image-2019-12-16-13-37-21-547.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193067.1534441884000.8031.1576483680263%40Atlassian.JIRA.
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title MANJU GL commented on JENKINS-53073 Re: HPLauncher Throws Error (HP PlugIn) Hi, command given in jenkins file is : c:\jenkins\workspace\TA\HpToolsLauncher.exe -paramfile props13122019112708250.txt i executed this command directly in slaves's command prompt, it throws an error- path for paramfile doesn't exist hence I executed the following command with the complete path to paramfile, it's working c:\jenkins\workspace\TA\HpToolsLauncher.exe -paramfile c:\jenkins\workspace\TA\props13122019112708250.txt but if i execute the job from jenkins it won't work, please refer the screenshot below: Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193067.1534441884000.8035.1576483740370%40Atlassian.JIRA.
[JIRA] (JENKINS-58345) Show trend graph on job summary, not full coverage results
Title: Message Title Shenyu Zheng updated an issue Jenkins / JENKINS-58345 Show trend graph on job summary, not full coverage results Change By: Shenyu Zheng Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200459.1562248796000.8038.1576483800586%40Atlassian.JIRA.
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title MANJU GL updated an issue Jenkins / JENKINS-53073 HPLauncher Throws Error (HP PlugIn) Change By: MANJU GL Attachment: image-2019-12-16-13-34-05-450.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193067.1534441884000.8041.1576483800782%40Atlassian.JIRA.
[JIRA] (JENKINS-60359) Use standard bread crumbs
Title: Message Title Shenyu Zheng updated an issue Jenkins / JENKINS-60359 Use standard bread crumbs Change By: Shenyu Zheng Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203380.1575442072000.8044.1576483860270%40Atlassian.JIRA.
[JIRA] (JENKINS-60484) Blue Ocean organization folder job can't be parsed by 2.204.1-rc build
Title: Message Title Mark Waite updated JENKINS-60484 Jenkins / JENKINS-60484 Blue Ocean organization folder job can't be parsed by 2.204.1-rc build Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203573.1576374806000.8049.1576484340811%40Atlassian.JIRA.
[JIRA] (JENKINS-60484) Blue Ocean organization folder job can't be parsed by 2.204.1-rc build
Title: Message Title Mark Waite updated JENKINS-60484 Thanks Oleg Nenashev! You are exactly correct. I made a mistake in a merge of that configuration file on Nov 15, 2019 and lost the opening scm tag that you detected. Thanks for finding it and my apologies for the distraction during the late stages of 2.204.1-rc testing. Jenkins / JENKINS-60484 Blue Ocean organization folder job can't be parsed by 2.204.1-rc build Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this messag
[JIRA] (JENKINS-54064) Gradle plugin uses legacy plugin format
Title: Message Title
Daniel Beck commented on JENKINS-54064
Re: Gradle plugin uses legacy plugin format
René Scheibe It's a problem that manifests in Gradle Plugin (as reported) but if it's packaged using Gradle JPI Plugin, then the latter needs to be updated, or changed, to implement a change similar to https://github.com/jenkinsci/maven-hpi-plugin/commit/603535119122e820751607812bb7d0bd3b8c3556 The corresponding core change is https://github.com/jenkinsci/jenkins/commit/f7330d7a158eff6705706b1f812993a9b918c351 Basically, do not deliver a WEB-INF/classes directory, but a WEB-INF/${pluginName}.jar file.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194683.1539463436000.8055.1576485120526%40Atlassian.JIRA.
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title Anda Sorina Laakso commented on JENKINS-53073 Re: HPLauncher Throws Error (HP PlugIn) As I see from the pictured attached, you are using "Execute Windows batch command" type of task, not the tasks included in our plugin. And I was referring to this command: "Unable to change DCOM settings. To chage it manually: run dcomcnfg.exe -> My Computer -> DCOM Config -> QuickTest Professional Automation -> Identity -> and select The Interactive Userdetailed error is : Requested registry access is not allowed." Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193067.1534441884000.8072.1576486020485%40Atlassian.JIRA.
[JIRA] (JENKINS-60493) Configure System page save redirect broken when Job Import is installed
Title: Message Title Emilio Escobar assigned an issue to Emilio Escobar Jenkins / JENKINS-60493 Configure System page save redirect broken when Job Import is installed Change By: Emilio Escobar Assignee: Emilio Escobar Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203582.1576452931000.8076.1576486321528%40Atlassian.JIRA.
[JIRA] (JENKINS-60493) Configure System page save redirect broken when Job Import is installed
Title: Message Title Emilio Escobar started work on JENKINS-60493 Change By: Emilio Escobar Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203582.1576452931000.8078.1576486321708%40Atlassian.JIRA.
[JIRA] (JENKINS-59840) NullPointerException when activating the plugin
Title: Message Title Stefan commented on JENKINS-59840 Re: NullPointerException when activating the plugin I just saw that 1.7 was released including #18. Should that fix this issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202575.157138872.8080.1576487100254%40Atlassian.JIRA.
[JIRA] (JENKINS-22494) Multiconfiguration project does not respect label restrictions
Title: Message Title Mark Waite commented on JENKINS-22494 Re: Multiconfiguration project does not respect label restrictions Shai Shapira all the details of using exclusions are included in the comments. If that's not enough, you might consider switching to the Jenkins pipeline. Blog posts for Declarative pipeline and scripted pipeline describe the techniques to define matrix configurations and to exclude portions of the matrix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154296.1396565762000.8082.1576487820850%40Atlassian.JIRA.
[JIRA] (JENKINS-53208) Split main configuration page, takes too long to load
Title: Message Title Dirk Heinrichs commented on JENKINS-53208 Re: Split main configuration page, takes too long to load While that's perfectly true, it's also true that not everyone who uses Jenkins is also a (Java) developer. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193234.1535030695000.8116.1576487940152%40Atlassian.JIRA.
[JIRA] (JENKINS-50157) Zip step fails to execute and dies with syntax error in a parallel stage with post step
Title: Message Title Andreas Urban commented on JENKINS-50157 Re: Zip step fails to execute and dies with syntax error in a parallel stage with post step Works in script blocks: https://issues.jenkins-ci.org/browse/JENKINS-44078?focusedCommentId=349855&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-349855 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189174.1520985892000.8119.1576488000224%40Atlassian.JIRA.
[JIRA] (JENKINS-60496) Support for incremental maven module build
Title: Message Title Christian Schmitt created an issue Jenkins / JENKINS-60496 Support for incremental maven module build Issue Type: Improvement Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2019-12-16 09:28 Labels: maven incrementals feature-request pipeline-maven Priority: Minor Reporter: Christian Schmitt Until now we used to process multibranch maven projects with the Multi-Branch Project Plugin which under the hood uses the maven-project-plugin for maven builds. This maven-project-plugin has this great feature for doing incremental builds - meaning just rebuild the maven modules which have changed in the SCM since the last build. We used this feature heavily beacause we have many multimodule maven projects (also multi levels) and this feature could decrease build times fundamentally. Now the Multi-Branch Project Plugin is deprecated and we are advised to move to the Pipeline-Multibranch Plugin. This plugin uses the pipeline-maven-plugin under the hood for maven builds. In this plugin we are missing an incremental build mechanism. Build times would increase dramatically. Is there any hope to get this feaure also into the pipeline-maven-plugin? Thanks and best Regards Christian
[JIRA] (JENKINS-60489) beta forensics plugin reports no class def found for FilteredLog
Title: Message Title Ulli Hafner commented on JENKINS-60489 Re: beta forensics plugin reports no class def found for FilteredLog Thanks for reporting! Seems that I forgot to release the corresponding warning-ng plugin as well. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203578.1576439299000.8124.1576488720828%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60479 Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203564.1576265676000.8140.1576490640545%40Atlassian.JIRA.
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title Marslo Jiao started work on JENKINS-60343 Change By: Marslo Jiao Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203357.1575290252000.8157.1576491720187%40Atlassian.JIRA.
[JIRA] (JENKINS-59840) NullPointerException when activating the plugin
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59840 NullPointerException when activating the plugin Change By: Oliver Gondža Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202575.157138872.8159.1576492080295%40Atlassian.JIRA.
[JIRA] (JENKINS-59840) NullPointerException when activating the plugin
Title: Message Title Oliver Gondža commented on JENKINS-59840 Re: NullPointerException when activating the plugin Stefan, My apology for not waiting for your confirmation. Yes, this is expected to resolve that issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202575.157138872.8163.1576492140485%40Atlassian.JIRA.
[JIRA] (JENKINS-60497) Filesystem list parameter reset to default when rebuilding previous job
Title: Message Title René Korthaus created an issue Jenkins / JENKINS-60497 Filesystem list parameter reset to default when rebuilding previous job Issue Type: Bug Assignee: Unassigned Components: filesystem-list-parameter-plugin Created: 2019-12-16 10:28 Environment: Jenkins 2.190.3 Java OpenJDK Runtime Environment 1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10 filesystem-list-parameter-plugin 0.0.5 rebuild 1.31 Priority: Minor Reporter: René Korthaus When trying to rebuild a previous job using the rebuild plugin, any filesystem list parameter value of job run to rebuild is discarded and the parameter values are set to the default value. Steps to reproduce: Create a test directory on the master node with two empty subdirectories "A" and "B" Create a new freestyle job Open job configuration Check "This project is parameterized" Click "Add Parameter" Choose "File system objects list parameter" Configure name "test123", NodeName "master", Path "/path/to/test/dir" (created in step 1), Filesystem object type "ALL" Save configuration Build job with parameters: parameter directory list shows "A" by default, select "B" and click "Build"
[JIRA] (JENKINS-60493) Configure System page save redirect broken when Job Import is installed
Title: Message Title Emilio Escobar resolved as Fixed Jenkins / JENKINS-60493 Configure System page save redirect broken when Job Import is installed Change By: Emilio Escobar Status: In Progress Resolved Resolution: Fixed Released As: job-import-plugin:3.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203582.1576452931000.8161.1576492140456%40Atlassian.JIRA.
[JIRA] (JENKINS-59840) NullPointerException when activating the plugin
Title: Message Title Oliver Gondža edited a comment on JENKINS-59840 Re: NullPointerException when activating the plugin [~stefan_kb], even when using the file you provided, I di did not get the NPE you have witnessed. I could have been caused by the fact config was essentially reset to defaults and spnego misbehaved this way, but I am not convinced. I have proposed a fix to address that and added logging with the effective config that is being passed to spnego. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202575.157138872.8166.1576492140532%40Atlassian.JIRA.
[JIRA] (JENKINS-59840) NullPointerException when activating the plugin
Title: Message Title Oliver Gondža resolved as Fixed Jenkins / JENKINS-59840 NullPointerException when activating the plugin Change By: Oliver Gondža Status: Open Resolved Resolution: Fixed Released As: 1.7 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202575.157138872.8170.1576492202670%40Atlassian.JIRA.
[JIRA] (JENKINS-59840) NullPointerException when activating the plugin
Title: Message Title Oliver Gondža edited a comment on JENKINS-59840 Re: NullPointerException when activating the plugin [~stefan_kb], My apology for not waiting for your confirmation. Yes, this is expected to resolve that the issue with config lost . The NPE will either go away as well or we will have better diagnostics. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202575.157138872.8168.1576492201751%40Atlassian.JIRA.
[JIRA] (JENKINS-60457) NullPointerException in h.p.e.p.content.ScriptContent.renderTemplate
Title: Message Title Andrea Giardini commented on JENKINS-60457 Re: NullPointerException in h.p.e.p.content.ScriptContent.renderTemplate I forgot to mention that this is quite annoying for us because the email with the stacktrace is sent to every contributor of our project Looks like every email that is part of the git history is included Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203535.1576141507000.8188.1576495020235%40Atlassian.JIRA.
[JIRA] (JENKINS-60498) Duplicate Ids for ConfigFiles when using CasC
Title: Message Title Sebastian Mahr created an issue Jenkins / JENKINS-60498 Duplicate Ids for ConfigFiles when using CasC Issue Type: Bug Assignee: Dominik Bartholdi Attachments: image-2019-12-16-12-21-51-944.png Components: config-file-provider-plugin, configuration-as-code-plugin Created: 2019-12-16 11:29 Environment: Jenkins 2.190.2 (docker) config-file-provider-plugin 3.6.2 configuration-as-code-plugin 1.34 Labels: plugin Priority: Minor Reporter: Sebastian Mahr In our organization, we configure our jenkins instances using configuration-as-code for initial provisioning, but allow changes to the configuration over time. When providing a set of config files like that and modifying a configuration like maven settings, the edited object does not get modified, instead a new config file object with the same id is created when saving: grep -B 1 "" org.jenkinsci.plugins.configfiles.GlobalConfigFiles.xml GlobalSettingsNexus -- GlobalSettingsNexus -- GlobalSettingsNexus When jobs request a config file by id, which instance th
[JIRA] (JENKINS-60499) Plugin of JCloud won't work anymore because of GCP zone changes
Title: Message Title Donatas Navidonskis created an issue Jenkins / JENKINS-60499 Plugin of JCloud won't work anymore because of GCP zone changes Issue Type: Task Assignee: Fritz Elfert Components: jclouds-plugin Created: 2019-12-16 11:59 Priority: Critical Reporter: Donatas Navidonskis Hi, it seems plugin of jcloud have hardcoded zones in the code and it doesn't fetching directly from the api. So when the GCP changed, or one of the datacenter went down, JCloud won't work anymore, because that zone can be found anymore. Here is the trace message: java.lang.IllegalStateException: zone https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/us-central1-d not present in [https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/asia-east1-a, https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/asia-east1-b, https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/asia-east1-c, https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/asia-east2-c, https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/asia-east2-b, https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/asia-east2-a, https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/asia-northeast1-a, https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/asia-northeast1-b, https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/asia-northeast1-c, https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/asia-northeast2-b, https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/asia-northeast2-c, https://www.googleapis.com/compute/v1/projects/PROJECT_NAME_IN_GCP/zones/asia-northeast2-a, https://www.googleapis.com/compute/v1/projects/PRO
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title MANJU GL updated an issue Jenkins / JENKINS-53073 HPLauncher Throws Error (HP PlugIn) Change By: MANJU GL Attachment: image-2019-12-16-17-47-32-199.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193067.1534441884000.8211.1576498680262%40Atlassian.JIRA.
[JIRA] (JENKINS-60499) Plugin of JCloud won't work anymore because of GCP zone changes
Title: Message Title Fritz Elfert commented on JENKINS-60499 Re: Plugin of JCloud won't work anymore because of GCP zone changes In the jenkins pugin, there are no hardcoded zones for shure. The zones come from the apache-jclouds library (which also provides the gcloud CLI). Please report a bug there at https://jclouds.apache.org/reference/report-a-bug/ (or find an already open one). After that, add a link to that bug here, so I can track it. If a fix gets released by the apache-jclouds project, I will be happy to upgrade to the fixed version) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203590.1576497582000.8214.1576498740132%40Atlassian.JIRA.
[JIRA] (JENKINS-60117) Rework sorting for the Enabled columns of Installed in Plugin Manager
Title: Message Title Kalana Wijethunga updated an issue Jenkins / JENKINS-60117 Rework sorting for the Enabled columns of Installed in Plugin Manager Change By: Kalana Wijethunga Attachment: jenkins.jpg Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202966.157338165.8220.1576498860588%40Atlassian.JIRA.
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title MANJU GL updated an issue Jenkins / JENKINS-53073 HPLauncher Throws Error (HP PlugIn) Change By: MANJU GL Attachment: image-2019-12-16-17-50-41-355.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193067.1534441884000.8217.1576498860538%40Atlassian.JIRA.
[JIRA] (JENKINS-60117) Rework sorting for the Enabled columns of Installed in Plugin Manager
Title: Message Title Kalana Wijethunga commented on JENKINS-60117 Re: Rework sorting for the Enabled columns of Installed in Plugin Manager Hi Oleg Nenashev, I was able to reproduce the issue and I followed the same process used in https://github.com/jenkinsci/jenkins/pull/4298 to group the data rows into Enabled, Enabled and cannot disable and Disabled and add the group name to data attribute of the table data column. I used the following logic to group these 3 categories. Enabled - plugin.Enabled and !hasMandatoryDependencies Enabled and cannot disable - plugin.Enabled and hasMandatoryDependencies Disabled - If it doesnt belong to above 2 categories(essentially !plugin.Enabled should belong to this) I am able to correctly sort by Enable column using these groups. But some of the actually enabled plugins are yielding false for plugin.Enabled and therefore they are categorized into the Disabled group, which is wrong. I cant understand why some of the actually working plugins are giving the result false for plugin.Enabled . Do you have any idea what is causing this? I have attached a screenshot for further clarification. I have setup the checked attribute of the highlighted input tab directly from the value plugin.Enabled. You can see that it has resulted in a false Any help would be much appreciated Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title MANJU GL commented on JENKINS-53073 Re: HPLauncher Throws Error (HP PlugIn) Hi, sorry that was the wrong screenshot, as i was also trying to use execute from windows batch command. its the same error when i execute using the plugin given option : I checked the dcom settings, it is 'Interactve' user only. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193067.1534441884000.8223.1576498980629%40Atlassian.JIRA.
[JIRA] (JENKINS-36089) Pipeline support for Promoted Builds Plugin
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-36089 Pipeline support for Promoted Builds Plugin Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172050.1466438354000.8372.1576499175316%40Atlassian.JIRA.
[JIRA] (JENKINS-57634) GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-57634 GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I) Change By: Oleg Nenashev Assignee: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199564.1558605601000.8666.1576499220534%40Atlassian.JIRA.
[JIRA] (JENKINS-36089) Pipeline support for Promoted Builds Plugin
Title: Message Title Oleg Nenashev started work on JENKINS-36089 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172050.1466438354000.8374.1576499175338%40Atlassian.JIRA.
[JIRA] (JENKINS-36089) Pipeline support for Promoted Builds Plugin
Title: Message Title Oleg Nenashev commented on JENKINS-36089 Re: Pipeline support for Promoted Builds Plugin I am marking it as "In progress", because I am working on some bits as my Christmas hack Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172050.1466438354000.8520.1576499177426%40Atlassian.JIRA.
[JIRA] (JENKINS-57634) GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)
Title: Message Title Oleg Nenashev updated JENKINS-57634 This GSoC 2019 project was not completed. I will move the relevant tasks to JENKINS-36089 Jenkins / JENKINS-57634 GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I) Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr
[JIRA] (JENKINS-57689) Custom Steps for remaining promotion Conditions
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Moving the issue to the JENKINS-36089 EPIC Jenkins / JENKINS-57689 Custom Steps for remaining promotion Conditions Change By: Oleg Nenashev Assignee: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199624.155888260.8695.1576499462779%40Atlassian.JIRA.
[JIRA] (JENKINS-57877) PromotionBadge compatibility with pipelines
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Moving the issue to the JENKINS-36089 EPIC Jenkins / JENKINS-57877 PromotionBadge compatibility with pipelines Change By: Oleg Nenashev Assignee: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199840.1559812947000.8693.1576499462573%40Atlassian.JIRA.
[JIRA] (JENKINS-57687) Create new custom steps to be included in the declarative pipeline for Upstream Promotion.
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Moving the issue to the JENKINS-36089 EPIC Jenkins / JENKINS-57687 Create new custom steps to be included in the declarative pipeline for Upstream Promotion. Change By: Oleg Nenashev Assignee: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199622.1558882281000.8685.1576499461437%40Atlassian.JIRA.
[JIRA] (JENKINS-57777) Make the Upstream Promotion Condition Compatible with Pipeline.
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Moving the issue to the JENKINS-36089 EPIC Jenkins / JENKINS-5 Make the Upstream Promotion Condition Compatible with Pipeline. Change By: Oleg Nenashev Assignee: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199724.1559288134000.8678.1576499461066%40Atlassian.JIRA.
[JIRA] (JENKINS-57861) Make(Manual Condition) work incorporating all the required dependencies.
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Moving the issue to the JENKINS-36089 EPIC Jenkins / JENKINS-57861 Make(Manual Condition) work incorporating all the required dependencies. Change By: Oleg Nenashev Assignee: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199823.1559746182000.8700.1576499463324%40Atlassian.JIRA.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Moving the issue to the JENKINS-36089 EPIC Jenkins / JENKINS-57903 New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin. Change By: Oleg Nenashev Assignee: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199868.1559891975000.8698.1576499463074%40Atlassian.JIRA.
[JIRA] (JENKINS-57937) Write a criteria list for steps in release flow
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Moving the issue to the JENKINS-36089 EPIC Jenkins / JENKINS-57937 Write a criteria list for steps in release flow Change By: Oleg Nenashev Assignee: Jon Brohauge Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199913.1560169778000.8689.1576499461641%40Atlassian.JIRA.
[JIRA] (JENKINS-57921) Add new Custom Step for Self-Promotion
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Moving the issue to the JENKINS-36089 EPIC Jenkins / JENKINS-57921 Add new Custom Step for Self-Promotion Change By: Oleg Nenashev Assignee: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199893.1560090278000.8687.1576499461529%40Atlassian.JIRA.
[JIRA] (JENKINS-57688) Refactor the remaining Extension points inside "promoted_builds.conditions" and also refactor those inside the "promoted_builds.integrations.jobdsl" package
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Moving the issue to the JENKINS-36089 EPIC Jenkins / JENKINS-57688 Refactor the remaining Extension points inside "promoted_builds.conditions" and also refactor those inside the "promoted_builds.integrations.jobdsl" package Change By: Oleg Nenashev Assignee: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199623.1558882486000.8683.1576499461332%40Atlassian.JIRA.
[JIRA] (JENKINS-57816) Make (Self-Promotion)condition work incorporating all the dependencies.
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Moving the issue to the JENKINS-36089 EPIC Jenkins / JENKINS-57816 Make (Self-Promotion)condition work incorporating all the dependencies. Change By: Oleg Nenashev Assignee: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199770.1559556651000.8676.1576499461009%40Atlassian.JIRA.
[JIRA] (JENKINS-57839) Make the existing features,processes and implementations pipeline compatible (eg: Assigning Badges,Promoting Builds)
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Moving the issue to the JENKINS-36089 EPIC Jenkins / JENKINS-57839 Make the existing features,processes and implementations pipeline compatible (eg: Assigning Badges,Promoting Builds) Change By: Oleg Nenashev Assignee: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199797.1559647559000.8674.1576499460977%40Atlassian.JIRA.
[JIRA] (JENKINS-57637) Detach the required classes and their descriptors from "hudson.plugins.promoted_builds" package and refactor them for Pipeline Compatibility.
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Moving the issue to the JENKINS-36089 EPIC Jenkins / JENKINS-57637 Detach the required classes and their descriptors from "hudson.plugins.promoted_builds" package and refactor them for Pipeline Compatibility. Change By: Oleg Nenashev Assignee: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199567.1558606596000.8681.1576499461190%40Atlassian.JIRA.
[JIRA] (JENKINS-60500) Break out the Promotion API plugin
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-60500 Break out the Promotion API plugin Issue Type: Task Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2019-12-16 12:32 Priority: Minor Reporter: Oleg Nenashev It would be great to have a new Promotion API plugin which includes shareable functionality from the Promoted Builds plugin. It would help us to reuse the plugin on instances without AbstractProject and Freestyle builds in the future Add Comment
[JIRA] (JENKINS-60499) Plugin of JCloud won't work anymore because of GCP zone changes
Title: Message Title Fritz Elfert edited a comment on JENKINS-60499 Re: Plugin of JCloud won't work anymore because of GCP zone changes In the jenkins pugin, there are no hardcoded zones for shure.The zones come from the apache-jclouds library (which also provides the gcloud CLI as far as I know ).Please report a bug there at [https://jclouds.apache.org/reference/report-a-bug/] (or find an already open one). After that, add a link to that bug here, so I can track it. If a fix gets released by the apache-jclouds project, I will be happy to upgrade to the fixed version) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203590.1576497582000.8703.1576499640140%40Atlassian.JIRA.
[JIRA] (JENKINS-60499) Plugin of JCloud won't work anymore because of GCP zone changes
Title: Message Title Fritz Elfert started work on JENKINS-60499 Change By: Fritz Elfert Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203590.1576497582000.8705.1576499701048%40Atlassian.JIRA.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Oleg Nenashev stopped work on JENKINS-57903 Change By: Oleg Nenashev Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199868.1559891975000.8710.1576499703088%40Atlassian.JIRA.
[JIRA] (JENKINS-60500) Break out the Promotion API plugin
Title: Message Title Oleg Nenashev started work on JENKINS-60500 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203591.1576499557000.8706.1576499701541%40Atlassian.JIRA.
[JIRA] (JENKINS-57877) PromotionBadge compatibility with pipelines
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-57877 PromotionBadge compatibility with pipelines Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199840.1559812947000.8713.1576499704110%40Atlassian.JIRA.
[JIRA] (JENKINS-57921) Add new Custom Step for Self-Promotion
Title: Message Title Oleg Nenashev stopped work on JENKINS-57921 Change By: Oleg Nenashev Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199893.1560090278000.8708.1576499702301%40Atlassian.JIRA.
[JIRA] (JENKINS-57937) Write a criteria list for steps in release flow
Title: Message Title Oleg Nenashev assigned an issue to Jon Brohauge Jenkins / JENKINS-57937 Write a criteria list for steps in release flow Change By: Oleg Nenashev Assignee: Jon Brohauge Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199913.1560169778000.8719.1576499760979%40Atlassian.JIRA.
[JIRA] (JENKINS-57816) Make (Self-Promotion)condition work incorporating all the dependencies.
Title: Message Title Oleg Nenashev stopped work on JENKINS-57816 Change By: Oleg Nenashev Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199770.1559556651000.8717.1576499760579%40Atlassian.JIRA.
[JIRA] (JENKINS-57937) Write a criteria list for steps in release flow
Title: Message Title Oleg Nenashev commented on JENKINS-57937 Re: Write a criteria list for steps in release flow Jon Brohaugeshould we just close it? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199913.1560169778000.8721.1576499761519%40Atlassian.JIRA.
[JIRA] (JENKINS-60499) Plugin of JCloud won't work anymore because of GCP zone changes
Title: Message Title Donatas Navidonskis commented on JENKINS-60499 Re: Plugin of JCloud won't work anymore because of GCP zone changes Well it seems it was fixed in 2.2.0 https://issues.apache.org/jira/browse/JCLOUDS-1463 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203590.1576497582000.8723.1576499822926%40Atlassian.JIRA.
[JIRA] (JENKINS-60499) Plugin of JCloud won't work anymore because of GCP zone changes
Title: Message Title Donatas Navidonskis commented on JENKINS-60499 Re: Plugin of JCloud won't work anymore because of GCP zone changes But jcloud plugin is not released with latest version https://github.com/jenkinsci/jclouds-plugin only in master at the moment. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203590.1576497582000.8725.1576499880421%40Atlassian.JIRA.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-57903 New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin. Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199868.1559891975000.8728.1576499880464%40Atlassian.JIRA.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Oleg Nenashev started work on JENKINS-57903 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199868.1559891975000.8730.1576499880492%40Atlassian.JIRA.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Oleg Nenashev commented on JENKINS-57903 Re: New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin. Some code from Prastik Gyawali which could be reused: https://github.com/jenkinsci/promoted-builds-plugin/pull/137/commits/9c51d9e14d021769b4f38a80f0b08f65637cff62 https://github.com/jenkinsci/promoted-builds-plugin/pull/137/commits/d1ce53de6aa5622899b21768cca4e813c0fab024 https://github.com/jenkinsci/promoted-builds-plugin/pull/137/commits/8aa5cec8c4feada2e5d14e6a8eaab66dc8c75cca https://github.com/jenkinsci/promoted-builds-plugin/pull/137/commits/4fa0b38bf7dc5dc832ede16b522fc896d970ee62 Some of this code can be retrieved from commits though it might be easier to just rewrite the code. https://github.com/jenkinsci/promoted-builds-plugin/pull/131 will be closed as discussed above Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199868.1559891975000.8734.1576500240181%40Atla
[JIRA] (JENKINS-60499) Plugin of JCloud won't work anymore because of GCP zone changes
Title: Message Title Fritz Elfert commented on JENKINS-60499 Re: Plugin of JCloud won't work anymore because of GCP zone changes The upcoming version (which uses jclouds-2.2.0) is available here: https://ci.jenkins.io/job/Plugins/job/jclouds-plugin/job/master/lastSuccessfulBuild/artifact/jclouds-plugin/target/jclouds-jenkins.hpi Please install that manually, test it and let me know if that fixes your problem. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203590.1576497582000.8736.1576500600210%40Atlassian.JIRA.
[JIRA] (JENKINS-60305) Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Title: Message Title Calin Caliman commented on JENKINS-60305 Re: Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required Same issue here. Jenkins 2.206 (deployed on CentOS) Jira Plugin 3.0.11 Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203300.1574868719000.8746.1576501740539%40Atlassian.JIRA.
[JIRA] (JENKINS-60489) beta forensics plugin reports no class def found for FilteredLog
Title: Message Title Ulli Hafner resolved as Fixed Warnings plugin 8.0.0-beta1 is available now. Jenkins / JENKINS-60489 beta forensics plugin reports no class def found for FilteredLog Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Released As: 8.0.0-beta1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are su
[JIRA] (JENKINS-60499) Plugin of JCloud won't work anymore because of GCP zone changes
Title: Message Title Donatas Navidonskis commented on JENKINS-60499 Re: Plugin of JCloud won't work anymore because of GCP zone changes Snapshot works (2.16-SNAPSHOT (private-015f6e5d-?)). Go ahead and release it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203590.1576497582000.8752.1576501920438%40Atlassian.JIRA.
[JIRA] (JENKINS-60477) Jenkins job is over running while creating jar files
Title: Message Title Divya Ganesan commented on JENKINS-60477 Re: Jenkins job is over running while creating jar files Hi Pierre Beitz, Thanks for your response. Provided Heap size in individual job as -Xmx512m and -Xmx1024m and ran the job. But still not working and getting the below error but now it is not showing 'out of memory ' error. Error: "[xmlbean] warning: [options] bootstrap class path not set in conjunction with -source 1.4" Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203560.1576254956000.8750.1576501920255%40Atlassian.JIRA.
[JIRA] (JENKINS-60499) Plugin of JCloud won't work anymore because of GCP zone changes
Title: Message Title Fritz Elfert updated JENKINS-60499 Will be released soon. Jenkins / JENKINS-60499 Plugin of JCloud won't work anymore because of GCP zone changes Change By: Fritz Elfert Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https:
[JIRA] (JENKINS-60501) Trigger change requests depending on source and/or target branch name
Title: Message Title Mauricio Villegas created an issue Jenkins / JENKINS-60501 Trigger change requests depending on source and/or target branch name Issue Type: New Feature Assignee: Unassigned Components: basic-branch-build-strategies-plugin Created: 2019-12-16 13:28 Priority: Minor Reporter: Mauricio Villegas The current version of the basic-branch-build-strategies-plugin (1.3.2) the change requests strategy triggers for all change requests. It would be a good extension to allow triggering only change requests whose source and/or target branch name matches a regular _expression_ pattern. Add Comment
[JIRA] (JENKINS-57634) GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)
Title: Message Title Jesse Glick updated JENKINS-57634 Jenkins / JENKINS-57634 GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I) Change By: Jesse Glick Resolution: Won't Do Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199564.1558605601000.8774.1576503240903%40Atlassian.JIRA.
[JIRA] (JENKINS-57634) GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I)
Title: Message Title Jesse Glick resolved as Won't Do (just correcting Status) Jenkins / JENKINS-57634 GSoC '19: artifact promotion in Jenkins' pipeline. (Coding Phase-I) Change By: Jesse Glick Status: Reopened Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.g
[JIRA] (JENKINS-51225) Support for GitHub Checks API
Title: Message Title Ian Katz commented on JENKINS-51225 Re: Support for GitHub Checks API I can probably take on a proof of concept for this work as a groovy script. It would end up being something like the "junit" pipeline step, which reads a file from the workspace. What I would need to know before I can start is how to read the stored GitHub credentials and/or instantiate a REST client with them. Is the proper way to do that described somewhere? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190545.1525878773000.8794.1576504321544%40Atlassian.JIRA.
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title MANJU GL updated an issue Jenkins / JENKINS-53073 HPLauncher Throws Error (HP PlugIn) Change By: MANJU GL Attachment: image-2019-12-16-19-26-37-556.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193067.1534441884000.8846.1576504621654%40Atlassian.JIRA.
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title MANJU GL updated an issue Jenkins / JENKINS-53073 HPLauncher Throws Error (HP PlugIn) Change By: MANJU GL Attachment: image-2019-12-16-19-28-03-270.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193067.1534441884000.8850.1576504740236%40Atlassian.JIRA.
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title MANJU GL edited a comment on JENKINS-53073 Re: HPLauncher Throws Error (HP PlugIn) Hi, I just added opened DCOM config in admin mode and added my user in the configuration permissions of DCOM securitynow, its working fine.!image-2019-12-16-19-26-37-556.png|width=345,height=350! !image-2019-12-16-19-28-03-270.png|width=328,height=141!Regards,Manju Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193067.1534441884000.8858.1576504800487%40Atlassian.JIRA.
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title MANJU GL commented on JENKINS-53073 Re: HPLauncher Throws Error (HP PlugIn) Hi, I just added opened DCOM config in admin mode and added my user in the configuration permissions of DCOM security now, its working fine. Regards, Manju Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193067.1534441884000.8854.1576504800367%40Atlassian.JIRA.
[JIRA] (JENKINS-60502) when conditions at pipeline and/or stages level
Title: Message Title Mauricio Villegas created an issue Jenkins / JENKINS-60502 when conditions at pipeline and/or stages level Issue Type: New Feature Assignee: Unassigned Components: core Created: 2019-12-16 14:01 Priority: Minor Reporter: Mauricio Villegas It would be a nice feature to allow to have `when` conditions at a pipeline or at stages level. This way it would be possible in the jenkins file (version controlled along with the code) which pipelines are built and which are skipped. Add Comment
[JIRA] (JENKINS-60503) What plugin causes the error
Title: Message Title Dave Rogers created an issue Jenkins / JENKINS-60503 What plugin causes the error Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-12-16 14:02 Priority: Minor Reporter: Dave Rogers One of my 400 Jenkins plugins is frequently throwing this error in my Jenkins log. But which plugin ??? rejecting javax.management.RuntimeErrorException according to standard blacklist; see https://jenkins.io/redirect/class-filter/ java.lang.SecurityException: Class rejected by the class filter: javax.management.RuntimeErrorException at jenkins.security.ClassFilterImpl.notifyRejected(ClassFilterImpl.java:335) at jenkins.security.ClassFilterImpl.isBlacklisted(ClassFilterImpl.java:323) at hudson.remoting.ClassFilter$1.isBlacklisted(ClassFilter.java:125) at hudson.remoting.ClassFilter.check(ClassFilter.java:64) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:130) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1819) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1713) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1986) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1535) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:422) at hudson.remoting.UserRequest.deserialize(UserRequest.java:291) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:349) at hudson.remoting.Channel$2.adapt(Channel.java:992) at hudson.remoting.Channel$2.adapt(Channel.java:988) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at net.bull.javamelody.RemoteCallHelper.collectDataByNodeName(RemoteCallHelper.java:201) at net.bull.javamelody.RemoteCallHelper.collectJavaInformationsListByName(RemoteCallHelper.java:213) at net.bull.javamelody.NodesCollector.collectWithoutErrorsNow(NodesCollector.java:159) at net.bull.javamelody.NodesCollector.collectWithoutErrors(NodesCollector.java:147) at net.bull.javamelody.NodesC
[JIRA] (JENKINS-60502) when conditions at pipeline and/or stages level
Title: Message Title Mauricio Villegas updated an issue Jenkins / JENKINS-60502 when conditions at pipeline and/or stages level Change By: Mauricio Villegas It would be a nice feature to allow to have `when` conditions at a pipeline or at stages level. This way it would be possible in the jenkins file (version controlled along with the code) which pipelines are built and which are skipped. I know it is possible to have nested stages, but doing this just makes the script less readable and looks to be just a hack to get the when block in that location. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203593.1576504911000.8865.1576505220074%40Atlassian.JIRA.
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Jesse Glick commented on JENKINS-59788 Re: Timestamps missing for agent-based steps in Pipeline Job 2.190.1 mock-slave creates a separate process and a Remoting channel so it suffices to reproduce issues of this kind (you would need to use something like a Docker agent to reproduce most issues about things like process launching). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.1571132852000.8867.1576505580263%40Atlassian.JIRA.
[JIRA] (JENKINS-60504) Nullpointer exception
Title: Message Title Matt Wilson created an issue Jenkins / JENKINS-60504 Nullpointer exception Issue Type: Bug Assignee: Gustaf Lundh Attachments: image-2019-12-16-09-09-04-827.png, jenkins-issue.txt Components: downstream-build-cache-plugin, yet-another-build-visualizer-plugin Created: 2019-12-16 14:14 Environment: Centos 7 Jenkins LTSS 2.190.3 Labels: plugin Priority: Major Reporter: Matt Wilson I tagged both components because I'm not sure which is triggering this behavior. We installed the visualizer plugin on Friday (its awesome btw!). The Update Center was used to apply the plugin, the only dependency added was the "down stream build cache" plugin. Everything seemed to be functioning fine after that. The flowcharts looked great. Exactly what we've been looking for. I come in Monday and I'm seeing the jenkins "oops!" screen all over the place. 16-Dec-2019 07:42:55.880 SEVERE [Handling GET /job/lb/job/ecs/job/ECS_12.10.0/74/yabv/buildFlow from 10.4.160.104 : https-jsse-nio-9443-exec-16] org.apache.catalina.core.ApplicationContext.log Error while serving https:///74/yabv/buildFlow java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Oliver Gondža commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI permissive-script-security maintainer here, I failed to reproduce this with version 0.5 installed and enabled so I suspect there must be something else involved. Please share the config.xml of the affected job and org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml, where there is reported the stored config (of one or the other) is not rendered in UI. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.8897.1576507082768%40Atlassian.JIRA.
[JIRA] (JENKINS-59227) Global Pipeline Libraries configuration lost
Title: Message Title Oliver Gondža commented on JENKINS-59227 Re: Global Pipeline Libraries configuration lost permissive-script-security maintainer here, I failed to reproduce this with version 0.5 installed and enabled so I suspect there must be something else involved. Please share the config.xml of the affected job and org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml, where there is reported the stored config (of one or the other) is not rendered in UI. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201684.1567609146000.8895.1576507082546%40Atlassian.JIRA.
[JIRA] (JENKINS-60504) Nullpointer exception
Title: Message Title Matt Wilson updated an issue Jenkins / JENKINS-60504 Nullpointer exception Change By: Matt Wilson Attachment: jenkins-issue-sg.txt I tagged both components because I'm not sure which is triggering this behavior.We installed the visualizer plugin on Friday (its awesome btw!). The Update Center was used to apply the plugin, the only dependency added was the "down stream build cache" plugin.Everything seemed to be functioning fine after that. The flowcharts looked great. Exactly what we've been looking for.I come in Monday and I'm seeing the jenkins "oops!" screen all over the place.!image-2019-12-16-09-09-04-827.png! 16-Dec-2019 07:42:55.880 SEVERE [Handling GET /job/lb/job/ecs/job/ECS_12.10.0/74/yabv/buildFlow from 10.4.160.104 : https-jsse-nio-9443-exec-16] org.apache.catalina.core.ApplicationContext.log Error while serving [ https:///74/yabv/buildFlow |https://%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A%2A/74/yabv/buildFlow] java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)<...>at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748)Caused by: java.lang.NullPointerException I've attached a sample dump from the logs (jenkins-issue . txt), and a dump from the screen of what a page outputs (jenkins-issue-sg.txt). These plugin additions where the only change in my system in the last week or so. I tried a Jenkins service restart but the problem persisted.Disabling the two new plugins returned my system to normal.We'd love to get this functionality back. If there is an information I can provide to help debug let me know. Add Comment
[JIRA] (JENKINS-60457) NullPointerException in h.p.e.p.content.ScriptContent.renderTemplate
Title: Message Title Alex Earl commented on JENKINS-60457 Re: NullPointerException in h.p.e.p.content.ScriptContent.renderTemplate What template are you using? What does your config look like? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203535.1576141507000.8921.1576508820249%40Atlassian.JIRA.
[JIRA] (JENKINS-60505) Microfocus Application Automation Tools Ver:6.0 not supporting ALM 12.55
Title: Message Title Edward Dyer created an issue Jenkins / JENKINS-60505 Microfocus Application Automation Tools Ver:6.0 not supporting ALM 12.55 Issue Type: Bug Assignee: Maria Narcisa Galan Components: hp-application-automation-tools-plugin Created: 2019-12-16 15:12 Labels: plugin Priority: Critical Reporter: Edward Dyer We were working without problem with Jenkins Ver 2.164.2 and Micro Focus Application Automation tools Ver 5.5. Last Monday 2 of the lab Jenkins systems went off-line with the Micro Focus plugin missing. Version 5.5 of the plugin was not available so we migrated to Jenkins 2.190.3 and Micro Focus Application Automation tools Ver 6.0 The Micro Focus Application Automaton Tools states that it supports V 12.00 to 15.0. However when connected to our version 12.55 it fails as it ties to connect with the API Key error. I verified this with my Micro Focus support team. They had a similar setup and when they started Jenkins it uninstalled their Earlier version of the plugin. Version 6.0 on their test sandbox will not work against version 12.55 of ALM According to Micro focus, The API Key was not available until version 12.60 of ALM. I need a way to get my CT setups operational. Is there a way to disable use of this Key in the plugin so version 12.55 of ALM will work correctly.
[JIRA] (JENKINS-60506) UFT test with Warning is reported as successful
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-60506 UFT test with Warning is reported as successful Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-12-16 15:22 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed
[JIRA] (JENKINS-60506) UFT test with Warning is reported to ALM Octane as successful
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-60506 UFT test with Warning is reported to ALM Octane as successful Change By: Radi Berkovich Summary: UFT test with Warning is reported to ALM Octane as successful Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203597.1576509733000.8925.1576509780244%40Atlassian.JIRA.
[JIRA] (JENKINS-60506) UFT test with Warning is reported to ALM Octane as successful
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-60506 UFT test with Warning is reported to ALM Octane as successful Change By: Radi Berkovich Labels: 6.0.3-BETA Octane Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203597.1576509733000.8926.1576509780264%40Atlassian.JIRA.
[JIRA] (JENKINS-60507) Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled
Title: Message Title Mihai Stoichitescu created an issue Jenkins / JENKINS-60507 Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled Issue Type: Bug Assignee: Unassigned Attachments: plugins_versions.txt, queue.logs.zip Components: core, workflow-durable-task-step-plugin Created: 2019-12-16 15:33 Priority: Minor Reporter: Mihai Stoichitescu Our build system is sometimes showing this in the Thread Dump of a Pipeline while waiting for free executors Thread #94 at DSL.node(node block appears to be neither running nor scheduled) at WorkflowScript.runOnNode(WorkflowScript:1798) at DSL.timeout(body has another 3 hr 14 min to run) at WorkflowScript.runOnNode(WorkflowScript:1783) at DSL.retry(Native Method) at WorkflowScript.runOnNode(WorkflowScript:1781) at WorkflowScript.getClosure(WorkflowScript:1901) In BlueOcean this appears, but the build queue is empty, and executors are available with those labels. Still waiting to schedule task Waiting for next available executor on pr&&prod&&mac&&build The job can only be completed by aborting or waiting for the timeout step to do it’s work. We started observing it since v2.12
[JIRA] (JENKINS-60507) Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled
Title: Message Title
Mihai Stoichitescu updated an issue
Jenkins / JENKINS-60507
Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled
Change By:
Mihai Stoichitescu
Our build system is sometimes showing this in the Thread Dump of a Pipeline while waiting for free executors {code:java}Thread #94at DSL.node(node block appears to be neither running nor scheduled)at WorkflowScript.runOnNode(WorkflowScript:1798)at DSL.timeout(body has another 3 hr 14 min to run)at WorkflowScript.runOnNode(WorkflowScript:1783)at DSL.retry(Native Method)at WorkflowScript.runOnNode(WorkflowScript:1781)at WorkflowScript.getClosure(WorkflowScript:1901){code} In BlueOcean this appears, but the build queue is empty, and executors are available with those labels. {code:java}Still waiting to schedule taskWaiting for next available executor on pr&&prod&&mac&&build{code} The job can only be completed by aborting or waiting for the timeout step to do it’s work. We started observing it since v2.121.3 (workflow-durable-task-step v2.19) but recently we updated to v2.190.1 (workflow-durable-task-step v2.28) and still seeing stuck pipelines when waiting for executors. The only reference I could find was in the last comment of this issue: https://issues.jenkins-ci.org/browse/JENKINS-42556 and there’s no way we can reproduce it. We’ve noticed this fix made by [~jglick] but not sure if it will help us. We tried turning on Anonymous for a week and we still saw the problem. Please let me know if there’s more information/logs that I can help with to track down what might be the cause of this. Thanks. I've attached _FINEST_ level logs on _hudson.model.Queue_, not sure if that will help a lot. Our Jenkins runs on RedHat, on Tomcat/9.0.14 and Java 1.8.0_171.
Add Comment
[JIRA] (JENKINS-60507) Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled
Title: Message Title Mihai Stoichitescu updated an issue Jenkins / JENKINS-60507 Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled Change By: Mihai Stoichitescu Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203598.157651039.8929.1576510561530%40Atlassian.JIRA.
[JIRA] (JENKINS-60506) UFT test that finished with Warning is reported to ALM Octane as successful
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-60506 UFT test that finished with Warning is reported to ALM Octane as successful Change By: Radi Berkovich Summary: UFT test that finished with Warning is reported to ALM Octane as successful Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203597.1576509733000.8930.1576511340084%40Atlassian.JIRA.
[JIRA] (JENKINS-60508) Nodes Patterns
Title: Message Title Nahuel Cassinari created an issue Jenkins / JENKINS-60508 Nodes Patterns Issue Type: Bug Assignee: Oleg Nenashev Attachments: Screenshot 2019-12-16 at 16.41.23.png, Screenshot 2019-12-16 at 16.41.43.png, Screenshot 2019-12-16 at 16.42.06.png, Screenshot 2019-12-16 at 16.42.13.png Components: authorize-project-plugin, role-strategy-plugin Created: 2019-12-16 15:52 Labels: plugin jenkins Priority: Minor Reporter: Nahuel Cassinari Hello, Im trying to restrict the nodes in jenkins but doesn't matters what i do, always shows me that the user has lack of permission. Jenkins v2.190.3 Role-based Authorization Strategy v2.15 Authorize Project v1.3.0 So for this example is: Acces Control: Role-Based Strategy Access Control for Builds: Project default Build Authorization - Strategy Run as anonymous (the idea is make it work with Run as the user who triggered the build) Later, I have this configuration: A global role called general which just have view A Slave role which the pattern is "gradle-.* (I tested with gradle*, g
