[JIRA] (JENKINS-55273) recordIssues step fails silently when it can't get get version control information
Title: Message Title
Jonathan Rogers updated an issue
Jenkins / JENKINS-55273
recordIssues step fails silently when it can't get get version control information
Change By:
Jonathan Rogers
I am attempting to display errors and warnings from flake8 with the following step in a pipeline:{code:java}recordIssues enabledForFailure: true, ignoreFailedBuilds: false, tools: [flake8(pattern: 'flake8.txt')]{code} {{The step finds issues, then immediately fails, which fails the entire build. There was nothing relevant to the failure in the output from the step:}} {code:java} {code}{code:java} 00:03:17.360 [Flake8] Searching for all files in '/home/sscadmin/git/pippin' that match the pattern 'flake8.txt' 00:03:17.361 [Flake8] -> found 1 file * 00:03:17.361 * [Flake8] Successfully parsed file /home/sscadmin/git/pippin/flake8.txt * 00:03:17.361 * [Flake8] -> found 73 issues (skipped 0 duplicates) > git rev-parse HEAD^{commit} # timeout=10 {code}There was a traceback in the job console output:{code:java}org.eclipse.jgit.errors.MissingObjectException: Missing unknown 56520e2e8da7a76d073b60ba663faee3a18ee6f0 at org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:158) at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:227) at org.eclipse.jgit.blame.BlameGenerator.push(BlameGenerator.java:317) at org.eclipse.jgit.api.BlameCommand.call(BlameCommand.java:214)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.12.4.4/10.12.4.4:38848 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1072) at hudson.FilePath.act(FilePath.java:1061) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcess(IssuesScanner.java:83) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:67) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:654) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:622) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:597) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:51) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:48) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)Caused:
[JIRA] (JENKINS-55273) recordIssues step fails silently when it can't get get version control information
Title: Message Title
Jonathan Rogers updated an issue
Jenkins / JENKINS-55273
recordIssues step fails silently when it can't get get version control information
Change By:
Jonathan Rogers
I am attempting to display errors and warnings from flake8 with the following step in a pipeline:{code:java}recordIssues enabledForFailure: true, ignoreFailedBuilds: false, tools: [flake8(pattern: 'flake8.txt')]{code} {{The step finds issues, then immediately fails, which fails the entire build. There was nothing relevant to the failure in the output from the step:}} ** {code:java} {code}{code:java} 00:03:17.360 [Flake8] Searching for all files in '/home/sscadmin/git/pippin' that match the pattern 'flake8.txt'00:03:17.361 [Flake8] -> found 1 file*00:03:17.361* [Flake8] Successfully parsed file /home/sscadmin/git/pippin/flake8.txt*00:03:17.361* [Flake8] -> found 73 issues (skipped 0 duplicates) > git rev-parse HEAD^{commit} # timeout=10{code} There was a traceback in the job console output:{code:java}org.eclipse.jgit.errors.MissingObjectException: Missing unknown 56520e2e8da7a76d073b60ba663faee3a18ee6f0 at org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:158) at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:227) at org.eclipse.jgit.blame.BlameGenerator.push(BlameGenerator.java:317) at org.eclipse.jgit.api.BlameCommand.call(BlameCommand.java:214)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.12.4.4/10.12.4.4:38848 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1072) at hudson.FilePath.act(FilePath.java:1061) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcess(IssuesScanner.java:83) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:67) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:654) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:622) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:597) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:51) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:48) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)Caused:
[JIRA] (JENKINS-55273) recordIssues step fails silently when it can't get get version control information
Title: Message Title
Jonathan Rogers updated an issue
Jenkins / JENKINS-55273
recordIssues step fails silently when it can't get get version control information
Change By:
Jonathan Rogers
I am attempting to display errors and warnings from flake8 with the following step in a pipeline: { { code:java} recordIssues enabledForFailure: true, ignoreFailedBuilds: false, tools: [flake8(pattern: 'flake8.txt')] {code } } {{The step finds issues, then immediately fails, which fails the entire build. There was nothing relevant to the failure in the output from the step:}}* *{code:java} 00:03:17.360 * [Flake8] Searching for all files in '/home/sscadmin/git/pippin' that match the pattern 'flake8.txt' * 00:03:17.361 * [Flake8] -> found 1 file*00:03:17.361* [Flake8] Successfully parsed file /home/sscadmin/git/pippin/flake8.txt*00:03:17.361* [Flake8] -> found 73 issues (skipped 0 duplicates) > git rev-parse HEAD^ \ {commit} # timeout=10 {code} There was a traceback in the job console output:{code:java}org.eclipse.jgit.errors.MissingObjectException: Missing unknown 56520e2e8da7a76d073b60ba663faee3a18ee6f0 at org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:158) at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:227) at org.eclipse.jgit.blame.BlameGenerator.push(BlameGenerator.java:317) at org.eclipse.jgit.api.BlameCommand.call(BlameCommand.java:214)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.12.4.4/10.12.4.4:38848 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1072) at hudson.FilePath.act(FilePath.java:1061) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcess(IssuesScanner.java:83) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:67) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:654) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:622) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:597) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:51) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:48) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)Caused:
[JIRA] (JENKINS-55273) recordIssues step fails silently when it can't get get version control information
Title: Message Title
Jonathan Rogers created an issue
Jenkins / JENKINS-55273
recordIssues step fails silently when it can't get get version control information
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2018-12-20 07:51
Environment:
Jenkins 2.150.1 Warnings Next Generation Plugin 1.0.0-beta9
Priority:
Minor
Reporter:
Jonathan Rogers
I am attempting to display errors and warnings from flake8 with the following step in a pipeline: recordIssues enabledForFailure: true, ignoreFailedBuilds: false, tools: [flake8(pattern: 'flake8.txt')] The step finds issues, then immediately fails, which fails the entire build. There was nothing relevant to the failure in the output from the step: 00:03:17.360 [Flake8] Searching for all files in '/home/sscadmin/git/pippin' that match the pattern 'flake8.txt'00:03:17.361 [Flake8] -> found 1 file*00:03:17.361* [Flake8] Successfully parsed file /home/sscadmin/git/pippin/flake8.txt*00:03:17.361* [Flake8] -> found 73 issues (skipped 0 duplicates) > git rev-parse HEAD^{commit} # timeout=10 There was a traceback in the job console output:
org.eclipse.jgit.errors.MissingObjectException: Missing unknown 56520e2e8da7a76d073b60ba663faee3a18ee6f0
at org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:158)
at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:227)
at org.eclipse.jgit.blame.BlameGenerator.push(BlameGenerator.java:317)
at org.eclipse.jgit.api.BlameCommand.call(BlameCommand.java:214)
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from
[JIRA] (JENKINS-55272) Bitbucket plugin not able to trigger the job
Title: Message Title
satyam karn created an issue
Jenkins / JENKINS-55272
Bitbucket plugin not able to trigger the job
Issue Type:
Bug
Assignee:
Unassigned
Components:
bitbucket-plugin
Created:
2018-12-20 07:49
Priority:
Blocker
Reporter:
satyam karn
Jenkins is not able to trigger the job . I could see that it receiving the webhook payload but could not able to trigger the job . Below are the logs generated . Considering candidate job Bitbucket_webhooktest Dec 20, 2018 8:03:32 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbe Considering to poke HAL_Driver » Bitbucket_webhooktest Dec 20, 2018 8:03:32 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbe Trying to match ssh://g...@bcds01.de.bosch.com:7999/ahal/cob_project_ahal_bmi2xy.git<-->https://bcds01.de.bosch.com/bitbucket/ahal/cob_project_ahal_bmi2xy Dec 20, 2018 8:03:32 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbe Bitbucket_webhooktest SCM doesnt match remote repo {1}
Add Comment
[JIRA] (JENKINS-42643) Conditional application of triggers in Declarative
Title: Message Title Igwe Kalu commented on JENKINS-42643 Re: Conditional application of triggers in Declarative These discussions are quite are useful and I can relate with many of the ideas/suggestions in my own use cases. Andrew Bayer, is there any plan to start progressing this issue soon? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55271) Jenkinsfile Active Choice Parameter
Title: Message Title
Georgi Hagi created an issue
Jenkins / JENKINS-55271
Jenkinsfile Active Choice Parameter
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-12-20 06:30
Environment:
Jenkins 2.107.3
Priority:
Critical
Reporter:
Georgi Hagi
How can i use this dsl script in Multibranch Pipeline jenkinsfile(declerative)? {{parameters { activeChoiceParam('States') { description('Select a state option') filterable() choiceType('SINGLE_SELECT') groovyScript { script('["Sao Paulo", "Rio de Janeiro", "Parana:selected", "Acre"]') fallbackScript('return ["ERROR"]') } } activeChoiceReactiveParam('Cities') { description('Active Choices Reactive parameter') filterable() choiceType('CHECKBOX') groovyScript { script(''' if (States.equals('Sao Paulo')) { return ['Barretos', 'Sao Paulo', 'Itu']; } else if (States.equals('Rio de Janeiro')) { return ['Rio de Janeiro', 'Mangaratiba'] } else if (States.equals('Parana')) { return ['Curitiba', 'Ponta Grossa'] } else if (States.equals('Acre')) { return ['Rio Branco', 'Acrelandia'] } else { return ['Unknown state'] } ''') fallbackScript('return ["Script error!"]') } referencedParameter('States') } }}} When i use this script in jenkinsfile i get this error: WorkflowScript: 23: Build parameters definitions cannot have blocks @ line 23, column 5. activeChoiceParam('States') { ^ WorkflowScript: 32: Build parameters definitions cannot have blocks @ line 32, column 9. activeChoiceReactiveParam('Cities') { ^ 2 errors {{at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at
[JIRA] (JENKINS-49789) NPE when attempting to parse exception
Title: Message Title
Roufique Hossain updated an issue
Jenkins / JENKINS-49789
NPE when attempting to parse exception
Change By:
Roufique Hossain
From a comment on the wiki: [ https://wiki.jenkins.io/display/JENKINS/Google+Play+Android+Publisher+Plugin?focusedCommentId=138450677#comment-138450677 ] {code:java}ERROR: Build step failed pass with exceptionjava.lang.NullPointerExceptionat org.jenkinsci.plugins.googleplayandroidpublisher.Util.getPublisherErrorMessage(Util.java:97)at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.publishApk(ApkPublisher.java:383)at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.perform(ApkPublisher.java:198)at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)at hudson.model.Build$BuildExecution.post2(Build.java:186)at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)at hudson.model.Run.execute(Run.java:1753)at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:405)Build step 'Upload Android APK to Google Play' marked build as failure{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins
Title: Message Title Danilo Castilho commented on JENKINS-29725 Re: Application starting issue websphere application server 8.5 after deployment Jenkins Greg Peters we're using the latest version of the plugin (1.6.1), and that checkbox is not visible (the start application checkbox) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55250) Upload external test result failed when using API key to login ALM14
Title: Message Title Roy Lu updated JENKINS-55250 Jenkins / JENKINS-55250 Upload external test result failed when using API key to login ALM14 Change By: Roy Lu Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55094) "commands" and "args" are being defaulted using Kubernetes plugin
Title: Message Title Mohammad Norouzi commented on JENKINS-55094 Re: "commands" and "args" are being defaulted using Kubernetes plugin Carlos Sanchez Yes we're using config-as-code plugin and the values are defined in a yaml file which then will be imported. If there is no command/args defined in the file, what you see in the UI is those default values. This causes all the builds that resume after Jenkins is up will wait forever because the containers' command/args are not correct and therefore they don't function properly Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55236) jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0
Title: Message Title harry king commented on JENKINS-55236 Re: jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0 Oh. Thanks a lot Runze. I didn't get such infomation from the doc. Whaterver, I can use this feature now, please kindly close the issue. Thanks again! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Dmitry Chernivetsky commented on JENKINS-41662 Re: Proceed button fails (investigate) i can reroduce this issue. jenkins version 2.150.1 blueocean plugin 1.9.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52736) Occasionally the plugin leaves orphaned, stopped VMs
Title: Message Title June Rhodes commented on JENKINS-52736 Re: Occasionally the plugin leaves orphaned, stopped VMs That's very weird - I would expect preempted instances on Google Cloud to be deleted, not stopped. Otherwise customers will continue to billed for storage after the VM is stopped. Certainly in the case where we use Kubernetes Engine with preemptible VMs, the VMs don't stick around in a stopped 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27457) deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)
Title: Message Title Greg Peters commented on JENKINS-27457 Re: deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E) Antonio Smoljo Did you resolve the issue you were having? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55270) JavaDoc for UpdateCenter.getPlugin() references hudson.util.VersionNumber but returns 404
Title: Message Title Phil Dudley created an issue Jenkins / JENKINS-55270 JavaDoc for UpdateCenter.getPlugin() references hudson.util.VersionNumber but returns 404 Issue Type: Bug Assignee: Max Spring Components: jenkow-plugin Created: 2018-12-19 22:52 Priority: Minor Reporter: Phil Dudley When looking at the JavaDoc for Jenkins' UpdateCetner https://javadoc.jenkins.io/hudson/model/UpdateCenter.html#getPlugin-java.lang.String-hudson.util.VersionNumber- getPlugin() is referencing the hudson.util.VersionNumber. However, it is not listed in the JavDocs, the CLI docs return a 404, and while its listed here: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/UpdateCenter.java#L35 Its not actually in the Jenkins code base: https://github.com/jenkinsci/jenkins/tree/master/core/src/main/java/hudson/util I found this when attempting to setup Jenkins using Groovy to go from zero-to-hero and it failed to run on a fresh install, but worked after I had initially setup by hand. #!groovy import jenkins.model.Jenkins import hudson.util.VersionNumber // Create a reference to the PluginManager Class. pm = Jenkins.instance.pluginManager // Create a reference to the UpdateCenter Class. uc = Jenkins.instance.updateCenter// Disable all the plugins on the
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Cyrille Le Clerc commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Understood. I am sorry but I have no clue of who could do this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55269) Provide a way to delete all used workspaces
Title: Message Title Ilya Lederman created an issue Jenkins / JENKINS-55269 Provide a way to delete all used workspaces Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2018-12-19 20:45 Priority: Minor Reporter: Ilya Lederman It would be great if there was an ability to clean all used workspaces at the end of the build. Currently, I use deleteDir as a post step, but some of my jobs have steps that run in parallel on separate nodes/workspaces. For that, I need to keep track of the stages that will use a separate workspace and I will have to add a post cleanup stage there as well. It would be great if we did not have to be very careful about each stages workspace and instead at the end of the build, delete all used workspaces. Add Comment
[JIRA] (JENKINS-51645) Add support for claims plugin in xUnit
Title: Message Title Mark Hermon commented on JENKINS-51645 Re: Add support for claims plugin in xUnit Kasia Gauza We don't have any high level dashboard for my company, Developers just check a couple of specific jobs per branch and claim there. We also use it for custom emails via Extended Email Plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52420) [JEP-200] Can't serialize class
Title: Message Title Lucas Oliveira commented on JENKINS-52420 Re: [JEP-200] Can't serialize class I'm also waiting for the fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55242) AzureVMCloud: createProvisionedAgent: Deployment failed with timeout
Title: Message Title Muhammad Faizan ul haq commented on JENKINS-55242 Re: AzureVMCloud: createProvisionedAgent: Deployment failed with timeout We found a cause. The subnet that we are using, is full. No IP is free but this is strange that I dont see any cause in logs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55249) Upstream and Downstream columns are not displaying properly
Title: Message Title Mark Berchem updated an issue Jenkins / JENKINS-55249 Upstream and Downstream columns are not displaying properly Change By: Mark Berchem When I upgraded from Jenkins 1.144 to 1.146 the Upstream and Downstream columns no longer displayed properly (see attached image). The page source shows '& amp; lt;' where I think a '<' should be (see attached source). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55249) Upstream and Downstream columns are not displaying properly
Title: Message Title Mark Berchem updated an issue Jenkins / JENKINS-55249 Upstream and Downstream columns are not displaying properly Change By: Mark Berchem When I upgraded from Jenkins 1.144 to 1.146 the Upstream and Downstream columns no longer displayed properly (see attached image) . The page source shows '& amp; lt;' where I think a '<' should be (see attached source). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55249) Upstream and Downstream columns are not displaying properly
Title: Message Title Mark Berchem updated an issue Jenkins / JENKINS-55249 Upstream and Downstream columns are not displaying properly Change By: Mark Berchem When I upgraded from Jenkins 1.144 to 1.146 the Upstream and Downstream columns no longer displayed properly. The page source shows ' \ ' where I think a '<' should be (see attached source). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55249) Upstream and Downstream columns are not displaying properly
Title: Message Title Mark Berchem updated an issue Jenkins / JENKINS-55249 Upstream and Downstream columns are not displaying properly Change By: Mark Berchem When I upgraded from Jenkins 1.144 to 1.146 the Upstream and Downstream columns no longer displayed properly. The page source shows ' \ & amp; lt;' where I think a '<' should be (see attached source). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55249) Upstream and Downstream columns are not displaying properly
Title: Message Title Mark Berchem updated an issue Jenkins / JENKINS-55249 Upstream and Downstream columns are not displaying properly Change By: Mark Berchem When I upgraded from Jenkins 1.144 to 1.146 the Upstream and Downstream columns no longer displayed properly. The page source shows ' & & lt; ' where I think a '<' should be (see attached source). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55249) Upstream and Downstream columns are not displaying properly
Title: Message Title Mark Berchem updated an issue Jenkins / JENKINS-55249 Upstream and Downstream columns are not displaying properly Change By: Mark Berchem When I upgraded from Jenkins 1.144 to 1.146 the Upstream and Downstream columns no longer displayed properly. The page source shows & & lt; where I think a '<' should be (see attached source). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55267) A failed Gradle task does not log any of the error details
Title: Message Title
Jon McKenzie edited a comment on JENKINS-55267
Re: A failed Gradle task does not log any of the error details
Here's a snippet from the console log. The gradle build is run from within a Docker container using the Docker pipeline plugin. {code:java}Download https:///artifactory/libs-release/com/esotericsoftware/minlog/1.3.0/minlog-1.3.0.jarDownload https:///artifactory/libs-release/org/yaml/snakeyaml/1.23/snakeyaml-1.23.jarDownload https:///artifactory/libs-release/org/apache/logging/log4j/log4j-api/2.11.1/log4j-api-2.11.1.jarDownload https:///artifactory/libs-release/io/netty/netty-buffer/4.1.31.Final/netty-buffer-4.1.31.Final.jarDownload https:///artifactory/libs-release/software/amazon/awssdk/protocol-core/2.1.0/protocol-core-2.1.0.jar[Pipeline] }[Pipeline] // ansiColor[Pipeline] }[Pipeline] // withEnv[Pipeline] }$ docker stop --time=1 bc401b3124b5997f5c8a254b525737b1629050fb9058ba2e68741a5d4ee14a2e[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinehudson.model.Run$RunnerAbortedException at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$Execution.exe(ArtifactoryGradleBuild.java:193) at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$Execution.run(ArtifactoryGradleBuild.java:119) at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$Execution.run(ArtifactoryGradleBuild.java:80) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Finished: FAILURE{code} When we change the job to publish using Gradle directly instead of the plugin, we get an error from Gradle itself telling us what the problem is, namely that it's looking for a JAR file that doesn't exist:{code:java}> Task :bootJar> Task :jar SKIPPED> Task :assemble> Task :check> Task :build> Task :uploadArchives FAILEDFAILURE: Build failed with an exception.* What went wrong:Execution failed for task ':uploadArchives'.> Could not publish configuration 'archives' > Cannot publish artifact 'sanitized.jar' (/path/to/sanitized.jar) as it does not exist.* Try:Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.* Get more help at https://help.gradle.orgBUILD FAILED in 2m 37s5 actionable tasks: 4 executed, 1 up-to-date{code}
[JIRA] (JENKINS-55267) A failed Gradle task does not log any of the error details
Title: Message Title Jon McKenzie commented on JENKINS-55267 Re: A failed Gradle task does not log any of the error details Here's a snippet from the console log. The gradle build is run from within a Docker container using the Docker pipeline plugin. Download https:///artifactory/libs-release/com/esotericsoftware/minlog/1.3.0/minlog-1.3.0.jar Download https:///artifactory/libs-release/org/yaml/snakeyaml/1.23/snakeyaml-1.23.jar Download https:///artifactory/libs-release/org/apache/logging/log4j/log4j-api/2.11.1/log4j-api-2.11.1.jar Download https:///artifactory/libs-release/io/netty/netty-buffer/4.1.31.Final/netty-buffer-4.1.31.Final.jar Download https:///artifactory/libs-release/software/amazon/awssdk/protocol-core/2.1.0/protocol-core-2.1.0.jar [Pipeline] } [Pipeline] // ansiColor [Pipeline] } [Pipeline] // withEnv [Pipeline] } $ docker stop --time=1 bc401b3124b5997f5c8a254b525737b1629050fb9058ba2e68741a5d4ee14a2e [Pipeline] // withDockerContainer [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline hudson.model.Run$RunnerAbortedException at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$Execution.exe(ArtifactoryGradleBuild.java:193) at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$Execution.run(ArtifactoryGradleBuild.java:119) at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$Execution.run(ArtifactoryGradleBuild.java:80) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE Add Comment
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Stuart Rowe commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Georg Henzler, I currently use FlowInterruptedException to achieve the same thing. The added benefit is this exception has a Result field. I've submitted pipeline-graph-analysis-plugin#PR22 to use the FlowInterruptedException's Result to determine the Stage status rather than using FAILURE (pipeline-graph-analysis-plugin 1.7) or ABORTED (pipeline-graph-analysis-plugin 1.9). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title D Pasto commented on JENKINS-55257 Re: Timestamper break builds on Windows agents FWIW - I'm running into what looks like the same issue. I have a declarative pipeline and couldn't understand why it's only my branch blowing up this way, and I see it with the default checkout, an explicit 'checkout scm', or 'git ...'. I'm running timestamper 1.8.10 and java 1.8.0_191-b12 64bit. Commenting out the timestamps option got me past this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55268) Multibranch pipelines cannot have different "Named Branch" configurations when created by the organization plugin
Title: Message Title Maxwell Flanders created an issue Jenkins / JENKINS-55268 Multibranch pipelines cannot have different "Named Branch" configurations when created by the organization plugin Issue Type: Bug Assignee: Unassigned Components: basic-branch-build-strategies-plugin, branch-api-plugin Created: 2018-12-19 16:56 Labels: jenkins pipeline organization multi-branch git Priority: Minor Reporter: Maxwell Flanders I am utilizing the Jenkins Organization Job to scan and track Jenkinsfiles across a number of different github repositories, which trigger builds using a github webhook configuration that notifies jenkins. Our repositories Jenkinsfiles are managed by the developers. Some of them want their pipeline to build on pushes to only the "master" branch. Others want them to build on pushes to the "develop", "staging", and "master" branches. However, the "Named Branch" build strategy setting is only configurable at the Organization job level, and is passed down to all jobs created by it. This prevent developers from configuring their jobs independently.
[JIRA] (JENKINS-18088) Build flow execute on slave but write file on master
Title: Message Title Tri Nguyen commented on JENKINS-18088 Re: Build flow execute on slave but write file on master What is a way to get around this for InetAddress.getLocalHost()? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55267) A failed Gradle task does not log any of the error details
Title: Message Title Jon McKenzie updated an issue Jenkins / JENKINS-55267 A failed Gradle task does not log any of the error details Change By: Jon McKenzie If When run via Jenkins pipeline, if a Gradle task fails or Gradle exits with a non-zero exit code, this line swallows the error message:[https://github.com/jenkinsci/artifactory-plugin/blob/master/src/main/java/org/jfrog/hudson/pipeline/steps/ArtifactoryGradleBuild.java#L184] This makes it extremely difficult to troubleshoot failed builds, especially as you start to mix in other things like the Docker plugin, etc. Reproducing the build is not trivial. The full error details should be displayed in the Jenkins console log. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55267) A failed Gradle task does not log any of the error details
Title: Message Title Jon McKenzie created an issue Jenkins / JENKINS-55267 A failed Gradle task does not log any of the error details Issue Type: New Feature Assignee: Eyal Ben Moshe Components: artifactory-plugin Created: 2018-12-19 16:30 Labels: artifactory-plugin Priority: Major Reporter: Jon McKenzie If a Gradle task fails or Gradle exits with a non-zero exit code, this line swallows the error message: https://github.com/jenkinsci/artifactory-plugin/blob/master/src/main/java/org/jfrog/hudson/pipeline/steps/ArtifactoryGradleBuild.java#L184 This makes it extremely difficult to troubleshoot failed builds, especially as you start to mix in other things like the Docker plugin, etc. Reproducing the build is not trivial. The full error details should be displayed in the Jenkins console log. Add Comment
[JIRA] (JENKINS-55267) A failed Gradle task does not log any of the error details
Title: Message Title Jon McKenzie updated an issue Jenkins / JENKINS-55267 A failed Gradle task does not log any of the error details Change By: Jon McKenzie Issue Type: New Feature Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55266) Add possibility to pass in commands for workspace cleanup
Title: Message Title
Timo Sand created an issue
Jenkins / JENKINS-55266
Add possibility to pass in commands for workspace cleanup
Issue Type:
New Feature
Assignee:
Oliver Gondža
Components:
ws-cleanup-plugin
Created:
2018-12-19 16:28
Priority:
Minor
Reporter:
Timo Sand
We run everything with `docker-compose` in our Jobs and we have to add a `docker-compose down` to the end of each stage, which takes unnecessary time from the jobs completion. It would be great if we could add a closure to `cleanWs` in order to run some commands deferredly at the end of the build
cleanWs() {
docker-compose -f docker-compose.ci.yml down --volumes --remove-orphans
}
Add Comment
[JIRA] (JENKINS-55248) workspace mixup when 2 jobs running on 2 diff nodes at the same time
Title: Message Title Karl Wirth commented on JENKINS-55248 Re: workspace mixup when 2 jobs running on 2 diff nodes at the same time Hi Mei Liu. I would like to see some more details about your setup so have sent you a request for more information via email. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55265) Unsuccessful post stage fires even on Success status
Title: Message Title Timo Sand created an issue Jenkins / JENKINS-55265 Unsuccessful post stage fires even on Success status Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-12-19 16:23 Priority: Minor Reporter: Timo Sand I tried adding an `unsuccessful` block to my post stage today, but instead of working like it should it first ran everything from the `success` block and then from the `unsuccessful` block Add Comment This message was sent by
[JIRA] (JENKINS-55248) workspace mixup when 2 jobs running on 2 diff nodes at the same time
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-55248 workspace mixup when 2 jobs running on 2 diff nodes at the same time Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline
Title: Message Title Warren Humphreys commented on JENKINS-48897 Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline Any progress on this? I'm just attempting to switch from standard git to using the bitbucket-branch-source plugin so I can build PRs and I'm facing this issue too. Username not being passed? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52590) p4-plugin sets client root to null
Title: Message Title Paul Allen updated JENKINS-52590 Ready for release. Jenkins / JENKINS-52590 p4-plugin sets client root to null Change By: Paul Allen Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52590) p4-plugin sets client root to null
Title: Message Title Paul Allen updated JENKINS-52590 Jenkins / JENKINS-52590 p4-plugin sets client root to null Change By: Paul Allen Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52590) p4-plugin sets client root to null
Title: Message Title Paul Allen started work on JENKINS-52590 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55264) Threshold Number of tests not working
Title: Message Title Maxime Lavocat created an issue Jenkins / JENKINS-55264 Threshold Number of tests not working Issue Type: Bug Assignee: Nalin Makar Components: testng-plugin Created: 2018-12-19 15:40 Environment: Windows Server 2012 64bit, Firefox 64, Jenkins 2.150.1, Testng plugin 1.15 Priority: Major Reporter: Maxime Lavocat When selecting "Number of tests" mode for "Threshold to mark build Failed" and saving, this parameter is not saved. I can check that in the config.xml of the job : 2 Even if I modify manually this parameter by puting "1" in this file, the plugin still uses percent mode threshold. Add Comment
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Antonio Muñiz commented on JENKINS-55257 Re: Timestamper break builds on Windows agents It's JRE-8u151 to launch the agent and then the build uses a regular tool installer for 1.8.0_192. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55255) FlowInterruptedException always marks stages as Aborted despite Result
Title: Message Title Stuart Rowe updated an issue Jenkins / JENKINS-55255 FlowInterruptedException always marks stages as Aborted despite Result Change By: Stuart Rowe This issue is a knock-on from [ https://github.com/jenkinsci/pipeline-graph-analysis-plugin/commit/20e4807f35be96ea07a9c66d4238edf75705e4b5 ] . In our scripted pipelines we throw FlowInterruptedExceptions to set the Stage status. After upgrading from 1.7 to 1.9, stages in this context are now being marked Aborted. Previously the stages were marked as Failure. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55263) Jira plugin. Show only released version parameters
Title: Message Title Foxy BOA created an issue Jenkins / JENKINS-55263 Jira plugin. Show only released version parameters Issue Type: Improvement Assignee: Unassigned Components: jira-plugin Created: 2018-12-19 15:28 Priority: Minor Reporter: Foxy BOA It would be awesome if "Referencing JIRA Release version " could show only released versions (right now it can show unreleased or unreleased AND released). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54628) Poll error when no view in Manual workspace for stream
Title: Message Title Paul Allen updated JENKINS-54628 Ready for release. Jenkins / JENKINS-54628 Poll error when no view in Manual workspace for stream Change By: Paul Allen Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47992) Instance capping is based on AMI ID
Title: Message Title Yves Le Maout commented on JENKINS-47992 Re: Instance capping is based on AMI ID Hi guys, Is anyone looking into this issue? Let me know if you need any additional information about it. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55253) Client MODTIME is not set using source: depotSource(spec)
Title: Message Title Alisdair Robertson commented on JENKINS-55253 Re: Client MODTIME is not set using source: depotSource(spec) Seems like this report may have been a bit premature - I'm seeing the expected behaviour after a few builds have populated the workspaces of most of our nodes. Does the workspace MODTIME option not have influence over the -m option for p4 reconcile? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55239) FilesystemSCM is not annotated properly in JFR
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-55239 FilesystemSCM is not annotated properly in JFR Given org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class io.jenkins.jenkinsfile.runner.FileSystemSCM at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames(ClassDescriptor.java:265) at org.jenkinsci.plugins.structs.describable.DescribableModel.(DescribableModel.java:144) at org.jenkinsci.plugins.structs.describable.DescribableModel.of(DescribableModel.java:114) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:294) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeMapAndRecordMutation(ArgumentsActionImpl.java:386) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.(ArgumentsActionImpl.java:74) I think this could also be treated as a request to turn down the logging in workflow-cps. In particular ArgumentsActionImpl.sanitizeObjectAndRecordMutation should probably be catching NoStaplerConstructorException and recording this as NotStoredReason.UNSERIALIZABLE. Change By: Jesse Glick Component/s: workflow-cps-plugin Add Comment
[JIRA] (JENKINS-47776) sonarqube integration doesn't authenticate
Title: Message Title Christoph Forster commented on JENKINS-47776 Re: sonarqube integration doesn't authenticate Jonas Lindström: yes Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55262) Missing content-type on serverStatuses REST API
Title: Message Title
Florian Ramillien updated an issue
Jenkins / JENKINS-55262
Missing content-type on serverStatuses REST API
Change By:
Florian Ramillien
Jelly template serving /gerrit-trigger/serverStatuses REST API doesn't add a Content-Type header to HTTP Response.In almost all cases this is harmless (JSON result is accepted) but on some combination of Browser / HTTP Proxy + Gzip compression this result to corrupted JSON response.Actual Response response headers:{code:java}HTTP/1.1 200 OKDate: Wed, 19 Dec 2018 13:52:44 GMTX-Content-Type-Options: nosniffContent-Encoding: gzipContent-Length: 143Server: Jetty(9.4.z-SNAPSHOT){code}Expected response headers : {code:java}HTTP/1.1 200 OKDate: Wed, 19 Dec 2018 14:16:50 GMTX-Content-Type-Options: nosniffContent-Encoding: gzipContent-Type: application/jsonContent-Length: 145Server: Jetty(9.4.z-SNAPSHOT{code}Adding Jelly:stapler 'contentType' tag fix this./src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritManagement/serverStatuses.jelly{code:java} xmlns:t="/lib/hudson" xmlns:f="/lib/form" xmlns:i="jelly:fmt">${it.serverStatuses}{code}
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-54628) Poll error when no view in Manual workspace for stream
Title: Message Title Charusheela Bopardikar started work on JENKINS-54628 Change By: Charusheela Bopardikar Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54628) Poll error when no view in Manual workspace for stream
Title: Message Title Charusheela Bopardikar updated JENKINS-54628 Jenkins / JENKINS-54628 Poll error when no view in Manual workspace for stream Change By: Charusheela Bopardikar Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55262) Missing content-type on serverStatuses REST API
Title: Message Title Florian Ramillien commented on JENKINS-55262 Re: Missing content-type on serverStatuses REST API In our case, missing content-type header cause problem with: HTTP response compressed in gzip Proxy: traefik (add wrong content-type: application/x-gzip) Browser: Firefox (wrap raw gzip in base64) JS client receive base64 instead of expected JSON leading to "Data error." in servers list. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55082) No @DataBoundConstructor on io.jenkins.jenkinsfile.runner.FileSystemSCM
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-55082 No @DataBoundConstructor on io.jenkins.jenkinsfile.runner.FileSystemSCM Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55262) Missing content-type on serverStatuses REST API
Title: Message Title Florian Ramillien created an issue Jenkins / JENKINS-55262 Missing content-type on serverStatuses REST API Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2018-12-19 14:22 Environment: Gerrit-trigger-plugin 2.27.7 Priority: Trivial Reporter: Florian Ramillien Jelly template serving /gerrit-trigger/serverStatuses REST API doesn't add a Content-Type header to HTTP Response. In almost all cases this is harmless (JSON result is accepted) but on some combination of Browser / HTTP Proxy + Gzip compression this result to corrupted JSON response. Actual Response headers: HTTP/1.1 200 OK Date: Wed, 19 Dec 2018 13:52:44 GMT X-Content-Type-Options: nosniff Content-Encoding: gzip Content-Length: 143 Server: Jetty(9.4.z-SNAPSHOT) Expected response: HTTP/1.1 200 OK Date: Wed, 19 Dec 2018 14:16:50 GMT X-Content-Type-Options: nosniff Content-Encoding: gzip Content-Type: application/json Content-Length: 145 Server: Jetty(9.4.z-SNAPSHOT Adding Jelly:stapler 'contentType' tag fix this. /src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritManagement/serverStatuses.jelly
[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Oleg Nenashev commented on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free I am thinking about a separate issue, because it looks reasonable to have OpenJDK Installer as a separate plugin (and to rename the existing one to the Oracle one) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48661) Execute stage only after initial pipeline execution
Title: Message Title Andrew Bayer commented on JENKINS-48661 Re: Execute stage only after initial pipeline execution Actually, now that I think about it, the added-in-1.3.2 isRestartedRun() when condition does this exactly. I probably should have marked this as a dupe earlier. =) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48661) Execute stage only after initial pipeline execution
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-48661 Execute stage only after initial pipeline execution Change By: Andrew Bayer Assignee: Jose Blas Camacho Taboada Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48661) Execute stage only after initial pipeline execution
Title: Message Title Andrew Bayer updated JENKINS-48661 Jenkins / JENKINS-48661 Execute stage only after initial pipeline execution Change By: Andrew Bayer Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55259) Copyartifact plugin requires Matrix Project plugin
Title: Message Title ikedam assigned an issue to Unassigned Sounds good. But I don’t plan to work for that for now. Contributions are welcome. Jenkins / JENKINS-55259 Copyartifact plugin requires Matrix Project plugin Change By: ikedam Issue Type: Bug Improvement Assignee: ikedam Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55094) "commands" and "args" are being defaulted using Kubernetes plugin
Title: Message Title Carlos Sanchez commented on JENKINS-55094 Re: "commands" and "args" are being defaulted using Kubernetes plugin This works fine from the UI, are you using config-as-code plugin ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55261) Errors visible in UI are hidden if you use job-dsl
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-55261
Errors visible in UI are hidden if you use job-dsl
Change By:
Jakub Bochenski
If you try to enter a cron _expression_ in the Web UI like {{H/2 * * * * *}} you will get an error. If you use job-dsl construct like { code} { { scm 'H/2 * * * *' } {code } } the job will be created without any issues. The incorrect values will be there in the config.xml, but if you open the Web UI you will not see the trigger at all. There is nothing to be seen in jenkins log. This won't be flagged in the Manage Old Data monitor either.Best solution would be too tighten validation for the executed job-dsl to not allow such values. If that's not possible it would be nice to at least be able to see a notification about the error somewhere.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Baptiste Mathus commented on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free Yeah, TBH I do not really care. Given the title here and the discussion, using this report to actually fix would also make sense. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55261) Errors visible in UI are hidden if you use job-dsl
Title: Message Title
Jakub Bochenski created an issue
Jenkins / JENKINS-55261
Errors visible in UI are hidden if you use job-dsl
Issue Type:
Improvement
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2018-12-19 13:57
Priority:
Major
Reporter:
Jakub Bochenski
If you try to enter a cron _expression_ in the Web UI like H/2 * * * * * you will get an error. If you use job-dsl construct like {{ { scm 'H/2 * * * *' } }} the job will be created without any issues. The incorrect values will be there in the config.xml, but if you open the Web UI you will not see the trigger at all. There is nothing to be seen in jenkins log. This won't be flagged in the Manage Old Data monitor either. Best solution would be too tighten validation for the executed job-dsl to not allow such values. If that's not possible it would be nice to at least be able to see a notification about the error somewhere.
Add Comment
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Andrew Widdersheim commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub I wonder if it has anything to do with the cache just being recently turned on again by default here: https://github.com/jenkinsci/github-branch-source-plugin/commit/1b3a370d78a4f8b431a55bc79ee795f1d8cece88 The time when people started reporting this issue and when that changed happened in early October seem to line up. https://wiki.jenkins.io/display/JENKINS/GitHub+Branch+Source+Plugin The cache can be disabled by setting -Dorg.jenkinsci.plugins.github_branch_source.GitHubSCMSource.cacheSize=0. My guess is that will serve as a decent work around seeing as the cache wasn't on prior and shouldn't have any adverse affects AFAIK. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55260) withRegistry() does not supports AWS - ECR login in region eu-north-1
Title: Message Title
Deepanraj S created an issue
Jenkins / JENKINS-55260
withRegistry() does not supports AWS - ECR login in region eu-north-1
Issue Type:
New Feature
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2018-12-19 13:35
Labels:
pipeline plugin
Priority:
Blocker
Reporter:
Deepanraj S
Amazon web services(AWS) introduced a new EU region Stockholm(eu-north-1) and we you want to push the docker image into an ECR repository which was created in that particular region, the docker.withRegistry() throws following error,
ERROR: Could not find credentials matching ecr:eu-north-1:dev-aws-keys
Code snippet:
docker.withRegistry('https://1234567890.dkr.ecr.us-east-1.amazonaws.com', 'ecr:eu-north-1:demo-ecr-credentials') { docker.image('demo').push('latest') }
Region Id: eu-north-1 PlugIn: Docker Pipeline Plugin Does the docker pipeline plugin have support for the region eu-north-1? Could someone tell what is wrong here?
[JIRA] (JENKINS-55260) withRegistry() does not supports AWS - ECR login in region eu-north-1
Title: Message Title
Deepanraj S updated an issue
Jenkins / JENKINS-55260
withRegistry() does not supports AWS - ECR login in region eu-north-1
Change By:
Deepanraj S
Amazon web services(AWS) introduced a new *EU* region *Stockholm(eu-north-1)* and we you want to push the docker image into an *ECR* repository which was created in that particular region, the *docker.withRegistry()* throws following error, {code:java}ERROR: Could not find credentials matching ecr:eu-north-1:dev-aws-keys{code} *Code snippet*: {code:java} docker.withRegistry('https://1234567890.dkr.ecr.us-east-1.amazonaws.com', 'ecr:eu-north-1:demo-ecr-credentials') { docker.image('demo').push('latest') }{code} *Region Id*: eu-north-1*PlugIn*: Docker Pipeline PluginDoes the *docker pipeline plugin* have support for the region eu-north-1?Could someone tell what is wrong here?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55257) Timestamper break builds on Windows agents
Title: Message Title Jesse Glick commented on JENKINS-55257 Re: Timestamper break builds on Windows agents Likely a configuration issue rather than a Jenkins bug per se. Channel.executor is public and should be in the same JAR file. What version of Java is the agent running? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55221) Warnings NG plugin can't resolve absolute paths with gcc4
Title: Message Title David Aldrich commented on JENKINS-55221 Re: Warnings NG plugin can't resolve absolute paths with gcc4 Thanks for the link and for your help with this issue. Hopefully it has helped you as well as me. I will watch the new issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55221) Warnings NG plugin can't resolve absolute paths with gcc4
Title: Message Title Ulli Hafner commented on JENKINS-55221 Re: Warnings NG plugin can't resolve absolute paths with gcc4 Since the problem is unrelated to this issue I created a followup issue: JENKINS-55258. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47776) sonarqube integration doesn't authenticate
Title: Message Title Jonas Lindström commented on JENKINS-47776 Re: sonarqube integration doesn't authenticate Christoph Forster Are you using Jenkins Pipeline? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55259) Copyartifact plugin requires Matrix Project plugin
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-55259 Copyartifact plugin requires Matrix Project plugin Change By: Jakub Bochenski Component/s: copyartifact-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55259) Copyartifact plugin requires Matrix Project plugin
Title: Message Title Jakub Bochenski assigned an issue to ikedam Jenkins / JENKINS-55259 Copyartifact plugin requires Matrix Project plugin Change By: Jakub Bochenski Assignee: ikedam Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55259) Copyartifact plugin requires Matrix Project plugin
Title: Message Title Jakub Bochenski assigned an issue to Unassigned Jenkins / JENKINS-55259 Copyartifact plugin requires Matrix Project plugin Change By: Jakub Bochenski Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55259) Copyartifact plugin requires Matrix Project plugin
Title: Message Title Jakub Bochenski created an issue Jenkins / JENKINS-55259 Copyartifact plugin requires Matrix Project plugin Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-12-19 12:56 Priority: Minor Reporter: Jakub Bochenski This makes no sense to me. Shouldn't it be an optional dependency at best? AFAIK it's best practice to minimize the amount of plugins installed. We have no use for the matrix project type, but we are forced to install it because of it. Add Comment
[JIRA] (JENKINS-55258) Support scanning of console log with parallel steps
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-55258 Support scanning of console log with parallel steps Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2018-12-19 12:55 Priority: Major Reporter: Ulli Hafner If a pipeline contains parallel stages, then the console log will contain an unordered mix of stdout of all parallel stages. This makes it impossible to decided which log message is from which parallel stage. Especially if the step is using make then the log will contain the information messages about the current directory in any order: so file names will be not resolved because of assigning the wrong path. Workaround so far: cat the console log of each step into a file and parse the file instead. Add Comment
[JIRA] (JENKINS-22337) Support highlighting of non Java files
Title: Message Title Ulli Hafner stopped work on JENKINS-22337 Change By: Ulli Hafner Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51267) Detection of path names does not work
Title: Message Title Ulli Hafner updated JENKINS-51267 Jenkins / JENKINS-51267 Detection of path names does not work Change By: Ulli Hafner Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-1528) Provide generic way to upload warnings descriptions
Title: Message Title Ulli Hafner updated JENKINS-1528 Jenkins / JENKINS-1528 Provide generic way to upload warnings descriptions Change By: Ulli Hafner Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35255) Show all warnings in source code visualization
Title: Message Title Ulli Hafner stopped work on JENKINS-35255 Change By: Ulli Hafner Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47776) sonarqube integration doesn't authenticate
Title: Message Title Christoph Forster edited a comment on JENKINS-47776 Re: sonarqube integration doesn't authenticate I managed it to send the Authentication using a "Jenkins Global Environment Variable" named "SONAR_AUTH_TOKEN".Also it is important (using SonarQube 7.4 and InfluxDB Plugin 1.20.1) to set an Environment Variable "SONAR_HOST_URL". Nevertheless I receive a JSonException now, but I don't receive JSon Content but the loading page of SonarQube this is another Problem ... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55031) Deactivate undesired Generators
Title: Message Title Christoph Forster updated an issue Jenkins / JENKINS-55031 Deactivate undesired Generators Change By: Christoph Forster Summary: Deactivate undesired Genrators Generators Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55221) Warnings NG plugin can't resolve absolute paths with gcc4
Title: Message Title Ulli Hafner commented on JENKINS-55221 Re: Warnings NG plugin can't resolve absolute paths with gcc4 Seems that you did not see the link above https://unix.stackexchange.com/questions/67652/copy-stdout-and-stderr-to-a-log-file-and-leave-them-on-the-console-within-the-sc/383271#383271 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Evaristo Gutierrez updated JENKINS-54375 Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Evaristo Gutierrez Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Evaristo Gutierrez commented on JENKINS-54375 Re: Setup a release flow for Jenkinsfile Runner Reproduction steps: https://github.com/oleg-nenashev/ci.jenkins.io-runner/pull/20 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Evaristo Gutierrez updated JENKINS-54375 Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Evaristo Gutierrez Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48874) Markdown build badge does not show for a job with spaces in it
Title: Message Title Thomas Döring started work on JENKINS-48874 Change By: Thomas Döring Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42452) build badge icon unprotected URL escaping incorrectly
Title: Message Title Thomas Döring started work on JENKINS-42452 Change By: Thomas Döring Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33953) embeddable-build-status images are returned as 404 non-jenkins admins
Title: Message Title Thomas Döring started work on JENKINS-33953 Change By: Thomas Döring Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50368) Allow status of last finished build
Title: Message Title Thomas Döring updated JENKINS-50368 With v2.0 you can select builds by states like last, lastCompleted, lastFailed and so on. See README.md Jenkins / JENKINS-50368 Allow status of last finished build Change By: Thomas Döring Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19319) Distinguish between Aborted and Failed in the status icon
Title: Message Title Thomas Döring updated an issue Jenkins / JENKINS-19319 Distinguish between Aborted and Failed in the status icon Change By: Thomas Döring Labels: v2.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19319) Distinguish between Aborted and Failed in the status icon
Title: Message Title Thomas Döring updated JENKINS-19319 Jenkins / JENKINS-19319 Distinguish between Aborted and Failed in the status icon Change By: Thomas Döring Status: Open Fixed but Unreleased Assignee: Kohsuke Kawaguchi Thomas Döring Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52736) Occasionally the plugin leaves orphaned, stopped VMs
Title: Message Title James Robson commented on JENKINS-52736 Re: Occasionally the plugin leaves orphaned, stopped VMs I'm seeing this as well, I believe it is caused by pre-emptible instances actually getting pre-empted. I didn't check every instance that gets into this state but all the ones I did look at had a message about getting pre-empted in the stackdriver logs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21951) Support running status with correct background in the embeddable-build-status plugin.
Title: Message Title Thomas Döring updated JENKINS-21951 Jenkins / JENKINS-21951 Support running status with correct background in the embeddable-build-status plugin. Change By: Thomas Döring Status: Open Fixed but Unreleased Assignee: Kohsuke Kawaguchi Thomas Döring Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24089) Please add embeddable images for last build date
Title: Message Title
Thomas Döring edited a comment on JENKINS-24089
Re: Please add embeddable images for last build date
With v2.0 you will be able to configure the subject and status of the badge using query parameters that support variables.For example: 1. {{?subject=${duration}}} or 2. {{?subject=${runningTime}}}1. will show the actual build duration2. will show how "old" is the build See [README.md|https://github.com/jenkinsci/embeddable-build-status-plugin#subject-and-status]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21951) Support running status with correct background in the embeddable-build-status plugin.
Title: Message Title Thomas Döring updated an issue Jenkins / JENKINS-21951 Support running status with correct background in the embeddable-build-status plugin. Change By: Thomas Döring Labels: v2.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
