[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Naresh Rayapati edited a comment on JENKINS-56304 Re: jiraAddComment terminates the step prematurely I doubt it is either _@NonCPS_ annotation or the _msg.findAll_, cause not all the steps can be invoked in @NonCPS method and also not all the groovy syntax supported in Jenkins pipeline especially those loops and methods on collections. Can you try: * Just replace jiraAddComment with another echo, if it went through the loop * Try removing the @NonCPS annotation. * or just try couple of jiraAddComment steps in sequence outside the loop 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-56304) jiraAddComment terminates the step prematurely
Title: Message Title Naresh Rayapati commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely I doubt it is either @NonCPS annotation or the msg.findAll, cause not all the steps can be invoked in @NonCPS method and also not all the groovy syntax supported in Jenkins pipeline especially those loops and methods on collections. Can you try: Just replace jiraAddComment with another echo, if it went through the loop Try removing the @NonCPS annotation. 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-56262) Upload external test result has issue with ALM15p3 with client type restriction on
Title: Message Title Roy Lu closed an issue as Not A Defect Jenkins / JENKINS-56262 Upload external test result has issue with ALM15p3 with client type restriction on Change By: Roy Lu Status: Open Closed Resolution: Not A Defect 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-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett At the end of my pipeline, I am iterating the changeSets and the commits therein looking for strings that match Jira tickets, in order to update all Jira's with code present in a build. In theory, this could result in multiple Jiras needing to be updated, so this is done in a loop, potentially making multiple calls to jiraAddComment(..). However, the entire step stops (seems to return success) once the first jiraAddComment is completed. See attached source and output. Following call to jiraAddComment(..), the subsequent echo should fire indicating that execution flow has continued. The first jiraAddComment appears in the log (and the comment appears in Jira). However, no subsequent echos in the log. No subsequent call to jiraAddComment in the log, and no subsequent comments in Jira. It is as-if execution stops at the first call to jiraAddComment 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-56305) Need some help with init scripts on this plugin
Title: Message Title
Naresh Rayapati updated an issue
Jenkins / JENKINS-56305
Need some help with init scripts on this plugin
Change By:
Naresh Rayapati
I am trying to create a groovy init script to save multiple maven config files and custom config files within a single script, for some reasons it is honoring either one of them. Looks like I am missing something. Appreciate if someone can help me look into this file. {code}import org.jenkinsci.plugins.configfiles.maven.MavenSettingsConfigimport org.jenkinsci.plugins.configfiles.custom.CustomConfigimport org.jenkinsci.plugins.configfiles.maven.security.ServerCredentialMapping// Maven config files.def mavenProvider = instance.getExtensionList('org.jenkinsci.plugins.configfiles.maven.MavenSettingsConfig$MavenSettingsConfigProvider')[0]config?.maven?.each { key, config ->println("Adding maven settings with key: ${key}")def serverCreds = new ArrayList()config.servers.each { server ->def serverCredentialMapping = new ServerCredentialMapping(server.serverId, server.credentialsId)serverCreds.add(serverCredentialMapping)}def mavenConfig = new MavenSettingsConfig(config.id, config.name, config.comment, config.content, Boolean.parseBoolean(config.replaceAll), serverCreds)mavenProvider.save(mavenConfig)}// Custom config files.def customProvider = instance.getExtensionList('org.jenkinsci.plugins.configfiles.custom.CustomConfig$CustomConfigProvider')[0]config?.custom?.each { key, config ->println("Adding custom file with key: ${key}")def customConfig = new CustomConfig(config.id, config.name, config.comment, config.content)customProvider.save(customConfig)}{code}I got to remove one of these two like either custom config files section or the maven config files section to get this work, I have also tried moving this one of the sections to different files but no luck.
Add Comment
[JIRA] (JENKINS-56305) Need some help with init scripts on this plugin
Title: Message Title
Naresh Rayapati updated an issue
Jenkins / JENKINS-56305
Need some help with init scripts on this plugin
Change By:
Naresh Rayapati
I am trying to create a groovy init script to save multiple maven config files and custom config files within a single script, for some reasons it is honoring either one of them. Looks like I am missing something. Appreciate if someone can help me look into this file. {code}import org.jenkinsci.plugins.configfiles.maven.MavenSettingsConfigimport org.jenkinsci.plugins.configfiles.custom.CustomConfigimport org.jenkinsci.plugins.configfiles.maven.security.ServerCredentialMapping// Maven config files.def mavenProvider = instance.getExtensionList('org.jenkinsci.plugins.configfiles.maven.MavenSettingsConfig$MavenSettingsConfigProvider')[0]config?.maven?.each { key, config ->println("Adding maven settings with key: ${key}")def serverCreds = new ArrayList()config.servers.each { server ->def serverCredentialMapping = new ServerCredentialMapping(server.serverId, server.credentialsId)serverCreds.add(serverCredentialMapping)}def mavenConfig = new MavenSettingsConfig(config.id, config.name, config.comment, config.content, Boolean.parseBoolean(config.replaceAll), serverCreds)mavenProvider.save(mavenConfig)}// Custom config files.def customProvider = instance.getExtensionList('org.jenkinsci.plugins.configfiles.custom.CustomConfig$CustomConfigProvider')[0]config?.custom?.each { key, config ->println("Adding custom file with key: ${key}")def customConfig = new CustomConfig(config.id, config.name, config.comment, config.content)customProvider.save(customConfig)}{code} I got to remove one of these two like either custom config files section or the maven config files section to get this work, I have also tried moving this to different files but no luck.
Add Comment
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett Attachment: output.txt Attachment: source.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56305) Need some help with init scripts on this plugin
Title: Message Title
Naresh Rayapati created an issue
Jenkins / JENKINS-56305
Need some help with init scripts on this plugin
Issue Type:
Improvement
Assignee:
Dominik Bartholdi
Components:
config-file-provider-plugin
Created:
2019-02-27 05:41
Environment:
Jenkins 2.165 Latest version of this plugin: 3.5
Priority:
Minor
Reporter:
Naresh Rayapati
I am trying to create a groovy init script to save multiple maven config files and custom config files within a single script, for some reasons it is honoring either one of them. Looks like I am missing something. Appreciate if someone can help me look into this file.
import org.jenkinsci.plugins.configfiles.maven.MavenSettingsConfig
import org.jenkinsci.plugins.configfiles.custom.CustomConfig
import org.jenkinsci.plugins.configfiles.maven.security.ServerCredentialMapping
// Maven config files.
def mavenProvider = instance.getExtensionList('org.jenkinsci.plugins.configfiles.maven.MavenSettingsConfig$MavenSettingsConfigProvider')[0]
config?.maven?.each { key, config ->
println("Adding maven settings with key: ${key}")
def serverCreds = new ArrayList()
config.servers.each { server ->
def serverCredentialMapping = new ServerCredentialMapping(server.serverId, server.credentialsId)
serverCreds.add(serverCredentialMapping)
}
def mavenConfig = new MavenSettingsConfig(config.id, config.name, config.comment, config.content, Boolean.parseBoolean(config.replaceAll), serverCreds)
mavenProvider.save(mavenConfig)
}
// Custom config files.
def customProvider = instance.getExtensionList('org.jenkinsci.plugins.confi
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett created an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Issue Type: Bug Assignee: Naresh Rayapati Components: jira-steps-plugin Created: 2019-02-27 05:37 Environment: jenkins 2.150.3 Jira Pipeline Steps 1.4.4 Priority: Critical Reporter: Jeffrey Bennett At the end of my pipeline, I am iterating the changeSets and the commits therein looking for strings that match Jira tickets, in order to update all Jira's with code present in a build. In theory, this could result in multiple Jiras needing to be updated, so this is done in a loop, potentially making multiple calls to jiraAddComment(..). However, the entire step stops (seems to return success) once the first jiraAddComment is completed. Add Comment
[JIRA] (JENKINS-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Saheta B updated an issue Jenkins / JENKINS-56277 Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Change By: Saheta B Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. One observation here is , whatever value we pass in "Section Header Text" of parameter separator, it is being treated as plain text instead of HTML or CSS even if it contains tags like div, p, h1, span etc. Steps to reproduce : * Just upgrade the jenkins from 2.60 to 2.150.3. * After upgrading here are the plugins versions: h2. Jenkins Plugins:|Active Choices Plug-in|2.1||Amazon Web Services SDK|1.11.457||AnsiColor|0.6.2||Ant Plugin|1.9||Apache HttpComponents Client 4.x API Plugin|4.5.5-3.0||Authentication Tokens API Plugin|1.3||Bitbucket Plugin|1.1.8||Branch API Plugin|2.1.2||Build Timeout|1.19||CloudBees AWS Credentials Plugin|1.25||Command Agent Launcher Plugin|1.3||Conditional BuildStep|1.3.6||Config File Provider Plugin|3.5||Copy Artifact Plugin|1.41||Credentials Binding Plugin|1.17||Credentials Plugin|2.1.18||Display URL API|2.3.0||Docker Commons Plugin|1.13||Docker Pipeline|1.17||Durable Task Plugin|1.29||Email Extension Plugin|2.63||EnvInject API Plugin|1.5||Environment Injector Plugin|2.1.6||Extended Choice Parameter Plug-In|0.76||External Monitor Job Type Plugin|1.7||File System SCM Plugin|2.1||Folders Plugin|6.7||GIT server Plugin|1.7||Generic Webhook Trigger Plugin|1.52||Git client plugin|2.7.6||Git plugin|3.9.3||GitHub API Plugin|1.95||GitHub Branch Source Plugin|2.4.2||GitHub plugin|1.29.4||GitLab Plugin|1.5.11||Gradle Plugin|1.30||Groovy Events Listener Plugin|1.014||HTTP Request Plugin|1.8.22||Hidden Parameter plugin|0.0.4||Icon Shim Plugin|2.0.3||JDK Tool Plugin|1.2||JSch dependency plugin|0.1.55||JUnit Plugin|1.27||Jackson 2 API Plugin|2.9.8||_javascript_ GUI Lib: ACE Editor bundle plugin|1.1||_javascript_ GUI Lib: Handlebars bundle plugin|1.1.1||_javascript_ GUI Lib: Moment.js bundle plugin|1.1.1||_javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin|1.2.1||Javadoc Plugin|1.4||Job DSL|1.71||Job and Node ownership plugin|0.12.1||Kony Build Input Parameters|8.4.0||Kony Custom View Plugin|8.2.1||LDAP Plugin|1.20||Lockable Resources plugin|2.4||Mailer Plugin|1.23||MapDB API Plugin|1.0.9.0||Mask Passwords Plugin|2.12.0||Matrix Authorization Strategy Plugin|2.3||Matrix Project Plugin|1.13||Maven Integration plugin|3.2||Mercurial plugin|2.5||NodeJS Plugin|1.2.7||OWASP Markup Formatter Plugin|1.5||PAM Authentication plugin|1.4||Parameter Separator Plugin|1.1||Parameterized Trigger plugin|2.35.2||Pipeline|2.6||Pipeline Graph Analysis Plugin|1.9||Pipeline Utility Steps|2.2.0||Pipeline: API|2.33||Pipeline: AWS Steps|1.36||Pipeline: Basic Steps|2.14||Pipeline: Build Step|2.7||Pipeline: Declarative|1.3.4.1||Pipeline: Declarative Agent API|1.1.1||Pipeline: Declarative Extension Points API|1.3.4.1||Pipeline: GitHub Groovy Libraries|1.0||Pipeline: Groovy|2.63||Pipeline: Input Step|2.9||Pipeline: Job|
[JIRA] (JENKINS-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Saheta B commented on JENKINS-56277 Re: Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Hi Bruno, I am really sorry as I did the provide enough information initially. Now I updated the description and provided some steps to reproduce. Please take a look at this issue and let me know if I need to share anymore details. 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-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Saheta B updated an issue Jenkins / JENKINS-56277 Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Change By: Saheta B Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Steps to reproduce : * Just upgrade the jenkins from 2.60 to 2.150.3. * After upgrading here are the plugins versions: h2. Jenkins Plugins:|Active Choices Plug-in|2.1||Amazon Web Services SDK|1.11.457||AnsiColor|0.6.2||Ant Plugin|1.9||Apache HttpComponents Client 4.x API Plugin|4.5.5-3.0||Authentication Tokens API Plugin|1.3||Bitbucket Plugin|1.1.8||Branch API Plugin|2.1.2||Build Timeout|1.19||CloudBees AWS Credentials Plugin|1.25||Command Agent Launcher Plugin|1.3||Conditional BuildStep|1.3.6||Config File Provider Plugin|3.5||Copy Artifact Plugin|1.41||Credentials Binding Plugin|1.17||Credentials Plugin|2.1.18||Display URL API|2.3.0||Docker Commons Plugin|1.13||Docker Pipeline|1.17||Durable Task Plugin|1.29||Email Extension Plugin|2.63||EnvInject API Plugin|1.5||Environment Injector Plugin|2.1.6||Extended Choice Parameter Plug-In|0.76||External Monitor Job Type Plugin|1.7||File System SCM Plugin|2.1||Folders Plugin|6.7||GIT server Plugin|1.7||Generic Webhook Trigger Plugin|1.52||Git client plugin|2.7.6||Git plugin|3.9.3||GitHub API Plugin|1.95||GitHub Branch Source Plugin|2.4.2||GitHub plugin|1.29.4||GitLab Plugin|1.5.11||Gradle Plugin|1.30||Groovy Events Listener Plugin|1.014||HTTP Request Plugin|1.8.22||Hidden Parameter plugin|0.0.4||Icon Shim Plugin|2.0.3||JDK Tool Plugin|1.2||JSch dependency plugin|0.1.55||JUnit Plugin|1.27||Jackson 2 API Plugin|2.9.8||_javascript_ GUI Lib: ACE Editor bundle plugin|1.1||_javascript_ GUI Lib: Handlebars bundle plugin|1.1.1||_javascript_ GUI Lib: Moment.js bundle plugin|1.1.1||_javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin|1.2.1||Javadoc Plugin|1.4||Job DSL|1.71||Job and Node ownership plugin|0.12.1||Kony Build Input Parameters|8.4.0||Kony Custom View Plugin|8.2.1||LDAP Plugin|1.20||Lockable Resources plugin|2.4||Mailer Plugin|1.23||MapDB API Plugin|1.0.9.0||Mask Passwords Plugin|2.12.0||Matrix Authorization Strategy Plugin|2.3||Matrix Project Plugin|1.13||Maven Integration plugin|3.2||Mercurial plugin|2.5||NodeJS Plugin|1.2.7||OWASP Markup Formatter Plugin|1.5||PAM Authentication plugin|1.4||Parameter Separator Plugin|1.1||Parameterized Trigger plugin|2.35.2||Pipeline|2.6||Pipeline Graph Analysis Plugin|1.9||Pipeline Utility Steps|2.2.0||Pipeline: API|2.33||Pipeline: AWS Steps|1.36||Pipeline: Basic Steps|2.14||Pipeline: Build Step|2.7||Pipeline: Declarative|1.3.4.1||Pipeline: Declarative Agent API|1.1.1||Pipeline: Declarative Extension Points API|1.3.4.1||Pipeline: GitHub Groovy Libraries|1.0||Pipeline: Groovy|2.63||Pipeline: Input Step|2.9||Pipeline: Job|2.31||Pipeline: Milestone Step|1.3.1||Pipeline: Model API|1.3.4.1||Pipeline: Multibranch|2.20||Pipeline: Nodes and Processes|2.29||Pipeline: REST API Plugin|2.10||Pipeline: SCM Step|2.7||Pipeline: Shared Groo
[JIRA] (JENKINS-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Saheta B updated an issue Jenkins / JENKINS-56277 Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Change By: Saheta B Component/s: parameter-separator-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-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Saheta B updated an issue Jenkins / JENKINS-56277 Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Change By: Saheta B Attachment: image-2019-02-27-10-44-06-624.png 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-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Saheta B updated an issue Jenkins / JENKINS-56277 Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Change By: Saheta B Attachment: image-2019-02-27-10-43-36-595.png 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-56012) stash-pullrequest-builder-plugin variables not seen in multi-configuration jobs unless listed in safeParameters
Title: Message Title Pavel Roskin commented on JENKINS-56012 Re: stash-pullrequest-builder-plugin variables not seen in multi-configuration jobs unless listed in safeParameters It looks like the remaining warnings are a migration issue. They happen when the new plugin (i.e. the one with PR44 merged) loads builds created with the old (pre-PR44) plugin. I made Jenkins dump stack after reporting the SECURITY-170 warning, and here's what it shows. WARNING: Skipped parameter `sourceCommitHash` as it is undefined on `TestRepository_Matrix_PR_Builder`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters=true` to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even though it represents a security breach or `-Dhudson.model.ParametersAction.keepUndefinedParameters=false` to no longer show this message. java.lang.Exception: Stack trace at java.lang.Thread.dumpStack(Thread.java:1336) at hudson.model.ParametersAction.filter(ParametersAction.java:333) at hudson.model.ParametersAction.getParameters(ParametersAction.java:183) at hudson.matrix.MatrixChildParametersAction.onLoad(MatrixChildParametersAction.java:87) at hudson.model.Run.onLoad(Run.java:364) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:346) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:74) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:63) at java.util.AbstractMap$2$1.next(AbstractMap.java:418) at hudson.matrix.LinkedLogRotator.perform(LinkedLogRotator.java:69) at hudson.model.Job.logRotate(Job.java:468) at hudson.model.Run.execute(Run.java:1880) at hudson.matrix.MatrixRun.run(MatrixRun.java:153) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Maybe stash-pullrequest-builder-plugin should still use and recognize the parameters? I see that the GitHub pull request builder took a different approach and used a class derived from ParametersAction. I know, that plugin is obsolete, but I'm sure it was getting more attention than stash-pullrequest-builder-plugin. Add Comment
[JIRA] (JENKINS-56303) Existing user loses build history and other views
Title: Message Title Andrew Palmer created an issue Jenkins / JENKINS-56303 Existing user loses build history and other views Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-02-27 02:01 Environment: Ubuntu 14.04 Jenkins 2.135 Java 8 Chrome/Firefox Browser Priority: Minor Reporter: Andrew Palmer An existing administrator sent a complaint about missing build history for any given job. That is, they can not see the left build history navigation, or the trends, it is completely missing from the page. Note, the security is configured with google oauth, using matrix based security. User is an admin, and all checkboxes are present. No security or user changes were made after seeing this behavior. After diffing my user's config.xml with this user, I noticed the following was showing in the affected users config.xml: executors buildHistory What we have tried: Completely remove user via UI, remove user/config.xml User log out, close browser, then re login User tried multiple browsers, also tried logging in through another's laptop Adjusted security matrix settings, turn admin off, then on Delete the 'collapsed' info noted above (but are not able to restart jenkins). I noticed that after removing and replacing with , after some time, the change is reverted. Checked user settings pages, don't see anything relevant to fix this.
[JIRA] (JENKINS-56301) [blueocean] Restrict referrer display to same origin
Title: Message Title Nicolae Pascu updated JENKINS-56301 Jenkins / JENKINS-56301 [blueocean] Restrict referrer display to same origin Change By: Nicolae Pascu 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-56301) [blueocean] Restrict referrer display to same origin
Title: Message Title Nicolae Pascu started work on JENKINS-56301 Change By: Nicolae Pascu 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-56302) Update empty-plugin archetype to parent POM 3.3
Title: Message Title Jacek Duszenko updated JENKINS-56302 Jenkins / JENKINS-56302 Update empty-plugin archetype to parent POM 3.3 Change By: Jacek Duszenko Status: Fixed but Unreleased Closed 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-56302) Update empty-plugin archetype to parent POM 3.3
Title: Message Title Jacek Duszenko updated JENKINS-56302 There are four plugin versions to choose from. They correspondingly set parent POM version to 3.1, 3.2, 3.3 and 3.4. I must've mistakenly chosen the second archetype version thinking that I've got the newest one. But everything is correct as I checked the archetype source code. Jenkins / JENKINS-56302 Update empty-plugin archetype to parent POM 3.3 Change By: Jacek Duszenko Status: Open Fixed but Unreleased Resolution: Not A Defect 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-13916) Multiline text parameter displays as single line
Title: Message Title Hwang Jae-young commented on JENKINS-13916 Re: Multiline text parameter displays as single line That issue has been reproduced with Jenkins 2.138.2 version. Symptom is same with Peter MacNeil it is displayed as a multi-line at first execute promotion time, but after than (Re-execute promotion), it has been displayed as a single line parameter. Reagards, Francis 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-51004) slave.jar -loggingConfig argument not working as documented
Title: Message Title William Brode commented on JENKINS-51004 Re: slave.jar -loggingConfig argument not working as documented Jeff Thompson, how did you test this? I just cloned the repo and tried to debug and found that -loggingConfig just doesn't work at all. The tests work because they bypass the Launcher (wherein the problem resides). So I'm wondering if you were just trying to reproduce using the maven tests? In any case I'll fork the repo and do a pull request with what I think is 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-51004) slave.jar -loggingConfig argument not working as documented
Title: Message Title William Brode reopened an issue Jenkins / JENKINS-51004 slave.jar -loggingConfig argument not working as documented Change By: William Brode Resolution: Cannot Reproduce Status: Closed Reopened 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-51004) slave.jar -loggingConfig argument not working as documented
Title: Message Title William Brode assigned an issue to William Brode Jenkins / JENKINS-51004 slave.jar -loggingConfig argument not working as documented Change By: William Brode Assignee: Jeff Thompson William Brode 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-56302) Update empty-plugin archetype to parent POM 3.3
Title: Message Title Jacek Duszenko created an issue Jenkins / JENKINS-56302 Update empty-plugin archetype to parent POM 3.3 Issue Type: Improvement Assignee: Jacek Duszenko Components: archetypes Created: 2019-02-27 00:45 Environment: Irrelevant Priority: Minor Reporter: Jacek Duszenko 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...
[JIRA] (JENKINS-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Bruno P. Kinoshita commented on JENKINS-56277 Re: Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. Hi Saheta B, thanks for reporting the issue. I am working on other issues at the moment. Even though your issue has a good title, and you set the priority to Critical, this bug may very well be ignored during the next triage. The reason for that is that you are not providing enough information. You need to imagine yourself as a developer trying to fix it. Then ask yourself could it be a problem with the previous version the user had installed? Maybe he didn't upgrade from the latest to 2.150.3. Could it be another plug-in? What are the exact steps that I need to perform to reproduce? Would a screenshot help? Would a config.xml help? etc etc. So if you logged a Minor priority bug, but with good information for troubleshooting, that could have more chances of being quickly fixed then the other way. 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-56301) [blueocean] Restrict referrer display to same origin
Title: Message Title David Lin created an issue Jenkins / JENKINS-56301 [blueocean] Restrict referrer display to same origin Issue Type: Improvement Assignee: Nicolae Pascu Components: blueocean-plugin Created: 2019-02-27 00:28 Labels: blueocean Priority: Minor Reporter: David Lin Not all referrers are warranted to be displayed publicly in the case of private repositories and specific project names. Therefore we should restrict referrers to the same-origin in Blue Ocean as described here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy#Integration_with_HTML Add Comment
[JIRA] (JENKINS-41709) Blue Ocean doesnt render Active Choices parameters
Title: Message Title Bruno P. Kinoshita commented on JENKINS-41709 Re: Blue Ocean doesnt render Active Choices parameters Hi Omit Rathore. Increasing the priority won't have any effect for me. We (mainly Ioannis and myself) triage the issues, looking for bugs and things that we need for our environments or that are missing from the plug-in. We have already triaged a few bugs for the next development cycle. But given that Ioannis and myself are not using Blue Ocean, we wouldn't know how to start working to add support to it. A pull request or some work that work ease the work for somebody else to create a pull request would better IMO. 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-41709) Blue Ocean doesnt render Active Choices parameters
Title: Message Title Omit Rathore commented on JENKINS-41709 Re: Blue Ocean doesnt render Active Choices parameters We need to support blue ocean as well , please can we increase its priority. Thank you. 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-56300) New step or option that does not block on individual job completion
Title: Message Title
Thomas Cooper updated an issue
Jenkins / JENKINS-56300
New step or option that does not block on individual job completion
Change By:
Thomas Cooper
Using Ansible Tower in a pipeline, there is no way to trigger multiple Tower jobs to be run concurrently then poll each for completion status. I'd like some sort of option on the ansibleTower step that prevents the AnsibleTowerRunner from blocking on job completion before continuing. This might warrant a separate step. Below is my use case: {noformat}script { def myapps = [...] def jobs = myapps.collect {ansibleTower( jobTemplate: 'deploy-one-app', extraVars: "---\napp_to_deploy: ${it}", throwExceptionWhenFail: false, waitForCompletion: false) // return Job ID? } timeout(10) {waitUntil { jobs.every { def job = ansibleTowerJob(id: it )job . JOB_RESULT status == " SUCCESS successful " }} }}{noformat}
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-56300) New step or option that does not block on individual job completion
Title: Message Title
Thomas Cooper created an issue
Jenkins / JENKINS-56300
New step or option that does not block on individual job completion
Issue Type:
Improvement
Assignee:
John Westcott
Components:
ansible-tower-plugin
Created:
2019-02-27 00:11
Labels:
plugin
Priority:
Major
Reporter:
Thomas Cooper
Using Ansible Tower in a pipeline, there is no way to trigger multiple Tower jobs to be run concurrently then poll each for completion status. I'd like some sort of option on the ansibleTower step that prevents the AnsibleTowerRunner from blocking on job completion before continuing. This might warrant a separate step. Below is my use case:
script {
def myapps = [...]
def jobs = myapps.collect {
ansibleTower(
jobTemplate: 'deploy-one-app',
extraVars: "---\napp_to_deploy: ${it}",
throwExceptionWhenFail: false,
waitForCompletion: false
)
}
timeout(10) {
waitUntil {
jobs.every {
it.JOB_RESULT == "SUCCESS"
}
}
}
}
[JIRA] (JENKINS-53988) skipDefaultCheckout not honored in Pull Requests
Title: Message Title Jason Tarver commented on JENKINS-53988 Re: skipDefaultCheckout not honored in Pull Requests I also ran into this exact problem. I have to use this as a workaround git config --global url."g...@github.com:".insteadOf "https://github.com/" 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Narayanan Singaram edited a comment on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN We see this error very . frequently. This exception stack trace appears in the job console output. However when I see the kubernetes plugin logs (Our log level is ALL) I don't find any related error / exception. How do I find co-relating error / messages in kubernetes 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Narayanan Singaram commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN We see this error very. frequently. This exception stack trace appears in the job console output. However when I see the kubernetes plugin logs (Our log level is ALL) I don't find any related error / exception. How do I find co-relating error / messages in kubernetes 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-56298) 'authenticated' role not shown in role strategy using AD
Title: Message Title Bob Ashforth updated JENKINS-56298 I actually found that although the role 'authenticated' does not appear, once I had my AD settings working completely and correctly, when I "created" the role it was recognized as a 'user' for which I could define permissions. Closing the bug accordingly. Jenkins / JENKINS-56298 'authenticated' role not shown in role strategy using AD Change By: Bob Ashforth Status: Open Fixed but Unreleased Resolution: Not A Defect 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-56255) occasionally builds the branch for a PR also
Title: Message Title Brian J Murrell commented on JENKINS-56255 Re: occasionally builds the branch for a PR also The other possibility for this issue is to have a whiltelist filter of branches to build and ignore the rest assuming they will eventually become a PR. 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-56203) ECS - Support Placement Strategy
Title: Message Title Sushant Pradhan commented on JENKINS-56203 Re: ECS - Support Placement Strategy I am also looking for this feature 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-56299) Allow quality gates to apply to specific static analysis tool
Title: Message Title Ulli Hafner resolved as Duplicate Jenkins / JENKINS-56299 Allow quality gates to apply to specific static analysis tool Change By: Ulli Hafner 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-55798) Performance: Offer Enum APIs instead of String APIs in RoleBasedAuthorizationStrategy
Title: Message Title Deepansh Nagaria assigned an issue to Deepansh Nagaria Jenkins / JENKINS-55798 Performance: Offer Enum APIs instead of String APIs in RoleBasedAuthorizationStrategy Change By: Deepansh Nagaria Assignee: Deepansh Nagaria 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-55916) Performance: Rewriting RoleMap#RoleWalker such that it includes a breaking(aborting) logic, reducing the execution time in many cases and avoid creation of new collection for ro
Title: Message Title Deepansh Nagaria updated JENKINS-55916 Jenkins / JENKINS-55916 Performance: Rewriting RoleMap#RoleWalker such that it includes a breaking(aborting) logic, reducing the execution time in many cases and avoid creation of new collection for roles every time RoleWalker is invoked, reducing the memory usage. Change By: Deepansh Nagaria 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-56299) Allow quality gates to apply to specific static analysis tool
Title: Message Title Steve Muskiewicz updated an issue Jenkins / JENKINS-56299 Allow quality gates to apply to specific static analysis tool Change By: Steve Muskiewicz I am trying to use the warnings-ng plugin along with the quality gates to configure which warnings will cause an unstable build. However it seems as if the current setup for quality gates isn't granular enough to achieve what I'm looking for which is basically that both either of the following conditions result in an unstable build: * any checkstyle warnings (regardless of priority) * any Open tasks scanner warnings with a priority of HighHowever it seems like if I change the quality gates setting type to "Total number of warnings (severity high)" then my lower priority checkstyle warnings result in a passing build and if I change the type to "Total number of issues (any severity)" then my open tasks cause an unstable build, neither of which is a desirable result.It almost seems like there would need to be another field in the quality gate to allow selection of which static analysis tool the gate should apply to (maybe with the default being "all results"?)Note that previously we were able to do this as separate post-build actions using the deprecated "Post checkstyle analysis results" and "Scan workspace for open tasks" plugins but we'd like to avoid having to use these going forward if it's still possible to achieve this result with Warnings NG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56299) Allow quality gates to apply to specific static analysis tool
Title: Message Title Steve Muskiewicz created an issue Jenkins / JENKINS-56299 Allow quality gates to apply to specific static analysis tool Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-02-26 20:36 Priority: Major Reporter: Steve Muskiewicz I am trying to use the warnings-ng plugin along with the quality gates to configure which warnings will cause an unstable build. However it seems as if the current setup for quality gates isn't granular enough to achieve what I'm looking for which is basically that both of the following conditions result in an unstable build: any checkstyle warnings (regardless of priority) any Open tasks scanner warnings with a priority of High However it seems like if I change the quality gates setting type to "Total number of warnings (severity high)" then my lower priority checkstyle warnings result in a passing build and if I change the type to "Total number of issues (any severity)" then my open tasks cause an unstable build, neither of which is a desirable result. It almost seems like there would need to be another field in the quality gate to allow selection of which static analysis tool the gate should apply to (maybe with the default being "all results"?) Note that previously we were able to do this as separate post-build actions using the deprecated "Post checkstyle analysis results" and "Scan workspace for open tasks" plugins but we'd like to avoid having to use these going forward if it's still possible to achieve this result with Warnings NG
[JIRA] (JENKINS-56298) 'authenticated' role not shown in role strategy using AD
Title: Message Title Bob Ashforth created an issue Jenkins / JENKINS-56298 'authenticated' role not shown in role strategy using AD Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin, role-strategy-plugin Created: 2019-02-26 20:25 Environment: Administration of Jenkins 2.138.1 Priority: Major Reporter: Bob Ashforth I'm using Jenkins 2.138.1, with the Active Directory plugin used for authorization. This is working, as indicated by the population of group membership for users who have logged into the system. I've also selected the role-based strategy, which is supposed to include a built-in 'authenticated' role which is assigned to any and all logged-in users. This role does not show up, and if I create it and assign specific permissions to the role, those permissions are not applied to logged-in users. Another Jenkins instanced used by my team is using the Matrix-based project security, and that plugin provides both Anonymous Users and Authenticated Users built-in 'roles.' I'd really like to continue with the role-based approach, in order to make use of folder and node ownership for corresponding teams. I hope this issue can be prioritized for triage, at least.
[JIRA] (JENKINS-21104) Confluence Publisher Plugin ignores Jenkins proxy settings
Title: Message Title Radha Medasani commented on JENKINS-21104 Re: Confluence Publisher Plugin ignores Jenkins proxy settings Hi Joe, Could you please if there is any future release which fixes confluence plugin not working behind proxy even after adding proxy info in Jenkins-Manage Plugins-Proxy Info. Any help in this regards much appreciated. 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-55750) IAR parser not finding warnings of IAR ARM compiler
Title: Message Title Lorenz Aebi started work on JENKINS-55750 Change By: Lorenz Aebi 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-55750) IAR parser not finding warnings of IAR ARM compiler
Title: Message Title Lorenz Aebi assigned an issue to Lorenz Aebi Jenkins / JENKINS-55750 IAR parser not finding warnings of IAR ARM compiler Change By: Lorenz Aebi Assignee: Lorenz Aebi 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-53665) Micro Focus Application Automation Tools - file descriptor leak
Title: Message Title Alejandro Jurado Walls commented on JENKINS-53665 Re: Micro Focus Application Automation Tools - file descriptor leak Same problem 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-53665) Micro Focus Application Automation Tools - file descriptor leak
Title: Message Title Alejandro Jurado Walls updated an issue Jenkins / JENKINS-53665 Micro Focus Application Automation Tools - file descriptor leak Change By: Alejandro Jurado Walls Comment: Same problem 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-56297) kubernetes-cli-plugin configure does not interpolate build/environment variables
Title: Message Title Ben Fiedler commented on JENKINS-56297 Re: kubernetes-cli-plugin configure does not interpolate build/environment variables Wow, thank you for the speedy resolution. 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-56297) kubernetes-cli-plugin configure does not interpolate build/environment variables
Title: Message Title Max Laverse started work on JENKINS-56297 Change By: Max Laverse 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-56297) kubernetes-cli-plugin configure does not interpolate build/environment variables
Title: Message Title Max Laverse closed an issue as Fixed Jenkins / JENKINS-56297 kubernetes-cli-plugin configure does not interpolate build/environment variables Change By: Max Laverse Status: Resolved Closed 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-56297) kubernetes-cli-plugin configure does not interpolate build/environment variables
Title: Message Title Max Laverse updated JENKINS-56297 Jenkins / JENKINS-56297 kubernetes-cli-plugin configure does not interpolate build/environment variables Change By: Max Laverse 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-56297) kubernetes-cli-plugin configure does not interpolate build/environment variables
Title: Message Title Max Laverse commented on JENKINS-56297 Re: kubernetes-cli-plugin configure does not interpolate build/environment variables Implemented in https://github.com/jenkinsci/kubernetes-cli-plugin/pull/26 Released in version 1.6.0. Please download the new version from the release GitHub page or wait for the Jenkins plugin repositories to show the new version. https://github.com/jenkinsci/kubernetes-cli-plugin/releases/tag/kubernetes-cli-1.6.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-56297) kubernetes-cli-plugin configure does not interpolate build/environment variables
Title: Message Title Max Laverse updated JENKINS-56297 Jenkins / JENKINS-56297 kubernetes-cli-plugin configure does not interpolate build/environment variables Change By: Max Laverse 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-49135) Support for reusable sharing Declarative directives
Title: Message Title Andrew Bayer stopped work on JENKINS-49135 Change By: Andrew Bayer 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-55996) jacoco: Error while reading the sourcefile!
Title: Message Title Daniel Richardson commented on JENKINS-55996 Re: jacoco: Error while reading the sourcefile! Ferry Huberts I found that if you append a '/' to the end you get the sources back. however you do see this warning in the logs: [JaCoCo plugin] WARNING: You are using directory patterns with trailing /, /* or /** . This will most likely multiply the copied files in your build directory. Check the list below and ignore this warning if you know what you are doing. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Carlos Sanchez commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN are you using the containerLog step ? seems that step is closing the connections when it shouldn't 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56292) Job launching parameterized build on other project fails
Title: Message Title Adi Adrian commented on JENKINS-56292 Re: Job launching parameterized build on other project fails I checked different Jenkins versions and this problem appeared in version 2.164. Version 2.163 does not have this 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Matt Nuzzaco commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN We're experiencing this quite often, I'll try to gather a sanitized log for you to review today. And to answer your latest question, we do execute long running scripts in our pipeline. Like kicking off a suite of integration tests that can last 10+ minutes (not sure if that's considered long 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Carlos Sanchez commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN are you executing long shell scripts in one jenkinsfile step? 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-56297) kubernetes-cli-plugin configure does not interpolate build/environment variables
Title: Message Title Max Laverse updated an issue Jenkins / JENKINS-56297 kubernetes-cli-plugin configure does not interpolate build/environment variables Change By: Max Laverse Issue Type: Bug Improvement 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-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Thanks Wadeck Follonier, I will try a deployment with the WAR once it becomes available and let you know my results. 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-56297) kubernetes-cli-plugin configure does not interpolate build/environment variables
Title: Message Title
Ben Fiedler created an issue
Jenkins / JENKINS-56297
kubernetes-cli-plugin configure does not interpolate build/environment variables
Issue Type:
Bug
Assignee:
Max Laverse
Components:
kubernetes-cli-plugin
Created:
2019-02-26 18:09
Environment:
kubernetes-cli-1.5.0 , jenkins 2.150.2 , kubectl 1.13
Priority:
Minor
Reporter:
Ben Fiedler
For a non-pipeline job, if I setup the build environment and try to set the Kubernetes server endpoint to an environment/build variable, e.g. either $K8S_URL or ${K8S_URL} , it is not interpolated and results in these failures, respectively: Unable to connect to the server: dial tcp: lookup $K8S_URL: no such host Unable to connect to the server: invalid character "{" in host name For a pipeline job, I can just use env.K8S_URL and it works perfectly. Some of our job's steps do not support pipeline, and with multiple kubernetes clusters it would be very useful to have this functionality in a Freestyle job.
Add Comment
[JIRA] (JENKINS-33285) Old jenkins versions are not listed in Debian repository Packages.gz
Title: Message Title Kohsuke Kawaguchi updated JENKINS-33285 Jenkins / JENKINS-33285 Old jenkins versions are not listed in Debian repository Packages.gz Change By: Kohsuke Kawaguchi Status: Open 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-33285) Old jenkins versions are not listed in Debian repository Packages.gz
Title: Message Title Kohsuke Kawaguchi updated JENKINS-33285 Jenkins / JENKINS-33285 Old jenkins versions are not listed in Debian repository Packages.gz Change By: Kohsuke Kawaguchi Status: Fixed but Unreleased Resolved 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-33285) Old jenkins versions are not listed in Debian repository Packages.gz
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-33285 Re: Old jenkins versions are not listed in Debian repository Packages.gz I came across this old issue that I happened to confirm has been fixed since then. 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-56295) multibranch jobs triggering repeatedly
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-56295 multibranch jobs triggering repeatedly Change By: Karl Wirth Assignee: Matthew DeTullio Karl Wirth 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-56286) Multibranch Pipeline + P4Plugin + Polling = Infinite Build Loop
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-56286 Multibranch Pipeline + P4Plugin + Polling = Infinite Build Loop Change By: Karl Wirth Assignee: Karl Wirth 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-56286) Multibranch Pipeline + P4Plugin + Polling = Infinite Build Loop
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-56286 Multibranch Pipeline + P4Plugin + Polling = Infinite Build Loop 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-56295) multibranch jobs triggering repeatedly
Title: Message Title Karl Wirth commented on JENKINS-56295 Re: multibranch jobs triggering repeatedly Hi Nancy Belser, Brad Wehmeier, I will email you directly with requests for more information. 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-56295) multibranch jobs triggering repeatedly
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-56295 multibranch jobs triggering repeatedly 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-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Filip Trönnbergq edited a comment on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ We had the exact same problem but were able to get this to work by going to "Manage Jenkins -> Configure System" and adding an environment variable called ` " PATH+EXTRA ` " with the value ` /usr/local/bin ` .After initially attempting to manually set the path we saw the following output in the console that suggested the use of ` " PATH+EXTRA ` " ` Warning: JENKINS-41339 probably bogus PATH=""$PATH":/usr/local/bin":/usr/local/bin; perhaps you meant to use 'PATH+EXTRA=/something/bin'? ` 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-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Filip Trönnbergq commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ We had the exact same problem but were able to get this to work by going to "Manage Jenkins -> Configure System" and adding an environment variable called `PATH+EXTRA` with the value `/usr/local/bin`. After initially attempting to manually set the path we saw the following output in the console that suggested the use of `PATH+EXTRA` `Warning: JENKINS-41339 probably bogus PATH=""$PATH":/usr/local/bin":/usr/local/bin; perhaps you meant to use 'PATH+EXTRA=/something/bin'?` 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-56296) EOFException while reading exec file (running on agent docker)
Title: Message Title Jorge Hidalgo closed an issue as Not A Defect After doing some extra tests on the project and similar ones, it seems that the issue may be related with the generation of the exec files, and not on the plugin. Apologies for the noise. Jenkins / JENKINS-56296 EOFException while reading exec file (running on agent docker) Change By: Jorge Hidalgo Status: Open Closed Resolution: Not A Defect 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-56295) multibranch jobs triggering repeatedly
Title: Message Title Brad Wehmeier commented on JENKINS-56295 Re: multibranch jobs triggering repeatedly We have a full backup of the job folder when the issue was occurring this time. I attached the polling log from one of the branches in a multi-branch pipeline that was having issues. It seems to be checking the included libraries and finally the specific branch but the log never shows any changelists that it identified as being new but yet still says "Changes found" at the end. The only thing that my untrained eye sees that might be concerning is "no polling baseline in ". I can provide more details if needed. 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-56295) multibranch jobs triggering repeatedly
Title: Message Title Brad Wehmeier commented on JENKINS-56295 Re: multibranch jobs triggering repeatedly We have a full backup of the job folder when the issue was occurring this time. I attached the polling log from one of the branches in a multi-branch pipeline that was having issues. It seems to be checking the included libraries and finally the specific branch but the log never shows any changelists that it identified as being new but yet still says "Changes found" at the end. The only thing that my untrained eye sees that might be concerning is "no polling baseline in ". I can provide more details if needed. 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-56295) multibranch jobs triggering repeatedly
Title: Message Title Brad Wehmeier updated an issue Jenkins / JENKINS-56295 multibranch jobs triggering repeatedly Change By: Brad Wehmeier Attachment: scm-polling.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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Karl Wirth commented on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. Hi Nancy Belser - Thanks but no. This is the bug tracking system so the developers should be working off this job and I have highlighted this one to them. However note that if you are a supported Perforce customer and want us to look into specifics of your problem you can raise a seperate ticket by emailing 'supp...@perforce.com'. However this Jenkins Jira system is the system I use to log bugs and communicate with the developers. 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-56296) EOFException while reading exec file (running on agent docker)
Title: Message Title
Jorge Hidalgo updated an issue
Jenkins / JENKINS-56296
EOFException while reading exec file (running on agent docker)
Change By:
Jorge Hidalgo
When running the jacoco plug-in inside a pipeline using a Docker container as the build agent, the call randomly crashes with an EOFException (see stack trace below).Minimum example in this repo: [https://github.com/deors/deors-demos-java-pipeline]Re-launching the pipeline, no changes in sources, sometimes it work, but some other not. No pattern observed on failure. {{ [Pipeline] junitRecording test results }}{{ [Pipeline] step }}{{ [JaCoCo plugin] Collecting JaCoCo coverage data... }}{{ [JaCoCo plugin] target/jacoco.exec;*/classes;*/src/main/java; locations are configured }}{{ [JaCoCo plugin] Number of found exec files for pattern target/jacoco.exec: 1 }}{{ [JaCoCo plugin] Saving matched execfiles: /var/jenkins_home/jobs//workspace/target/jacoco.exec }}{{ [JaCoCo plugin] Saving matched class directories for class-pattern: **/classes: }}{{[JaCoCo plugin] - /var/jenkins_home/jobs//workspace/target/classes 1 files }}{{ [JaCoCo plugin] Saving matched source directories for source-pattern: **/src/main/java: }}{{[JaCoCo plugin] Source Inclusions: */.java }}{{ [JaCoCo plugin] Source Exclusions: }}{{[JaCoCo plugin] - /var/jenkins_home/jobs//workspace/src/main/java 1 files }}{{ [JaCoCo plugin] Loading inclusions files.. }}{{ [JaCoCo plugin] inclusions: [] }}{{ [JaCoCo plugin] exclusions: [] }}{{ [Pipeline] }}{{ ... }}{{ ... }}{{ [Pipeline] // node }}{{ [Pipeline] End of Pipeline }}{{ java.io.EOFException }}{{ at java.io.DataInputStream.readByte(DataInputStream.java:267) }}{{ at org.jacoco.core.internal.data.CompactDataInput.readVarInt(CompactDataInput.java:44) }}{{ at org.jacoco.core.internal.data.CompactDataInput.readBooleanArray(CompactDataInput.java:59) }}{{ at org.jacoco.core.data.ExecutionDataReader.readExecutionData(ExecutionDataReader.java:149) }}{{ at org.jacoco.core.data.ExecutionDataReader.readBlock(ExecutionDataReader.java:115) }}{{ at org.jacoco.core.data.ExecutionDataReader.read(ExecutionDataReader.java:92) }}{{ at hudson.plugins.jacoco.ExecutionFileLoader.loadExecutionData(ExecutionFileLoader.java:95) }}{{ Caused: java.io.IOException: While reading execution data-file: /var/jenkins_home/jobs/deors-demos-microservices-eurekaservice-local/builds/34/jacoco/execFiles/exec0/jacoco.exec }}{{ at hudson.plugins.jacoco.ExecutionFileLoader.loadExecutionData(ExecutionFileLoader.java:98) }}{{ at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:139) }}{{ at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:110) }}{{ at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:339) }}{{ at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:326) }}{{ at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:657) }}{{ at org.jenkinsci.plugins.workflow.ste
[JIRA] (JENKINS-56296) EOFException while reading exec file (running on agent docker)
Title: Message Title
Jorge Hidalgo updated an issue
Jenkins / JENKINS-56296
EOFException while reading exec file (running on agent docker)
Change By:
Jorge Hidalgo
When running the jacoco plug-in inside a pipeline using a Docker container as the build agent, the call randomly crashes with an EOFException (see stack trace below).Minimum example in this repo: [https://github.com/deors/deors-demos-java-pipeline]Re-launching the pipeline, no changes in sources, sometimes it work, but some other not. No pattern observed on failure. {{ [Pipeline] junitRecording test results}} {{[Pipeline] step}} {{[JaCoCo plugin] Collecting JaCoCo coverage data...}} {{ [JaCoCo plugin] target/jacoco.exec;* * /classes;* * /src/main/java; locations are configured}} {{ [JaCoCo plugin] Number of found exec files for pattern target/jacoco.exec: 1}} {{ [JaCoCo plugin] Saving matched execfiles: /var/jenkins_home/jobs//workspace/target/jacoco.exec}} {{ [JaCoCo plugin] Saving matched class directories for class-pattern: **/classes: }} {{ [JaCoCo plugin] - /var/jenkins_home/jobs//workspace/target/classes 1 files}} {{ [JaCoCo plugin] Saving matched source directories for source-pattern: **/src/main/java: }} {{ [JaCoCo plugin] Source Inclusions: * * / * .java}} {{ [JaCoCo plugin] Source Exclusions: }} {{ [JaCoCo plugin] - /var/jenkins_home/jobs//workspace/src/main/java 1 files}} {{ [JaCoCo plugin] Loading inclusions files..}} {{ [JaCoCo plugin] inclusions: []}} {{ [JaCoCo plugin] exclusions: [] }}{{ [Pipeline] } }{{ ...}} {{ ...}} {{ [Pipeline] // node}} {{ [Pipeline] End of Pipeline}} {{ java.io.EOFException}} {{ at java.io.DataInputStream.readByte(DataInputStream.java:267)}} {{ at org.jacoco.core.internal.data.CompactDataInput.readVarInt(CompactDataInput.java:44)}} {{ at org.jacoco.core.internal.data.CompactDataInput.readBooleanArray(CompactDataInput.java:59)}} {{ at org.jacoco.core.data.ExecutionDataReader.readExecutionData(ExecutionDataReader.java:149)}} {{ at org.jacoco.core.data.ExecutionDataReader.readBlock(ExecutionDataReader.java:115)}} {{ at org.jacoco.core.data.ExecutionDataReader.read(ExecutionDataReader.java:92)}} {{ at hudson.plugins.jacoco.ExecutionFileLoader.loadExecutionData(ExecutionFileLoader.java:95)}} {{ Caused: java.io.IOException: While reading execution data-file: /var/jenkins_home/jobs/deors-demos-microservices-eurekaservice-local/builds/34/jacoco/execFiles/exec0/jacoco.exec}} {{ at hudson.plugins.jacoco.ExecutionFileLoader.loadExecutionData(ExecutionFileLoader.java:98)}} {{ at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:139)}} {{ at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:110)}} {{ at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:339)}} {{ at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:326)}} {{ at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:657)}} {{ at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(C
[JIRA] (JENKINS-56296) EOFException while reading exec file (running on agent docker)
Title: Message Title
Jorge Hidalgo updated an issue
Jenkins / JENKINS-56296
EOFException while reading exec file (running on agent docker)
Change By:
Jorge Hidalgo
When running the jacoco plug-in inside a pipeline using a Docker container as the build agent, the call randomly crashes with an EOFException (see stack trace below).Minimum example in this repo: [https://github.com/deors/deors-demos-java-pipeline]Re-launching the pipeline, no changes in sources, sometimes it work, but some other not. No pattern observed on failure. {{ [Pipeline] junitRecording test results }}{{ [Pipeline] step }}{{ [JaCoCo plugin] Collecting JaCoCo coverage data... }} {{ [JaCoCo plugin] target/jacoco.exec;**/classes;**/src/main/java; locations are configured }} {{ [JaCoCo plugin] Number of found exec files for pattern target/jacoco.exec: 1 }} {{ [JaCoCo plugin] Saving matched execfiles: /var/jenkins_home/jobs/ -demos-microservices-eurekaservice-local /workspace/target/jacoco.exec }} {{ [JaCoCo plugin] Saving matched class directories for class-pattern: **/classes:}}{{ [JaCoCo plugin] - /var/jenkins_home/jobs/ -demos-microservices-eurekaservice-local /workspace/target/classes 1 files }} {{ [JaCoCo plugin] Saving matched source directories for source-pattern: **/src/main/java:}}{{ [JaCoCo plugin] Source Inclusions: **/*.java }} {{ [JaCoCo plugin] Source Exclusions:}}{{ [JaCoCo plugin] - /var/jenkins_home/jobs/ -demos-microservices-eurekaservice-local /workspace/src/main/java 1 files }} {{ [JaCoCo plugin] Loading inclusions files.. }} {{ [JaCoCo plugin] inclusions: [] }} {{ [JaCoCo plugin] exclusions: [][Pipeline] }... }} {{ ... }} {{ [Pipeline] // node }} {{ [Pipeline] End of Pipeline }} {{ java.io.EOFException }} {{ at java.io.DataInputStream.readByte(DataInputStream.java:267) }} {{ at org.jacoco.core.internal.data.CompactDataInput.readVarInt(CompactDataInput.java:44) }} {{ at org.jacoco.core.internal.data.CompactDataInput.readBooleanArray(CompactDataInput.java:59) }} {{ at org.jacoco.core.data.ExecutionDataReader.readExecutionData(ExecutionDataReader.java:149) }} {{ at org.jacoco.core.data.ExecutionDataReader.readBlock(ExecutionDataReader.java:115) }} {{ at org.jacoco.core.data.ExecutionDataReader.read(ExecutionDataReader.java:92) }} {{ at hudson.plugins.jacoco.ExecutionFileLoader.loadExecutionData(ExecutionFileLoader.java:95) }} {{ Caused: java.io.IOException: While reading execution data-file: /var/jenkins_home/jobs/deors-demos-microservices-eurekaservice-local/builds/34/jacoco/execFiles/exec0/jacoco.exec }} {{ at hudson.plugins.jacoco.ExecutionFileLoader.loadExecutionData(ExecutionFileLoader.java:98) }} {{ at hudson.plugins.jacoco.ExecutionFileLoader.loadBundleCoverage(ExecutionFileLoader.java:139) }} {{ at hudson.plugins.jacoco.JacocoReportDir.parse(JacocoReportDir.java:110) }} {{ at hudson.plugins.jacoco.JacocoBuildAction.loadRatios(JacocoBuildAction.java:339) }} {{ at hudson.plugins.jacoco.JacocoBuildAction.load(JacocoBuildAction.java:326) }} {
[JIRA] (JENKINS-56296) EOFException while reading exec file (running on agent docker)
Title: Message Title Jorge Hidalgo created an issue Jenkins / JENKINS-56296 EOFException while reading exec file (running on agent docker) Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2019-02-26 16:32 Environment: Jenkins and JaCoCo plug-in latest version, running on latest Docker (official image, no customisation). Pipeline runs on Docker agent. Priority: Major Reporter: Jorge Hidalgo When running the jacoco plug-in inside a pipeline using a Docker container as the build agent, the call randomly crashes with an EOFException (see stack trace below). Minimum example in this repo: https://github.com/deors/deors-demos-java-pipeline Re-launching the pipeline, no changes in sources, sometimes it work, but some other not. No pattern observed on failure. [Pipeline] junitRecording test results[Pipeline] step[JaCoCo plugin] Collecting JaCoCo coverage data... [JaCoCo plugin] target/jacoco.exec;*/classes;*/src/main/java; locations are configured [JaCoCo plugin] Number of found exec files for pattern target/jacoco.exec: 1 [JaCoCo plugin] Saving matched execfiles: /var/jenkins_home/jobs/-demos-microservices-eurekaservice-local/workspace/target/jacoco.exec [JaCoCo plugin] Saving matched class directories for class-pattern: **/classes: [JaCoCo plugin] - /var/jenkins_home/jobs/-demos-microservices-eurekaservice-local/workspace/target/classes 1 files [JaCoCo plugin] Saving matched source directories for source-pattern: **/src/main/java: [JaCoCo plugin] Source Inclusions: */.java [JaCoCo plugin] Source Exclusions: [JaCoCo plugin] - /var/jenkins_home/jobs/-demos-microservices-eurekaservice-local/workspace/src/main/java 1 files [JaCoCo plugin] Loading inclusions files.. [JaCoCo plugin] inclusions: [] [JaCoCo plugin] exclusions: [][Pipeline] }
[JIRA] (JENKINS-56295) multibranch jobs triggering repeatedly
Title: Message Title Nancy Belser commented on JENKINS-56295 Re: multibranch jobs triggering repeatedly See our comments on jenkins-55075 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-56295) multibranch jobs triggering repeatedly
Title: Message Title Nancy Belser commented on JENKINS-56295 Re: multibranch jobs triggering repeatedly Brad Wehmeier adding Brad to the thread for more details. 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-56295) multibranch jobs triggering repeatedly
Title: Message Title Nancy Belser created an issue Jenkins / JENKINS-56295 multibranch jobs triggering repeatedly Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin (not Pipeline), p4-plugin Created: 2019-02-26 16:22 Environment: jenkins 2.150.2 p4 plugin 1.9.6 Priority: Major Reporter: Nancy Belser multi-branch project jobs suddenly start triggering repeatedly. Our only option is to clean up project history manually. This has happened 4 times already and is very disruptive. Add Comment
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Wadeck Follonier assigned an issue to Wadeck Follonier Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Wadeck Follonier Assignee: Wadeck Follonier 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-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Wadeck Follonier updated JENKINS-56114 Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Wadeck Follonier 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-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Wadeck Follonier started work on JENKINS-56114 Change By: Wadeck Follonier 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-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Henry Borchers commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Sam Van Oort, it's been a few months since you teased us about something on your roadmap that would alleviate this issue. Any chance you could provide a little more info or at least tease us enough to wet our appetite? I'm running against the limit way too often these days. 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-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Wadeck Follonier commented on JENKINS-56114 Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) The WAR will be available in this PR once the build is completed. 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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Nancy Belser commented on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. This continues to happen to us. Should we create a separate ticket? 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-55088) Jenkins Home config.xml reset upon restart
Title: Message Title Michael Schneider commented on JENKINS-55088 Re: Jenkins Home config.xml reset upon restart There were many backup files in the plugins directories and a queue.xml.bak file. Nothing for config.xml queue.xml.bak contained XX 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-56294) dockerfile: ARG in FROM breaks docker inspect
Title: Message Title
Christian Ciach updated an issue
Jenkins / JENKINS-56294
dockerfile: ARG in FROM breaks docker inspect
Change By:
Christian Ciach
Please note that there is already an issue with a very similar name regarding the docker-workflow plugin here: https://issues.jenkins-ci.org/browse/JENKINS-46105The issue actually has been fixed already at the docker-workflow plugin, but the pipeline-model-definition-plugin fails to take advantage of that.The issue in a nutshell:I have this Dockerfile (excerpt): {code:java}ARG VERSION=latestFROM repo-vp.development.ems:5000/emsys-adoptopenjdk11:${VERSION}{code} This is part of my declarative Jenkinsfile:{code:java}stage('Build') { agent { dockerfile { filename 'Dockerfile' additionalBuildArgs "--build-arg VERSION=jdk-11.0.2.9" reuseNode true} } steps {(...) }}{code} This results in a failed build with the following error log:{code:java}java.io.IOException: Cannot retrieve .Id from 'docker inspect repo-vp.development.ems:5000/emsys-adoptopenjdk11:${VERSION}' at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:220) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:133) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:85) 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}This has already been fixed by the docker-workflow plugin (see JENKINS-46105), but "pipeline-model-definition" has yet to take advantage of that.Please see this line in your plugin: [https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/7502d14aa4db891302abf48a2c7de7c9ced97f95/pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/DockerPipelineFromDockerfileScript.groovy#L83]As you can see, you don't pass the new parameter "buildArgs" to the instance of `dockerFingerprintFrom`. See the setter here: [https://github.com/jenkinsci/docker-workflow-plugin/blob/dbeb7cf23961fdb5cbc495e8067bd42c56dcdfc5/src/main/java/org/jenkinsci/plugins/docker/workflow/FromFingerprintStep.java#L81]If you just pass the build-args to this step, the issue should be resolved.
[JIRA] (JENKINS-56294) dockerfile: ARG in FROM breaks docker inspect
Title: Message Title
Christian Ciach created an issue
Jenkins / JENKINS-56294
dockerfile: ARG in FROM breaks docker inspect
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2019-02-26 15:51
Environment:
docker-workflow 1.17, pipeline-model-definition 1.3.4.1, Jenkins 2.165
Priority:
Minor
Reporter:
Christian Ciach
Please note that there is already an issue with a very similar name regarding the docker-workflow plugin here: https://issues.jenkins-ci.org/browse/JENKINS-46105 The issue actually has been fixed already at the docker-workflow plugin, but the pipeline-model-definition-plugin fails to take advantage of that. The issue in a nutshell: I have this Dockerfile (excerpt):
ARG VERSION=latest
FROM repo-vp.development.ems:5000/emsys-adoptopenjdk11:${VERSION}
This is part of my declarative Jenkinsfile:
stage('Build') {
agent {
dockerfile {
filename 'Dockerfile'
additionalBuildArgs "--build-arg VERSION=jdk-11.0.2.9"
reuseNode true
}
}
steps {
(...)
}
}
This results in a failed build with
[JIRA] (JENKINS-56294) dockerfile: ARG in FROM breaks docker inspect
Title: Message Title
Christian Ciach updated an issue
Jenkins / JENKINS-56294
dockerfile: ARG in FROM breaks docker inspect
Change By:
Christian Ciach
Please note that there is already an issue with a very similar name regarding the docker-workflow plugin here: https://issues.jenkins-ci.org/browse/JENKINS-46105The issue actually has been fixed already at the docker-workflow plugin, but the pipeline-model-definition-plugin fails to take advantage of that.The issue in a nutshell:I have this Dockerfile (excerpt): {code:java}ARG VERSION=latestFROM repo-vp.development.ems:5000/emsys-adoptopenjdk11:${VERSION}{code} This is part of my declarative Jenkinsfile: {code:java}stage('Build') { agent { dockerfile { filename 'Dockerfile' additionalBuildArgs "--build-arg VERSION=jdk-11.0.2.9" reuseNode true} } steps {(...) }}{code} This results in a failed build with the following error log:{code:java}java.io.IOException: Cannot retrieve .Id from 'docker inspect repo-vp.development.ems:5000/emsys-adoptopenjdk11:${VERSION}' at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:220) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:133) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:85) 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}This has already been fixed by the docker-workflow plugin (see JENKINS-46105), but "pipeline-model-definition" has yet to take advantage of that.Please see this line in your plugin: [https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/7502d14aa4db891302abf48a2c7de7c9ced97f95/pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/DockerPipelineFromDockerfileScript.groovy#L83]As you can see, you don't pass the new parameter "buildArgs" to the instance of `dockerFingerprintFrom`. See the setter here: [https://github.com/jenkinsci/docker-workflow-plugin/blob/dbeb7cf23961fdb5cbc495e8067bd42c56dcdfc5/src/main/java/org/jenkinsci/plugins/docker/workflow/FromFingerprintStep.java#L81]If you just pass the build-args to this step, the issue should be resolved.
[JIRA] (JENKINS-56293) Unable to update or install plugins
Title: Message Title Luba Pyat created an issue Jenkins / JENKINS-56293 Unable to update or install plugins Issue Type: Bug Assignee: Nikolas Falco Components: core, nodejs-plugin, plugin-usage-plugin Created: 2019-02-26 15:47 Environment: windows Labels: plugin jenkins Priority: Critical Reporter: Luba Pyat We cannot upload ANY plugin to Jenkins. I tried NodesJS, GitHub, JIRA. My netops open the firewall to test but I got the same errors, so it is not a firewall. Please advice! Here is the errors: Failure -java.io.FileNotFoundException: http://updates.jenkins-ci.org/download/plugins/nodejs/1.2.7/nodejs.hpi at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(Unknown Source) at java.net.URLConnection.getHeaderFieldLong(Unknown Source) at java.net.URLConnection.getContentLengthLong(Unknown Source) at java.net.URLConnection.getContentLength(Unknown Source) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1125) Caused: java.io.FileNotFoundException: http://updates.jenkins
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Denis Zakharov commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Josh McDonald thank you. When can we get build with this 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-56281) missing changelog for 2.166
Title: Message Title Oleg Nenashev updated JENKINS-56281 Jenkins / JENKINS-56281 missing changelog for 2.166 Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved 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-56281) missing changelog for 2.166
Title: Message Title Oleg Nenashev updated JENKINS-56281 Fixed by Daniel Beck in https://github.com/jenkins-infra/jenkins.io/pull/2131 Jenkins / JENKINS-56281 missing changelog for 2.166 Change By: Oleg Nenashev Status: Open 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.
