[JIRA] (JENKINS-61410) Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator
Title: Message Title Alexander Mai created an issue Jenkins / JENKINS-61410 Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-03-10 07:17 Environment: Linux, JDK8 Priority: Critical Reporter: Alexander Mai Yesterday I updated plugins and now a job running fine before crashes always. Here's the callstack: 00:02:15.215 ERROR: Build step failed with exception 00:02:15.216 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from MYMACHINE 00:02:15.216 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) 00:02:15.216 at hudson.remoting.UserResponse.retrieve(UserRequest.java:388) 00:02:15.216 at hudson.remoting.Channel.call(Channel.java:955) 00:02:15.216 at hudson.FilePath.act(FilePath.java:1069) 00:02:15.216 at hudson.FilePath.act(FilePath.java:1058) 00:02:15.216 at io.jenkins.plugins.analysis.core.model.ReportScanningTool.scanInWorkspace(ReportScanningTool.java:149) 00:02:15.216 at io.jenkins.plugins.analysis.core.model.ReportScanningTool.scan(ReportScanningTool.java:131) 00:02:15.216 at com.parasoft.xtest.reports.jenkins.tool.ParasoftTool.scan(ParasoftTool.java:90) 00:02:15.216 at io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:101) 00:02:15.216 at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:666) 00:02:15.216 at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:631)
[JIRA] (JENKINS-61410) Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator
Title: Message Title Alexander Mai commented on JENKINS-61410 Re: Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator I forgot to tell: I had version 7.3.0 installed before. Also installed: https://github.com/jenkinsci/parasoft-findings-plugin/releases/tag/parasoft-findings-10.4.3 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205064.1583824667000.3702.1583825820149%40Atlassian.JIRA.
[JIRA] (JENKINS-61410) Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator
Title: Message Title Alexander Mai commented on JENKINS-61410 Re: Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator I tried downgrading warning-ng-plugin but that seems to be a nightmare to get it working, because other things break with similar errors. Isn't there any compatability check betweens plugins available which prevents such a mess? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205064.1583824667000.3704.1583827620313%40Atlassian.JIRA.
[JIRA] (JENKINS-61410) Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61410 Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator Seems that Parasoft-findings has not been updated to the new breaking 8.0.0 API yet. Change By: Ulli Hafner Component/s: parasoft-findings-plugin Component/s: warnings-ng-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from i
[JIRA] (JENKINS-61410) Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator
Title: Message Title Ulli Hafner assigned an issue to Jacek Marzec Jenkins / JENKINS-61410 Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator Change By: Ulli Hafner Assignee: Ulli Hafner Jacek Marzec Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205064.1583824667000.3709.1583828220182%40Atlassian.JIRA.
[JIRA] (JENKINS-61384) warnings-ng plugin doesn't copy files from workspace if source directory is given
Title: Message Title Juergen Lorenz updated an issue Jenkins / JENKINS-61384 warnings-ng plugin doesn't copy files from workspace if source directory is given Change By: Juergen Lorenz Environment: Jenkins ver. 2.204. 2 4 Warnings Next Generation Plugin 8.0.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205037.1583678174000.3711.1583829060200%40Atlassian.JIRA.
[JIRA] (JENKINS-61411) No build status information is sent to bitbucket when using pipeline job with script
Title: Message Title
Stefan Drzazga created an issue
Jenkins / JENKINS-61411
No build status information is sent to bitbucket when using pipeline job with script
Issue Type:
Bug
Assignee:
Kristy Hughes
Components:
atlassian-bitbucket-server-integration-plugin
Created:
2020-03-10 08:40
Environment:
Jenkins- 2.204.5 BitBucket-Server-Integration Plugin: 1.1.0
Priority:
Major
Reporter:
Stefan Drzazga
When running a pipeline job using "pipeline script" instead of "pipeline script from SCM" with a script using the step bbs_checkout no build status information is sent to bitbucket.
pipeline{
agent any
stages{
stage('scm'){
steps{
bbs_checkout ...
}
}
}
}
This limits me in my flexibility to use plugins such as https://plugins.jenkins.io/pipeline-multibranch-defaults/ or implementing a pipeline definition in a shared library.
[JIRA] (JENKINS-61390) Filtering out branches also affects MR visibility
Title: Message Title Damian Szuberski updated an issue Jenkins / JENKINS-61390 Filtering out branches also affects MR visibility Change By: Damian Szuberski Within project -> Filter by name (with regular _expression_) -> '^(develop|master).*' removes all MR from Merge Requests tab which is completely counterintuitive (MRs should not be affected by branch filters IMHO).Workaround: add catching '^MR \ -\ \ d+$' to the regex, e. g. '^(develop|master|MR).*' Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205043.158375213.3715.1583830140291%40Atlassian.JIRA.
[JIRA] (JENKINS-61390) Filtering out branches also affects MR visibility
Title: Message Title Damian Szuberski updated an issue Jenkins / JENKINS-61390 Filtering out branches also affects MR visibility Change By: Damian Szuberski Within project -> Filter by name (with regular _expression_) -> '^(develop|master).*' removes all MR from Merge Requests tab which is completely counterintuitive (MRs should not be affected by branch filters IMHO).Workaround: add catching ' \ ^MR \ -\ \ d+$' to the regex, e. g. '^(develop|master|MR).*' Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205043.158375213.3717.1583830140351%40Atlassian.JIRA.
[JIRA] (JENKINS-61384) warnings-ng plugin doesn't copy files from workspace if source directory is given
Title: Message Title Juergen Lorenz commented on JENKINS-61384 Re: warnings-ng plugin doesn't copy files from workspace if source directory is given Our programming language is C++ und we have several pre-build libraries with header files at a distinct server. In the build process we include this header files and the linker use the pre-build libs. Some cppcheck messages refer to this header files. This messages will not shown, when the library was build itself (in a other project), because it will be find by the cppcheck only when the class is used. So I have 2 roots: the workspace of the project and the folder of the pre-build lib. If I give the source directory in the configuration (the common folder of all pre-build libs), the plugin will only copy the header files of the pre-build libs. If I let the source directory empty, the plugin will only copy the header and source files from the project. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205037.1583678174000.3719.1583831220219%40Atlassian.JIRA.
[JIRA] (JENKINS-61399) Improve How to use RefSpecsSCMSourceTrait
Title: Message Title
Guilherme Souza updated an issue
Jenkins / JENKINS-61399
Improve How to use RefSpecsSCMSourceTrait
Change By:
Guilherme Souza
I've been trying to populate the RefSpec template on the GitSCM source, but I cannot seem to get it to work. I've failed to find any examples of how to do it.Does anyone have an idea how to use it?{code:java}package utilsimport groovy.transform.builder.Builderimport groovy.transform.builder.SimpleStrategyimport javaposse.jobdsl.dsl.DslFactoryimport javaposse.jobdsl.dsl.Jobimport javaposse.jobdsl.dsl.jobs.MultibranchWorkflowJob// Created to make it easy to creade new jobs without duplicating the code@Builder(builderStrategy = SimpleStrategy, prefix = '')class GithubPipeline {String viewPrefixString repositoryString jobSuffix = ""String includes = "*"String jenkinsfileLocation = "Jenkinsfile"Boolean discoverBranches = trueBoolean discoverTags = trueBoolean includeMasterRef = falseMultibranchWorkflowJob build(DslFactory dslFactory) {def cleanedRepoString = this.repository.toLowerCase().replaceAll(/_/, '-');def jobId = "${this.viewPrefix.toLowerCase()}-${cleanedRepoString}"if (this.jobSuffix) jobId += "-${jobSuffix}"dslFactory.multibranchPipelineJob(jobId) {branchSources {github {id(jobId)includes(this.includes)repoOwner('comp')repository(this.repository)scanCredentialsId('github-appscicomp-dev-token')checkoutCredentialsId('github-appscicomp-dev-token')}}factory {workflowBranchProjectFactory {scriptPath(this.jenkinsfileLocation)}}configure {def traits = it / sources / data / 'jenkins.branch.BranchSource' / source / traitsif (this.discoverBranches) {traits << 'org.jenkinsci.plugins.github_branch_source.BranchDiscoveryTrait' { strategyId(3) // detect all branches -refer the plugin source code for various options}}if (this.discoverTags) {traits << 'org.jenkinsci.plugins.github_branch_source.TagDiscoveryTrait' { }}if (this.includeMasterRef) {traits << 'jenkins.plugins.git.traits.RefSpecsSCMSourceTrait' { tempates << 'jenkins.plugins.git.traits.RefSpecsSCMSourceTrait$RefSpecTemplate' { value('+refs/heads/master:refs/remotes/@{remote}/master') }}}}orphanedItemStrategy {discardOldItems {daysToKeep(20)numToKeep(25)}}}}}{code} The part which I'm struggling is:{code:java} traits << 'jenkins.plugins.git.traits.RefSpecsSCMSourceTrai
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title Oleg Nenashev updated JENKINS-61398 Jenkins / JENKINS-61398 Source Code Management for build job is forgotten on save Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Released As: Jenkins 2.225 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205052.1583762717000.3732.1583834220434%40Atlassian.JIRA.
[JIRA] (JENKINS-61410) Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator
Title: Message Title Jacek Marzec commented on JENKINS-61410 Re: Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator Parasoft Findings plugin does not support WNG API 8.0 yet. We plan to work on this issue soon and publish it by the end of March. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205064.1583824667000.3738.1583834640169%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Andrew Sumner commented on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error First of all, I am quite concerned that you're getting the Gateway Timeout error (good news for my plugin as it proves that it's not faulty). Please raise a support request with Inedo to get to the bottom of that at https://my.inedo.com/tickets/new. To ignore the error and continue you could use a try-catch block (see https://jenkins.io/doc/book/pipeline/syntax/). This is not something I would recommend except as a temporary measure while you're getting to the bottom of what is causing the gateway timeout. Even then I would investigate to see if you can catch only the 504 Gateway Timeout error. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204701.1582203816000.3740.1583834940118%40Atlassian.JIRA.
[JIRA] (JENKINS-51495) descriptorRadioList does not honor DescriptorVisibilityFilter
Title: Message Title Oleg Nenashev updated JENKINS-51495 Jenkins / JENKINS-51495 descriptorRadioList does not honor DescriptorVisibilityFilter Change By: Oleg Nenashev Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.190856.1527063169000.3755.1583835600346%40Atlassian.JIRA.
[JIRA] (JENKINS-51495) descriptorRadioList does not honor DescriptorVisibilityFilter
Title: Message Title Oleg Nenashev commented on JENKINS-51495 Re: descriptorRadioList does not honor DescriptorVisibilityFilter We rolled back the fix in 2.225 to fix the regression. https://github.com/jenkinsci/jenkins/pull/4562 was created for a new implementation Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.190856.1527063169000.3760.1583835660369%40Atlassian.JIRA.
[JIRA] (JENKINS-51495) descriptorRadioList does not honor DescriptorVisibilityFilter
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-51495 descriptorRadioList does not honor DescriptorVisibilityFilter Change By: Oleg Nenashev Assignee: Sho Matsumoto Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.190856.1527063169000.3765.1583835660459%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Oleg Nenashev assigned an issue to Jesse Glick Jenkins / JENKINS-61409 Websocket connections crash if message size is greater than 64Kb Change By: Oleg Nenashev Assignee: Jeff Thompson Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205063.1583801943000.3776.1583836080619%40Atlassian.JIRA.
[JIRA] (JENKINS-61384) warnings-ng plugin doesn't copy files from workspace if source directory is given
Title: Message Title Ulli Hafner commented on JENKINS-61384 Re: warnings-ng plugin doesn't copy files from workspace if source directory is given I see. Currently I do not see a way how this could be achieved with the new version of the plugin (without relocating the files in question to the same root). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205037.1583678174000.3769.1583836080309%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Oleg Nenashev commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb CC Jesse Glick as a JEP-222 sponsor Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205063.1583801943000.3772.1583836080372%40Atlassian.JIRA.
[JIRA] (JENKINS-61391) Incompatible with java 11
Title: Message Title Oleg Nenashev commented on JENKINS-61391 Re: Incompatible with java 11 If you expect some triage from the Java 11 support team, it would be great to have some details in the issue. https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205044.1583752853000.3778.1583836140102%40Atlassian.JIRA.
[JIRA] (JENKINS-60482) EC2 Alternate Endpoint and Region are reset when managing jenkins configuration
Title: Message Title Troy Mohl commented on JENKINS-60482 Re: EC2 Alternate Endpoint and Region are reset when managing jenkins configuration I have submitted a PR that I believe fixes this problem when using an alternate endpoint to select the AWS region: https://github.com/jenkinsci/ec2-plugin/pull/439 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203569.1576277084000.3781.1583836920181%40Atlassian.JIRA.
[JIRA] (JENKINS-60423) Powershell fails when the script starts with 'CmdletBinding' attribut
Title: Message Title Filipe Roque commented on JENKINS-60423 Re: Powershell fails when the script starts with 'CmdletBinding' attribut I'am able to reproduce the problem with the following script: param( [Parameter()][String] $Param1 = "this parameter #1", [Parameter()][String] $Param2 = "this parameter #2" ) Write-Host $Param1 Write-Host $Param2 This runs fine, directly in the powershell: $ pwsh -NonInteractive -File Script.ps1 this parameter #1 this parameter #2 But, powershell version 1.4, prepends '$ErrorActionPreference="Stop"' or '$ErrorActionPreference="Continue"' to the script: $ErrorActionPreference="Continue" param( [Parameter()][String] $Param1 = "this parameter #1", [Parameter()][String] $Param2 = "this parameter #2" ) Write-Host $Param1 Write-Host $Param2 $ pwsh -NonInteractive -File Script.ps1 ParserError: /home/froque/repos/jenkins-workspace/powershell-plugin/Script.ps1:3 Line | 3 | [Parameter()][String] $Param1 = "this parameter #1", | ~~~ | The assignment _expression_ is not valid. The input to an assignment operator must be an object that is able to accept assignments, such as a variable or a property. Kamil Mackow Aleksander Kasprzyk My question to you is: What's the point in defining these parameters, if there is no way to define its values? I fail to see how is this useful. A use case would be helpful. I could change the plugin only add '$ErrorActionPreference="Stop"' if configured as such or something else like it. Add Comment
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Adam Gabryś updated an issue Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Change By: Adam Gabryś Attachment: view-build-with-parameters.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204555.1581528008000.3792.1583839200370%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Adam Gabryś updated an issue Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Change By: Adam Gabryś Attachment: view-parambuild.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204555.1581528008000.3796.1583839320212%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Adam Gabryś updated an issue Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Change By: Adam Gabryś Attachment: parameter-configuration.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204555.1581528008000.3800.1583839440226%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Adam Gabryś commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL Ioannis Moutsatsos you are testing an incorrect page. You opened Build with Parameters. On it everything looks good. The problem is that this page can be used only by humans (impossible to set parameters by using POST data or GET parameters). The pages which should be used by robots are: parambuild - takes parameters from GET buildWithParameters - takes parameters from POST Example for parambuild: As you can see, the default value is set incorrectly (should be 3, but it is filled with 1). My parameter configuration: Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204555.1581528008000.3804.1583839500239%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Hi Philip Aston - Thanks. I'll test on WIndows and Linux build slaves and get back to you. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.168534.1456438321000.3812.1583842560252%40Atlassian.JIRA.
[JIRA] (JENKINS-61410) Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator
Title: Message Title Alexander Mai commented on JENKINS-61410 Re: Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator I remember at least another compatibility issue before. Isn't there anything to warn about mismatching plugin versions? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205064.1583824667000.3819.1583842860249%40Atlassian.JIRA.
[JIRA] (JENKINS-61412) UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-61412 UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder Issue Type: Bug Assignee: Veaceslav Gaidarji Components: plot-plugin Created: 2020-03-10 12:30 Environment: Jenkins Core 2.223 Jenkins Plot Plugin 2.1.5 Priority: Critical Reporter: Reinhold Füreder After upgrade from Jenkins Plot Plugin 2.1.4 => 2.1.5 Jenkins log: 2020-03-10 10:40:02.722+ [id=177] WARNING o.j.p.s.d.DescribableParameter#uncoerce: failed to uncoerce hudson.plugins.plot.PlotBuilder@4bf77f69 java.lang.UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder at org.jenkinsci.plugins.structs.describable.DescribableParameter.getValue(DescribableParameter.java:161) at org.jenkinsci.plugins.structs.describable.DescribableParameter.inspect(DescribableParameter.java:142) at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2(DescribableModel.java:655) at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2_(DescribableModel.java:752) at org.jenkinsci.plugins.structs.describable.DescribableParameter.uncoerce(DescribableParameter.java:196) at org.jenkinsci.plugins.structs.describable.DescribableParameter.inspect(DescribableParameter.java:142) at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2(DescribableModel.java:655) at org.jenkinsci.plugins.workflow.actions.ArgumentsActi
[JIRA] (JENKINS-61007) pipeline-model-definition is using findbugs without providing / depending on it
Title: Message Title Jesse Glick updated JENKINS-61007 Jenkins / JENKINS-61007 pipeline-model-definition is using findbugs without providing / depending on it Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Released As: pipeline-model-definition 1.6.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204477.1581032748000.3833.1583844420328%40Atlassian.JIRA.
[JIRA] (JENKINS-60250) "Pipeline script from SCM": Git branch field cannot expand property from file
Title: Message Title
Max Golionko commented on JENKINS-60250
Re: "Pipeline script from SCM": Git branch field cannot expand property from file
We have same problem, but in our case we don't have readTrusted But we are using kubernetes with kubernetes-plugin, and we were using yaml file for pod configuration
agent {
kubernetes {
yamlFile "downloader.yaml"
}
}
seems that underhood it calls readTrusted we tried to use
agent {
kubernetes {
yaml readFile("./pod.yaml")
}
}
but this also didn't work only inline pod yaml helped to solve this issue
agent {
kubernetes {
yaml """
apiVersion: v1
kind: Pod
spec:
containers:
- name: jnlp
image: imagename
imagePullPolicy: Always
"""
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-42971) Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
Title: Message Title
Max Golionko commented on JENKINS-42971
Re: Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
We have same problem, but in our case we don't have readTrusted But we are using kubernetes with kubernetes-plugin, and we were using yaml file for pod configuration
agent {
kubernetes {
yamlFile "pod.yaml"
}
}
seems that underhood it calls readTrusted we tried to use
agent {
kubernetes {
yaml readFile("./pod.yaml")
}
}
but this also didn't work only inline pod yaml helped to solve this issue
agent {
kubernetes {
yaml """
apiVersion: v1
kind: Pod
spec:
containers:
- name: jnlp
image: imagename
imagePullPolicy: Always
"""
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60250) "Pipeline script from SCM": Git branch field cannot expand property from file
Title: Message Title
Max Golionko edited a comment on JENKINS-60250
Re: "Pipeline script from SCM": Git branch field cannot expand property from file
We have same problem, but in our case we don't have readTrustedBut we are using kubernetes with kubernetes-plugin, and we were using yaml file for pod configuration{code:java} agent {kubernetes { yamlFile " downloader pod .yaml"} } {code} seems that underhood it calls readTrustedwe tried to use{code:java} agent {kubernetes { yaml readFile("./pod.yaml")} }{code}but this also didn't workonly inline pod yaml helped to solve this issue{code:java}agent {kubernetes { yaml """apiVersion: v1kind: Podspec: containers: - name: jnlpimage: imagenameimagePullPolicy: Always"""} }{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.203240.1574450609000.3838.1583844540879%40Atlassian.JIRA.
[JIRA] (JENKINS-58975) Executing shell in a container with a custom workingDir times out
Title: Message Title Francis JAC edited a comment on JENKINS-58975 Re: Executing shell in a container with a custom workingDir times out his This Jira is a regression. It used to work on the 1.17.3 version. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201324.1566067268000.3871.1583845260325%40Atlassian.JIRA.
[JIRA] (JENKINS-58975) Executing shell in a container with a custom workingDir times out
Title: Message Title Francis JAC commented on JENKINS-58975 Re: Executing shell in a container with a custom workingDir times out his Jira is a regression. It used to work on the 1.17.3 version. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201324.1566067268000.3869.1583845260270%40Atlassian.JIRA.
[JIRA] (JENKINS-60423) Powershell fails when the script starts with 'CmdletBinding' attribut
Title: Message Title
Aleksander Kasprzyk commented on JENKINS-60423
Re: Powershell fails when the script starts with 'CmdletBinding' attribut
Hi Filipe Roque, I'm using the Standard PowerShell arguments, like -ErrorAction and -Verbose in my scripts that are set up before the call from Jenkins (as constants or as Jenkins Job parameter). For exemple, the -ErrorAction is sometimes "Stop" or "SilentlyContinue", depending of a given need. And a script might be called outside Jenkins.
Param (
[string]$workspace = $ENV:WORKSPACE,
[string]$buildMode = $ENV:BUILD_MODE
)
$script = Join-Path $workspace "AthicAuthentication.$buildMode.ps1"
$code = 0
if (Test-Path -Path $script -ErrorAction SilentlyContinue) {
$code = Invoke-_expression_ "$script" -ErrorAction Stop
}
exit $code
What changed between 1.3 and 1.4 version that causes this issues ?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.203495.1575993533000.3878.1583845740118%40Atlassian.JIRA.
[JIRA] (JENKINS-61402) Jenkins Docker Start Up Very Slow
Title: Message Title Oleg Nenashev commented on JENKINS-61402 Re: Jenkins Docker Start Up Very Slow Looks like it is something related to plugin loading and, maybe, their initialization handlers. It would be great to have this timeframe with FINEST logging so that we could pin-point the root cause Mar 09 15:37:46 ip-10-0-2-71.us-west-2.compute.internal docker[15997]: 2020-03-09 15:37:46.379+ [id=26] INFO hudson.PluginManager#loadDetachedPlugins: Upgraded Jenkins from version 2.204.4 to version 2.204.5. Loaded detached plugins (and dependencies): [] Mar 09 16:06:13 ip-10-0-2-71.us-west-2.compute.internal docker[15997]: 2020-03-09 16:06:13.602+ [id=31] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205056.1583771459000.3881.1583847000124%40Atlassian.JIRA.
[JIRA] (JENKINS-61410) Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator
Title: Message Title Ulli Hafner commented on JENKINS-61410 Re: Crash using 8.1.0: java.lang.NoClassDefFoundError: io/jenkins/plugins/analysis/core/util/AbsolutePathGenerator In general, this is hard to spot without testing (for instance with an integration test or an ATH test). As a user you can at least check the version numbers of the plugins you upgrade. My plugin uses semantic versioning, so if you upgrade from 7.x to 8.x you can expect that there are API changes. If a dependency did not upgrade accordingly, then there might be potential problems. We also have a tool called https://github.com/jenkinsci/plugin-compat-tester, but this is not used yet for such a thing. Another thing you can do: use beta versions in your Jenkins staging area (the 8.x version was in the experimental beta update center for more than three months). Then you can spot errors before a final release has been done. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205064.1583824667000.3884.1583847120307%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Change By: Ioannis Moutsatsos Attachment: image-2020-03-10-09-32-13-452.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204555.1581528008000.3887.1583847180325%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL Adam Gabryś thank you for the clatification. I missed this point (since I never use the parameters this way). In this case YES I can reproduce the issue with previous versions of the plugin, and INDEED it is corrected in this version. I would love to see an example where you can set other Active Choices parameters to a value using GET or POST. Does the cascading of other Active Choices still works? For the plugin documentation we state that this plugin only works and is intended for interactive use by a human and not by API. Has this PR changed that? See: https://plugins.jenkins.io/uno-choice/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204555.1581528008000.3894.1583847240133%40Atlassian.JIRA.
[JIRA] (JENKINS-61261) Ivy ClassNotFoundException when using Grab
Title: Message Title Gowtham Subramanian commented on JENKINS-61261 Re: Ivy ClassNotFoundException when using Grab Found the issue is related to downloaded plugins not present at the plugins path. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204831.1582834029000.3898.1583847780710%40Atlassian.JIRA.
[JIRA] (JENKINS-61261) Ivy ClassNotFoundException when using Grab
Title: Message Title Gowtham Subramanian updated JENKINS-61261 Jenkins / JENKINS-61261 Ivy ClassNotFoundException when using Grab Change By: Gowtham Subramanian Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204831.1582834029000.3904.1583847781049%40Atlassian.JIRA.
[JIRA] (JENKINS-61261) Ivy ClassNotFoundException when using Grab
Title: Message Title Gowtham Subramanian updated JENKINS-61261 Jenkins / JENKINS-61261 Ivy ClassNotFoundException when using Grab Change By: Gowtham Subramanian Status: Reopened Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204831.1582834029000.3899.1583847780739%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-60199 jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Change By: Oliver Gondža Labels: 2.204.5-fixed lts 2.222.1 - candidate fixed regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203169.1574080196000.3911.1583847960678%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Form Submission Length Cap
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-60409 Form Submission Length Cap Change By: Oliver Gondža Labels: 2.204.5-fixed lts-candidate lts-candidate-for- 2. 204-and-2. 222 .1-fixed regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203466.1575915955000.3925.1583848020834%40Atlassian.JIRA.
[JIRA] (JENKINS-60857) Wildcard certificates rejected by Winstone after Jetty update
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-60857 Wildcard certificates rejected by Winstone after Jetty update Change By: Oliver Gondža Labels: 2.204.4-fixed 2.222.1-fixed SSL keystore lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204231.1579860751000.3948.1583848380950%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Oliver Gondža Labels: 2.204.3-fixed 2.204.5-rejected lts 2.222.1 - candidate fixed regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.199852.1559834581000.3974.1583848680301%40Atlassian.JIRA.
[JIRA] (JENKINS-61413) Prometheus Plugin does not deliver Informations for a large Jenkins Installation.
Title: Message Title Stephan Leiser created an issue Jenkins / JENKINS-61413 Prometheus Plugin does not deliver Informations for a large Jenkins Installation. Issue Type: Task Assignee: Marky Jackson Components: prometheus-plugin Created: 2020-03-10 14:07 Environment: Jenkins 2.204.2 Priority: Major Reporter: Stephan Leiser When having the Jenkins Plugin Prometheus installed and enabled for a large Jenkins instance > 1k Jobs the Plugin stops to deliver Values when Jobs are selected in Configure -> System. The Prometheus plugin will then don't deliver new info to the Prometheus Server. Add Comment
[JIRA] (JENKINS-61413) Prometheus Plugin does not deliver Informations for a large Jenkins Installation.
Title: Message Title Marky Jackson commented on JENKINS-61413 Re: Prometheus Plugin does not deliver Informations for a large Jenkins Installation. Stephan Leiser Can you provide any logs/output? Also, can you provide the basic of your configuration (eg. Jenkins version & plugin version)? Thanks Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205073.1583849238000.3990.1583849410766%40Atlassian.JIRA.
[JIRA] (JENKINS-61413) Prometheus Plugin does not deliver Informations for a large Jenkins Installation.
Title: Message Title Stephan Leiser commented on JENKINS-61413 Re: Prometheus Plugin does not deliver Informations for a large Jenkins Installation. Marky Jackson which logs do you need? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205073.1583849238000.3995.1583849580222%40Atlassian.JIRA.
[JIRA] (JENKINS-61413) Prometheus Plugin does not deliver Informations for a large Jenkins Installation.
Title: Message Title Stephan Leiser updated an issue Jenkins / JENKINS-61413 Prometheus Plugin does not deliver Informations for a large Jenkins Installation. Change By: Stephan Leiser When having the Jenkins Plugin Prometheus installed and enabled for a large Jenkins instance > 1k Jobs the Plugin stops to deliver Values when Jobs are selected in Configure -> System.The Prometheus plugin will then don't deliver new info to the Prometheus Server. Jenkins Version : 2.204.2Prometheus Metrics Plugin : 2.0.6 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205073.1583849238000.3993.1583849580184%40Atlassian.JIRA.
[JIRA] (JENKINS-61413) Prometheus Plugin does not deliver Informations for a large Jenkins Installation.
Title: Message Title Marky Jackson commented on JENKINS-61413 Re: Prometheus Plugin does not deliver Informations for a large Jenkins Installation. You general Jenkins log output. Also if you can provide the Prometheus logs (depending on your os /var/lib/docker/containers//.log) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205073.1583849238000.3998.1583849760168%40Atlassian.JIRA.
[JIRA] (JENKINS-61406) Allow for use of password-based encryption of confidential store
Title: Message Title Matt Sicker commented on JENKINS-61406 Re: Allow for use of password-based encryption of confidential store I'll note that based on some info I read on Wikipedia, PBKDF2 and PBEwithFooAndBar schemes seem to be somewhat weak due to ASIC attacks and such. Seems like the recommended alternative is some non-described combination of Argon2 (current recommended password hashing algorithm) as the input of an AES key. Alternatively, if using PBKDF2, make sure to use a large number of iterations and a salt of like at least 128 bits. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205060.1583784341000.3999.1583850420053%40Atlassian.JIRA.
[JIRA] (JENKINS-61413) Prometheus Plugin does not deliver Informations for a large Jenkins Installation.
Title: Message Title Stephan Leiser updated an issue Jenkins / JENKINS-61413 Prometheus Plugin does not deliver Informations for a large Jenkins Installation. Change By: Stephan Leiser Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205073.1583849238000.4001.1583850660152%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Take a look at this test: https://github.com/jenkinsci/ssh-credentials-plugin/blob/master/src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/TrileadSSHPublicKeyAuthenticatorTest.java If you run that test locally but instead put the contents of your private key in the getPrivateKey() method, does the test still pass? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204941.158343741.4009.1583851260138%40Atlassian.JIRA.
[JIRA] (JENKINS-61414) ERROR: No item named xxx/yyy found
Title: Message Title
Cyril Feraudet created an issue
Jenkins / JENKINS-61414
ERROR: No item named xxx/yyy found
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2020-03-10 14:41
Environment:
Jenkins ver. 2.204.2
Priority:
Blocker
Reporter:
Cyril Feraudet
Hello, Previously working pipeline fail with error ERROR: No item named xxx/yyy found
pipeline {
agent any
stages {
stage('xxx') {
steps {
build(job:'xxx/yyy', propagate: false)
}
}
}
}
job xxx/yyy exist and can be trigger from Thanks in advance
Add Comment
[JIRA] (JENKINS-61415) Polling baselines cannot be easily removed from Pipelines once added
Title: Message Title Devin Nusbaum started work on JENKINS-61415 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205075.1583853088000.4016.1583853120628%40Atlassian.JIRA.
[JIRA] (JENKINS-61415) Polling baselines cannot be easily removed from Pipelines once added
Title: Message Title Devin Nusbaum updated JENKINS-61415 Jenkins / JENKINS-61415 Polling baselines cannot be easily removed from Pipelines once added Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205075.1583853088000.4018.1583853120655%40Atlassian.JIRA.
[JIRA] (JENKINS-61415) Polling baselines cannot be easily removed from Pipelines once added
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-61415 Polling baselines cannot be easily removed from Pipelines once added Change By: Devin Nusbaum Labels: pipeline Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205075.1583853088000.4014.1583853120571%40Atlassian.JIRA.
[JIRA] (JENKINS-61415) Polling baselines cannot be easily removed from Pipelines once added
Title: Message Title Devin Nusbaum created an issue Jenkins / JENKINS-61415 Polling baselines cannot be easily removed from Pipelines once added Issue Type: Bug Assignee: Alex Taylor Components: workflow-job-plugin Created: 2020-03-10 15:11 Priority: Minor Reporter: Devin Nusbaum Once a Pipeline has a polling baseline added to it for a given SCM (shared library, main repo, etc), that baseline cannot be removed directly, and the job will always be built when the SCM is updated. The only way to remove the baseline is to disable polling for the SCM, build the job, and then restart Jenkins after the build completes. Once that is done, the polling baseline will no longer be present for that SCM and the job will not be built when the SCM is updated. It should be possible to remove the polling baseline without needing to restart Jenkins. There are probably some related issues that should be closed as a duplicate of this issue. Add Comment
[JIRA] (JENKINS-61412) UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder
Title: Message Title Veaceslav Gaidarji updated JENKINS-61412 Jenkins / JENKINS-61412 UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder Change By: Veaceslav Gaidarji Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205069.1583843413000.4022.1583853180649%40Atlassian.JIRA.
[JIRA] (JENKINS-61412) UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder
Title: Message Title Veaceslav Gaidarji updated JENKINS-61412 Fixed in https://github.com/jenkinsci/plot-plugin/pull/59. Jenkins / JENKINS-61412 UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder Change By: Veaceslav Gaidarji Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-61412) UnsupportedOperationException: no public field ‘description’ (or getter method) found in class hudson.plugins.plot.PlotBuilder
Title: Message Title Veaceslav Gaidarji started work on JENKINS-61412 Change By: Veaceslav Gaidarji Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205069.1583843413000.4020.1583853180614%40Atlassian.JIRA.
[JIRA] (JENKINS-55948) Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked
Title: Message Title Marcus Philip commented on JENKINS-55948 Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked I had the same symptoms, ie cat: command not found error: unable to read askpass response from ... fatal: could not read Username for 'http://': No such device or address Eventually I realized that I had a build param called 'path'. Go figure the rest for yourself... When I renamed it, everything worked fine. This is probably another bug that should be reported somewhere, it's absolutely crazy that you can affect the PATH of the git commands this way, but maybe they'll say working as designed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.197357.1549280175000.4026.1583853780316%40Atlassian.JIRA.
[JIRA] (JENKINS-61331) Make the header "Jenkins" open the main menu, instead of the tiny arrow icon
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-61331 Make the header "Jenkins" open the main menu, instead of the tiny arrow icon Change By: Baptiste Mathus Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204849.1582926952000.4037.1583854080385%40Atlassian.JIRA.
[JIRA] (JENKINS-61416) Include JGit 5.7.0 in a git client plugin release
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-61416 Include JGit 5.7.0 in a git client plugin release Issue Type: Improvement Assignee: Mark Waite Components: git-client-plugin Created: 2020-03-10 15:57 Labels: dependencies Priority: Minor Reporter: Mark Waite Git client plugin 5.7.0 is scheduled to release March 18, 2020. It should be included in a git client plugin release so that the git client plugin remains current with the latest JGit. Refer to the release notes for more details Add Comment
[JIRA] (JENKINS-61416) Include JGit 5.7.0 in a git client plugin release
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61416 Include JGit 5.7.0 in a git client plugin release Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205076.158385587.4047.1583855940056%40Atlassian.JIRA.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Uliul Carpatin commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once +1 for this feature .. A solution to not break the compatibility would be to: add an extra parameter, 'returnBothOutputs' return as a list the two items [ returnStatusOptionContent , returnStdoutOptionContent ] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.183003.149756330.4149.1583856124822%40Atlassian.JIRA.
[JIRA] (JENKINS-61417) maven plugin does not load .mvn config (jvm.config,maven.config)
Title: Message Title Adam Gent created an issue Jenkins / JENKINS-61417 maven plugin does not load .mvn config (jvm.config,maven.config) Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2020-03-10 16:17 Environment: Jenkins version 2.164.2 maven integration plugin 3.4 Priority: Major Reporter: Adam Gent Maven style builds (which use the maven integration plugin) do not load or respect .mvn/*.config. This is not to be confused with a previous issue with Maven itself where -f could not find .mvn. That is freestyle builds work fine and even executing maven pre or post steps work fine. An easy way to test this is to create a project with .mvn/jvm.config or .mvn/maven.config with some property defined like -DsomeProperty=true Then set the goal to: org.apache.maven.plugins:maven-help-plugin:3.2.0:evaluate -Dexpression='someProperty' Add Comment
[JIRA] (JENKINS-41845) Suppress default pipeline output
Title: Message Title
Mark Sanders commented on JENKINS-41845
Re: Suppress default pipeline output
I'm on Jenkins version 2.195, running in classic mode, and I added the following to the Simple Theme Plugin.
.pipeline-annotated {
display: none;
}
.pipeline-new-node {
display: none;
}
Works for me. The console is nice and clean. Only seeing the output I want/need to.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.178692.1486564607000.4158.1583857080555%40Atlassian.JIRA.
[JIRA] (JENKINS-61418) MSYS2 shell can not be used in pipeline shell (mixed linux/win32 pipeline)
Title: Message Title
stephane ancelot created an issue
Jenkins / JENKINS-61418
MSYS2 shell can not be used in pipeline shell (mixed linux/win32 pipeline)
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2020-03-10 16:24
Environment:
v2.204.5 / linux64 / jdk 1.8
Priority:
Critical
Reporter:
stephane ancelot
I want to launch my commands from a pipeline shell executed on a remote windows slave. In my pipeline I have linux and windows agent, I can not change shell for the whole pipeline unfortunately using this command in the pipleine fails sh("""E:/msys2/msys2_shell.cmd -mingw64 cmake ... make """) the commands are not executed within the shell
Add Comment
[JIRA] (JENKINS-61419) Aqua security scanner IOException Failed to copy styles.css with non-default hudson.PluginManager.workDir
Title: Message Title Jonathan Bull created an issue Jenkins / JENKINS-61419 Aqua security scanner IOException Failed to copy styles.css with non-default hudson.PluginManager.workDir Issue Type: Bug Assignee: Moshe Cohen Components: aqua-security-scanner-plugin Created: 2020-03-10 16:24 Environment: Jenkins version: 2.190.2.2 Aqua security scanner version: 3.0.21 Priority: Major Reporter: Jonathan Bull The plugin is hard coded to copy the styles.css file from $JENKINS_HOME/plugins/aqua-security-scanner/css/styles.css to the workspace directory (See github). However, if the Jenkins setting hudson.PluginManager.workDir has been changed to a non-default value then plugins are unpacked at that location instead of $JENKINS_HOME/plugins which causes the following exception: Exception:java.io.IOException: Failed to copy [$JENKINS_HOME]/plugins/aqua-security-scanner/css/styles.css to [$WORKSPACE]/styles.css How to reproduce Stop jenkins Remove all plugin folders from $JENKINS_HOME/plugins. Leave the jpi files. Start jenkins with hudson.PluginManager.workDir set to a directory other than $JENKINS_HOME/plugins
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Adam Gabryś updated an issue Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Change By: Adam Gabryś Attachment: reference-parameter.gif Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204555.1581528008000.4182.1583857740300%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Adam Gabryś commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL Does the cascading of other Active Choices still works? The parambuild and buildWithParameters pages take parameter default values and render them as inputs. No other logic is available or executed. It means that if one field should be changed when another field is changed - the logic won't be executed. Example: For the plugin documentation we state that this plugin only works and is intended for interactive use by a human and not by API. Has this PR changed that? All dynamic actions and validations are still able only for the humans (don't allow checking two radio buttons at the same time etc.). The PR only changes the way of setting the default values of the most basic parameter (not support for references). I know it is not perfect, but make the plugin more usable in basic cases. It also partially solves problem mentioned here JENKINS-28735 (set correct default values for basic parameters when jobs are executed by timers). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving ema
[JIRA] (JENKINS-61420) The SOAP endpoint could not be contacted. HTTP status: 503
Title: Message Title Lucy Sang created an issue Jenkins / JENKINS-61420 The SOAP endpoint could not be contacted. HTTP status: 503 Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 2020-03-10 16:52 Priority: Blocker Reporter: Lucy Sang Our DevOps team recently ran maintenance on our jenkins master and I am no longer able to run our pipelines. These connections were working consistently prior to the maintenance and now it consistently not working. Please advise, this is stopping all jenkins pipelines from running. Below is the console output: Lightweight checkout support not available, falling back to full checkout. Checking out hudson.plugins.tfs.TeamFoundationServerScm into /var/lib/jenkins/workspace/FXL/7.5 DevTest@script to read Jenkins_DevTest.groovy Querying for remote changeset at '$/TwoFour Version 7.5' as of 'D2020-03-10T16:30:44Z'... ERROR: Checkout failed com.microsoft.tfs.core.ws.runtime.exceptions.EndpointNotFoundException: The SOAP endpoint http://:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx could not be contacted. HTTP status: 503 at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineHeadersForErrorMessage(SOAPService.java:1101) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:660) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:444) at ms.tfs.versioncontrol.clientservices._03._RepositorySoap12Service.queryHistory(_RepositorySoap12Service.java:1503) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.queryHistory(WebServiceLayer.java:1573) Caused: com.microsoft.tfs.core.exceptions.TECoreException: The SOAP endpoint http://teamfoundation:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx could not be contacted. HTTP status: 503 at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:92) at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.ma
[JIRA] (JENKINS-61420) The SOAP endpoint could not be contacted. HTTP status: 503
Title: Message Title Lucy Sang updated an issue Jenkins / JENKINS-61420 The SOAP endpoint could not be contacted. HTTP status: 503 Change By: Lucy Sang Our DevOps team recently ran maintenance on our jenkins master and I am no longer able to run our pipelines. These connections were working consistently prior to the maintenance and now it consistently not working. Please advise, this is stopping all jenkins pipelines from running. Below is the console output: Lightweight checkout support not available, falling back to full checkout.Checking out hudson.plugins.tfs.TeamFoundationServerScm into /var/lib/jenkins/workspace/FXL/7.5 DevTest@script to read Jenkins_DevTest.groovyQuerying for remote changeset at '$/TwoFour Version 7.5' as of 'D2020-03-10T16:30:44Z'...ERROR: Checkout failedcom.microsoft.tfs.core.ws.runtime.exceptions.EndpointNotFoundException: The SOAP endpoint [http://:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx|http://teamfoundation:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx] could not be contacted. HTTP status: 503 at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineHeadersForErrorMessage(SOAPService.java:1101) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:660) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:444) at ms.tfs.versioncontrol.clientservices._03._RepositorySoap12Service.queryHistory(_RepositorySoap12Service.java:1503) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.queryHistory(WebServiceLayer.java:1573)Caused: com.microsoft.tfs.core.exceptions.TECoreException: The SOAP endpoint [http:// |http:// teamfoundation:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx] [|http://teamfoundation:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx] [:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx|http://teamfoundation:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx] could not be contacted. HTTP status: 503 at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:92) at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.map(VersionControlExceptionMapper.java:43) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.queryHistory(WebServiceLayer.java:1589) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayerLocalWorkspaces.queryHistory(WebServiceLayerLocalWorkspaces.java:1254) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.queryHistory(VersionControlClient.java:4264) at hudson.plugins.tfs.model.MockableVersionControlClient.queryHistory(MockableVersionControlClient.java:255) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:66) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:34) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:23
[JIRA] (JENKINS-61384) warnings-ng plugin doesn't copy files from workspace if source directory is given
Title: Message Title Juergen Lorenz commented on JENKINS-61384 Re: warnings-ng plugin doesn't copy files from workspace if source directory is given Relocating the files in question to the same root is not so easy, I'm afraid. I'm only had a look in IssuesScanner and see a easy way to solve this problem. If you give the folder as a property of the report, then it wouldn't be possible to have multiple roots. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205037.1583678174000.4193.1583859300199%40Atlassian.JIRA.
[JIRA] (JENKINS-61156) Regression: P4 Plugin 1.10.10 trigger doesn't run jobs
Title: Message Title Matthew Smeeth commented on JENKINS-61156 Re: Regression: P4 Plugin 1.10.10 trigger doesn't run jobs Hi William Brode, I'm a bit surprised that it would work without build access, however given that anonymous user has read access on your system, It's possible that's all that's needed to avoid this issue. However once you upgrade to 1.10.11 I think you'll almost certainly hit this issue due to extra security measures we've implemented. For now unfortunately I'm going to revert the changes, with a plan to look into implementing this another way in the future. FYI Adam Butler Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204686.158215634.4195.1583859360264%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL Thank you Adam Gabryś. I've learned something! Bruno P. Kinoshita it should be safe to incorporate these basic improvements into a new release. Thank you! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204555.1581528008000.4204.1583864280262%40Atlassian.JIRA.
[JIRA] (JENKINS-61421) Use the Java KeyStore API instead of home grown solution
Title: Message Title Matt Sicker created an issue Jenkins / JENKINS-61421 Use the Java KeyStore API instead of home grown solution Issue Type: Improvement Assignee: Unassigned Components: core Created: 2020-03-10 18:17 Priority: Minor Reporter: Matt Sicker Introduced long ago as a way to manage secrets, ConfidentialStore and ConfidentialKey largely duplicate the API provided by Java's KeyStore class. Jenkins should migrate toward using a proper keystore for storing secret keys, private keys, and certificates. This would allow for the use of a standardized file format (PKCS12), pluggable key store implementations (e.g., on macOS, there's a KeyStore provider that uses the macOS Keychain), and more secure management of keys (allows for third party tools to be used to easily rotate keys and other manipulations). Implementing this would go well with JENKINS-61406, though the features can be implemented separately. Add Comment
[JIRA] (JENKINS-61406) Allow for use of password-based encryption of confidential store
Title: Message Title Matt Sicker commented on JENKINS-61406 Re: Allow for use of password-based encryption of confidential store Added link to incomplete proof of concept code. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205060.1583784341000.4208.1583865300050%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jesse Glick commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb Possibly also affects WebSocket-based CLI. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205063.1583801943000.4210.1583866320276%40Atlassian.JIRA.
[JIRA] (JENKINS-61384) warnings-ng plugin doesn't copy files from workspace if source directory is given
Title: Message Title Ulli Hafner commented on JENKINS-61384 Re: warnings-ng plugin doesn't copy files from workspace if source directory is given I'm not sure if I can follow your argumentation, or if I miss something obvious. Affected files of the warnings are now stored using the relative path per issue and a global path prefix from the report. Every access to the file (fingerprint, affected files, etc.) is now using the absolute path of the issue (issue.getAbsolutePath()). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205037.1583678174000.4215.1583866440208%40Atlassian.JIRA.
[JIRA] (JENKINS-61384) warnings-ng plugin doesn't copy files from workspace if source directory is given
Title: Message Title
Ulli Hafner edited a comment on JENKINS-61384
Re: warnings-ng plugin doesn't copy files from workspace if source directory is given
I'm not sure if I can follow your argumentation, or if I miss something obvious. Affected files of the warnings are now stored using the relative path per issue and a global path prefix from the report. Every access to the file (fingerprint, affected files, etc.) is now using the absolute path of the issue ({{issue.getAbsolutePath()}}). Or what exactly is returned in your case for this header files? Maybe we should use an actual example of those files in order to solve the problem...
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google 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.205037.1583678174000.4217.1583866500142%40Atlassian.JIRA.
[JIRA] (JENKINS-58732) Invert pipeline-model-definition → docker-workflow dependency
Title: Message Title Jesse Glick updated JENKINS-58732 Jenkins / JENKINS-58732 Invert pipeline-model-definition → docker-workflow dependency Change By: Jesse Glick Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201031.1564500516000.4223.1583869920367%40Atlassian.JIRA.
[JIRA] (JENKINS-60423) Powershell fails when the script starts with 'CmdletBinding' attribut
Title: Message Title Kamil Mackow commented on JENKINS-60423 Re: Powershell fails when the script starts with 'CmdletBinding' attribut Hi Filipe Roque, We use these parameters as default values as these scripts are included in some of our build repositories and having commonly used defaults is a nice convenience for end users so they don't have to know every value but can override if they choose to without modifying the script itself. Does that answer the question? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203495.1575993533000.4226.1583870340232%40Atlassian.JIRA.
[JIRA] (JENKINS-58975) Executing shell in a container with a custom workingDir times out
Title: Message Title Francis JAC updated an issue Jenkins / JENKINS-58975 Executing shell in a container with a custom workingDir times out Change By: Francis JAC Comment: This Jira is a regression. It used to work on the 1.17.3 version. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201324.1566067268000.4232.1583870946492%40Atlassian.JIRA.
[JIRA] (JENKINS-58975) Executing shell in a container with a custom workingDir times out
Title: Message Title Francis JAC commented on JENKINS-58975 Re: Executing shell in a container with a custom workingDir times out Is it considered solved by https://github.com/jenkinsci/kubernetes-plugin/pull/610 ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.201324.1566067268000.4230.1583870946467%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jesse Glick commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb There seems to be a configurable maximum size for binary packets. (WebSocketPolicy.setMaxBinaryMessageSize) There is no particular reason to impose a limit in Jenkins that I know of, so it could just be set to some large value. Or Remoting may already have a maximum frame size; would have to dig into it. In this case the packet is coming via a RemoteOutputStream, I think, though the behavior may vary depending on whether or not org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.USE_WATCHING is set. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205063.1583801943000.4236.1583871120198%40Atlassian.JIRA.
[JIRA] (JENKINS-33925) Test framework for Jenkinsfile
Title: Message Title Jesse Glick commented on JENKINS-33925 Re: Test framework for Jenkinsfile Sergei Parshev Interesting but I doubt maintainers of groovy-sandbox / groovy-cps can take on any testability enhancements—keeping production code running is more than enough work. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.169416.145942296.4367.1583872445191%40Atlassian.JIRA.
[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-60239 Aborted catchError sets build result to ABORTED if fail fast is true Change By: Devin Nusbaum Component/s: workflow-basic-steps-plugin Component/s: pipeline-model-definition-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203219.1574333797000.4374.1583875020199%40Atlassian.JIRA.
[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true
Title: Message Title Devin Nusbaum commented on JENKINS-60239 Re: Aborted catchError sets build result to ABORTED if fail fast is true Did you try using catchError(catchInterruptions: false)? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203219.1574333797000.4377.1583875080171%40Atlassian.JIRA.
[JIRA] (JENKINS-61415) Polling baselines cannot be easily removed from Pipelines once added
Title: Message Title Devin Nusbaum updated JENKINS-61415 A fix for this issue was released in Pipeline: Job Plugin version 2.37. See the changelog for details. Jenkins / JENKINS-61415 Polling baselines cannot be easily removed from Pipelines once added Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-job 2.37 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60862) Truncated build logs do not show parallel branch names that began before the truncation point
Title: Message Title Devin Nusbaum resolved as Fixed A fix for this issue was released in Pipeline: Job Plugin version 2.37. See the changelog for details. Jenkins / JENKINS-60862 Truncated build logs do not show parallel branch names that began before the truncation point Change By: Devin Nusbaum Status: In Progress Resolved Resolution: Fixed Released As: workflow-job 2.37 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61051) Jobs are started on master instead of EC2 slaves randomly
Title: Message Title Laszlo Gaal commented on JENKINS-61051 Re: Jobs are started on master instead of EC2 slaves randomly I have run into a similar problem with Jenkins v2.204.2 and EC2 plugin v1.49.1. In our case the master was actually overloaded by the misdirected job, and the Jenkins process was killed by the OOM-killer. One symptom I found was that the Jenkins log lines that normally log the connection attempt from the EC2 plugin to the newly created worker missed the IP address, printing "null" instead: Regular log entry: 2020-03-10 04:47:57.202+ [id=797295]INFOhudson.plugins.ec2.EC2Cloud#log: Connecting to 172.31.26.224 on port 22, with timeout 1. Bad log line (only 2 instances in several weeks, immediately before the failure): 2020-03-10 04:47:57.113+ [id=797326]INFOhudson.plugins.ec2.EC2Cloud#log: Connecting to null on port 22, with timeout 1. Observe the "null" instead of a valid IP address. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this me
[JIRA] (JENKINS-61051) Jobs are started on master instead of EC2 slaves randomly
Title: Message Title Jeff Thompson commented on JENKINS-61051 Re: Jobs are started on master instead of EC2 slaves randomly That sounds like it is an issue in the EC2 plugin. Possibly a timing problem. Presumably if the IP address isn't specified it runs the job on the master. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204531.158142564.4394.1583877180238%40Atlassian.JIRA.
[JIRA] (JENKINS-33925) Test framework for Jenkinsfile
Title: Message Title Sergei Parshev commented on JENKINS-33925 Re: Test framework for Jenkinsfile Jesse Glick Ok, got it. Will work on preparing the changes for groovy-cps unit testing in this intercepting way, if you think it's a good idea. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.169416.145942296.4397.1583877242314%40Atlassian.JIRA.
[JIRA] (JENKINS-14138) New git branch has empty changelist
Title: Message Title Mark Waite stopped work on JENKINS-14138 Change By: Mark Waite Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.144769.1340072991000.4542.1583877842301%40Atlassian.JIRA.
[JIRA] (JENKINS-14138) New git branch has empty changelist
Title: Message Title Mark Waite updated JENKINS-14138 Jenkins / JENKINS-14138 New git branch has empty changelist Change By: Mark Waite Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.144769.1340072991000.4540.1583877842249%40Atlassian.JIRA.
