[JIRA] (JENKINS-54439) Support configuration as code plugin
Title: Message Title Tim Jacomb assigned an issue to Tim Jacomb Jenkins / JENKINS-54439 Support configuration as code plugin Change By: Tim Jacomb Assignee: Tomas Westling Tim Jacomb Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195200.1541367672000.12259.1558936461592%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57696) Make list view JCasC compliant
Title: Message Title Tim Jacomb updated JENKINS-57696 Jenkins / JENKINS-57696 Make list view JCasC compliant Change By: Tim Jacomb Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199632.1558936371000.12252.1558936446023%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54439) Support configuration as code plugin
Title: Message Title Tim Jacomb started work on JENKINS-54439 Change By: Tim Jacomb Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195200.1541367672000.12260.1558936461707%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57696) Make list view JCasC compliant
Title: Message Title Tim Jacomb started work on JENKINS-57696 Change By: Tim Jacomb Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199632.1558936371000.12250.1558936442235%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57696) Make list view JCasC compliant
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-57696 Make list view JCasC compliant Issue Type: Improvement Assignee: Joseph Petersen Components: core Created: 2019-05-27 05:52 Priority: Minor Reporter: Tim Jacomb Currently most of ListView, doesn't work with the configuration-as-code plugin Some minor changes would be enough to fix that Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title Sachin Gahlawat created an issue Jenkins / JENKINS-57695 Jira issue not created when jenkins build failed Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2019-05-27 05:40 Environment: Jenkins ver. 2.150.1, Centos OS Labels: plugin jenkins exception Priority: Blocker Reporter: Sachin Gahlawat I have setup the 3.6.0 version of Jira plugin for jenkins with my jenkins instance. I am having issue with "Create jira issue" upon job failure. Below is the error i am getting (from Console Output) Build step 'Execute shell' marked build as failure ERROR: Build step failed with exception java.lang.NullPointerException at hudson.plugins.jira.JiraSession.createIssue(JiraSession.java:413) at hudson.plugins.jira.JiraCreateIssueNotifier.createJiraIssue(JiraCreateIssueNotifier.java:202) at hudson.plugins.jira.JiraCreateIssueNotifier.currentBuildResultFailure(JiraCreateIssueNotifier.java:357) at hudson.plugins.jira.JiraCreateIssueNotifier.perform(JiraCreateIssueNotifier.java:157) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1843) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97)
[JIRA] (JENKINS-12615) Discard Old Builds does not warn the user when no builds will be discarded
Title: Message Title Nisarg Shah updated an issue Jenkins / JENKINS-12615 Discard Old Builds does not warn the user when no builds will be discarded Change By: Nisarg Shah Comment: [~jglick] In implementation, I have just added one if condition(type of flag) in LogRotator.java. Whenever value of numToKeep and daysToKeep are not blank, then according to flag(new variable declared) message will be displayed. Currently I have added only if condition and I got error. I have searched regarding this error, but I am not getting it clear. Error is of failure of JUnit tests. But I don't know why it failed.[ERROR] Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 0.006 s <<< FAILURE! - in hudson.cli.PrivateKeyProviderTest[ERROR] loadKeyBroken(hudson.cli.PrivateKeyProviderTest) Time elapsed: 0.001 s <<< ERROR!java.lang.Exception: Unexpected exception, expected but was at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:28) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143)Caused by: java.nio.file.NoSuchFileException: C:\Open%20Source\cli\target\test-classes\hudson\cli\openssh-broken at sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:79) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97) at sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102) at sun.nio.fs.WindowsFileSystemProvider.newByteChannel(WindowsFileSystemProvider.java:230) at java.nio.file.Files.newByteChannel(Files.java:361) at java.nio.file.Files.newByteChannel(Files.java:407) at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384) at java.nio.file.Files.newInputStream(Files.java:152) at hudson.cli.PrivateKeyProvider.readPemFile(PrivateKeyProvider.java:132) at hudson.cli.PrivateKeyProvider.loadKey(PrivateKeyProvider.java:128) at hudson.cli.PrivateKeyProviderTest.loadKeyBroken(PrivateKeyProviderTest.java:102) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov resolved as Fixed You can either wait for the plugin to be listed via Jenkins (or force yor server to list manually) or dl from here: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/zos-connector/2.3.1 Kindly test and close the issue as appropriate. Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Alexander Shcherbakov Status: In Progress Resolved Resolution: Fixed Released As: zos-connector-2.3.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57581) Jenkins job created by seed job using jobdsl script does't shows JMS message checks on job UI.
Title: Message Title sachin pathare commented on JENKINS-57581 Re: Jenkins job created by seed job using jobdsl script does't shows JMS message checks on job UI. Hey thank you very much Scott Hebert, it solved my issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199498.1558437008000.12239.1558934400130%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Daniel Stratton commented on JENKINS-57549 Re: Jenkins job doesn't detect completion of mainframe job I've run 3 successful jobs back to back with no obvious signs of problems, so it looks to be good from my side. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199458.1558312268000.12234.1558933260096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Daniel Stratton updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Daniel Stratton Attachment: debugLog.20190527.1456.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199458.1558312268000.12232.1558933200129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57659) jenkins share library Cannot cast object 'true' with class 'java.lang.Boolean'
Title: Message Title wang xingmin commented on JENKINS-57659 Re: jenkins share library Cannot cast object 'true' with class 'java.lang.Boolean' I found that it happens in jenkins share library, when I remove the method nexusArtifactUploader to the parent jenkinsfile ,there's no error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199592.1558694534000.12200.1558931820042%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Alexander Shcherbakov Attachment: zos-connector.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199458.1558312268000.12199.1558931460176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov commented on JENKINS-57549 Re: Jenkins job doesn't detect completion of mainframe job OK, I found the issue now. It seems that during restructuring changes for 2.3.0 I accidentally broke JESINTERFACELEVEL=2 check (it doesn't try to extract RC at all) by misplacing single '}'. I decided to leave logon as in 2.2.0 (more stable) + fixed the rc check. Kindly retest. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199458.1558312268000.12197.1558931460141%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Alexander Shcherbakov Attachment: zos-connector-old-logon-connect.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199458.1558312268000.12195.1558931340116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38293) Unable to create Jira issue using Jira plugin for jenkins
Title: Message Title Sachin Gahlawat commented on JENKINS-38293 Re: Unable to create Jira issue using Jira plugin for jenkins Hi, We are also experiencing this issue. It's critical for us. Can you please share the updates on this issue. Sachin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174461.1474064021000.12184.1558930920273%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-57694 BuildChooser logs a missing descriptor message Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-05-27 02:53 Environment: Jenkins 2.176.1-rc Git plugin 4.0 pre-release Git client 3.0 pre-release Priority: Minor Reporter: Mark Waite The git plugin 4.0 logs the following stack trace: May 26, 2019 8:50:01 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for org.jenkinsci.plugins.workflow.job.WorkflowJob@3e088f1b[Bugs-Pipeline-Checks/jenkins-bugs-multibranch-pipeline-no-localbranch/JENKINS-43468] java.lang.AssertionError: class jenkins.plugins.git.AbstractGitSCMSource$SpecificRevisionBuildChooser is missing its descriptor at jenkins.model.Jenkins.getDescriptorOrDie(Jenkins.java:1541) at hudson.plugins.git.util.BuildChooser.getDescriptor(BuildChooser.java:229) at hudson.plugins.git.util.BuildChooser.getDisplayName(BuildChooser.java:49) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:679) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:668) at org.jenkinsci.plugins.workflow.job.WorkflowJob.poll(WorkflowJob.java:617) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:603) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:649) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
[JIRA] (JENKINS-57693) groovy-axis should accept an array of GString
Title: Message Title
trejkaz created an issue
Jenkins / JENKINS-57693
groovy-axis should accept an array of GString
Issue Type:
Improvement
Assignee:
emanuelez
Components:
groovyaxis-plugin
Created:
2019-05-27 01:20
Priority:
Minor
Reporter:
trejkaz
I tried a script like this: return "this${1}" And the groovy-axis plugin considers this not a string, and treats it as ['default']. Since GString is essentially a language construct for groovy, I'd expect them to be treated as string here, even though they are technically a different type. I think you'd only have to call toString() in the returned objects to deal with this.
Add Comment
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title Mark Waite commented on JENKINS-57587 Re: Lightweight checkout gives NPE Any further details Jeff Blaine? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199505.1558465141000.12176.1558919640080%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit
Title: Message Title
Mark Waite edited a comment on JENKINS-57660
Re: Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit
I believe the stack trace message is correct. The refspec is invalid. It needs to be corrected.If the Amazon Code Commit plugin created that refspec, it needs to be changed to provide a correct refspec.If a person entered that refspec, then they need to change the refspec to use a correct value. I agree that this is a bug, since the stack trace is much too ugly a way of showing a failure to the user.When I use that invalid refspec in the "Advanced" section of the git repository configuration, saving the form shows the following message:{noformat}java.lang.IllegalArgumentException: Invalid wildcards refs/remotes/*/master/* at org.eclipse.jgit.transport.RefSpec.(RefSpec.java:196) at org.eclipse.jgit.transport.RefSpec.(RefSpec.java:226) at org.eclipse.jgit.lib.DefaultTypedConfigGetter.getRefSpecs(DefaultTypedConfigGetter.java:302) at org.eclipse.jgit.lib.Config.getRefSpecs(Config.java:502) at org.eclipse.jgit.transport.RemoteConfig.(RemoteConfig.java:195) at org.eclipse.jgit.transport.RemoteConfig.getAllRemoteConfigs(RemoteConfig.java:124) at hudson.plugins.git.GitSCM$DescriptorImpl.createRepositoryConfigurations(GitSCM.java:1612)Caused: hudson.plugins.git.GitException: Error creating repositories at hudson.plugins.git.GitSCM$DescriptorImpl.createRepositoryConfigurations(GitSCM.java:1614) at hudson.plugins.git.GitSCM.updateFromUserData(GitSCM.java:264) at hudson.plugins.git.GitSCM.(GitSCM.java:214) at jdk.internal.reflect.GeneratedConstructorAccessor213.newInstance(Unknown Source) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:474) at hudson.model.Descriptor.newInstance(Descriptor.java:596){noformat} It should instead use the more common Jenkins field validation techniques to check that the refspec is valid and highlight the field when the refspec is not valid.
Add Comment
[JIRA] (JENKINS-57660) Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit
Title: Message Title
Mark Waite edited a comment on JENKINS-57660
Re: Git plugin crash on saving the project on Amazon EC while using git for Amazon Code Commit
I believe the stack trace message is correct. The refspec is invalid. It needs to be corrected.If the Amazon Code Commit plugin created that refspec, it needs to be changed to provide a correct refspec.If a person entered that refspec, then they need to change the refspec to use a correct value. I agree that this is a bug, since the stack trace is much too ugly a way of showing a failure to the user.When I use that invalid refspec in the "Advanced" section of the git repository configuration, saving the form shows the following message:{noformat}java.lang.IllegalArgumentException: Invalid wildcards refs/remotes/*/master/* at org.eclipse.jgit.transport.RefSpec.(RefSpec.java:196) at org.eclipse.jgit.transport.RefSpec.(RefSpec.java:226) at org.eclipse.jgit.lib.DefaultTypedConfigGetter.getRefSpecs(DefaultTypedConfigGetter.java:302) at org.eclipse.jgit.lib.Config.getRefSpecs(Config.java:502) at org.eclipse.jgit.transport.RemoteConfig.(RemoteConfig.java:195) at org.eclipse.jgit.transport.RemoteConfig.getAllRemoteConfigs(RemoteConfig.java:124) at hudson.plugins.git.GitSCM$DescriptorImpl.createRepositoryConfigurations(GitSCM.java:1612)Caused: hudson.plugins.git.GitException: Error creating repositories at hudson.plugins.git.GitSCM$DescriptorImpl.createRepositoryConfigurations(GitSCM.java:1614) at hudson.plugins.git.GitSCM.updateFromUserData(GitSCM.java:264) at hudson.plugins.git.GitSCM.(GitSCM.java:214) at jdk.internal.reflect.GeneratedConstructorAccessor213.newInstance(Unknown Source) at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:478) at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:474) at hudson.model.Descriptor.newInstance(Descriptor.java:596){noformat}
Add Comment
[JIRA] (JENKINS-57659) jenkins share library Cannot cast object 'true' with class 'java.lang.Boolean'
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57659
jenkins share library Cannot cast object 'true' with class 'java.lang.Boolean'
Change By:
Mark Waite
I use jenkins share library to upload maven jar package to nexus3 , it upload success , but finally report an error .my upload script : {noformat} pipeline {stage("publish to nexus") { script { echo "ok" pom = readMavenPom file: "pom.xml" filesByGlob = findFiles(glob: "target/*.${pom.packaging}") artifactPath = filesByGlob[0].path nexusArtifactUploader( nexusVersion: NEXUS_VERSION, protocol: NEXUS_PROTOCOL, nexusUrl: NEXUS_URL, groupId: pom.groupId, version: "${ env.BRANCH_NAME }", repository: NEXUS_REPOSITORY, credentialsId: NEXUS_CREDENTIAL_ID,artifacts: [ [artifactId: pom.artifactId, classifier: "${ env.BUILD_NUMBER }-${GIT_COMMIT_SHORT}", file: artifactPath, type: pom.packaging], ] ) } }} {noformat} the error messages: {noformat} [Pipeline] // node[Pipeline] End of Pipelinehudson.remoting.ProxyException: org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'true' with class 'java.lang.Boolean' to class 'org.jenkinsci.plugins.pipeline.modeldefinition.model.Root' at org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.continueCastOnSAM(DefaultTypeTransformation.java:405) at org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.continueCastOnNumber(DefaultTypeTransformation.java:319) at org.codehaus.groovy.runtime.typehandling.DefaultTypeTransformation.castToType(DefaultTypeTransformation.java:232) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.castToType(ScriptBytecodeAdapter.java:603) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter$castToType.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 com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.call(ModelInterpreter.groovy:60) at uploadToNexus.call(uploadToNexus.groovy:15) at WorkflowScript.run(WorkflowScript:58) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.delegateAndExecute(ModelInterpreter.groovy:137) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executeSingleStage(ModelInterpreter.groovy:682) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.catchRequiredContextForNode(ModelInterpreter.groovy:417) at
[JIRA] (JENKINS-57683) ClassCastException in git plugin on GitHub branch scan
Title: Message Title Mark Waite updated JENKINS-57683 Was only a problem in unreleased versions of the git plugin. Will be fixed in the next pre-release of git plugin 4.0, likely named 4.0.0-beta11. Jenkins / JENKINS-57683 ClassCastException in git plugin on GitHub branch scan Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199618.155881147.12168.1558916400130%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56764) Pipeline fails on some AMI images / node types because of Broken Pipe
Title: Message Title Valentyn Klindukh commented on JENKINS-56764 Re: Pipeline fails on some AMI images / node types because of Broken Pipe It seems to be failing because of nvidia-docker2 which is used by GPU AMIs I tried several AMIs (amazon-eks-gpu-node-1.10 amazon-eks-gpu-node-1.11 amazon-eks-gpu-node-1.12) and same issue occured Any ideas? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198407.1553610802000.12166.1558909500145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Daniel Stratton commented on JENKINS-57549 Re: Jenkins job doesn't detect completion of mainframe job Forward progress, but it's still stuck in a loop. It can find the job, but for some reason seems unable to determine it has finished (and it most definitely has). But now it's submitting and listing. Can't offer you much insight from my side - for me, I can always just roll back to 2.2.0 and it works, albeit with extra messages. Wish I knew more to offer insight. This is a low volume usage mainframe (only a handful of developer users), so there won't be much churn on state Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199458.1558312268000.12160.1558908240178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57549) Jenkins job doesn't detect completion of mainframe job
Title: Message Title Daniel Stratton updated an issue Jenkins / JENKINS-57549 Jenkins job doesn't detect completion of mainframe job Change By: Daniel Stratton Attachment: debugLog.20190527.0800.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199458.1558312268000.12158.1558908120128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57543) Support PostgreSQL database
Title: Message Title Cyrille Le Clerc commented on JENKINS-57543 Re: Support PostgreSQL database benoit guerin as you "liked" https://github.com/jenkinsci/pipeline-maven-plugin/pull/214, could you test the PostgreSQL support using pipeline-maven-3.7.0-beta-1.hpi. Please don't forget to install the PostgreSQL API plugin to load the postgresql driver in the classpath of Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199451.1558248334000.12156.1558907460051%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51947) Symbol from unrelated Extension point conflicts with syntax?
Title: Message Title Kanstantsin Shautsou commented on JENKINS-51947 Re: Symbol from unrelated Extension point conflicts with syntax? Hi, issues discussion is here https://github.com/KostyaSha/github-integration-plugin/issues/274 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191436.152899281.12154.1558905000119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57692) Implement the AWS service class
Title: Message Title Yufei Zhang started work on JENKINS-57692 Change By: Yufei Zhang Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199627.1558902031000.12125.1558902180065%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57692) Implement the AWS service class
Title: Message Title Yufei Zhang created an issue Jenkins / JENKINS-57692 Implement the AWS service class Issue Type: Task Assignee: Yufei Zhang Components: external-workspace-manager-plugin Created: 2019-05-26 20:20 Labels: gsoc-2019 Priority: Major Reporter: Yufei Zhang Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57686) A list of improvements in GitLab Server Configuration
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57686 A list of improvements in GitLab Server Configuration Change By: Parichay Barpanda Sprint: GSoC 2019. Coding Phase 1 Community Bonding Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199621.1558824827000.12122.1558901220148%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57685) Add button for Server config doesn't work
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57685 Add button for Server config doesn't work Change By: Parichay Barpanda Sprint: GSoC 2019. Coding Phase 1 Community Bonding Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199620.1558824489000.12121.1558901220103%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57691) GitLabAuthSourceTest fails
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57691 GitLabAuthSourceTest fails Change By: Parichay Barpanda Sprint: GSoC 2019. Coding Phase 1 Community Bonding Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199626.1558901074000.12123.1558901220162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57691) GitLabAuthSourceTest fails
Title: Message Title
Parichay Barpanda created an issue
Jenkins / JENKINS-57691
GitLabAuthSourceTest fails
Issue Type:
Improvement
Assignee:
Parichay Barpanda
Components:
gitlab-branch-source-plugin
Created:
2019-05-26 20:04
Labels:
gsoc-2019
Priority:
Critical
Reporter:
Parichay Barpanda
The test fails in `given_tokenCredentialwhenconvertthen_tokenAuth()` method of `GitLabAuthSourceTest` class. This function is responsible for checking if the `GitLabAuth` object returned by `AuthenticationTokens.convert(GitLabAuth, PersonalAccessToken)` is actually an instance of `GitLabAuthToken`. But the object returned is null while `PersonalAccessToken` object is not null. The error shown: ``` java.lang.AssertionError: java.lang.AssertionError: Expected: an instance of io.jenkins.plugins.gitlabbranchsource.client.api.GitLabAuthToken but: null {{ at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) at org.junit.Assert.assertThat(Assert.java:956) at org.junit.Assert.assertThat(Assert.java:923) at io.jenkins.plugins.gitlabbranchsource.authentication.GitLabAuthSourceTest.given_tokenCredentialwhenconvertthen_tokenAuth(GitLabAuthSourceTest.java:31) 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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
[JIRA] (JENKINS-57690) Support more sophisticated versioning
Title: Message Title
chris cooney updated an issue
Jenkins / JENKINS-57690
Support more sophisticated versioning
Change By:
chris cooney
At the moment, the ` @Library ` annotation supports the exact tag from a repository. This is great, but simplistic. As a team who are semantically versioning the shared library and regularly pushing out patch and minor versions, the overhead of expecting teams to constantly update their Jenkinsfiles is a little unfair. We want teams to be able to pin to a major version but be able to accept minor or patch version updates.For example, the following syntax should be valid: ` @Library('library@v0.1. * ') ` . It should find the latest tag matching ` v0.1.* ` and pull in that version.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199625.155081000.12119.155140129%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57690) Support more sophisticated versioning
Title: Message Title
chris cooney created an issue
Jenkins / JENKINS-57690
Support more sophisticated versioning
Issue Type:
New Feature
Assignee:
Unassigned
Components:
workflow-cps-global-lib-plugin
Created:
2019-05-26 16:28
Labels:
plugins
Priority:
Minor
Reporter:
chris cooney
At the moment, the `@Library` annotation supports the exact tag from a repository. This is great, but simplistic. As a team who are semantically versioning the shared library and regularly pushing out patch and minor versions, the overhead of expecting teams to constantly update their Jenkinsfiles is a little unfair. We want teams to be able to pin to a major version but be able to accept minor or patch version updates. For example, the following syntax should be valid: `@Library('library@v0.1.')`. It should find the latest tag matching `v0.1.` and pull in that version.
Add Comment
[JIRA] (JENKINS-57689) Use run-selector/CopyArtifacts plugin to pass parameters/build description to the promotion job
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57689 Use run-selector/CopyArtifacts plugin to pass parameters/build description to the promotion job Issue Type: Task Assignee: Prastik Gyawali Components: copyartifact-plugin, promoted-builds-plugin, run-selector-plugin Created: 2019-05-26 14:56 Labels: gsoc-2019 Priority: Major Reporter: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe
[JIRA] (JENKINS-57688) Make promotion job triggerable using parameterized-trigger concept.
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57688 Make promotion job triggerable using parameterized-trigger concept. Issue Type: Task Assignee: Prastik Gyawali Components: promoted-builds-plugin Created: 2019-05-26 14:54 Labels: gsoc-2019 Priority: Major Reporter: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57687) Create new custom steps to be included in the declarative pipeline for promotion description.
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57687 Create new custom steps to be included in the declarative pipeline for promotion description. Issue Type: Task Assignee: Prastik Gyawali Components: promoted-builds-plugin Created: 2019-05-26 14:51 Labels: gsoc-2019 Priority: Major Reporter: Prastik Gyawali Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-57605) Use the "H2 API Plugin" to load H2
Title: Message Title Cyrille Le Clerc updated JENKINS-57605 Jenkins / JENKINS-57605 Use the "H2 API Plugin" to load H2 Change By: Cyrille Le Clerc Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199531.1558531518000.12105.1558881000202%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57543) Support PostgreSQL database
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-57543 Re: Support PostgreSQL database Download: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3. 6 7 . 15 0 -beta-1/pipeline-maven-3. 6 7 . 15 0 -beta-1.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199451.1558248334000.12106.1558881000231%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping
Title: Message Title Wisen Tanasa commented on JENKINS-57630 Re: Support Multi User Picker custom field parameter mapping Thanks for the confirmation. I've converted this issue as a new feature. Feel free to contribute! For a workaround, you can always use the injected JIRA_ISSUE_KEY environment variable, then hit JIRA and get the information by yourself. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199560.1558603816000.12104.1558879260111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping
Title: Message Title Deakey Tan commented on JENKINS-57630 Re: Support Multi User Picker custom field parameter mapping Yes, it's "User Picker (multiple users)". And I have read CustomFieldParameterResolverTest file, confirm that I can't use it now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199560.1558603816000.12099.1558874460110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52325) Archiving artifacts fails if jenkins is not owner of builds dir
Title: Message Title Patrick Trabocchi commented on JENKINS-52325 Re: Archiving artifacts fails if jenkins is not owner of builds dir Matt Sicker, sincerely i don't know how to create a unit test that reproduce this bug, if you want i can attach the output console stacktrace, and the configured shared folder between host and guest. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192110.153055342.12080.1558864860154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
