[JIRA] (JENKINS-54839) Match Text not working on GitHub multibranch pipeline for PRs
Title: Message Title Tim Jacomb updated JENKINS-54839 Jenkins / JENKINS-54839 Match Text not working on GitHub multibranch pipeline for PRs Change By: Tim Jacomb Status: Fixed but Unreleased Closed Released As: 1.21 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-54839) Match Text not working on GitHub multibranch pipeline for PRs
Title: Message Title Tim Jacomb updated JENKINS-54839 Jenkins / JENKINS-54839 Match Text not working on GitHub multibranch pipeline for PRs Change By: Tim Jacomb Status: In Review 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-56077) New Stapler routing rules result in the URL "/descriptorByName/com.microsoft.azure.vmagent.AzureVMAgentTemplate/fillAvailabilityTypeItems" no longer being allowed.
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-56077 New Stapler routing rules result in the URL "/descriptorByName/com.microsoft.azure.vmagent.AzureVMAgentTemplate/fillAvailabilityTypeItems" no longer being allowed. Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2019-02-11 08:04 Environment: jenkins: 2.150.2 azure-vm-agents:0.8.0 Priority: Minor Reporter: Tim Jacomb Every refresh of the /configure page shows the following warning: Feb 11, 2019 7:56:53 AM jenkins.security.stapler.StaplerFilteredActionListener onDoActionTrigger jenkins| WARNING: New Stapler routing rules result in the URL "/descriptorByName/com.microsoft.azure.vmagent.AzureVMAgentTemplate/fillAvailabilityTypeItems" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "method com.microsoft.azure.vmagent.AzureVMAgentTemplate$DescriptorImpl doFillAvailabilityTypeItems". Learn more: https://jenkins.io/redirect/stapler-routing
[JIRA] (JENKINS-54159) Support configuration as code plugin
Title: Message Title Tim Jacomb commented on JENKINS-54159 Re: Support configuration as code plugin Hi Jie Shen is there any progress on this? It's our last plugin that isn't compatible, and we would love to get it sorted. 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-54159) Support configuration as code plugin
Title: Message Title Tim Jacomb commented on JENKINS-54159 Re: Support configuration as code plugin Hi Jie Shen is there any progress on this? It's our last plugin that isn't compatible, and we would love to get it sorted. 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-56078) Documentation uses wrong pmd command
Title: Message Title
Bukama Marenellin created an issue
Jenkins / JENKINS-56078
Documentation uses wrong pmd command
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-02-11 08:10
Environment:
warnings-n-g-plugin 2.2.1
Labels:
pipeline
Priority:
Minor
Reporter:
Bukama Marenellin
I'm testing the new warning plugin (2.2.1) to prepare for migration our pipelines and jobs to it. For this I've created thze following pipeline. To do my first steps I used the examples given in the documentation: https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#advanced-pipeline-configuration There, for PMD reports, the following example is shown: def pmd = scanForIssues tool: pmd(pattern: '**/target/pmd.xml') {{ publishIssues issues: [pmd]}} Trying to execute this ended in a NPE. After some hours of searching I found that this is caused by the (still installed) "old" PMD-plugin (see #JENKINS-55328). But until I found this JIRA-Ticket I found that in the jenkins step documention there is no step "pmd" but a step called "pmdParser" and using this worked. https://jenkins.io/doc/pipeline/steps/warnings-ng/#scanforissues-scan-files-or-the-console-log-for-warnings-or-issues So I suggest to update the documentation and correct this mistake / add a hint as it is very misleading for beginners.
[JIRA] (JENKINS-56078) Documentation uses wrong pmd command
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-56078 Documentation uses wrong pmd command Change By: Ulli Hafner Status: Open 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-56072) Jenkins Job failed - pipeline-maven-plugin
Title: Message Title sharon mordechai commented on JENKINS-56072 Re: Jenkins Job failed - pipeline-maven-plugin Hi, I just want to confirm with you that this bug will not effect the other pipelines in this Jenkins, becuase currently there're a lot of pipelines of the other teams here and they're working fine! this bug is only on my pipeline. can you please confirm it won't effect the others ? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56072) Jenkins Job failed - pipeline-maven-plugin
Title: Message Title sharon mordechai updated JENKINS-56072 Jenkins / JENKINS-56072 Jenkins Job failed - pipeline-maven-plugin Change By: sharon mordechai Status: Open Fixed but Unreleased Resolution: Won't Do 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-56078) Documentation uses wrong pmd command
Title: Message Title Bukama Marenellin commented on JENKINS-56078 Re: Documentation uses wrong pmd command Created a PR for this small fix: https://github.com/jenkinsci/warnings-ng-plugin/pull/9 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56072) Jenkins Job failed - pipeline-maven-plugin
Title: Message Title sharon mordechai edited a comment on JENKINS-56072 Re: Jenkins Job failed - pipeline-maven-plugin Hi, I just want There's no need to confirm with you that this bug will not effect the other pipelines in this Jenkins fix enything , becuase currently there're a lot of pipelines of the other teams here and they're working fine! this bug is only on my pipeline.can you please confirm it won pipelins isn 't effect the others ? productive. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56079) Passing the wrong directories to Bootstrap ends in a unhelpful ClassNotFoundException
Title: Message Title Carlos Sanchez created an issue Jenkins / JENKINS-56079 Passing the wrong directories to Bootstrap ends in a unhelpful ClassNotFoundException Issue Type: Improvement Assignee: Carlos Sanchez Components: jenkinsfile-runner Created: 2019-02-11 08:42 Priority: Minor Reporter: Carlos Sanchez When building projects on top of jenkinsfile-runner if you pass the wrong directories it just thows ClassNotFoundException with no hints to what's wrong eg. https://github.com/carlossg/jenkinsfile-runner-lambda/blob/master/src/main/java/org/csanchez/jenkins/lambda/Handler.java#L172 Add Comment
[JIRA] (JENKINS-56079) Passing the wrong directories to Bootstrap ends in a unhelpful ClassNotFoundException
Title: Message Title Carlos Sanchez updated JENKINS-56079 Jenkins / JENKINS-56079 Passing the wrong directories to Bootstrap ends in a unhelpful ClassNotFoundException Change By: Carlos Sanchez 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-56079) Passing the wrong directories to Bootstrap ends in a unhelpful ClassNotFoundException
Title: Message Title Carlos Sanchez started work on JENKINS-56079 Change By: Carlos Sanchez 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-56080) Publish jenkinsfile-runner docker images to docker hub
Title: Message Title Carlos Sanchez created an issue Jenkins / JENKINS-56080 Publish jenkinsfile-runner docker images to docker hub Issue Type: Improvement Assignee: Unassigned Components: jenkinsfile-runner Created: 2019-02-11 08:53 Priority: Minor Reporter: Carlos Sanchez There are several images published but none official. A docker auto build could be enough Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56046) FATAL: Remote call on Slave failed
Title: Message Title Oleg Nenashev commented on JENKINS-56046 Re: FATAL: Remote call on Slave failed I believe this is a duplicate of JENKINS-46523 which was fixed in 2.144 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-56081) Slave node environment path is duplicated
Title: Message Title
Wim Bekker created an issue
Jenkins / JENKINS-56081
Slave node environment path is duplicated
Issue Type:
Bug
Assignee:
Giuseppe Landolfi
Components:
slave-setup-plugin
Created:
2019-02-11 09:12
Environment:
Jenkins ver. 2.150.2 Windows 10 pro Environment injector plugin 2.1.6
Priority:
Minor
Reporter:
Wim Bekker
When running a slave with the path set in environment variables the (added) path is duplicated. Steps
Created a slave to run on localhost by Java Web Start.
Add node properties environment variables, name: Path value: $Path;X;Y;Z
Run pipeline job that displays the path
Expected To see the path ending with ;X;Y;Z Actual The path ends with :X;Y;Z;X;Y;Z
pipeline {
agent {
label 'slave-1'
}
stages {
stage('path') {
steps {
bat('path')
}
} //stage
} //stages
} //pipeline
[JIRA] (JENKINS-56046) FATAL: Remote call on Slave failed
Title: Message Title Adrien Lecharpentier updated an issue Jenkins / JENKINS-56046 FATAL: Remote call on Slave failed Change By: Adrien Lecharpentier Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56046) FATAL: Remote call on Slave failed
Title: Message Title Adrien Lecharpentier updated JENKINS-56046 Resolve as duplicate. Jenkins / JENKINS-56046 FATAL: Remote call on Slave failed Change By: Adrien Lecharpentier 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-56046) FATAL: Remote call on Slave failed
Title: Message Title Adrien Lecharpentier updated JENKINS-56046 Jenkins / JENKINS-56046 FATAL: Remote call on Slave failed Change By: Adrien Lecharpentier 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-55150) [jenkins-dev] jenkins-dev:run no longer has hot reload after 2.152
Title: Message Title Adrien Lecharpentier updated an issue Jenkins / JENKINS-55150 [jenkins-dev] jenkins-dev:run no longer has hot reload after 2.152 Change By: Adrien Lecharpentier Labels: DEVTOOLS java11 java11-compatibility regression triaged 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-56079) Passing the wrong directories to Bootstrap ends in a unhelpful ClassNotFoundException
Title: Message Title Adrien Lecharpentier updated an issue Jenkins / JENKINS-56079 Passing the wrong directories to Bootstrap ends in a unhelpful ClassNotFoundException Change By: Adrien Lecharpentier Labels: triaged 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-56080) Publish jenkinsfile-runner docker images to docker hub
Title: Message Title Adrien Lecharpentier assigned an issue to Evaristo Gutierrez Jenkins / JENKINS-56080 Publish jenkinsfile-runner docker images to docker hub Change By: Adrien Lecharpentier Assignee: Evaristo Gutierrez 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-56080) Publish jenkinsfile-runner docker images to docker hub
Title: Message Title Adrien Lecharpentier updated an issue Jenkins / JENKINS-56080 Publish jenkinsfile-runner docker images to docker hub Change By: Adrien Lecharpentier Labels: triaged 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-14530) Allow to upgrade/downgrade to any plugin version
Title: Message Title Gary Watson commented on JENKINS-14530 Re: Allow to upgrade/downgrade to any plugin version Just encountered a major issue with auto-upgrading plugins in Jenkins. We were unable to workaround by downgrading in the Jenkins UI. This issue was created nearly 7 years ago and nothing done! Either specify why this is not achievable or state the steps required and schedule. 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-56033) plugin issue with the jenkins all the jobs are failing
Title: Message Title Baptiste Mathus closed an issue as Not A Defect Jenkins / JENKINS-56033 plugin issue with the jenkins all the jobs are failing Change By: Baptiste Mathus 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-56033) plugin issue with the jenkins all the jobs are failing
Title: Message Title Baptiste Mathus commented on JENKINS-56033 Re: plugin issue with the jenkins all the jobs are failing Which version of parameterized scheduler plugin were you using? Indeed, latest release require 1.642.3. You seem to have installed the Pipeline suite, but WorkflowRun also requires Jenkins 2.121.1 or higher (cf. https://github.com/jenkinsci/workflow-job-plugin/blob/master/pom.xml#L67). AFAICT, this is not a bug. Going to close as such. Please use the users Mailing list (https://jenkins.io/mailing-lists/) to get help. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52284) Java 11: Support in LTS
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52284 Java 11: Support in LTS Change By: Oleg Nenashev Epic Name: Java 11 Support in JDK11- LTS -GA 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-51990) Running docker Image build with plugins.txt produces warnings in the Java 10 base image
Title: Message Title Baptiste Mathus closed an issue as Fixed Will be fixed once 2.164 is released (expected later today). Oleg Nenashev can you add a link to the right Jenkins JIRAs for completeness and cross-referencing? Spassiba Jenkins / JENKINS-51990 Running docker Image build with plugins.txt produces warnings in the Java 10 base image Change By: Baptiste Mathus Status: Open Closed 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-51998) Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller
Title: Message Title Baptiste Mathus closed an issue as Fixed Considering this fixed given it didn't resurface since early December 2018. Jenkins / JENKINS-51998 Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller Change By: Baptiste Mathus Status: Reopened Closed 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-47827) Support passing a user/uid into containerTemplate
Title: Message Title Carlos Sanchez commented on JENKINS-47827 Re: Support passing a user/uid into containerTemplate Feel free to open 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-52285) Extras Executable WAR: Allow running with JDK 11 without "--enable-future-java"
Title: Message Title Baptiste Mathus updated JENKINS-52285 Jenkins / JENKINS-52285 Extras Executable WAR: Allow running with JDK 11 without "--enable-future-java" Change By: Baptiste Mathus Status: In Review 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-52285) Extras Executable WAR: Allow running with JDK 11 without "--enable-future-java"
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-52285 Extras Executable WAR: Allow running with JDK 11 without "--enable-future-java" Change By: Baptiste Mathus Released As: 2.164 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-52309) Release Candidate Testing: Run ATH of Jenkins WAR with Java 11 support
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-52309 Release Candidate Testing: Run ATH of Jenkins WAR with Java 11 support Change By: Baptiste Mathus h3. Acceptance criteria* Run ATH over release candidate with all the changes (might be 2.164) 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-55096) can not override jnlp container
Title: Message Title Carlos Sanchez closed an issue as Not A Defect Jenkins / JENKINS-55096 can not override jnlp container Change By: Carlos Sanchez 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-52309) Release Candidate Testing: Run ATH of Jenkins WAR with Java 11 support
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-52309 Release Candidate Testing: Run ATH of Jenkins WAR with Java 11 support Change By: Baptiste Mathus * h3. Acceptance criteria * * ** Run ATH over release candidate with all the changes 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-55096) can not override jnlp container
Title: Message Title Carlos Sanchez commented on JENKINS-55096 Re: can not override jnlp container you are overriding the jnlp container in your pod template, so that's the one that gets picked up, with no env vars 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-56080) Publish jenkinsfile-runner docker images to docker hub
Title: Message Title Evaristo Gutierrez commented on JENKINS-56080 Re: Publish jenkinsfile-runner docker images to docker hub Carlos Sanchez which is your use case for this? I don't think it makes much sense as per the current use cases that were taken into account. The idea for that Dockerfile is allow custom configurations through the plugins.txt file and an specific Jenkins version, so I don't think it makes much sense to publish a specific Docker image with a closed set of plugins. 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-52310) Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-52310 Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support Change By: Baptiste Mathus Component/s: blueocean-plugin Component/s: core 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-52309) Release Candidate Testing: Run ATH of Jenkins WAR with Java 11 support
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-52309 Release Candidate Testing: Run ATH of Jenkins WAR with Java 11 support Change By: Baptiste Mathus Labels: java11 java11-compatibility scrub triaged 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-52310) Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support
Title: Message Title Baptiste Mathus commented on JENKINS-52310 Re: Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support Not sure who this will be handled by. And if we even do it. To be discussed with Blue Ocean team possibly... 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-52310) Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support
Title: Message Title Baptiste Mathus assigned an issue to Gavin Mogan Jenkins / JENKINS-52310 Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support Change By: Baptiste Mathus Assignee: Gavin Mogan 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-56082) Merge yaml from parent pod template
Title: Message Title Carlos Sanchez assigned an issue to Unassigned Jenkins / JENKINS-56082 Merge yaml from parent pod template Change By: Carlos Sanchez Assignee: Carlos Sanchez 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-56082) Merge yaml from parent pod template
Title: Message Title Carlos Sanchez created an issue Jenkins / JENKINS-56082 Merge yaml from parent pod template Issue Type: New Feature Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-02-11 10:19 Priority: Minor Reporter: Carlos Sanchez The yaml field in pod template overrides the parent yaml, it is not merged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-52310) Release Candidate Testing: Run BlueOcean ATH of Jenkins WAR with Java 11 support
Title: Message Title Baptiste Mathus started work on JENKINS-52310 Change By: Baptiste Mathus 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-56061) Containers created in templates via Raw Yaml are completely ignored
Title: Message Title Carlos Sanchez commented on JENKINS-56061 Re: Containers created in templates via Raw Yaml are completely ignored yaml is not merged 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-56061) Containers created in templates via Raw Yaml are completely ignored
Title: Message Title Carlos Sanchez closed an issue as Duplicate Jenkins / JENKINS-56061 Containers created in templates via Raw Yaml are completely ignored Change By: Carlos Sanchez Status: Open Closed 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-53686) Kubernetes plugin documentation regarding YAML and merge seems contradictory
Title: Message Title Carlos Sanchez closed an issue as Duplicate tracking it in JENKINS-56082 Jenkins / JENKINS-53686 Kubernetes plugin documentation regarding YAML and merge seems contradictory Change By: Carlos Sanchez Status: Open Closed 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-53510) Nested podTemplate doesn't work correctly with yaml
Title: Message Title Carlos Sanchez closed an issue as Duplicate Jenkins / JENKINS-53510 Nested podTemplate doesn't work correctly with yaml Change By: Carlos Sanchez Status: Open Closed 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-52312) Release Candidate Testing; Run PCT against plugins recommended in the Jenkins installation wizard
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-52312 Release Candidate Testing; Run PCT against plugins recommended in the Jenkins installation wizard Change By: Baptiste Mathus Labels: java11 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-56080) Publish jenkinsfile-runner docker images to docker hub
Title: Message Title Carlos Sanchez commented on JENKINS-56080 Re: Publish jenkinsfile-runner docker images to docker hub we can publish one with the minimal set of plugins, people can extend and add plugins. Right now everybody needs to build their own image from scratch even if they just want 1 more 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-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-54305 Oracle JDK 10 not available anymore - Oracle JDK 11 is not free Change By: Baptiste Mathus Assignee: Ramon Leon 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-56083) pmd warnings trend disappear if the last build doesn't record issues
Title: Message Title Andrea me created an issue Jenkins / JENKINS-56083 pmd warnings trend disappear if the last build doesn't record issues Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-02-11 10:27 Priority: Minor Reporter: Andrea me I have configured my build to run and check PMD only for certain situations. Before Warnings Next Generation plugin, the graph were always shown, even when pmd were not executed. Also the link "PMD Warnings" on the top left area is not shown. I suspect that "test result trend" have the same problem, and maybe others like checkstyle etc. Add Comment
[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title Baptiste Mathus commented on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free More and more inclined to say this feature anyway was nice for demos, but for real usage should not be used. Because it means your internal servers are constantly downloading binaries from outside. It can end up with your company network being banned for excessive bandwidth consumption in case of public network glitch, all your builds start to die 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-55085) Revert the Java 11 Experimental Update Center patches in the core
Title: Message Title Baptiste Mathus updated JENKINS-55085 Jenkins / JENKINS-55085 Revert the Java 11 Experimental Update Center patches in the core Change By: Baptiste Mathus Status: In Review Closed Resolution: Fixed Released As: 2.164 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-55087) Revert the Java 11 Experimental Update Center patches in the Docker image
Title: Message Title Baptiste Mathus updated JENKINS-55087 Jenkins / JENKINS-55087 Revert the Java 11 Experimental Update Center patches in the Docker image Change By: Baptiste Mathus Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.164 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-55085) Revert the Java 11 Experimental Update Center patches in the core
Title: Message Title Baptiste Mathus updated JENKINS-55085 Jenkins / JENKINS-55085 Revert the Java 11 Experimental Update Center patches in the core Change By: Baptiste Mathus Status: Closed Fixed but Unreleased 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-55101) Create official Java 11 Docker Packaging for BlueOcean
Title: Message Title Baptiste Mathus commented on JENKINS-55101 Re: Create official Java 11 Docker Packaging for BlueOcean Not marking yet as WONTFIX, but I think this is where we are leaning towards. 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-55172) PCT on Java 11 shows issues for JNLP4 protocol initialization
Title: Message Title Baptiste Mathus closed an issue as Cannot Reproduce Oleg tried to reproduce, but couldn't make this reappear. So we're closing it for now at least as cannot reproduce. This is still concerning, given this relates to encryption, so we'll reopen and work on this as soon as/if this resurfaces as actual. Jenkins / JENKINS-55172 PCT on Java 11 shows issues for JNLP4 protocol initialization Change By: Baptiste Mathus Status: Open Closed Resolution: Cannot Reproduce 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-55176) Variant Plugin: PCT fails when running with Java 11
Title: Message Title Baptiste Mathus started work on JENKINS-55176 Change By: Baptiste Mathus 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-55176) Variant Plugin: PCT fails when running with Java 11
Title: Message Title Baptiste Mathus updated JENKINS-55176 Jenkins / JENKINS-55176 Variant Plugin: PCT fails when running with Java 11 Change By: Baptiste Mathus 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-55176) Variant Plugin: PCT fails when running with Java 11
Title: Message Title Baptiste Mathus commented on JENKINS-55176 Re: Variant Plugin: PCT fails when running with Java 11 Fix in https://github.com/jenkinsci/variant-plugin/pull/3 should be tested with PCT in source mode (to test the current tip of master) 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-55233) email-ext: PowerMock is not compatible with Java 11
Title: Message Title Baptiste Mathus updated JENKINS-55233 Jenkins / JENKINS-55233 email-ext: PowerMock is not compatible with Java 11 Change By: Baptiste Mathus Status: In Review 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-55391) Merge jenkins.sh and jenkins-jdk11.sh files
Title: Message Title Baptiste Mathus updated JENKINS-55391 File removed by Oleg in https://github.com/jenkinsci/docker/pull/798 Jenkins / JENKINS-55391 Merge jenkins.sh and jenkins-jdk11.sh files Change By: Baptiste Mathus 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-55303) [PCT] jenkins-test-harness - Using JDK internal classes
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55303 [PCT] jenkins-test-harness - Using JDK internal classes Change By: Baptiste Mathus Summary: [PCT] jenkins-test-harness - Using JDK internal classes 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-46354) Retry in Declarative options skips retried stages due to earlier failure
Title: Message Title Atharva Inamdar commented on JENKINS-46354 Re: Retry in Declarative options skips retried stages due to earlier failure Is there any update on this issue? Or a workaround until this is 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-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository
Title: Message Title Fran Aguiar commented on JENKINS-22752 Re: Initial poll (just after project creation) spawns builds for all the existing branches in repository Any workaround to avoid this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56084) High CPU usage when loading robot page with high fail count
Title: Message Title Chris Law created an issue Jenkins / JENKINS-56084 High CPU usage when loading robot page with high fail count Issue Type: Bug Assignee: jpiironen Components: robot-plugin Created: 2019-02-11 11:44 Environment: Jenkins 2.89.2 robot plugin 1.6.4 Priority: Minor Reporter: Chris Law I'm not the jenkins admin of this instance, so I'm limited to what I can do However, we use the robot plugin to report on test results. Recently, we had some builds fail a lot of the test suites (39 suites, 35 ish fails each run). Loading the /robot page for one of these takes between a minute to a minute and a half. My best guess is that is' due to the large number of fails - the build immediately prior to the fails starting (and normal useage) is that it takes at worst a few seconds to load. CPU is apparently jumping to 110% while it happens. Is there anything I can gather (as a user) that would help, or do I need to ask the admins to get any data? Add Comment
[JIRA] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository
Title: Message Title Robert Churchill commented on JENKINS-22752 Re: Initial poll (just after project creation) spawns builds for all the existing branches in repository I've not tried this, but you could look at "Additional behaviours" > "Strategy for choosing what to build" > "Maximum age of commit" to limit what is getting built. 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-56085) GNU Make + GCC warnings parser missing from warnings next gen plugin
Title: Message Title Øyvind R created an issue Jenkins / JENKINS-56085 GNU Make + GCC warnings parser missing from warnings next gen plugin Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-02-11 12:14 Priority: Minor Reporter: Øyvind R In the old warnings plugin, there is a parser option for parsing warnings from the combination GNU make + GCC. This parser seems to no longer be available in the next-gen plugin. Add Comment This message was sent by Atlassian Jir
[JIRA] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository
Title: Message Title Fran Aguiar commented on JENKINS-22752 Re: Initial poll (just after project creation) spawns builds for all the existing branches in repository Perfect! I set "Maximum age of commit" to 1 day and works like a charm. I want to build and test current working branches, so that solution is perfect for me. 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-56086) Tabs missing in configuration page after adding plot to freestyle job
Title: Message Title Michał Marcinkowski updated an issue Jenkins / JENKINS-56086 Tabs missing in configuration page after adding plot to freestyle job Change By: Michał Marcinkowski Summary: Tabs missing in configuration page after adding plot to freestyle job configuration 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-56086) Tabs missing in configuration page after adding plot to freestyle job configuration
Title: Message Title Michał Marcinkowski created an issue Jenkins / JENKINS-56086 Tabs missing in configuration page after adding plot to freestyle job configuration Issue Type: Bug Assignee: Veaceslav Gaidarji Attachments: After_adding_plot.png, Before_adding_plot.png Components: plot-plugin Created: 2019-02-11 12:50 Environment: Jenkins 2.150.2 Priority: Minor Reporter: Michał Marcinkowski I have an issue with job's configure view. I've created freestyle project. No changes at all. After adding to "Post-build actions" new "Plot Build Data" everything seems OK. But when I saved the configuration and re-open configure view I cannot see the top (navigation) tabs in the page. Please see the attached screenshots. Best Regards Add Comment
[JIRA] (JENKINS-56076) Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin
Title: Message Title Mark Waite commented on JENKINS-56076 Re: Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin Possibly related to the pull request from Nicolas De Loof to fix the execution location or remoting location of portions of the git plugin or git client plugin? I don't plan to work on this anytime soon since my focus is on the BuildData bloat fix and the JGit improvements in git plugin 4.0.0 and git client 3.0.0. Pull requests will be happily considered with tests to duplicate the problem and an implementation to fix the tests and solve the bug. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56076) Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-56076 Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Fabrice Pipart commented on JENKINS-50429 Re: Shell command are really slower than before Good news! I managed to solve the issue with a fix. I tried to avoid using reflection but did not manage to get it working. That would probably have required too many changes in the code of the plugin. In order to keep the change minimal, I used two lines of reflection. Object sink = FieldUtils.readField(watch.getInput(), "sink", true ); FieldUtils.writeField(sink, "buffer", new byte[8192 * 1024], true); Not very sexy honestly. But my execution was 1m43 and is now 8s ... 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-56076) Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin
Title: Message Title Nicolas De Loof commented on JENKINS-56076 Re: Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin issue known for a long time (already reported on docker-slaves-plugin) see https://github.com/jenkinsci/git-client-plugin/pull/219 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-55096) can not override jnlp container
Title: Message Title Ian Tewksbury commented on JENKINS-55096 Re: can not override jnlp container Carlos Sanchez I don't understand why you closed this? > you are overriding the jnlp container in your pod template, so that's the one that gets picked up, with no env vars the problem is that I am overriding the JNLP container in my pod template in the declarative pipeline, and that is not the one that is getting picked up, I am always getting the default JNLP container. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title benoit guerin commented on JENKINS-54305 Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free Files downloaded from oracle.com are cached in a folder on the master (~/cache/jdks) ... Maybe you can ask the community if this feature is used / usefull or not. 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-55096) can not override jnlp container
Title: Message Title Carlos Sanchez commented on JENKINS-55096 Re: can not override jnlp container That was for Dmitry yaml is not merged with parent and then UI defined containers take precedence over yaml defined containers You can't mix UI inheritance with overriding yaml fields, you need to override using containerTemplate 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-52232) Credentials not usable after upgrade to 1.14
Title: Message Title Wadeck Follonier commented on JENKINS-52232 Re: Credentials not usable after upgrade to 1.14 After the new tickets opened, I re-try to reproduce the case with the new information. The migration of the credentials keys was meant to be done after InitMilestone.JOB_LOADED is triggered, from credentials, in SystemCredentialsProvider.forceLoadDuringStartup(). At this point the running user should be SYSTEM. I discovered that the migration could be triggered before, when the credentials are stored in folder, or when they are used in the configuration of an agent (like ssh-agents). But at this point, both migration were done using SYSTEM in my case and so, passing with success the permission check on RUN_SCRIPTS that was added especially for the security patch. So now, to go further, I need to have the logs from people that encountered the issues. Especially if they can reproduce the case, perhaps they could provide more information about all the plugins, the log file, the config file of their Jenkins, or anything else that could be useful (be careful to not upload credentials in plain text). What are you using as AuthorizationStrategy ? My hypothesis is something force the current running user to be anonymous instead of System during the startup/migration, (even temporally) and call the credentials while loading. "Call for witnesses" => People from this: Claudio B, Jon Brohauge, Stuart Whelan => People from JENKINS-54746: Florian Bäuerle, Darryl Pogue, Pieter-Jan Busschaert, Tom Ghyselinck, Makson Lee, Michael Mrozek, Torsten Landschoff, Matthew Stewart, Johannes Rudolph, Aaron Marasco, Beat Guggisberg => People from JENKINS-55971: Steve Graham 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.
[JIRA] (JENKINS-52232) Credentials not usable after upgrade to 1.14
Title: Message Title Nathan Neulinger commented on JENKINS-52232 Re: Credentials not usable after upgrade to 1.14 I had the same symptom - just been watching the issues here, have not tried re-updating since the last failure. In the first iteration, I didn't pay any active attention to log during upgrade itself, only noticed the resolve errors afterwards. In my case, using project matrix auth. Will try to see if symptom reproduces and capture some additional logs for you if so. 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-52232) Credentials not usable after upgrade to 1.14
Title: Message Title Wadeck Follonier commented on JENKINS-52232 Re: Credentials not usable after upgrade to 1.14 Nathan Neulinger That could be very very appreciated! I tried with project matrix auth without success (=migration was smooth). Could you give me insights about the structure of your instance ? Multiple folders ? restricted ones that are hiding some projects ? Credentials used at folders level ? Do you use internal credential provider or external ones ? Any information about your setup that is not "out of the box" will be useful 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-56087) Chanel name case sensitive error ignored
Title: Message Title
Lionel FÉLICITÉ created an issue
Jenkins / JENKINS-56087
Chanel name case sensitive error ignored
Issue Type:
Bug
Assignee:
Martin Reinhardt
Components:
rocket-chat-notifier-plugin
Created:
2019-02-11 13:55
Environment:
jenkins 2.155 + rocketchat plugin 1.3.2 + rocket.chat server 0.68.0 jenkins 2.160 + rocketchat plugin 1.3.2 + rocket.chat server 0.68.0 jenkins 2.160 + rocketchat plugin 1.4.2 + rocket.chat server 0.68.0
Priority:
Major
Reporter:
Lionel FÉLICITÉ
Hi, I have a local jenkins user on rocket.chat In global config ( https://jenkins/configure) when clicking on "Test connection" button, with my rocket.chat local user login & password ( no wenhook used):
Success is print
No message in my test channel
here's the ouput in jenkins.log
févr. 06, 2019 10:14:27 PM jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl sendSingleMessage
GRAVE: Could not send message: Response{success=false, messages=null, message=null, users=null, user=null, channels=null, channel=null, info=null}
févr. 06, 2019 10:14:27 PM jenkins.plugins.rocketchatnotifier.RocketClientImpl publish
GRAVE: I/O error error during publishing message
jenkins.plugins.rocketchatnotifier.rocket.errorhandling.RocketClientException: The send of the message was unsuccessful.
at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClient
[JIRA] (JENKINS-52232) Credentials not usable after upgrade to 1.14
Title: Message Title Nathan Neulinger commented on JENKINS-52232 Re: Credentials not usable after upgrade to 1.14 Gotta love when failure = working fine. No folders, all jobs visible to anonymous, but have a handful of jobs that are restricted from execution. Didn't look at credentials related to anything within the jobs - only for the agent connections. It's possible there was impact inside the jobs as well - didn't get that far when I saw the upgrade fail. Aside from sitting behind apache, and being in a different directory structure the instance should be pretty vanilla. 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-52232) Credentials not usable after upgrade to 1.14
Title: Message Title Nathan Neulinger commented on JENKINS-52232 Re: Credentials not usable after upgrade to 1.14 For the credentials for me - it's almost entirely pre-existing use of ~jenkins/.ssh/id_rsa that was affected. Very little use of built-in creds - and none at all of that for agent connections. 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-55934) Auditing/Logging plugin changes
Title: Message Title Shaheryar Mohammed updated an issue Jenkins / JENKINS-55934 Auditing/Logging plugin changes Change By: Shaheryar Mohammed Priority: Minor Major 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-55934) Auditing/Logging plugin changes
Title: Message Title Shaheryar Mohammed commented on JENKINS-55934 Re: Auditing/Logging plugin changes Looking for some help 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-55721) Amazon Ec2Plugin Enhancement Request
Title: Message Title max allan commented on JENKINS-55721 Re: Amazon Ec2Plugin Enhancement Request Can you use instance roles? Give the Jenkins EC2 master instance the role to create new instances etc... 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-21104) Confluence Publisher Plugin ignores Jenkins proxy settings
Title: Message Title sanjay dc commented on JENKINS-21104 Re: Confluence Publisher Plugin ignores Jenkins proxy settings Joe Hansche Joseph PetersenEven we have issues while publishing documents to confluence wiki. Our Jenkins setup is in public cloud, any corporate site access should go through proxy. Confluence plugin is not respecting proxies settings in Jenkins. Any help here is 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-55826) Add '-f' to 'p4 client -d' with cleanup/p4cleanup
Title: Message Title Charusheela Bopardikar updated JENKINS-55826 Jenkins / JENKINS-55826 Add '-f' to 'p4 client -d' with cleanup/p4cleanup Change By: Charusheela Bopardikar Resolution: Fixed Status: Fixed but Unreleased 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-55826) Add '-f' to 'p4 client -d' with cleanup/p4cleanup
Title: Message Title Charusheela Bopardikar commented on JENKINS-55826 Re: Add '-f' to 'p4 client -d' with cleanup/p4cleanup -f requires admin permission. Need to look for an alternative way to do this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55769) Tag match filter shows more entries than direct command (git tag -l "$tagFilter")
Title: Message Title Kevin Bowen commented on JENKINS-55769 Re: Tag match filter shows more entries than direct command (git tag -l "$tagFilter") Please note that using "git ls-remote -t" appears to return a lot more tag refs than the actual "git tags" command. The "tags" returned in this case are not always appropriate. The limited wildcarding for the command makes it impossible to filter out the inappropriate tags. Could a configurable regex be applied to the returned tags to address the issue? Thanks for the follow-up on 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-56030) NG Warnings doesn't see files that are there or cannot be fingerprinted
Title: Message Title Shannon Kerr commented on JENKINS-56030 Re: NG Warnings doesn't see files that are there or cannot be fingerprinted I'll look this morning. 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-55900) Java memory mishandling identified
Title: Message Title Daniel Beck stopped work on JENKINS-55900 Change By: Daniel Beck 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-55900) Java memory mishandling identified
Title: Message Title Daniel Beck commented on JENKINS-55900 Re: Java memory mishandling identified Yevhen Bulatnikov It's unclear whether this issue describes a real problem, especially given your recent update. Could you please clarify? 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-56088) FinishLogin throws: Illegal character in query at index 89
Title: Message Title
Davíð Jóhannsson created an issue
Jenkins / JENKINS-56088
FinishLogin throws: Illegal character in query at index 89
Issue Type:
Bug
Assignee:
Sam Gleske
Components:
github-oauth-plugin
Created:
2019-02-11 16:00
Environment:
jenkins 2.150.1 github-oauth-plugin 0.31 openjdk version "1.8.0_191"
Priority:
Minor
Reporter:
Davíð Jóhannsson
I login using my git credentials and when I get redirect back to my jenkins server it throws an error: java.net.URISyntaxException: Illegal character in query at index 89: https://github.com/login/oauth/access_token?client_id=ce1924515def5c76245d&client_secret=\{AQAAABAwkmNjAgFf7A65AKARYLRCIalS2emHy8D8tGNAM8TM7XI5ue+HH/sH/Os4gmOId4DlDRS1Hhd8FjapnIYez07yWg==}&code=4ac763e5f4023c8e12b6 at java.net.URI$Parser.fail(URI.java:2848) Full Stack Trace Feb 11 15:32:27 ip-10-252-132-29 java[9117]: Feb 11, 2019 3:32:27 PM hudson.util.Secret toString Feb 11 15:32:27 ip-10-252-132-29 java[9117]: WARNING: Use of toString() on hudson.util.Secret from java.lang.String.valueOf(String.java:2994). Prefer getPlainText() or getEncryptedValue() depending your needs. see https://jenkins.io/redirect/hudson.util.Secret/ Feb 11 15:32:27 ip-10-252-132-29 java[9117]: Feb 11, 2019 3:32:27 PM org.eclipse.jetty.server.handler.ContextHandler$Context log Feb 11 15:32:27 ip-10-252-132-29 java[9117]: WARNING: Error while serving https://deployment-setup.icelandairlabs.com/securityRealm/finishLogin Feb 11 15:32:27 ip-10-252-132-29 java[9117]: java.lang.reflect.InvocationTargetException Feb 11 15:32:27 ip-10-252-132-29 java[9117]: at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) Feb 11 15:32:27 ip-10-252-132-29 java[9117]: at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) Feb 11 15:32:27 ip-10-252
[JIRA] (JENKINS-40723) Built Dockerfile images are never removed
Title: Message Title Michael Harris commented on JENKINS-40723 Re: Built Dockerfile images are never removed Having some mechanism to delete the generated image is really important. If we have a lot of builds in a short time our nodes still run out of disk space before the scheduled job runs and wipes out old images. Jenkins is creating the images, and at a minimum needs to expose a way to clean up the image. Even if t was only added in the scripting syntax that would be sufficient. 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-40723) Built Dockerfile images are never removed
Title: Message Title Michael Harris edited a comment on JENKINS-40723 Re: Built Dockerfile images are never removed Having some mechanism to delete the generated image is really important. If we have a lot of builds in a short time our nodes still run out of disk space before the scheduled job runs and wipes out old images. Jenkins is creating the images, and at a minimum needs to expose a way to clean up the image. Even if t it was only added in the [scripting syntax|https://jenkins.io/doc/book/pipeline/docker/#building-containers] that would be sufficient. 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-55721) Amazon Ec2Plugin Enhancement Request
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-55721 Re: Amazon Ec2Plugin Enhancement Request To raise new nodes from jenkins in the AWS is not need to login in the console and use login and password. In jenkins you need only the access key and secret key of a user that is able to raise node, the api interface doesn't require the OTP (MFA), you don't have to use the username and password, and jenkins doesn't need it (it doesn't loggin in the console to raise node). My suggestion is to create a bot user in the account where no one can logging, with the right role and access key/ secret key. 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.
