[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 Jenkins Health Advisor requires to restart the instance to be activated Change By: Arnaud Héritier Attachment: Screenshot 2019-10-16 08.57.20.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8490.1571209200250%40Atlassian.JIRA.
[JIRA] (JENKINS-59795) Option to skip any builds after indexing multibranch pipeline.
Title: Message Title Karl Wirth commented on JENKINS-59795 Re: Option to skip any builds after indexing multibranch pipeline. Hi Joel Brown - Can you please look into the answer in this article. It's possible this mechanism would need to be outside P4-Jenkins: https://stackoverflow.com/questions/44004636/jenkins-multibranch-pipeline-scan-without-execution Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202525.1571173727000.8492.1571209200301%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 Jenkins Health Advisor requires to restart the instance to be activated Change By: Arnaud Héritier Attachment: Screenshot 2019-10-16 09.00.42.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8494.1571209320747%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier stopped work on JENKINS-59696 Change By: Arnaud Héritier Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8497.1571209982133%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: Jenkins Health Advisor requires to restart the instance to be activated I did a lot of manual tests and the problem is always when support-core isn't yet installed. The problem isn't directly in advisor Ryan Campbell Otherwise we will have to see with Allan BURDAJEWICZ if we can isolate/fix the issue in support-core. The only thing I could try to do at the advisor level is to catch this error and ask to the administrator to restart the instance. For now the user is seeing this generic error in the Advisor config panel: And this warning monitor (note to myself: they should be unified ...) Note, that as soon the support-core is installed but the instance not restarted the logs are polluted with these errors Oct 16, 2019 8:49:05 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@2656884b failed java.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) 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) Oct 16, 2019 8:49:08 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@2656884b failed java.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.la
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 Jenkins Health Advisor requires to restart the instance to be activated Change By: Arnaud Héritier Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8500.1571210400360%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core requires to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 support-core requires to restart the instance to be activated Change By: Arnaud Héritier Summary: Jenkins Health Advisor support-core requires to restart the instance to be activated Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8501.1571210400374%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 support-core and thus advisor require to restart the instance to be activated Change By: Arnaud Héritier Summary: support-core requires and thus advisor require to restart the instance to be activated Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8503.1571211060262%40Atlassian.JIRA.
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier updated JENKINS-59767 Jenkins / JENKINS-59767 Replace the comma separated list for CC by a list of emails Change By: Arnaud Héritier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202490.1570998849000.8507.1571212200233%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Arnaud Héritier assigned an issue to Unassigned Jenkins / JENKINS-59696 support-core and thus advisor require to restart the instance to be activated Change By: Arnaud Héritier Assignee: Arnaud Héritier Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8506.1571212200214%40Atlassian.JIRA.
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier commented on JENKINS-59767 Re: Replace the comma separated list for CC by a list of emails https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/pull/55 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202490.1570998849000.8508.1571212260051%40Atlassian.JIRA.
[JIRA] (JENKINS-59784) Unable to view a pdf file from jenkins workspace
Title: Message Title Daniel Beck commented on JENKINS-59784 Re: Unable to view a pdf file from jenkins workspace When you said alternative you meant that we can relax the rule set right with the help fo this doc No, but if you actually read today's version of that wiki page it'll point out the alternative Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202514.1571129142000.8511.1571213640138%40Atlassian.JIRA.
[JIRA] (JENKINS-59799) Build Job Hangs Intermittently
Title: Message Title richard clegg created an issue Jenkins / JENKINS-59799 Build Job Hangs Intermittently Issue Type: Bug Assignee: Daniel Spilker Attachments: console.txt.txt, threaddumpafterjenkinsrestart.txt, threaddumpatstall.txt Components: core, job-dsl-plugin Created: 2019-10-16 08:24 Environment: Jenkins 2.176.2, linux centos 7, chrome Priority: Major Reporter: richard clegg Triggered job will occasionally hang at start, which can only be fixed by cancelling or restarting jenkins(in which case the job will run). The job is written in DSL and is triggered by a DSL job and it appears to happening more often. I attach the job symptoms and thread dumps. this is preventing our development pipelines from completing consistently. Add Comment
[JIRA] (JENKINS-59716) Variables in Workspace name returns actual date
Title: Message Title Grzesiek a updated an issue Jenkins / JENKINS-59716 Variables in Workspace name returns actual date Change By: Grzesiek a Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202428.1570632779000.8516.1571214900368%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Mathieu Delrocq updated an issue Jenkins / JENKINS-59790 Container cannot connect to node because it doesn't exist Change By: Mathieu Delrocq Priority: Critical Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.8526.1571218740796%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Philip Johnson commented on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. I wish I'd backed up that failure analyzer xml file. Dozens of causes lost . Anyone know if they'd be stored anywhere else? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202251.1569939008000.8519.1571218740646%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Mathieu Delrocq updated an issue Jenkins / JENKINS-59790 Container cannot connect to node because it doesn't exist Change By: Mathieu Delrocq Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.8532.1571218800768%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Mathieu Delrocq updated an issue Jenkins / JENKINS-59790 Container cannot connect to node because it doesn't exist Change By: Mathieu Delrocq Priority: Blocker Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.8534.1571218800804%40Atlassian.JIRA.
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title David Riemens commented on JENKINS-26138 Re: Support workspaces for Pipeline jobs Devin Nusbaum : can you point me to an example to "create a new step that looks through enclosing blocks for WorkspaceAction and uses that to return or print a link to the logs" ? I would not have an idea how to get that. For now I implemented a dirty workaround: I made a script that fetches (wget) the .../lastBuild/flowGraphTable page, and extracts the lines have the info that I need. This script I call from my job and generate a table of the numbers (the ID's) that I need. This is obviously far from perfect, but hopefully is sort of auto-correcting. I still am hoping for a simple currentBuild.Info.something.ID solution ... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159718.141883805.8538.1571219882387%40Atlassian.JIRA.
[JIRA] (JENKINS-59800) Overlapping Multiline Headlines in the 'Create Admin User' view
Title: Message Title Andreas Pabst created an issue Jenkins / JENKINS-59800 Overlapping Multiline Headlines in the 'Create Admin User' view Issue Type: Bug Assignee: Andreas Pabst Attachments: Bildschirmfoto am 2019-10-16 um 12.04.58.png Components: core Created: 2019-10-16 10:19 Environment: Jenkins version 2.201-SNAPSHOT Priority: Minor Reporter: Andreas Pabst In the 'Create Admin User' view at the beginning of setting up Jenkins, the headlines are overlapping if they span over more than one line. This is e.g. the case for the German version (see screenshot below) Add Comment
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Philip Johnson updated an issue Jenkins / JENKINS-59610 Build failure causes are deleted when saving Jenkins global configuration. Change By: Philip Johnson Comment: I wish I'd backed up that failure analyzer xml file. Dozens of causes lost :(. Anyone know if they'd be stored anywhere else? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202251.1569939008000.8664.1571221980531%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Tomas Westling updated JENKINS-59610 Jenkins / JENKINS-59610 Build failure causes are deleted when saving Jenkins global configuration. Change By: Tomas Westling Status: In Review Closed Resolution: Done Released As: 1.23.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202251.1569939008000.8671.1571222580558%40Atlassian.JIRA.
[JIRA] (JENKINS-59593) enableStatistics and successfulLogging config values are not loaded properly
Title: Message Title Tomas Westling updated JENKINS-59593 Jenkins / JENKINS-59593 enableStatistics and successfulLogging config values are not loaded properly Change By: Tomas Westling Status: In Review Closed Resolution: Fixed Released As: 1.23.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202234.1569877154000.8678.1571222640230%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Manuel Hampp started work on JENKINS-59665 Change By: Manuel Hampp Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.8682.1571222700244%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Manuel Hampp assigned an issue to Manuel Hampp Jenkins / JENKINS-59665 Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager Change By: Manuel Hampp Assignee: Manuel Hampp Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.8680.1571222700218%40Atlassian.JIRA.
[JIRA] (JENKINS-59754) Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines
Title: Message Title Radi Berkovich commented on JENKINS-59754 Re: Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines HI. I need more information - what is not working after some time? In log file , I see that relogins are succedded. The best will be , if you encounter you problem - take logs file and give me the time it happen, so it will be easier to search relevant log rows. Thanks. Radi. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202477.1570821116000.8684.1571224200132%40Atlassian.JIRA.
[JIRA] (JENKINS-59801) the input device is not a TTY
Title: Message Title Gugulethu Mabaso created an issue Jenkins / JENKINS-59801 the input device is not a TTY Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-10-16 11:39 Environment: shell Priority: Critical Reporter: Gugulethu Mabaso Good Day, I created a jenkins pipeline it work but the issue comes when I have to execute shell commands: eg When I try to execute a docker container after ssh I get the below error: the input device is not a TTY Add Comment
[JIRA] (JENKINS-24138) Archived file names can change when moved from slave to master
Title: Message Title Tomasz Fijarczyk commented on JENKINS-24138 Re: Archived file names can change when moved from slave to master I just followed article guidelines and used Windows env variables . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156612.1407335439000.8694.1571226180359%40Atlassian.JIRA.
[JIRA] (JENKINS-59801) the input device is not a TTY
Title: Message Title Gugulethu Mabaso updated an issue Jenkins / JENKINS-59801 the input device is not a TTY Change By: Gugulethu Mabaso Good Day, I created a jenkins pipeline it work but the issue comes when I have to execute shell commands: egWhen I try to execute a docker container after ssh I get the below error: the input device is not a TTY Agent pid 12446+ ssh-add -k /var/lib/jenkins/.ssh/mykeysIdentity added: /var/lib/jenkins/.ssh/mykeys (/var/lib/jenkins/.ssh/mykeys)+ ssh user@ip docker exec -it container_name bashthe input device is not a TTYBuild step 'Execute shell' marked build as failureFinished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-is
[JIRA] (JENKINS-59342) Ability to download Specific Objects bundles
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-59342
Ability to download Specific Objects bundles
Change By:
Allan BURDAJEWICZ
Administrators would benefit from a feature to download job bundle, build bundle, node bundle directly from the Jenkins UI. Those information are required to troubleshoot issues related to build / node failures or job / node configuration. While those can be retrieved from the file system, it would be really useful to b able to get this from the UI and also leverage anonymization of the Support Core.* Run Action to download Run information (build.xml, build logs, other files and directories)* Item Action to download Item information (config.xml, other files and directories)* Computer Action to download Node / Computer information (config.xml, remote working dir, remote logs, ...) As a Jenkins administrator, I would like to be able to click on a "Support" button for a build, a job, a folder, a node and generate a bundle which contains the contents of the item that I'm concerned about. When I click on this button, I'm prompted to select what I which to include from the item with relevant default selection.h3. Acceptance* Administrators shall see a new Support menu option on each Build, Item, Node (except master) page. * The Action shall only be available to users with sufficient permission on that item* The Action layout shall resemble the one of the root action* The bundle generation shall leverage the current anonymization model* The bundle generated shall contain a manifest* The user shall be able to select an option to add files from object root directory* The user shall be able to includes / excludes object root directory files from the bundle generation (Ant Style pattern)* The Menu option(s) to download content from the file system will only be available to users with {{Jenkins.ADMINISTER}} (or could be {{Jenkins.RUN_SCRIPTS}}) permission* The user shall be presented with meaningful / non performance impacting defaults (For example, when getting content of a top level item, do not allow defaults that would download the entire root directory)* For Nodes, the user shall be able to select an option to add files from the remote working directory* For Nodes, the user shall be able to includes / excludes remote work dir files from the bundle generation (Ant Style pattern)* For Nodes, the user shall be able to select options that exists in the Root action:** Agent System Properties** Agent System Configuration (Linux only)** Agent JVM System Metrics** Agent Config file** Agent Logs** Agent Launch Logs** Agent Command Statistics** Networks Interfaces** File Descriptors** Thread Dump** Environment Variables** Dump Export Table** Root CAsh3. Designh4. New type of Component* Abstract class {{ObjectComponent}} with generics for extensions of {{Actionable}} (or {{AbstractModelObject}} ?) items that implements a {{Describable}} (need components more complex than just a checkbox).** An {{ObjectComponent}} defines an abstract method to add contents
[JIRA] (JENKINS-59342) Ability to download Specific Objects bundles
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-59342 Ability to download Specific Objects bundles Change By: Allan BURDAJEWICZ Attachment: poc-node-action-components.png Attachment: poc-item-action-components.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201893.1568352322000.8697.1571227560070%40Atlassian.JIRA.
[JIRA] (JENKINS-59802) Changing access token credential causes 404 -Not Found error
Title: Message Title ethorsa created an issue Jenkins / JENKINS-59802 Changing access token credential causes 404 -Not Found error Issue Type: Bug Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2019-10-16 12:13 Environment: - Jenkins v2.176.1 - Bitbucket Server Integration v1.0-rc-1 Priority: Minor Reporter: ethorsa Changing an existing Bitbucket Credentials causes an 404 - Not Found error. HTTP ERROR 404 Problem accessing /credentials/store/system/domain/_/credential//. Reason: Not Found Reproduction Create a Bitbucket Access Token Credential Navigate to it's edit page Change a setting, eg. the description Save 404 Error is shown Workaround Ignore the error. Even though an error is shown, the save was successful and eg. the description has been updated.
[JIRA] (JENKINS-59802) Changing access token credential causes 404 -Not Found error
Title: Message Title
ethorsa updated an issue
Jenkins / JENKINS-59802
Changing access token credential causes 404 -Not Found error
Change By:
ethorsa
Changing an existing Bitbucket Credentials causes an _404 - Not Found error_. {noformat}HTTP ERROR 404Problem accessing /credentials/store/system/domain/_/credential//. Reason:Not Found{noformat} Even though an error is shown, the save was successful and eg. the description has been updated. h3. Reproduction # Create a Bitbucket Access Token Credential # Navigate to it's edit page # Change a setting, eg. the description # Save # 404 Error is shown (credential is updated) h3. WorkaroundIgnore the error. Even though an error is shown, the save was successful and eg. the description has been updated.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-59802) Changing access token credential causes 404 - Not Found error
Title: Message Title ethorsa updated an issue Jenkins / JENKINS-59802 Changing access token credential causes 404 - Not Found error Change By: ethorsa Summary: Changing access token credential causes 404 -Not Found error Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202532.1571228005000.8703.1571228220320%40Atlassian.JIRA.
[JIRA] (JENKINS-59803) Manual Resource reservation is ignored by job waiting for that resource
Title: Message Title
Daniel Horak created an issue
Jenkins / JENKINS-59803
Manual Resource reservation is ignored by job waiting for that resource
Issue Type:
Bug
Assignee:
Tobias Gruetzmacher
Components:
lockable-resources-plugin
Created:
2019-10-16 12:16
Environment:
Jenkins: 2.121.3 Lockable Resources plugin: 2.3
Priority:
Major
Reporter:
Daniel Horak
If Resource is reserved from Jenkins configuration page, already running job waiting for that resource ignores the new reservation. Create resource foo and prepare pipeline job with piece of code like this: lock(resource: "foo", quantity: 1) { sleep 120 } Then perform following steps:
Start this job twice in a row. {{ The first build should lock the resource and start the }}sleep step{{, the second will be waiting for the resource.}}
Go to Manage Jenkins -> Configure System -> Lockable Resources Manager section and fill Reserved by field for the foo resource }}{{by some text{{ and apply the changes (you should do this within the configured sleep time in the job - 2 minutes in the example above).}}{{}}
Wait till the first job finishes and check the second job.{{}}
Actual results: The second job acquires the lock and continue to the sleep step. Expected results: The second job should stay waiting for the resource, because the resource was manually reserved!
[JIRA] (JENKINS-59804) Support Multibranch Pipelines
Title: Message Title ethorsa created an issue Jenkins / JENKINS-59804 Support Multibranch Pipelines Issue Type: New Feature Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2019-10-16 12:25 Environment: - Jenkins v2.176.1 - Bitbucket Server Integration v1.0-rc-1 Priority: Major Reporter: ethorsa Please add support for Multibranch Pipelines. Unlike Freestyle and Pipeline jobs these aren't supported yet. Add Comment
[JIRA] (JENKINS-29893) Allow exclusions for git clean
Title: Message Title Borja Domínguez commented on JENKINS-29893 Re: Allow exclusions for git clean I know that. It's what I'm currently doing. But it would be nice that we could do it in "Clean before checkout" behaviour on Jenkins UI because everywhere where we are calling "checkout scm" uses that configuration. In this case I need to make two lines in my Jenkinsfile. 1-"git clean", 2-"checkout scm". In pipelines that you have stash and unstash you need to copy this code everywhere. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164471.1439300117000.8714.1571230020354%40Atlassian.JIRA.
[JIRA] (JENKINS-59805) Error when integrate with Azure AD
Title: Message Title patric Moore created an issue Jenkins / JENKINS-59805 Error when integrate with Azure AD Issue Type: Bug Assignee: Azure DevOps Components: azure-ad-plugin Created: 2019-10-16 12:49 Environment: Azure AD Priority: Critical Reporter: patric Moore I applied a certificate for jenkins then I followed the guidance here to integrate with Azure AD: https://wiki.jenkins.io/display/JENKINS/Azure+AD+Plugin First I enabled the https by using the keystore: openssl pkcs12 -export -out jenkins_keystore.p12 -passout 'pass:xxx' -inkey example.key -in example.crt -certfile CertCA.crt -name example keytool -importkeystore -srckeystore jenkins_keystore.p12 -srcstorepass 'xxx' -srcstoretype PKCS12 -srcalias example -deststoretype JKS -destkeystore jenkins_keystore.jks -deststorepass 'xxx' -destalias example After I installed the Azure AD plugin, the error occurs: ```
[JIRA] (JENKINS-59805) Error when integrate with Azure AD
Title: Message Title
patric Moore updated an issue
Jenkins / JENKINS-59805
Error when integrate with Azure AD
Change By:
patric Moore
I applied a certificate for jenkins then I followed the guidance here to integrate with Azure AD: [https://wiki.jenkins.io/display/JENKINS/Azure+AD+Plugin] First I enabled the https by using the keystore: {code:java}openssl pkcs12 -export -out jenkins_keystore.p12 -passout 'pass:xxx' -inkeyexample.key -in example.crt -certfile CertCA.crt -name examplekeytool -importkeystore -srckeystore jenkins_keystore.p12 -srcstorepass 'xxx' -srcstoretype PKCS12 -srcalias example -deststoretype JKS -destkeystore jenkins_keystore.jks -deststorepass 'xxx' -destalias example{code} After I installed the Azure AD plugin, the error occurs: ``` {code:java} org.jose4j.jwt.consumer.InvalidJwtException: JWT (claims-> \ {"aud":"9533d0f1-2b45-4ca0-88d3-f68fbf14b959","iss":"https://sts.windows.net/4e1eab56-1e20-410c-9a33-208f4489fbd3/v2.0","iat":1571229543,"nbf":1571229543,"exp":1571233443,"cloud_instance_name":"microsoftonline.us","cloud_graph_host_name":"graph.windows.net","msgraph_host":"graph.microsoft.com","aio":"AWQAm/8E1CKvXcdx/kWs/H9GLm4BKBJkNd2hV7AiP07c00YPdCiqcsaVig9Oi674f0poQOIXwp0Y91z1vX0cAm03oW9p1p9nRlPdTC6z+JmFDaKX6NMLv9v+fIgdPer15Yas4idi","email":"xxx","name":"xxx","nonce":"wGtXIHVvwR","oid":"29979360-f175-4da8-808e-4c03db48be59","preferred_username":"xxx","sub":"tg4kqDvDX3um45hIsQfrfexxEllNVI5JnL9tOo","tid":"4e1eab56c-9a33-xx208f4489fbd3","uti":"3l8w0S49w0Whx4_5FM0FAA","ver":"2.0"}) rejected due to invalid claims. Additional details: [[12] Issuer (iss) claim value (https://sts.windows.net/4e1eab56-1e20-410c-9a33-208f4489fbd3/v2.0) doesn't match expected value of https://login.microsoftonline.com/4e1eab56-1e20-410c-9a33-208f4489fbd3/v2.0] at org.jose4j.jwt.consumer.JwtConsumer.validate(JwtConsumer.java:449) at org.jose4j.jwt.consumer.JwtConsumer.processContext(JwtConsumer.java:294) at org.jose4j.jwt.consumer.JwtConsumer.process(JwtConsumer.java:416) at org.jose4j.jwt.consumer.JwtConsumer.processToClaims(JwtConsumer.java:164) at com.microsoft.jenkins.azuread.AzureSecurityRealm.validateAndParseIdToken(AzureSecurityRealm.java:237) at com.microsoft.jenkins.azuread.AzureSecurityRealm.doFinishLogin(AzureSecurityRealm.java:203) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Meta
[JIRA] (JENKINS-59805) Error when integrate with Azure AD
Title: Message Title
patric Moore updated an issue
Jenkins / JENKINS-59805
Error when integrate with Azure AD
Change By:
patric Moore
I applied a certificate for jenkins then I followed the guidance here to integrate with Azure AD: [https://wiki.jenkins.io/display/JENKINS/Azure+AD+Plugin] First I enabled the https by using the keystore: {code:java}openssl pkcs12 -export -out jenkins_keystore.p12 -passout 'pass:xxx' -inkeyexample.key -in example.crt -certfile CertCA.crt -name examplekeytool -importkeystore -srckeystore jenkins_keystore.p12 -srcstorepass 'xxx' -srcstoretype PKCS12 -srcalias example -deststoretype JKS -destkeystore jenkins_keystore.jks -deststorepass 'xxx' -destalias example{code} After I installed the Azure AD plugin, the error occurs:``` org.jose4j.jwt.consumer.InvalidJwtException: JWT (claims->\{"aud":"9533d0f1-2b45-4ca0-88d3-f68fbf14b959","iss":"https://sts.windows.net/4e1eab56-1e20-410c-9a33-208f4489fbd3/v2.0","iat":1571229543,"nbf":1571229543,"exp":1571233443,"cloud_instance_name":"microsoftonline.us","cloud_graph_host_name":"graph.windows.net","msgraph_host":"graph.microsoft.com","aio":"AWQAm/8E1CKvXcdx/kWs/H9GLm4BKBJkNd2hV7AiP07c00YPdCiqcsaVig9Oi674f0poQOIXwp0Y91z1vX0cAm03oW9p1p9nRlPdTC6z+JmFDaKX6NMLv9v+fIgdPer15Yas4idi","email":"xxx","name":"xxx","nonce":"wGtXIHVvwR","oid":"29979360-f175-4da8-808e-4c03db48be59","preferred_username":"xxx","sub":"tg4kqDvDX3um45hIsQfrfexxEllNVI5JnL9tOo","tid":"4e1eab56c-9a33-xx208f4489fbd3","uti":"3l8w0S49w0Whx4_5FM0FAA","ver":"2.0"}) rejected due to invalid claims. Additional details: [[12] Issuer (iss) claim value (https://sts.windows.net/4e1eab56-1e20-410c-9a33-208f4489fbd3/v2.0) doesn't match expected value of https://login.microsoftonline.com/4e1eab56-1e20-410c-9a33-208f4489fbd3/v2.0] at org.jose4j.jwt.consumer.JwtConsumer.validate(JwtConsumer.java:449) at org.jose4j.jwt.consumer.JwtConsumer.processContext(JwtConsumer.java:294) at org.jose4j.jwt.consumer.JwtConsumer.process(JwtConsumer.java:416) at org.jose4j.jwt.consumer.JwtConsumer.processToClaims(JwtConsumer.java:164) at com.microsoft.jenkins.azuread.AzureSecurityRealm.validateAndParseIdToken(AzureSecurityRealm.java:237) at com.microsoft.jenkins.azuread.AzureSecurityRealm.doFinishLogin(AzureSecurityRealm.java:203) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$2.doDispatch(M
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59707 Give more details in the connection success panel Change By: Arnaud Héritier Released As: cloudbees-jenkins-advisor- 2 3 . 12 0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.8766.1571231101886%40Atlassian.JIRA.
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor plugin
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59695 JCasC support for Jenkins Health Advisor plugin Change By: Arnaud Héritier Released As: cloudbees-jenkins-advisor-plugin- 2 3 . 12 0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202394.1570520934000.8760.1571231101687%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59697 Add an Apply button and enhance the UX Change By: Arnaud Héritier Released As: cloudbees-jenkins-advisor- 2 3 . 12 0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.8764.1571231101832%40Atlassian.JIRA.
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier updated JENKINS-59767 Jenkins / JENKINS-59767 Replace the comma separated list for CC by a list of emails Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: cloudbees-jenkins-advisor-3.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202490.1570998849000.8767.1571231162010%40Atlassian.JIRA.
[JIRA] (JENKINS-59675) Upgrading to 2.0.6 is causing UI issues in pipelines
Title: Message Title Maxim Danilov commented on JENKINS-59675 Re: Upgrading to 2.0.6 is causing UI issues in pipelines We're also facing the exact same issue with version 2.0.6 2.0.0 works very well. Our Jenkins instance is 2.190.1 (LTS) Marky Jackson did you have, by any chance, time to reproduce the behaviour? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202368.1570259911000.8791.1571231820195%40Atlassian.JIRA.
[JIRA] (JENKINS-59688) Collabnet jobs inside folders are invisible
Title: Message Title mohamed fouad assigned an issue to Sriram Gudapati Jenkins / JENKINS-59688 Collabnet jobs inside folders are invisible Change By: mohamed fouad Assignee: whsu Sriram Gudapati Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202386.1570462873000.8799.1571232780177%40Atlassian.JIRA.
[JIRA] (JENKINS-59796) Item names with U+00E7 (Cedilla) raise errors
Title: Message Title Bruno Meneguello closed an issue as Cannot Reproduce I'm closing this issue since I've tested with a pristine jenkins installation and the error doesn't happens. I think this could be caused by some old data format and some migration issue. Jenkins / JENKINS-59796 Item names with U+00E7 (Cedilla) raise errors Change By: Bruno Meneguello Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor plugin
Title: Message Title Arnaud Héritier updated JENKINS-59695 3.0 is out Jenkins / JENKINS-59695 JCasC support for Jenkins Health Advisor plugin Change By: Arnaud Héritier Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202394.1570520934000.8801.1571234700622%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier updated JENKINS-59697 3.0 is out Jenkins / JENKINS-59697 Add an Apply button and enhance the UX Change By: Arnaud Héritier Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.8806.1571234760097%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59707 Give more details in the connection success panel Change By: Arnaud Héritier Attachment: advisor-config-last-upload-error.png Attachment: advisor-monitor-error.png Attachment: advisor-config-current-status-error.png Attachment: advisor-config-last-upload-success.png Attachment: advisor-config-current-status-success.png Attachment: advisor-config-last-upload-skipped.png Attachment: advsior-config-last-upload-none.png Attachment: advisor-config-current-status-invalid.png Attachment: advisor-monitor-configure-it.png Add Comment
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier updated JENKINS-59707 3.0 is out Jenkins / JENKINS-59707 Give more details in the connection success panel Change By: Arnaud Héritier Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.8808.1571234830314%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier commented on JENKINS-59707 Re: Give more details in the connection success panel Monitors: Connection statusLast upload status Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.8813.1571235002055%40Atlassian.JIRA.
[JIRA] (JENKINS-59767) Replace the comma separated list for CC by a list of emails
Title: Message Title Arnaud Héritier updated JENKINS-59767 3.0 is out Jenkins / JENKINS-59767 Replace the comma separated list for CC by a list of emails Change By: Arnaud Héritier Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202490.1570998849000.8814.1571235060150%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-59696 support-core and thus advisor require to restart the instance to be activated Change By: Baptiste Mathus Labels: foundation-triage Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8816.1571235240297%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Mathieu Delrocq commented on JENKINS-59790 Re: Container cannot connect to node because it doesn't exist We are actually testing "Attach Docker container" wich seems to be a solution. But, in the documentation of the plugin, this functionnality is marked as experimental. Is this still the case ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.8821.1571236740242%40Atlassian.JIRA.
[JIRA] (JENKINS-21942) Unreliable defaulting of Jenkins.workspaceDir
Title: Message Title Jesse Glick commented on JENKINS-21942 Re: Unreliable defaulting of Jenkins.workspaceDir A relative path for $JENKINS_HOME? I would not consider that supported. Please use absolute paths only. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.153719.1393283635000.8826.1571236862196%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title
Mathieu Delrocq updated an issue
Jenkins / JENKINS-59790
Container cannot connect to node because it doesn't exist
Change By:
Mathieu Delrocq
We recently updated our version of Jenkins to 2.176.3. And now a connection error with docker-agent randomly block the queue of jobs :{code:java}Refusing headers from remote: Unknown client name: docker-00026wu6nor9w{code}The docker container is ready and try to connect to the Jenkins master but the node doesn't exist yet.I saw in the code of docker-plugin that the container is created and started before the Jenkins node. While the connection method is JNLP, the commands to download and run the remoting.jar are executed at the start of the container. But at this moment, the node wasn't added to Jenkins master.Have you ever encountered this error? Is there a solution?Is it possible to modify provision methods and create the Jenkins node before instanciate the container to fix this issue?Jenkins version : 2.176.3docker-plugin version : 1.1.7 docker host version : 1.13.1
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Manuel Hampp updated JENKINS-59665 Jenkins / JENKINS-59665 Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager Change By: Manuel Hampp Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.8842.1571237160771%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Manuel Hampp commented on JENKINS-59665 Re: Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager Hi, I fixed the sorting for the uninstall column. The enabled column already seems to work fine. BG Manuel pull request: https://github.com/jenkinsci/jenkins/pull/4298 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.8845.1571237280547%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Manuel Hampp assigned an issue to Josh Soref Jenkins / JENKINS-59665 Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager Change By: Manuel Hampp Assignee: Manuel Hampp Josh Soref Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.8847.1571237280584%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Manuel Hampp assigned an issue to Manuel Hampp Jenkins / JENKINS-59665 Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager Change By: Manuel Hampp Assignee: Josh Soref Manuel Hampp Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202357.1570213644000.8849.1571237340132%40Atlassian.JIRA.
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title Jesse Glick started work on JENKINS-59777 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202501.1571053962000.8853.1571237460392%40Atlassian.JIRA.
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title Jesse Glick assigned an issue to Art V Jenkins / JENKINS-59777 nested docker.withRegistry() does not work Change By: Jesse Glick Assignee: Jesse Glick Art V Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202501.1571053962000.8851.1571237460352%40Atlassian.JIRA.
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title Jesse Glick updated JENKINS-59777 Jenkins / JENKINS-59777 nested docker.withRegistry() does not work Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202501.1571053962000.8855.1571237460450%40Atlassian.JIRA.
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title Jesse Glick commented on JENKINS-59777 Re: nested docker.withRegistry() does not work Did not follow most of this, but please use the Link feature in JIRA to link to any related issues. From a quick glance it looks like this issue would only affect the legacy mode of directly editing config files; by default the plugin will try to use CLI docker login. As a general recommendation, if in doubt just use the generic withCredentials and sh 'docker login -u "$USER" -p "$PASS"'. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202501.1571053962000.8857.1571237580962%40Atlassian.JIRA.
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Jesse Glick commented on JENKINS-59788 Re: Timestamps missing for agent-based steps in Pipeline Job 2.190.1 Explicitly setting USE_WATCHING=false is irrelevant—that is the default. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.1571132852000.8860.1571237700268%40Atlassian.JIRA.
[JIRA] (JENKINS-59806) Want ability to stash and unstash between a parent job and a child job
Title: Message Title Basil Crow created an issue Jenkins / JENKINS-59806 Want ability to stash and unstash between a parent job and a child job Issue Type: New Feature Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2019-10-16 15:28 Priority: Minor Reporter: Basil Crow Before I explain my use case (which does not work today), I will explain a related use case (which does work today) to help illustrate my point. Working Use Case The working use case is as follows. We start with the naïve version: The user starts a Pipeline job against a branch of a fork in GitHub/GitLab. The job runs many tests in parallel using a parallel step: (unit tests, integration tests, and functional tests, for example). Each branch of the parallel step does a Git checkout of the user's code and then runs the relevant tests. The above tests take a while to run, during which the user might push again to their branch on GitHub/GitLab. Our users expect that once they start a Jenkins job, the job will test their code at a specific revision. Since the implementation described above checks out the Git repository in each test branch, this constraint could be violated, as evidenced by the following sequence of events: The user starts a Pipeline job against a branch of a fork in GitHub/GitLab. The job clones their Git repository and starts the unit tests. But there is no executor available for the functional tests, so the job blocks in that branch. The user pushes again to the same branch of their fork in GitHub/Gi
[JIRA] (JENKINS-59806) Want ability to stash and unstash between a parent job and a child job
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-59806 Want ability to stash and unstash between a parent job and a child job Change By: Basil Crow Component/s: workflow-api-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202537.1571239705000.8864.1571240040074%40Atlassian.JIRA.
[JIRA] (JENKINS-59440) Maven Parser should display module name
Title: Message Title Andreas Pabst assigned an issue to Andreas Pabst Jenkins / JENKINS-59440 Maven Parser should display module name Change By: Andreas Pabst Assignee: Andreas Pabst Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202025.1568878309000.8866.1571240160303%40Atlassian.JIRA.
[JIRA] (JENKINS-59806) Want ability to stash and unstash between a parent job and a child job
Title: Message Title Basil Crow commented on JENKINS-59806 Re: Want ability to stash and unstash between a parent job and a child job I could see two ways of adding support for the failing use case: The stash from the parent job isn't deleted until the parent job ends. Presumably each child job has a reference to its parent job. So in the unstash step, if the requested stash is not available in the current job, we could try to find the stash in its parent job recursively until we get to the top of the parent/child hierarchy, failing only if the topmost job does not have the requested stash. The unstash step could be modified to take in an optional project name and selector (like the copyArtifact step does). When such a project name and selector is provided, the unstash step could unstash from a different job. Jesse Glick and Devin Nusbaum, am I understanding the problem correctly, or is there some other solution for my use case that I've missed? If I've understood the problem correctly, what do you think of my two ideas for fixing this? Are there any security implications about having access to stashes from other jobs? If either of my ideas sounds acceptable, I could start working on a fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-59780) Automatically label Raspbian Linux agents
Title: Message Title Mark Waite started work on JENKINS-59780 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202507.1571071707000.8869.1571241660272%40Atlassian.JIRA.
[JIRA] (JENKINS-59780) Automatically label Raspbian Linux agents
Title: Message Title Mark Waite updated JENKINS-59780 Included in platformlabeler plugin release 5.1 Jenkins / JENKINS-59780 Automatically label Raspbian Linux agents Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.
[JIRA] (JENKINS-59780) Automatically label Raspbian Linux agents
Title: Message Title Mark Waite updated JENKINS-59780 Jenkins / JENKINS-59780 Automatically label Raspbian Linux agents Change By: Mark Waite Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202507.1571071707000.8872.1571241660349%40Atlassian.JIRA.
[JIRA] (JENKINS-59780) Automatically label Raspbian Linux agents
Title: Message Title Mark Waite updated JENKINS-59780 Jenkins / JENKINS-59780 Automatically label Raspbian Linux agents Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202507.1571071707000.8870.1571241660317%40Atlassian.JIRA.
[JIRA] (JENKINS-59780) Automatically label Raspbian Linux agents
Title: Message Title Mark Waite updated JENKINS-59780 Jenkins / JENKINS-59780 Automatically label Raspbian Linux agents Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202507.1571071707000.8873.1571241780186%40Atlassian.JIRA.
[JIRA] (JENKINS-57428) Duplicate warnings when using error-prone and java scan
Title: Message Title Andreas Pabst assigned an issue to Andreas Pabst Jenkins / JENKINS-57428 Duplicate warnings when using error-prone and java scan Change By: Andreas Pabst Assignee: Andreas Pabst Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199240.1557749846000.8875.1571242020253%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Ryan Campbell commented on JENKINS-59707 Re: Give more details in the connection success panel Really nice diagnostics – great work! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.8879.1571243340124%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Ryan Campbell updated an issue Jenkins / JENKINS-59696 support-core and thus advisor require to restart the instance to be activated Change By: Ryan Campbell Component/s: cloudbees-jenkins-advisor-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.8881.1571243880401%40Atlassian.JIRA.
[JIRA] (JENKINS-59778) Pipeline script fails to call Java code on slave: Failed to deserialize the Callable object
Title: Message Title Alexander Samoylov commented on JENKINS-59778 Re: Pipeline script fails to call Java code on slave: Failed to deserialize the Callable object Well, I understand. Thank you for the clarification. You wrote also above that "The supported way to do this from Pipeline is to implement Step in a plugin, and have the step handle the interactions with remoting". Probably you know some pipeline code which implements similar thing? I tried to look for on https://github.com/jenkinsci/jenkins-scripts/tree/master/scriptler, but did not find anything useful. Could you please refer to some code snippet, of course if you know such one? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202502.1571054173000.8884.1571244060153%40Atlassian.JIRA.
[JIRA] (JENKINS-30446) Recursive variable substitution
Title: Message Title Alexander Moiseenko commented on JENKINS-30446 Re: Recursive variable substitution Faced the same error in freestyle job when evninject is set twice: in General section of job config and in a build step. with 50% chance build stuck on envinject build step, fills heap memory with an int[] objects, gc reaches overhead threshold, and Full GC runs frequently. Workaround: 1. kill problem thread through javamelody (Monitoring Plugin,) in our case it was in RUNNING state on: at java.util.Arrays.copyOf(Arrays.java:3332) 2. Move all envinject parametes into one call (we have move all into buld step) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165043.1442262821000..1571244540213%40Atlassian.JIRA.
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-59788 Timestamps missing for agent-based steps in Pipeline Job 2.190.1 Change By: Jesse Glick Assignee: Steven G Brown Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.1571132852000.8904.1571244961348%40Atlassian.JIRA.
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-59788 Timestamps missing for agent-based steps in Pipeline Job 2.190.1 Change By: Jesse Glick Priority: Critical Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.1571132852000.8910.1571244961488%40Atlassian.JIRA.
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Jesse Glick commented on JENKINS-59788 Re: Timestamps missing for agent-based steps in Pipeline Job 2.190.1 Just tried it. I get timestamps for all lines, though display is corrupted on lines which have also have an attempt to apply coloring by the withMaven step, which I think would be better suppressed in favor of the ansicolor plugin and MAVEN_OPTS=-Djansi.force=true mvn -B -Dstyle.color=always … Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.1571132852000.8892.1571244961117%40Atlassian.JIRA.
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-59788 Timestamps missing for agent-based steps in Pipeline Job 2.190.1 Change By: Jesse Glick Component/s: pipeline-maven-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.1571132852000.8897.1571244961227%40Atlassian.JIRA.
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-59788 Timestamps missing for agent-based steps in Pipeline Job 2.190.1 Change By: Jesse Glick Component/s: ansicolor-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.1571132852000.8908.1571244961463%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Mathieu Delrocq commented on JENKINS-59790 Re: Container cannot connect to node because it doesn't exist You can follow this issue on github : Issue #757 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.8916.1571245080338%40Atlassian.JIRA.
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-59788 Timestamps missing for agent-based steps in Pipeline Job 2.190.1 Change By: Jesse Glick Attachment: colorized.png Attachment: mangled-timestamps.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.1571132852000.8918.1571245080410%40Atlassian.JIRA.
[JIRA] (JENKINS-59788) Timestamps missing for agent-based steps in Pipeline Job 2.190.1
Title: Message Title Jesse Glick commented on JENKINS-59788 Re: Timestamps missing for agent-based steps in Pipeline Job 2.190.1 In other words, I can reproduce a minor bug somewhere in interaction between timestamper, ansicolor, and pipeline-maven, but not the absence of any timestamps that you report. Would be best to describe a minimal, self-contained, reproducible test case. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202518.1571132852000.8922.1571245380263%40Atlassian.JIRA.
[JIRA] (JENKINS-59806) Want ability to stash and unstash between a parent job and a child job
Title: Message Title Jesse Glick commented on JENKINS-59806 Re: Want ability to stash and unstash between a parent job and a child job At this point, the job is testing an inconsistent set of code: the parallel branch from step 2 is testing the code before the user pushed the second commit, but the parallel branch from step 4 is testing the code after the user pushed the second commit. True if you are using the git step with, say, a simple branch argument. If you use checkout scm you are guaranteed to get the same commit regardless of when this step runs: the commit ID is fixed when the Jenkinsfile is loaded. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202537.1571239705000.8926.1571245500191%40Atlassian.JIRA.
[JIRA] (JENKINS-59806) Want ability to stash and unstash between a parent job and a child job
Title: Message Title Jesse Glick commented on JENKINS-59806 Re: Want ability to stash and unstash between a parent job and a child job "parallel within parallel" testing (which is not possible within a single pipeline) Sure it is. You can freely nest parallel steps (in Scripted syntax). Blue Ocean will not currently display the results neatly, but that I just consider a limitation in B.O. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202537.1571239705000.8928.1571245620096%40Atlassian.JIRA.
[JIRA] (JENKINS-59806) Want ability to stash and unstash between a parent job and a child job
Title: Message Title Jesse Glick commented on JENKINS-59806 Re: Want ability to stash and unstash between a parent job and a child job The stash from the parent job isn't deleted until the parent job ends. This is already true. (In some cases it is kept longer.) in the unstash step, if the requested stash is not available in the current job, we could try to find the stash in its parent job recursively Perhaps. Are there any security implications about having access to stashes from other jobs? Yes, and copyartifact security is a mine field. The recommendation is to use checkout scm within a single job. If for whatever reason you really need to have nested jobs and use the build step, you have at least two options available: Use def commit = checkout(scm).GIT_COMMIT (IIRC) to save the commit ID, then pass this to git steps in child builds using a string build parameter. Use archiveArtifacts in the parent build to save a checkout (and anything else you want), and copyartifact in the child build to retrieve it. Unlike stashes, copyartifact can freely refer to arbitrary builds of arbitrary projects (subject to certain permission checks). The recommendation is to pass the parent build number as a (string) build parameter to the child build. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-25275) groovy plugin sets GROOVY_HOME wrong when the path differs on the slaves from the master
Title: Message Title Basheer Radman assigned an issue to Basheer Radman Jenkins / JENKINS-25275 groovy plugin sets GROOVY_HOME wrong when the path differs on the slaves from the master Change By: Basheer Radman Assignee: vjuranek Basheer Radman Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.158785.1414070206000.8933.1571246100703%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Improve UX and users feedbacks
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59707 Improve UX and users feedbacks Change By: Arnaud Héritier Summary: Give more details in the connection success panel Improve UX and users feedbacks Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202408.1570569525000.8936.1571248380406%40Atlassian.JIRA.
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck created an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Issue Type: Bug Assignee: Unassigned Components: ssh-agent-plugin Created: 2019-10-16 18:04 Environment: Jenkins v2.200 RPM install directly on CentOS 7.7 Using OpenJDK Runtime Env 1.8 Credentials Plugin v2.3.0 SSH Credentials Plugin v1.18 SSH Agent Plugin v1.17 Client is Win10, Chrome 77.0.3865.120 and Firefox 69.0.1 Priority: Minor Reporter: Jonathan Buck I'm attempting to use the "SSH Agent" setting in the "Build Environment" section. My issue is credentials are not showing up when creating/modifying a freestyle project. This is the case with credentials created from the credential page or from the "Credentials" option under the "SSH Agent" option. I've tried multiple types of credentials to see what would populate the list, although my understanding is that this should work with credentials stored as "SSH Username with private key". I also use the Ansible plugin and all available credentials are showing up within that credentials drop-down menu within the same project configuration page. My assumption is that this has something to do with the "SSH Agent" plugin interacting with the "Credentials" or "SSH Credentials" plugin.
[JIRA] (JENKINS-59806) Want ability to stash and unstash between a parent job and a child job
Title: Message Title Basil Crow commented on JENKINS-59806 Re: Want ability to stash and unstash between a parent job and a child job Thanks for the reply, and I agree with all your points. I didn't realize the checkout step could return a Map that includes GIT_COMMIT. That definitely sounds like it would work, and I'll give it a shot. I still think the RFE described in this issue might be useful, but without a specific use case there doesn't seem to be a driver for implementing it at present. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202537.1571239705000.8969.1571251800110%40Atlassian.JIRA.
[JIRA] (JENKINS-59704) NoSuchMethodError occurs when promoting a build using parametrized trigger
Title: Message Title Filipe Roque commented on JENKINS-59704 Re: NoSuchMethodError occurs when promoting a build using parametrized trigger created PR for publish-over-plugin: https://github.com/jenkinsci/publish-over-plugin/pull/10 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202405.157054141.8972.1571252340376%40Atlassian.JIRA.
[JIRA] (JENKINS-59808) Jenkins PR(pull request) build fails for 1st time
Title: Message Title tanzeel rehman created an issue Jenkins / JENKINS-59808 Jenkins PR(pull request) build fails for 1st time Issue Type: Bug Assignee: Christian Del Monte Attachments: Screen Shot 2019-10-16 at 3.56.43 PM.png Components: bitbucket-branch-source-plugin, bitbucket-pullrequest-builder-plugin, bitbucket-push-and-pull-request-plugin, webhook-eventsource-plugin, webhook-step-plugin Created: 2019-10-16 20:08 Environment: Jenkins ver. 2.197 Bitbucket Branch Source plugin 2.4.6 Priority: Critical Reporter: tanzeel rehman When I create a pull request in Bitbucket my build fails, see attached image for details. Couldn't find remote ref refs/pull-requests/42/from Another thing I have noticed is that when I go to Jenkins UI and re-trigger the build it builds without any errors. Next when I decline the PR and then open the same PR it again fails and this time when I try to re trigger build from Jenkins UI it continues to fail with the same error and I end up with having to create a new PR with the only solution to run my build pipeline. My environments are: Jenkins ver. 2.197 Bitbucket Branch Source plugin 2.4.6
[JIRA] (JENKINS-59808) Jenkins PR(pull request) build fails for 1st time
Title: Message Title
tanzeel rehman updated an issue
Jenkins / JENKINS-59808
Jenkins PR(pull request) build fails for 1st time
Change By:
tanzeel rehman
When I create a pull request in Bitbucket my build fails, see attached image for details. {code:java} Couldn't find remote ref refs/pull-requests/42/from {code}Another thing I have noticed is that when I go to Jenkins UI and re-trigger the build it builds without any errors. Next when I decline the PR and then open the same PR it again fails and this time when I try to re trigger build from Jenkins UI it continues to fail with the same error and I end up with having to create a new PR with the only solution to run my build pipeline. My environments are: * Jenkins ver. 2.197 * Bitbucket Branch Source plugin 2.4.6
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it
[JIRA] (JENKINS-59808) Jenkins PR(pull request) build fails for 1st time
Title: Message Title
tanzeel rehman updated an issue
Jenkins / JENKINS-59808
Jenkins PR(pull request) build fails for 1st time
Change By:
tanzeel rehman
When I create a pull request in Bitbucket my build fails, see attached image for details. {code:java}Couldn't find remote ref refs/pull-requests/42/from{code} * Another thing I have noticed is that when I go to Jenkins UI and re-trigger the build it builds without any errors. * Next if I commit to my branch/PR build runs without errors * Next when I decline the PR and then open the same PR it again fails and this time when I try to re trigger build from Jenkins UI it continues to fail with the same error and I end up with having to create a new PR with the only solution to run my build pipeline. My environments are: * Jenkins ver. 2.197 * Bitbucket Branch Source plugin 2.4.6
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-59808) Jenkins PR(pull request) build fails for 1st time
Title: Message Title
tanzeel rehman updated an issue
Jenkins / JENKINS-59808
Jenkins PR(pull request) build fails for 1st time
Change By:
tanzeel rehman
When I create a pull request in Bitbucket my build fails, see attached image for details. {code:java}Couldn't find remote ref refs/pull-requests/42/from{code} * Another thing I have noticed is that when I go to Jenkins UI and re-trigger the build it builds without any errors. * Next if I commit to my branch/PR build runs without errors * Next when I decline the PR and then open the same PR it again fails and this time when I try to re trigger build from Jenkins UI it continues to fail with the same error and I end up with having to ** create a new PR with the only solution to run my build pipeline . , OR ** I do a new commit and that triggers a successful build My environments are: * Jenkins ver. 2.197 * Bitbucket Branch Source plugin 2.4.6
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message becaus
