[JIRA] (JENKINS-57260) git blame fails for out-of-tree builds
Title: Message Title
m l commented on JENKINS-57260
Re: git blame fails for out-of-tree builds
Unfortunately there are still errors when I start analyzing the warnings with dir statements including different IDs:
post {
always {
dir('Platform') {
recordIssues enabledForFailure: true, sourceCodeEncoding: 'UTF-8', tool: msBuild(id: 'Platform', reportEncoding: 'UTF-8')
}
dir('Modules') {
recordIssues enabledForFailure: true, sourceCodeEncoding: 'UTF-8', tool: msBuild(id: 'Modules', reportEncoding: 'UTF-8')
}
}
}
Git blame fails with:
[Pipeline] recordIssues
08:37:04 [MSBuild] Sleeping for 5 seconds due to JENKINS-32191...
08:37:09 [MSBuild] Parsing console log (workspace: 'C:\jenkins\w\_platform_feature_jenkins_master\Platform')
08:37:26 using credential buildpc-Git-User
08:37:27 using credential buildpc-Git-User
08:37:27 using credential buildpc-Git-User
08:37:26 > git rev-parse "HEAD^{commit}" # timeout=10
08:37:27 using credential buildpc-Git-User
08:37:27 > git rev-parse "HEAD^{commit}" # timeout=10
08:37:32 > git rev-parse "HEAD^{commit}" # timeout=10
08:37:34 [MSBuild] [-ERROR-] Errors while extracting author and commit information from Git:
08:37:34 [MSBuild] [-ERROR-] - skipping file 'C:/jenkins/w/_platform_feature_jenkins_master/Modules/XX/AvailabilityCheckFeatures.cs' (outside of work tree)
08:37:34 [MSBuild] [-ERROR-] - skipping file 'C:/jenkins/w/_platform_feature_jenkins_master/Platform/XX/EditableFlexibleAssociation.cs' (outside of work tree)
[...]
08:37:34 [MSBuild] [-ERROR-] ... skipped logging of 270 additional errors ...
08:37:34 [MSBuild] [-ERROR-] Errors while mining source control repository:
08:37:34 [MSBuild] [-ERROR-] Can't analyze history of file C:/jenkins/w/_platform_feature_jenkins_master/Modules/XX/AvailabilityCheckFeatures.cs
08:37:34 [MSBuild] [-ERROR-] org.eclipse.jgit.api.errors.NoHeadException: No HEAD exists and no explicit starting revision was specified
08:37:34 [MSBuild] [-ERROR-] at org.eclipse.jgit.api.LogCommand.call(LogCommand.java:150)
08:37:34 [MSBuild] [-ERROR-] at io.jenkins.plugins.forensics.git.miner.GitRepositoryMiner$RepositoryStatisticsCallback.analyzeHistory(GitRepositoryMiner.java:121)
[...]
[Pipeline] // dir
[Pipeline] dir
08:37:34 Running in C:\jenkins\w\_platform_feature_jenkins_master\Modules
[Pipeline] {
[Pipeline] recordIssues
08:37:34 [MSBuild] Sleeping for 5 seconds due to JENKINS-32191...
08:37:39 [MSBuild] Parsing console log (workspace: 'C:\jenkins\w\_platform_feature_jenkins_master\Modules')
08:37:56 using credential buildpc-Git-User
08:37:56 using credential buildpc-Git-User
08:37:57 using credential buildpc-Git-User
08:37:56 > git rev-parse "HEAD^{commit}" # timeout=10
08:37:57 using credential buildpc-Git-User
08:37:57 > git rev-parse "HEAD^{commit}" # timeout=10
08:38:00 > git rev-parse "HEAD^{commit}" # timeout=10
08:38:02 [MSBuild] [-ERROR-] Errors while extracting author and commit information from Git:
08:38:02 [MSBuild] [-ERROR-] - skipping file 'C:/jenkins/w/_platform_feature_jenkins_master/Modules/XX/AvailabilityChec
[JIRA] (JENKINS-57566) Default security prohibits ResultAction's getResult
Title: Message Title David Wright commented on JENKINS-57566 Re: Default security prohibits ResultAction's getResult Ulli Hafner is there any hint you could give me as to why this does not work? action.getQualityGateStatus().getResult() Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199480.1558369817000.2500.1578301020190%40Atlassian.JIRA.
[JIRA] (JENKINS-60642) Bitbucket Server Integration plugin breaks Role-based Authorization config
Title: Message Title L. G. created an issue Jenkins / JENKINS-60642 Bitbucket Server Integration plugin breaks Role-based Authorization config Issue Type: Bug Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2020-01-06 08:58 Environment: Debian x64 Server, running Jenkins v2.190.1, Role-based Authorization Strategy v2.13, Attlasian Bitbucket Server Integration v1.0.3 Priority: Major Reporter: L. G. My Jenkins configuration includes the usage of the Role-based Authorization Strategy plugin and it was working fine until I've decided to install and evaluate the Attlasian Bitbucket Server Integration plugin. Once I did, the Jenkins users had lost their ability to Configure any jobs in their designated Job folders, with any attempt to do so resulting in the " is missing the Job/Configure permission" error and following stack trace: Stack traceStack traceorg.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.190.1.jar!/lib/hudson/project/config-scm.jelly:36:91: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.190.1.jar!/lib/form/section.jelly:48:21: jenkins.user is missing the Job/Configure permission at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.do
[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided
Title: Message Title Reiner Wirtz commented on JENKINS-60641 Re: IllegalArgumentException: No script is provided I got the same error. I use now version 2.211. Thir version works for me. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203880.157829510.2502.1578301140366%40Atlassian.JIRA.
[JIRA] (JENKINS-57566) Default security prohibits ResultAction's getResult
Title: Message Title David Wright updated an issue Jenkins / JENKINS-57566 Default security prohibits ResultAction's getResult Change By: David Wright Comment: [~drulli] is there any hint you could give me as to why this does not work?action.getQualityGateStatus().getResult() Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199480.1558369817000.2507.1578301200445%40Atlassian.JIRA.
[JIRA] (JENKINS-60642) Bitbucket Server Integration plugin breaks Role-based Authorization config
Title: Message Title
L. G. updated an issue
Jenkins / JENKINS-60642
Bitbucket Server Integration plugin breaks Role-based Authorization config
Change By:
L. G.
My Jenkins configuration includes the usage of the Role-based Authorization Strategy plugin and it was working fine until I've decided to install and evaluate the Attlasian Bitbucket Server Integration plugin. Once I did, the Jenkins users had lost their ability to Configure any jobs in their designated Job folders, with any attempt to do so resulting in the " is missing the Job/Configure permission" error and following stack trace: { code:java noformat }Stack traceStack traceStack traceorg.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.190.1.jar!/lib/hudson/project/config-scm.jelly:36:91: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.190.1.jar!/lib/form/section.jelly:48:21: jenkins.user is missing the Job/Configure permission at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.ja
[JIRA] (JENKINS-60642) Bitbucket Server Integration plugin breaks Role-based Authorization config
Title: Message Title
L. G. updated an issue
Jenkins / JENKINS-60642
Bitbucket Server Integration plugin breaks Role-based Authorization config
Change By:
L. G.
My Jenkins configuration includes the usage of the Role-based Authorization Strategy plugin and it was working fine until I've decided to install and evaluate the Attlasian Bitbucket Server Integration plugin. Once I did, the Jenkins users had lost their ability to Configure any jobs in their designated Job folders, with where they have full privileges to do anything, and any attempt to do so resulting perform a job Configuration results in the " is missing the Job/Configure permission" error and following stack trace: {noformat}Stack traceStack traceorg.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.190.1.jar!/lib/hudson/project/config-scm.jelly:36:91: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.190.1.jar!/lib/form/section.jelly:48:21: jenkins.user is missing the Job/Configure permission at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title
davidkarlsen created an issue
Jenkins / JENKINS-60643
Auto-create project for maven-based jobs
Issue Type:
Improvement
Assignee:
Steve Springett
Components:
dependency-track-plugin
Created:
2020-01-06 09:05
Labels:
ux usability pipeline auto
Priority:
Minor
Reporter:
davidkarlsen
Currently the plugin/pipeline configuration requires an existing project by defining projectId. I think it would be smoother to auto-create project, and read name/version from pom-files like: name: ${groupId}-${artifactId} version: ${version} then the entry-barrier would be lowered and it would be easier to adopt DT at larger scale.
Add Comment
[JIRA] (JENKINS-60644) scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title kpop created an issue Jenkins / JENKINS-60644 scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Issue Type: Bug Assignee: Andrew Bayer Components: script-security-plugin Created: 2020-01-06 09:07 Environment: Ubuntu 14.04, Jenkins 2.212, Script Security Plugin 1.68 Priority: Blocker Reporter: kpop java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:183) at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:189) at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:193) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:100) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:86) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:113) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixName(FunctionCallBlock.java:78) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.c
[JIRA] (JENKINS-60644) scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-60644 scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Change By: Oleg Nenashev Assignee: Andrew Bayer Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2518.1578302160406%40Atlassian.JIRA.
[JIRA] (JENKINS-60644) scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Oleg Nenashev started work on JENKINS-60644 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2520.1578302160435%40Atlassian.JIRA.
[JIRA] (JENKINS-60644) scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60644 scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Change By: Oleg Nenashev Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2522.1578302160498%40Atlassian.JIRA.
[JIRA] (JENKINS-60644) scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Oleg Nenashev commented on JENKINS-60644 Re: scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError I suspect it is a regression after https://github.com/jenkinsci/jenkins/pull/4254 in 2.112, CC Josh Soref. I am working on it Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2524.1578302220180%40Atlassian.JIRA.
[JIRA] (JENKINS-60644) scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60644 scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Change By: Oleg Nenashev Labels: regression Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2526.1578302220243%40Atlassian.JIRA.
[JIRA] (JENKINS-60471) Jenkins polluting /tmp with thousands of TrueType font files
Title: Message Title Dirk Heinrichs commented on JENKINS-60471 Re: Jenkins polluting /tmp with thousands of TrueType font files Seems to be an issue with Java 8. After updating the Jenkins master to java 11 the problem disappeared. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203552.1576232486000.2528.1578302700107%40Atlassian.JIRA.
[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided
Title: Message Title Martin Stolle commented on JENKINS-60641 Re: IllegalArgumentException: No script is provided java.lang.IllegalArgumentException: No script is provided at hudson.util.spring.BeanBuilder.parse(BeanBuilder.java:130) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.createSecurityComponents(ActiveDirectorySecurityRealm.java:340) at hudson.security.SecurityRealm.getSecurityComponents(SecurityRealm.java:487) at hudson.security.HudsonFilter.reset(HudsonFilter.java:138) at jenkins.model.Jenkins.setSecurityRealm(Jenkins.java:2590) at jenkins.model.Jenkins$16.run(Jenkins.java:3287) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1142) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused: org.jvnet.hudson.reactor.ReactorException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:282) at jenkins.InitReactorRunner.run(InitReactorRunner.java:48) at jenkins.model.Jenkins.executeReactor(Jenkins.java:1175) at jenkins.model.Jenkins.(Jenkins.java:965) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) Caused: hudson.util.HudsonFailedToLoad at hudson.WebAppMain$3.run(WebAppMain.java:250) Same issue here, major problem with active directory plugin! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60154) Link to Results not clickable when Groovy Parser ID includes Spaces
Title: Message Title Niklas Lingenauber updated an issue Jenkins / JENKINS-60154 Link to Results not clickable when Groovy Parser ID includes Spaces Change By: Niklas Lingenauber Attachment: image-2020-01-06-10-45-03-826.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203020.1573635088000.2533.1578303960684%40Atlassian.JIRA.
[JIRA] (JENKINS-60154) Link to Results not clickable when Groovy Parser ID includes Spaces
Title: Message Title Niklas Lingenauber commented on JENKINS-60154 Re: Link to Results not clickable when Groovy Parser ID includes Spaces Ulli Hafner, thank you for your response. How can a failed validation be identified? Although validation is included since version V7.2.0, the problem seems to be still present in version 7.2.2. There are no warnings in the log or when saving a wrong parser ID. The used IDs are "Tasking ctc" and "IAR Warnings Parser". Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203020.1573635088000.2535.1578303960716%40Atlassian.JIRA.
[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided
Title: Message Title Oleg Nenashev started work on JENKINS-60641 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203880.157829510.2550.1578304381220%40Atlassian.JIRA.
[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-60641 IllegalArgumentException: No script is provided Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203880.157829510.2548.1578304380876%40Atlassian.JIRA.
[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided
Title: Message Title Oleg Nenashev commented on JENKINS-60641 Re: IllegalArgumentException: No script is provided I suspect the rott cause is similar to JENKINS-60644 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203880.157829510.2542.1578304380789%40Atlassian.JIRA.
[JIRA] (JENKINS-60154) Link to Results not clickable when Groovy Parser ID includes Spaces
Title: Message Title Niklas Lingenauber edited a comment on JENKINS-60154 Re: Link to Results not clickable when Groovy Parser ID includes Spaces [~drulli], thank you for your response. How can a failed validation be identified? Although validation is included since [version V7.2.0|https://github.com/jenkinsci/warnings-ng-plugin/releases/tag/warnings-ng-7.2.0], the problem seems to be still present in version 7.2.2.!image-2020-01-06-10-45-03-826.png!There are no warnings in the console log or when saving a wrong parser ID and the job succedes with defect links .The used IDs are "Tasking ctc" and "IAR Warnings Parser". Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203020.1573635088000.2540.1578304380758%40Atlassian.JIRA.
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60644 Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Change By: Oleg Nenashev Summary: Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2538.1578304380726%40Atlassian.JIRA.
[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60641 IllegalArgumentException: No script is provided Change By: Oleg Nenashev Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203880.157829510.2558.1578304441508%40Atlassian.JIRA.
[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60641 IllegalArgumentException: No script is provided Change By: Oleg Nenashev Labels: regression Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203880.157829510.2556.1578304441382%40Atlassian.JIRA.
[JIRA] (JENKINS-58727) Misleading log message when no e-mail is sent
Title: Message Title Harald Albers commented on JENKINS-58727 Re: Misleading log message when no e-mail is sent The issuse was fixed in #69, can someone please create a new release? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201021.1564483585000.2569.1578305820545%40Atlassian.JIRA.
[JIRA] (JENKINS-60517) Kubernetes plugin crashes with docker plugin .inside command
Title: Message Title Vincent Latombe updated JENKINS-60517 Jenkins / JENKINS-60517 Kubernetes plugin crashes with docker plugin .inside command Change By: Vincent Latombe Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203614.1576615322000.2585.1578305940928%40Atlassian.JIRA.
[JIRA] (JENKINS-60517) Kubernetes plugin crashes with docker plugin .inside command
Title: Message Title Vincent Latombe assigned an issue to Narayanan Singaram Jenkins / JENKINS-60517 Kubernetes plugin crashes with docker plugin .inside command Change By: Vincent Latombe Assignee: Narayanan Singaram Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203614.1576615322000.2582.1578305940845%40Atlassian.JIRA.
[JIRA] (JENKINS-53158) Pipelines leak OneOffExecutors when triggered on a temporary offline master
Title: Message Title Pierre Beitz commented on JENKINS-53158 Re: Pipelines leak OneOffExecutors when triggered on a temporary offline master Still reproducible: Jenkins 2.204.1 workflow-aggregator:2.6 workflow-cps:2.78 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193168.1534849944000.2592.1578306540298%40Atlassian.JIRA.
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title Charusheela Bopardikar updated JENKINS-60144 Jenkins / JENKINS-60144 Cant delete Jenkins job if the perforce template client has been deleted Change By: Charusheela Bopardikar Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203005.1573570536000.2594.1578306660563%40Atlassian.JIRA.
[JIRA] (JENKINS-58207) 2.181 JNA update breaks NegotiateSSO
Title: Message Title Stefan Rademacher commented on JENKINS-58207 Re: 2.181 JNA update breaks NegotiateSSO Hi. Any idea, when v1.4 is going to be visible via Jenkins Update Center? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200266.1561541748000.2599.1578306840332%40Atlassian.JIRA.
[JIRA] (JENKINS-53158) Pipelines leak OneOffExecutors when triggered on a temporary offline master
Title: Message Title Pierre Beitz commented on JENKINS-53158 Re: Pipelines leak OneOffExecutors when triggered on a temporary offline master Further testing shows that https://issues.jenkins-ci.org/browse/JENKINS-60348 fixed it. Successfully tested in 2.211! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193168.1534849944000.2614.1578308040774%40Atlassian.JIRA.
[JIRA] (JENKINS-53158) Pipelines leak OneOffExecutors when triggered on a temporary offline master
Title: Message Title Pierre Beitz resolved as Fixed Jenkins / JENKINS-53158 Pipelines leak OneOffExecutors when triggered on a temporary offline master Change By: Pierre Beitz Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193168.1534849944000.2619.1578308100487%40Atlassian.JIRA.
[JIRA] (JENKINS-58854) Cannot configure SonarQube plugin with JCasC
Title: Message Title Daniel Estermann updated JENKINS-58854 Released as 2.11 Jenkins / JENKINS-58854 Cannot configure SonarQube plugin with JCasC Change By: Daniel Estermann Status: Fixed but Unreleased Resolved Released As: sonar-2.11 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.googl
[JIRA] (JENKINS-60412) Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration
Title: Message Title Luca Domenico Milanesio closed an issue as Fixed Considering this as fixed from v0.4.1 Jenkins / JENKINS-60412 Additional behavior "Discover open changes" not working for using Gerrit as SCM in Jenkins Shared Library configuration Change By: Luca Domenico Milanesio Status: Open Closed Resolution: Fixed Released As: 0.4.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60645) Gerrit Code Review plugin requires dependent plugins that require Jenkins 2.150.1 or newer.
Title: Message Title Luca Domenico Milanesio created an issue Jenkins / JENKINS-60645 Gerrit Code Review plugin requires dependent plugins that require Jenkins 2.150.1 or newer. Issue Type: Bug Assignee: Luca Domenico Milanesio Components: gerrit-code-review-plugin Created: 2020-01-06 11:25 Environment: gerrit-code-review-0.4.1 jenkins 2.60.3 Priority: Major Reporter: Luca Domenico Milanesio The Gerrit Code Review plugin declares to support Jenkins v2.54+. However, that is not really true because it depends on other plugins that require at least Jenkins v2.150.1. Therefore, Gerrit Code Review plugin should be more transparent and clearly require v2.150.1 as well, so that it can be loaded and used consistently. Add Comment
[JIRA] (JENKINS-58949) If job fails in cleanup further triggering fails
Title: Message Title Charusheela Bopardikar closed an issue as Won't Do Workaround is available and possible fix may not be appropriate in all circumstances. Jenkins / JENKINS-58949 If job fails in cleanup further triggering fails Change By: Charusheela Bopardikar Status: In Progress Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@goo
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Oleg Nenashev commented on JENKINS-60644 Re: Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError In my case the JVM just hangs when I try to reproduce this issue. Not sure why, it should not happen in this way Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2651.1578310260301%40Atlassian.JIRA.
[JIRA] (JENKINS-60646) Unable to Login
Title: Message Title Shriram Narayanan created an issue Jenkins / JENKINS-60646 Unable to Login Issue Type: Task Assignee: Joseph Petersen Components: accurev-plugin Created: 2020-01-06 12:09 Priority: Critical Reporter: Shriram Narayanan Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-60647) EC2-Plugin time range for minimum no of instances does not work with JCASC
Title: Message Title Luis Piedra-Márquez created an issue Jenkins / JENKINS-60647 EC2-Plugin time range for minimum no of instances does not work with JCASC Issue Type: Bug Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin, ec2-plugin Created: 2020-01-06 13:50 Priority: Minor Reporter: Luis Piedra-Márquez The feature for limiting the minimum instances alive for a time range (https://github.com/jenkinsci/ec2-plugin/pull/404/) is really neat, but it does not work with Jenkins configuration as code. Details Jenkins version: 2.204.1 ec2-plugin version: 1.47 configuration-as-code-plugin version: 1.34 When running a configuration including this snippet: minimumNumberOfInstancesTimeRangeConfig: minimumNoInstancesActiveTimeRangeFrom: "08:00" minimumNoInstancesActiveTimeRangeTo: "19:00" minimumNoInstancesActiveTimeRangeDays: monday: true tuesday: true wednesday: true thursday: true friday: true saturday: false sunday: false Configuration fails with: io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class hudson.plugins.ec2.util.MinimumNumberOfInstancesTimeRangeConfig : minimumNoInstancesActiveTimeRangeDays. Available attributes : minimumNoInstancesActiveTimeRangeFrom, minimumNoInstancesActiveTimeRangeTo Looking at the logs:
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Jesse Glick assigned an issue to Jesse Glick I was able to reproduce this just by starting Jenkins (master) on a fresh home dir, installing suggested plugins, making a trivial Pipeline job, and running it. Root cause: java.lang.NullPointerException at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.loadBlacklist(StaticWhitelist.java:317) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.(StaticWhitelist.java:323) pointing here and suggesting a resource loading problem. Jenkins / JENKINS-60644 Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Change By: Jesse Glick Assignee: Oleg Nenashev Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided
Title: Message Title Jesse Glick resolved as Duplicate Also involves Class.getResourceAsStream so almost certainly a duplicate. Jenkins / JENKINS-60641 IllegalArgumentException: No script is provided Change By: Jesse Glick Status: In Progress Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion
[JIRA] (JENKINS-56471) Construct view using full path even when only one depot path is given
Title: Message Title Charusheela Bopardikar started work on JENKINS-56471 Change By: Charusheela Bopardikar Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198071.1552007329000.2724.1578321600221%40Atlassian.JIRA.
[JIRA] (JENKINS-60154) Link to Results not clickable when Groovy Parser ID includes Spaces
Title: Message Title Ulli Hafner reopened an issue Ah, seems that I added the ID check for all reporter parameters, but not for the groovy parser. Jenkins / JENKINS-60154 Link to Results not clickable when Groovy Parser ID includes Spaces Change By: Ulli Hafner Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@goo
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Jesse Glick commented on JENKINS-60644 Re: Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Verified that #4254 is responsible by bisecting using WorkflowPluginTest.linearFlow. So far I have not found a mistake by code inspection. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2739.1578322500549%40Atlassian.JIRA.
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Oleg Nenashev commented on JENKINS-60644 Re: Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Jesse Glick my theory is a race condition in the collection. The code changed from thread-safe Vector implementation to unsafe Array list. I did review the code before merging and it did not seem to be a problem, but this is my best bet at the moment Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2752.1578322680661%40Atlassian.JIRA.
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Baptiste Mathus commented on JENKINS-60644 Re: Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Could we maybe add a simple test in ATH SmokeTest set or so that would have caught this? Thanks Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2755.1578323220954%40Atlassian.JIRA.
[JIRA] (JENKINS-60505) Microfocus Application Automation Tools Ver:6.0 not supporting ALM 12.55
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-60505 Microfocus Application Automation Tools Ver:6.0 not supporting ALM 12.55 Change By: Paul-Adrian Tofan Assignee: Roy Lu Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203596.1576509162000.2770.1578323581525%40Atlassian.JIRA.
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Joshua Yates commented on JENKINS-59090 Re: Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing Anda Sorina Laakso This has been open for some time, can we please get an update?? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.2773.1578323940648%40Atlassian.JIRA.
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-60644 Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Change By: Jesse Glick Component/s: script-security-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2776.1578324240695%40Atlassian.JIRA.
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Jesse Glick commented on JENKINS-60644 Re: Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Tracked the problem down to a bad refactoring of a loop (took me a long time to notice this in the diff!). Will try to verify the fix using JTH. Baptiste Mathus regarding ATH @SmokeTest’s I think the issue is that they only include tests which do not use any plugins. Adding plugins to the mix would make the test run nondeterministic unless we also pinned versions rather than using the latest from the UC. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2790.1578324540388%40Atlassian.JIRA.
[JIRA] (JENKINS-60430) stopping a job while in reconcile will not stop the reconcile (the job itself will however stop)
Title: Message Title Eric Daigneault commented on JENKINS-60430 Re: stopping a job while in reconcile will not stop the reconcile (the job itself will however stop) Hi Karl, For the file handle, do you know if the file handle was released when the reconcile completed? The handle was not released and caused the next job to fail on sync as the next reconcile was trying to repair the file Also why did you need to workaround it? Was killing the jobs a frequent need? It is not a frequent need no, but anything that affects the next build is considered a blocking issue. Getting builds jobs must be independent of each-other unless explicitly specified in the job's config. Hence the workaround. Besides the clean option is really not practical beyond the simplest hello-world project. on very large projects a reconcile will take longer than a wipe and re-sync or just a force-sync which is the option we are currently using as a replacement (force sync with the occasional wipe and re-sync). It is not as clean but we gained some precious minutes in the build process.. For the p4j*.tmp files, is it possible they were from an earlier plugib version? it's possible but that would mean that the p4clean is not doing it's job as there have been a great many jobs run on these machines since the last update. Was .Sources\Floor_Base_Interior_01.ZTL a special file? For example a symlink/junction? No it was a normal file (zbrush I beleive) weighing around 50MB. As we are mostly under windows stay clear of symlinks and such, such a pain under windows ! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this me
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Jesse Glick commented on JENKINS-60644 Re: Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Ah and the problem only affects plugins which include some sort of library (i.e., non-hpi dependency). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2806.1578326040407%40Atlassian.JIRA.
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Jesse Glick updated JENKINS-60644 Jenkins / JENKINS-60644 Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.2820.1578326581225%40Atlassian.JIRA.
[JIRA] (JENKINS-52396) Integration with Blue Ocean?
Title: Message Title Charusheela Bopardikar closed an issue as Postponed The Jenkins Blue Ocean project is postponed hence postponing this. Jenkins / JENKINS-52396 Integration with Blue Ocean? Change By: Charusheela Bopardikar Status: In Progress Closed Resolution: Postponed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussio
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title Steve Springett commented on JENKINS-60643 Re: Auto-create project for maven-based jobs Auto-creating projects is already supported, but is limited to pipeline jobs. Non-pipeline jobs do not have the option. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203882.1578301543000.2846.1578328320326%40Atlassian.JIRA.
[JIRA] (JENKINS-54226) Script not approved for use exception at the end of every build log - even for jobs with no groovy scripts
Title: Message Title Ankur commented on JENKINS-54226 Re: Script not approved for use exception at the end of every build log - even for jobs with no groovy scripts I am facing the same issue. This is coming at end of every job. There is no script pending for approval. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194865.1540404456000.2850.1578328500198%40Atlassian.JIRA.
[JIRA] (JENKINS-60648) java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation
Title: Message Title
Carsten Kirschner created an issue
Jenkins / JENKINS-60648
java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2020-01-06 16:35
Environment:
Openjdk 1.8.0_222 Jenkins 2.112 Apache Maven 3.5.2 and 3.6.3 Linux ip-10-0-1-57 4.14.154-99.181.amzn1.x86_64 #1 SMP Sat Nov 16 01:38:34 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Priority:
Major
Reporter:
Carsten Kirschner
Jenkins 2.112 does not build our maven builds. Rollback to 2.111 fixed this. Update of apache maven did not help. Creating a ticket as the error says, search did not find anything: Running as SYSTEM [EnvInject] - Loading node environment variables. Building in workspace /mnt/storage/jenkins/workspace/guide.portal - Integration No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url g...@bitbucket.org:corussoft/guide.portal.git # timeout=10 Fetching upstream changes from g...@bitbucket.org:corussoft/guide.portal.git > git --version # timeout=10 > git fetch --tags --progress – g...@bitbucket.org:corussoft/guide.portal.git +refs/heads/:refs/remotes/origin/ # timeout=10 > git rev-parse refs/remotes/origin/integration^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/integration^{commit} # timeout=10 Checking out Revision c9483f7765f95bf4fe532c3311197e6cd370dff6 (refs/remotes/origin/integration) > git config core.sparsecheckout # timeout=10 > git checkout -f c9483f7765f95bf4fe532c3311197e6cd370dff6 # timeout=10 Commit message: "- speichern: schedulingPattern, start und end des Importers geht nun" > git rev-list --no-w
[JIRA] (JENKINS-54226) Script not approved for use exception at the end of every build log - even for jobs with no groovy scripts
Title: Message Title Ankur edited a comment on JENKINS-54226 Re: Script not approved for use exception at the end of every build log - even for jobs with no groovy scripts I am facing the same issue. This is coming at end of every job. There is no script pending for approval. This is the message I see in logs:org.jenkinsci.plugins.scriptsecurity.scripts.UnapprovedUsageException: script not yet approved for use at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.using(ScriptApproval.java:474) at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval$using$0.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:133) at com.splunk.splunkjenkins.UserActionDSL.perform(UserActionDSL.groovy:39) at com.splunk.splunkjenkins.listeners.LoggingRunListener.onCompleted(LoggingRunListener.java:85) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:209) at org.jenkinsci.plugins.workflow.job.WorkflowRun.finish(WorkflowRun.java:587) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$800(WorkflowRun.java:133) at org.jenkinsci.plugins.workflow.job.WorkflowRun$GraphL.onNewHead(WorkflowRun.java:1014) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:1463) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.run(CpsThreadGroup.java:493) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:38) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Add Comment
[JIRA] (JENKINS-60649) Bitbucket Server Integration plugin does not work for Pipelines
Title: Message Title Trung Nguyen created an issue Jenkins / JENKINS-60649 Bitbucket Server Integration plugin does not work for Pipelines Issue Type: Bug Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2020-01-06 16:43 Priority: Blocker Reporter: Trung Nguyen I followed the youtube video (https://www.youtube.com/watch?v=0-FugzVYJQU) to install and configure the Bitbucket Server Integration plugin on Jenkins so that a Pipeline can be automatically run when there is a push to our Bitbucket Server. However, after creating the Pipeline in Jenkins, I do not see the webhook being created on my Bitbucket Server. Before that ,I clicked Test Connection and it showed that Jenkins successfully connected to the repository on my Bitbucket server. The webhook is correctly created on my Bitbucket Server after I create a Freestyle Jenkins project, and the project is automatically triggered upon a push to my Bitbucket server. So I think the issue is just with the Pipeline project. Add Comment
[JIRA] (JENKINS-60649) Bitbucket Server Integration plugin does not work for Pipelines
Title: Message Title Trung Nguyen assigned an issue to Trung Nguyen Jenkins / JENKINS-60649 Bitbucket Server Integration plugin does not work for Pipelines Change By: Trung Nguyen Assignee: Kristy Hughes Trung Nguyen Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203891.1578329007000.2858.1578329100191%40Atlassian.JIRA.
[JIRA] (JENKINS-60353) Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404
Title: Message Title Karl Shultz commented on JENKINS-60353 Re: Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404 Now that everyone's back from various holidays, I'm going to pick this back up. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203370.1575386738000.2860.1578330001207%40Atlassian.JIRA.
[JIRA] (JENKINS-60353) Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404
Title: Message Title Karl Shultz edited a comment on JENKINS-60353 Re: Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404 Now that everyone's back from various holidays, I'm going hoping to pick this back up. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203370.1575386738000.2862.1578330001880%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Petr H commented on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge In our case it was failing even with the git client plugin 2.9.0 (git plugin 3.12.1) in some cases. However I noticed that after creating a copy of one problematic jenkins job the new one didn't exhibit the issue. Both (old&new) job bonfigs were identical, therefore I cleared the old job's workspace (at all jenkins slaves) and it started working again. You may try that if you encounter the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198962.1556378819000.2892.1578332400175%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Petr H edited a comment on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge In our case it was failing even with the git client plugin 2.9.0 (git plugin 3.12.1) in some cases. However I noticed that after creating a copy of one problematic jenkins job the new one didn't exhibit the issue. Both (old&new) job bonfigs configs were identical, therefore I cleared the old job's workspace (at all jenkins slaves) and it started working again. You may try that if you encounter the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198962.1556378819000.2897.1578332640258%40Atlassian.JIRA.
[JIRA] (JENKINS-50154) Webhook delivery failed as X-Hub-Signature did not match calculated
Title: Message Title steve erkel commented on JENKINS-50154 Re: Webhook delivery failed as X-Hub-Signature did not match calculated All webhooks fail with 400 from Jenkins with a message like this. URI:/github-webhook/ STATUS:400 MESSAGE:Provided signature [2ea5940025571f3314b15e7d1283a3c258f70912] did not match to calculated SERVLET:Stapler Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189171.1520980599000.2908.1578333240685%40Atlassian.JIRA.
[JIRA] (JENKINS-60650) Git LFS *sometimes* fails on when git merge is involved
Title: Message Title
Bryan Gillespie created an issue
Jenkins / JENKINS-60650
Git LFS *sometimes* fails on when git merge is involved
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-client-plugin
Created:
2020-01-06 17:53
Environment:
Jenkins version: 2.190.1 Plugin version: 2.5.0 Bitbucket server version: 6.1.2 Git LFS version: git-lfs/2.8.0 (GitHub; linux amd64; go 1.12.6) Git version: 2.11.0 Jenkins is running inside a docker container.
Labels:
plugin jenkins git
Priority:
Major
Reporter:
Bryan Gillespie
Sometimes when an LFS file change is merged to master, all PR CI jobs will start failing on the merge step with: {{Started by user Jupiter CI Restarted from build #11, stage Build Terminal Obtained Jenkinsfile from 5033c6390fdbbfa53f57975da66b0d55282353a3+bd68a4fb34dc8b2daf36f07c0d88bd8a740bc667 Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] milestone Trying to pass milestone 11 [Pipeline] milestone Trying to pass milestone 12 [Pipeline] stage [Pipeline] { (Build Terminal) [Pipeline] node Running on Jenkins in /var/jenkins_home/workspace/jupiter_PR-99 [Pipeline] { [Pipeline] checkout using credential e9b7d03e-0956-4e3c-b405-7c95be8c34de using credential e9b7d03e-0956-4e3c-b405-7c95be8c34de > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from 2 remote Git repositories > git config remote.origin.url http://gtswtbitsyslnxvm1:7990/scm/JUP/jupiter.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -
[JIRA] (JENKINS-60650) Git LFS *sometimes* fails on when git merge is involved
Title: Message Title
Bryan Gillespie updated an issue
Jenkins / JENKINS-60650
Git LFS *sometimes* fails on when git merge is involved
Change By:
Bryan Gillespie
Sometimes when an LFS file change is merged to master, _all_ PR CI jobs will start failing on the merge step with: { { noformat} Started by user Jupiter CIRestarted from build #11, stage Build TerminalObtained Jenkinsfile from 5033c6390fdbbfa53f57975da66b0d55282353a3+bd68a4fb34dc8b2daf36f07c0d88bd8a740bc667Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] milestoneTrying to pass milestone 11[Pipeline] milestoneTrying to pass milestone 12[Pipeline] stage[Pipeline] \ { (Build Terminal)[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/jupiter_PR-99[Pipeline] { { [Pipeline] checkout using credential e9b7d03e-0956-4e3c-b405-7c95be8c34de using credential e9b7d03e-0956-4e3c-b405-7c95be8c34de > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from 2 remote Git repositories > git config remote.origin.url http://gtswtbitsyslnxvm1:7990/scm/JUP/jupiter.git # timeout=10Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10Fetching without tags Fetching upstream changes from http://gtswtbitsyslnxvm1:7990/scm/JUP/jupiter.git > git --version # timeout=10 using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- http://gtswtbitsyslnxvm1:7990/scm/JUP/jupiter.git +refs/pull-requests/99/from:refs/remotes/origin/PR-99 > git config remote.upstream.url http://gtswtbitsyslnxvm1:7990/scm/JUP/jupiter.git # timeout=10Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Fetching without tags Fetching upstream changes from http://gtswtbitsyslnxvm1:7990/scm/JUP/jupiter.git using GIT_ASKPASS to set credentials > git fetch --no-tags --progress -- http://gtswtbitsyslnxvm1:7990/scm/JUP/jupiter.git +refs/heads/master:refs/remotes/upstream/master Merging remotes/upstream/master commit bd68a4fb34dc8b2daf36f07c0d88bd8a740bc667 into PR head commit 5033c6390fdbbfa53f57975da66b0d55282353a3 Enabling Git LFS pull > git config core.sparsecheckout # timeout=10 > git checkout -f 5033c6390fdbbfa53f57975da66b0d55282353a3 > git config --get remote.origin.url # timeout=10using GIT_ASKPASS to set credentials > git lfs pull origin > git merge bd68a4fb34dc8b2daf36f07c0d88bd8a740bc667 # timeout=10ERROR: Timeout after 10 minutesEnabling Git LFS pull > git config core.sparsecheckout # timeout=10 > git checkout -f 5033c6390fdbbfa53f57975da66b0d55282353a3 > git config --get remote.origin.url # timeout=10using GIT_ASKPASS to set credentials > git lfs pull origin [Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // stage[Pipeline] End of Pipeline[Bitbucket] Notifying pull request build result[Bitbucket] Build result notifiedhudson.plugins.git.GitException: Command "git merge bd68a4fb34dc8b2d
[JIRA] (JENKINS-60650) Git LFS *sometimes* fails on when git merge is involved
Title: Message Title Bryan Gillespie updated an issue Jenkins / JENKINS-60650 Git LFS *sometimes* fails on when git merge is involved Change By: Bryan Gillespie Environment: Jenkins version: 2.190.1 Bitbucket Source Branch Plugin version: 2.5.0 Git Plugin: 3.12.1 Git client Plugin: 2.8.6 Bitbucket server version: 6.1.2Git LFS version: git-lfs/2.8.0 (GitHub; linux amd64; go 1.12.6)Git version: 2.11.0Jenkins is running inside a docker container. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203892.1578333215000.2914.1578333660169%40Atlassian.JIRA.
[JIRA] (JENKINS-60651) Nested Stages are Linear (not nested) in Blue Ocean Pipeline Visualisation, but should be nested like Parallel Stages
Title: Message Title
Narendra Kumar created an issue
Jenkins / JENKINS-60651
Nested Stages are Linear (not nested) in Blue Ocean Pipeline Visualisation, but should be nested like Parallel Stages
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Jenkinsfile.groovy
Components:
blueocean-plugin
Created:
2020-01-06 18:01
Priority:
Critical
Reporter:
Narendra Kumar
I've got a lot of build steps. Three build configurations to action across multiple satellite projects as well as the main product. These three configurations require the same steps to be taken with different parameters. As such, I have grouped stages for configuration X under a parent stage ('X'), stages for configuration Y under stage('Y') When I use Parallel stages, I can see in the pipeline visualization in Blue Ocean that the parallel stages are within a parent stage. This promotes understanding of what is happening/why to someone who isn't a maintainer of the Jenkinsfile.groovy pipeline script, i.e. someone who isn't me. The same isn't true for nested stages: parent stages are simply illustrated as a previous stage. This is a shame, as I have altered my pipeline script to group related stages together. It's also misleading, indicating that a stage has completed when its child stages have in fact not completed. Please make Nested stages appear to be children of their parent stages in the visualization in Blue Ocean to reflect the nature of the jenkinsfile, it would promote understanding of what the build is doing,and also reduce the amount of horizontal scrolling required! I have attached a sample jenkinsfile.groovy that should illustrate the concept of what I would like to see reflected in the Jenkins visualization. If you've any questions or I need to clarify anything, please do get in touch at the e
[JIRA] (JENKINS-60474) streamline plugin-pom and support the jenkins-bom
Title: Message Title James Nord resolved as Fixed Jenkins / JENKINS-60474 streamline plugin-pom and support the jenkins-bom Change By: James Nord Status: In Progress Resolved Resolution: Fixed Released As: plugin-pom:4.0-beta-1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203556.1576237963000.2916.1578333720486%40Atlassian.JIRA.
[JIRA] (JENKINS-60652) plugin breaks most jenkins functionality without a connection to AWS
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-60652 plugin breaks most jenkins functionality without a connection to AWS Issue Type: Bug Assignee: Chris Kilding Components: aws-secrets-manager-credentials-provider-plugin Created: 2020-01-06 18:08 Environment: Jenkins: 2.204.1 aws-secrets-manager-credentials-provider: 0.1.2 Priority: Major Reporter: Dominik Bartholdi when ever this plugin does not have a connection to AWS it breaks many screens. e.g. every screen which wants to list some credentials in a dropdown will show an error message e.g. in http://localhost:8080/configure when the docker-commons-plugin or cloudbees-bitbucket-branch-source-plugin is installed. Also all build accessing any credential will fail, even if the credentials requested by the build are provided by a different credentials-provider (e.g. default jenkins provider). This can easily reproduced by just installing the plugin on a local instance and not configuring anything more. Add Comment
[JIRA] (JENKINS-60652) plugin breaks jenkins without a connection to AWS
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-60652 plugin breaks jenkins without a connection to AWS Change By: Dominik Bartholdi Summary: plugin breaks most jenkins functionality without a connection to AWS Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203894.157833410.2921.1578334205051%40Atlassian.JIRA.
[JIRA] (JENKINS-60653) Don't treat requested and dependency plugins the same for download
Title: Message Title leemeador created an issue Jenkins / JENKINS-60653 Don't treat requested and dependency plugins the same for download Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2020-01-06 18:15 Labels: plugin-manager Priority: Minor Reporter: leemeador The install plugins shell script will ALWAYS download a plugin that is requested. It will only download a dependency plugin, one needed by a requested plugin recursively, if that plugin is not already installed in a version equal or greater than the one required. The current plugin installation manager cli tool treats requested and dependency plugins identically in this regard. Neither requested nor dependency plugins are downloaded if the plugin is already installed and the required version is less than the installed version for that plugin. Change to download a requested plugin even if it is already installed and use the version calculated already using requested and dependency versions. Note that the script will download a plugin more than once since it does version comparisons (for dependency plugins) as it finds the dependencies. The cli tool adds the plugin to the "download list" as it find the dependencies and downloads only once for each plugin. I don't think we should change the cli tool to download multiple times for a single plugin but here are the cases in which the install plugins script it will do that. I may not have thought of all the possible cases: 1) If a plugin is requested more than once, it will be downloaded multiple times. Only the last version downloaded (last version in the requested plugin list) will remain. Note that requesting plugins in txt files, yaml files and via command line option does not make it clear what order plugins
[JIRA] (JENKINS-60648) java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation
Title: Message Title harika vegesna updated an issue Jenkins / JENKINS-60648 java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation Change By: harika vegesna Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203890.1578328547000.2925.1578334980321%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 I sort of thought doing that might prove difficult. It's solvable in other ways so it really is not a big deal. I had used that plugin before on an older server but I had to drop it as it ended up causing the server to become corrupted, or rather the scriptler portion. I never used the scriptler portion but it eventually made it so the Jenkins server could not be upgraded. I never had a chance to dig real deep into it. Then with Scriptler is of course a security issue plugin which here I cannot risk using. Anyway, thanks for spending the time to look into it. Have a great year! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203842.1577724088000.2927.1578334980351%40Atlassian.JIRA.
[JIRA] (JENKINS-60648) java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation
Title: Message Title harika vegesna commented on JENKINS-60648 Re: java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation Even i face the same issue .Till yesterday it's working fine ERROR: Processing failed due to a bug in the code. Please report this to the issue tracker ( https://jenkins.io/redirect/report-an-issue ). java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation at org.apache.maven.model.superpom.DefaultSuperPomProvider.getSuperModel(DefaultSuperPomProvider.java:67) at org.apache.maven.model.building.DefaultModelBuilder.getSuperModel(DefaultModelBuilder.java:1132) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:282) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:432) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:400) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:363) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:370) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:340) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1329) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1126) at hudson.FilePath.act(FilePath.java:1075) at hudson.FilePath.act(FilePath.java:1058) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:987) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:691) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1853) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428) project=hudson.maven.MavenModuleSet@74dc6e22[BLNQAAutomation] project.getModules()=[hudson.maven.MavenModule@4f6ca50a[BLNQAAutomation/BLNProject:Automation][BLNQAAutomation/BLNProject:Automation][relativePath:], hudson.maven.MavenModule@6661bacf[BLNQAAutomation/BLNProject:com.org.Automation][BLNQAAutomation/BLNProject:com.org.Automation][relativePath:]] project.getRootModule()=hudson.maven.MavenModule@6661bacf[BLNQAAutomation/BLNProject:com.org.Automation][BLNQAAutomation/BLNProject:com.org.Automation][relativePath:] FATAL: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation at org.apache.maven.model.superpom.DefaultSuperPomProvider.getSuperModel(DefaultSuperPomProvider.java:67) at org.apache.maven.model.building.DefaultModelBuilder.getSuperModel(DefaultModelBuilder.java:1132) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:282) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:432) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:400) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:363) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:370) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:340) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1329) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(Mave
[JIRA] (JENKINS-60648) java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation
Title: Message Title harika vegesna edited a comment on JENKINS-60648 Re: java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation Even i face the same issue .Till yesterday it's working fineERROR: Processing failed due to a bug in the code. Please report this to the issue tracker ([https://jenkins.io/redirect/report-an-issue]).java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation at org.apache.maven.model.superpom.DefaultSuperPomProvider.getSuperModel(DefaultSuperPomProvider.java:67) at org.apache.maven.model.building.DefaultModelBuilder.getSuperModel(DefaultModelBuilder.java:1132) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:282) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:432) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:400) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:363) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:370) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:340) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1329) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1126) at hudson.FilePath.act(FilePath.java:1075) at hudson.FilePath.act(FilePath.java:1058) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:987) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:691) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1853) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428)project=hudson.maven.MavenModuleSet@74dc6e22[BLNQAAutomation]project.getModules()= [hudson.maven.MavenModule@4f6ca50a[BLNQAAutomation/BLNProject:Automation][BLNQAAutomation/BLNProject:Automation][relativePath:], hudson.maven.MavenModule@6661bacf[BLNQAAutomation/BLNProject:com.org.Automation][BLNQAAutomation/BLNProject:com.org.Automation][relativePath:]]project.getRootModule()=hudson.maven.MavenModule@6661bacf[BLNQAAutomation/BLNProject:com.org.Automation][BLNQAAutomation/BLNProject:com.org.Automation][relativePath:]FATAL: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installationjava.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation at org.apache.maven.model.superpom.DefaultSuperPomProvider.getSuperModel(DefaultSuperPomProvider.java:67) at org.apache.maven.model.building.DefaultModelBuilder.getSuperModel(DefaultModelBuilder.java:1132) at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:282) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:432) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:400) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:363) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:370) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:340) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1329) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(Mav
[JIRA] (JENKINS-60648) java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation
Title: Message Title harika vegesna updated an issue Jenkins / JENKINS-60648 java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation Change By: harika vegesna Labels: jenkins Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203890.1578328547000.2933.1578335340151%40Atlassian.JIRA.
[JIRA] (JENKINS-60654) Add option to ignore bundled plugins
Title: Message Title leemeador created an issue Jenkins / JENKINS-60654 Add option to ignore bundled plugins Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2020-01-06 18:32 Labels: plugin-manager Priority: Minor Reporter: leemeador The use of bundled plugins in today's Jenkins is not well documented. In trying to find information about their usage, via the developers' email list, it was suggested my best bet might be to ignore bundled plugins alltogether. The question I have is whether Jenkins today installs all bundled plugins at startup time. And that could be at initial startup (the very first time after an install) or at every time the war starts running. The impact relates to when the plugin installation manager cli tool (or the install plugins shell script) run. The next paragraph is next to impossible to understand because its so circular. If update manger cli (or script) runs after bundled plugins have been installed automatically, it will take into account the plugins that are installed and the bundled ones are irrelevant. Then plugins might get put back when bundled ones get installed on the next startup. If iupdate manager cli (or script) runs before bundled plugins are installed, and they really are being installed, then the plugins installed by the update manager (or script) will get replaced when the bundled ones get installed. Proposal It's not clear to me that there is any solution to choosing versions for this circular sort of situation. So what I propose is to allow the user to have the plugin manager cli consider bundled plugins by default or, optionally by command line option, ignore bundled plugins completely. Ignoring means not collecting the list of bundled plugins. They will not be conside
[JIRA] (JENKINS-60654) Add option to ignore bundled plugins
Title: Message Title leemeador updated an issue Jenkins / JENKINS-60654 Add option to ignore bundled plugins Change By: leemeador URL: https://groups.google.com/forum/#!msg/jenkinsci-dev/8VnvgOVeVIs/9HG0JpfDDAAJ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203896.1578335562000.2937.1578335700290%40Atlassian.JIRA.
[JIRA] (JENKINS-60653) Don't treat requested and dependency plugins the same for download
Title: Message Title leemeador assigned an issue to leemeador Jenkins / JENKINS-60653 Don't treat requested and dependency plugins the same for download Change By: leemeador Assignee: Natasha Stopa leemeador Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203895.1578334517000.2941.1578335700388%40Atlassian.JIRA.
[JIRA] (JENKINS-60654) Add option to ignore bundled plugins
Title: Message Title leemeador assigned an issue to leemeador Jenkins / JENKINS-60654 Add option to ignore bundled plugins Change By: leemeador Assignee: Natasha Stopa leemeador Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203896.1578335562000.2939.1578335700325%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Mihai Stoichitescu updated an issue Jenkins / JENKINS-55287 Pipeline: Failure to load flow node: FlowNode was not found in storage for head Change By: Mihai Stoichitescu Attachment: plugins_versions_2.190.1.txt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196374.1545361815000.2943.1578336001061%40Atlassian.JIRA.
[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided
Title: Message Title Matthew Larrain commented on JENKINS-60641 Re: IllegalArgumentException: No script is provided Same issues for us as well. Reverted back to 2.211 until this is resolved. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203880.157829510.2975.1578336180256%40Atlassian.JIRA.
[JIRA] (JENKINS-60652) plugin breaks jenkins without a connection to AWS
Title: Message Title
Dominik Bartholdi updated an issue
Jenkins / JENKINS-60652
plugin breaks jenkins without a connection to AWS
Change By:
Dominik Bartholdi
when ever this plugin does not have a connection to AWS it breaks many screens. e.g. every screen which wants to list some credentials in a dropdown will show an error message e.g. in [http://localhost:8080/configure] when the [docker-commons-plugin|https://plugins.jenkins.io/docker-commons] or [cloudbees-bitbucket-branch-source-plugin|https://plugins.jenkins.io/cloudbees-bitbucket-branch-source] is installed. Also all build accessing any credential will fail, even if the credentials requested by the build are provided by a different credentials-provider (e.g. default jenkins provider).This can easily reproduced by just installing the plugin on a local instance and not configuring anything more. The exception looks like this:{code:java}com.amazonaws.SdkClientException: Unable to find a region via the region provider chain. Must provide an explicit region in the builder or setup environment to supply a region. at com.amazonaws.client.builder.AwsClientBuilder.setRegion(AwsClientBuilder.java:462) at com.amazonaws.client.builder.AwsClientBuilder.configureMutableProperties(AwsClientBuilder.java:424) at com.amazonaws.client.builder.AwsSyncClientBuilder.build(AwsSyncClientBuilder.java:46) at io.jenkins.plugins.credentials.secretsmanager.AwsCredentialsProvider.fetchCredentials(AwsCredentialsProvider.java:103) at com.google.common.base.Suppliers$ExpiringMemoizingSupplier.get(Suppliers.java:173) at io.jenkins.plugins.credentials.secretsmanager.AwsCredentialsProvider.getCredentials(AwsCredentialsProvider.java:61) at com.cloudbees.plugins.credentials.CredentialsProvider.getCredentials(CredentialsProvider.java:1147) at com.cloudbees.plugins.credentials.CredentialsProvider.getCredentials(CredentialsProvider.java:1222) at com.cloudbees.plugins.credentials.CredentialsProvider.lookupCredentials(CredentialsProvider.java:549) at com.cloudbees.plugins.credentials.CredentialsProvider.findCredentialById(CredentialsProvider.java:906) at com.cloudbees.plugins.credentials.CredentialsProvider.findCredentialById(CredentialsProvider.java:850) at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:144) at org.jenkinsci.plugins.credentialsbinding.impl.UsernamePasswordMultiBinding.bind(UsernamePasswordMultiBinding.java:75) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution2.doStart(BindingStep.java:135) {code}
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Mihai Stoichitescu commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head We are also getting this from time to time after updating Jenkins from 2.121.3 to 2.190.1 I've attached a list of our plugins used. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196374.1545361815000.2981.1578336720796%40Atlassian.JIRA.
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Jesse Glick updated JENKINS-60644 Jenkins / JENKINS-60644 Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.213 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.3010.1578336841008%40Atlassian.JIRA.
[JIRA] (JENKINS-60655) Not able to pick credentials at Publish to Bitbucket Server
Title: Message Title Sabitha Sathesh created an issue Jenkins / JENKINS-60655 Not able to pick credentials at Publish to Bitbucket Server Issue Type: Bug Assignee: Muhammad Ali Khan Attachments: image-2020-01-06-11-05-00-257.png Components: publish-to-bitbucket-plugin Created: 2020-01-06 19:05 Environment: Production Priority: Critical Reporter: Sabitha Sathesh Team, We are using publish to Bitbuket plugin. Even we added the credentials it is throwing an error Add Comment
[JIRA] (JENKINS-60656) Issue with docker build when there's an empty global properties
Title: Message Title Daniel Foulkes created an issue Jenkins / JENKINS-60656 Issue with docker build when there's an empty global properties Issue Type: Bug Assignee: vjuranek Components: docker-build-step-plugin Created: 2020-01-06 19:13 Labels: agents Priority: Minor Reporter: Daniel Foulkes Given using a docker agent When there's a global property that has a empty key and empty value Then the follow error is thrown. process apparently never started in /durable-4f3014cd Work Around Delete the empty global property Add Comment
[JIRA] (JENKINS-60644) Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError
Title: Message Title Cat England commented on JENKINS-60644 Re: Jenkins resource loading issue in AntClassloader. scriptsecurity.sandbox.whitelists.StaticWhitelist NoClassDefFoundError Is there a timeline for the release of 2.213? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203883.1578301631000.3030.1578338100540%40Atlassian.JIRA.
[JIRA] (JENKINS-60656) Issue with docker agent when there's empty global properties
Title: Message Title Daniel Foulkes updated an issue Jenkins / JENKINS-60656 Issue with docker agent when there's empty global properties Change By: Daniel Foulkes Summary: Issue with docker agent when there's an empty global properties Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203898.1578338029000.3047.1578338220272%40Atlassian.JIRA.
[JIRA] (JENKINS-60656) Issue with docker agent when there's an empty global properties
Title: Message Title Daniel Foulkes updated an issue Jenkins / JENKINS-60656 Issue with docker agent when there's an empty global properties Change By: Daniel Foulkes Summary: Issue with docker build agent when there's an empty global properties Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203898.1578338029000.3045.1578338220227%40Atlassian.JIRA.
[JIRA] (JENKINS-60656) Issue with docker agent when there's empty global properties
Title: Message Title Daniel Foulkes commented on JENKINS-60656 Re: Issue with docker agent when there's empty global properties the work around will resolve the issue, however a better solution would be not to allow the saving of global properties that have an empty key, as doing so is pointless. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203898.1578338029000.3049.1578338340119%40Atlassian.JIRA.
[JIRA] (JENKINS-50365) reload pipeline script without executing the job
Title: Message Title Geoff Alexander commented on JENKINS-50365 Re: reload pipeline script without executing the job I wonder how this is fixed? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189416.152180187.3065.1578339720566%40Atlassian.JIRA.
[JIRA] (JENKINS-50365) reload pipeline script without executing the job
Title: Message Title Geoff Alexander edited a comment on JENKINS-50365 Re: reload pipeline script without executing the job I also wonder how this is fixed? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189416.152180187.3067.1578339720609%40Atlassian.JIRA.
[JIRA] (JENKINS-60657) EC2 plugins with multiple templates: fails to start an instance for job in the middle of the queue
Title: Message Title Handi Gao created an issue Jenkins / JENKINS-60657 EC2 plugins with multiple templates: fails to start an instance for job in the middle of the queue Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-01-06 20:13 Environment: Jenkins: 2.204.1 Amazon EC2 plugin (ID: ec2): 1.47 Labels: ec2 ec2-plugin Priority: Minor Reporter: Handi Gao We have two templates for the ec2 plugin: template1 label: test instance cap: 1 template2 label: report instance cap: 3 Jenkins doesn't create a new instance with template 2 when there are jobs in queue waiting for an available excutor on a running instance created with template 1, for example in our queue: 1. test_job (waiting for template1:test as all exectuors on template1:test are taken and we only want 1 instance with template1:test) 2. report_job (waiting for template2:report as it does not exist) Job2 will be blocked until job1 is scheduled as Jenkins keeps trying to sc
[JIRA] (JENKINS-60657) EC2 plugins with multiple templates: fails to start an instance for job in the middle of the queue
Title: Message Title
Handi Gao updated an issue
Jenkins / JENKINS-60657
EC2 plugins with multiple templates: fails to start an instance for job in the middle of the queue
Change By:
Handi Gao
We have two templates for the ec2 plugin: {code:java}template1label: testinstance cap: 1{code} {code:java}template2label: reportinstance cap: 3{code} Jenkins doesn't create a new instance with template 2 when there are jobs in queue waiting for an available excutor on a running instance created with template 1, for example in our queue:1. test_job (waiting for _template1:test_ as all exectuors on _template1:test_ are taken and we only want 1 instance with _template1:test_)2. report_job (waiting for _template2:report_ as it does not exist) Job2 report_job will be blocked until job1 test_job is scheduled as Jenkins keeps trying to schedule job1 test_job and ignores the request of an instance with _template2_ from job2 report_job
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
Y
[JIRA] (JENKINS-60657) EC2 plugins with multiple templates: fails to start an instance for job in the middle of the queue
Title: Message Title
Handi Gao updated an issue
Jenkins / JENKINS-60657
EC2 plugins with multiple templates: fails to start an instance for job in the middle of the queue
Change By:
Handi Gao
We have two templates for the ec2 plugin: {code:java}template1label: testinstance cap: 1{code} {code:java}template2label: reportinstance cap: 3{code} Jenkins doesn't create a new instance with template 2 when there are jobs in queue waiting for an available excutor on a running instance created with template 1, for example in our queue:1. test_job (waiting for _template1:test_ as all exectuors on _template1:test_ are taken and we only want 1 instance with _template1:test_)2. report_job (waiting for _template2:report_ as it does not exist)report_job will be blocked until test_job is scheduled as Jenkins keeps trying to schedule test_job and ignores the request of an instance with _template2_ from report_job
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message
[JIRA] (JENKINS-57566) Default security prohibits ResultAction's getResult
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57566 Default security prohibits ResultAction's getResult Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/291 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199480.1558369817000.3084.1578345000844%40Atlassian.JIRA.
