[JIRA] (JENKINS-56135) Npm parallel builds failing.
Title: Message Title
Ravi Singh updated an issue
Jenkins / JENKINS-56135
Npm parallel builds failing.
Change By:
Ravi Singh
I am building a pipeline job with parallel stages. The pipeline will run on two slave machines. One is MAC and other is WINDOWS. If I execute more than one instance of the pipeline, it seems there is a permission error in windows. Like {code:java}npm ERR! path C:\workspace\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\node_modules\.staging\typescript-c52c96ba\lib\es\diagnosticMessages.generated.json npm ERR! code EPERM npm ERR! errno -4048 npm ERR! syscall unlink npm ERR! Error: EPERM: operation not permitted, unlink 'C:\workspace\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\node_modules\.staging\typescript-c52c96ba\lib\es\diagnosticMessages.generated.json' npm ERR! { [Error: EPERM: operation not permitted, unlink 'C:\workspace\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\node_modules\.staging\typescript-c52c96ba\lib\es\diagnosticMessages.generated.json'] npm ERR! cause: npm ERR! { Error: EPERM: operation not permitted, unlink 'C:\workspace\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\node_modules\.staging\typescript-c52c96ba\lib\es\diagnosticMessages.generated.json' npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'unlink', npm ERR! path: npm ERR! 'C:\\workspace\\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\\node_modules\\.staging\\typescript-c52c96ba\\lib\\es\\diagnosticMessages.generated.json' }, npm ERR! stack: npm ERR! 'Error: EPERM: operation not permitted, unlink \'C:\\workspace\\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\\node_modules\\.staging\\typescript-c52c96ba\\lib\\es\\diagnosticMessages.generated.json\'', npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'unlink', npm ERR! path: npm ERR! 'C:\\workspace\\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\\node_modules\\.staging\\typescript-c52c96ba\\lib\\es\\diagnosticMessages.generated.json', npm ERR! parent: 'IBMDigitalAppBuilder' } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR!{code} Even when I am using a dynamic workspace folder because of this. The workspace folder is working as they should but why these folders are created in the first place.{code:java}My pipeline code is something like this.- pipeline { agent { label { label "" customWorkspace "./workspace/BuildFor_${env.JOB_NAME}_${env.BRANCH_NAME}_${env.BUILD_NUMBER}" }} stages { stage ("Copywrite Check + Dynamically Generate .npmrc
[JIRA] (JENKINS-56135) Npm parallel builds failing.
Title: Message Title
Ravi Singh updated an issue
Jenkins / JENKINS-56135
Npm parallel builds failing.
Change By:
Ravi Singh
I am building a pipeline job with parallel stages. The pipeline will run on two slave machines. One is MAC and other is WINDOWS. If I execute more than one instance of the pipeline, it seems there is a permission error in windows. Like {code:java}npm ERR! path C:\workspace\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\node_modules\.staging\typescript-c52c96ba\lib\es\diagnosticMessages.generated.json npm ERR! code EPERM npm ERR! errno -4048 npm ERR! syscall unlink npm ERR! Error: EPERM: operation not permitted, unlink 'C:\workspace\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\node_modules\.staging\typescript-c52c96ba\lib\es\diagnosticMessages.generated.json' npm ERR! { [Error: EPERM: operation not permitted, unlink 'C:\workspace\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\node_modules\.staging\typescript-c52c96ba\lib\es\diagnosticMessages.generated.json'] npm ERR! cause: npm ERR! { Error: EPERM: operation not permitted, unlink 'C:\workspace\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\node_modules\.staging\typescript-c52c96ba\lib\es\diagnosticMessages.generated.json' npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'unlink', npm ERR! path: npm ERR! 'C:\\workspace\\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\\node_modules\\.staging\\typescript-c52c96ba\\lib\\es\\diagnosticMessages.generated.json' }, npm ERR! stack: npm ERR! 'Error: EPERM: operation not permitted, unlink \'C:\\workspace\\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\\node_modules\\.staging\\typescript-c52c96ba\\lib\\es\\diagnosticMessages.generated.json\'', npm ERR! errno: -4048, npm ERR! code: 'EPERM', npm ERR! syscall: 'unlink', npm ERR! path: npm ERR! 'C:\\workspace\\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\\node_modules\\.staging\\typescript-c52c96ba\\lib\\es\\diagnosticMessages.generated.json', npm ERR! parent: 'IBMDigitalAppBuilder' } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It's possible that the file was already in use (by a text editor or antivirus), npm ERR! or that you lack permissions to access it. npm ERR!{code} Even when I am using a dynamic workspace folder because of this. The workspace folder is working as they should but why these folders are created in the first place. {code:java} My pipeline code is something like this.- {code:java}// code placeholder pipeline {agent {label {label ""customWorkspace "./workspace/BuildFor_${env.JOB_NAME}_${env.BRANCH_NAME}_${env.BUILD_NUMBER}"}} environment {NODE_OPTIONS='--max-old-space-size=4096'github_token =
[JIRA] (JENKINS-56135) Npm parallel builds failing.
Title: Message Title
Ravi Singh created an issue
Jenkins / JENKINS-56135
Npm parallel builds failing.
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
declarative-pipeline-when-conditions-plugin
Created:
2019-02-14 07:40
Environment:
Jenkins 2.150.1 Operating system - MAC, Windows
Labels:
jenkins jenkins-cache parallel npm node
Priority:
Major
Reporter:
Ravi Singh
I am building a pipeline job with parallel stages. The pipeline will run on two slave machines. One is MAC and other is WINDOWS. If I execute more than one instance of the pipeline, it seems there is a permission error in windows. Like
npm ERR! path C:\workspace\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\node_modules\.staging\typescript-c52c96ba\lib\es\diagnosticMessages.generated.json
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall unlink
npm ERR! Error: EPERM: operation not permitted, unlink 'C:\workspace\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\node_modules\.staging\typescript-c52c96ba\lib\es\diagnosticMessages.generated.json'
npm ERR! { [Error: EPERM: operation not permitted, unlink 'C:\workspace\ntal_build_new_pull_request-BL7QHNTCEFER3V4N6SFI4MCLHOCO62H22UO6N4UOONFACJ44GBIA\node_modules\.staging\typescript-c52c96ba\lib\es\diagnosticMessages.generated.json']
npm ERR! cause:
npm ERR! {
[JIRA] (JENKINS-52189) GraphListener does not receive FlowStartNode
Title: Message Title Thomas Weißschuh commented on JENKINS-52189 Re: GraphListener does not receive FlowStartNode Devin Nusbaum so the easy way would be to just fire the listeners before the execution This however would break the behaviour of the `FlowExecution.onRunning()` method which is documented to receive an already started listener. (The testsuite however passes) We could also introduce a new method `FlowExecution.beforeRunning()` (or `onCreated()`) that fires before the flow is actually started. WDYT? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52150) High CPU sys time consumption after upgrade to 2.107.3
Title: Message Title ASHOK MOHANTY commented on JENKINS-52150 Re: High CPU sys time consumption after upgrade to 2.107.3 We are using Jenkins v.2.121.3 (upgraded couple of months back from v.2.73.3 ). We have around ~1000 MBranch + ~200 pipeline + ~200FreeStyle projects. Post upgrade we are seeing CPU spike in the master server. We are not running any builds in master (primarily only MB indexings runs in master box). Master Server - Linux 7.x (100+ cpu). We have gitLab* plugins for "SCM - GitLab" integration. GitLab hosted in separate Linux server. Can you please provide some tips to debug the issue !! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55955) Remove JAXB dependency from notification plugin
Title: Message Title Mrinal Dutta assigned an issue to Mrinal Dutta Jenkins / JENKINS-55955 Remove JAXB dependency from notification plugin Change By: Mrinal Dutta Assignee: Mrinal Dutta Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55955) Remove JAXB dependency from notification plugin
Title: Message Title Mrinal Dutta started work on JENKINS-55955 Change By: Mrinal Dutta Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52995) Make Display URL Provider configurable via JCasC
Title: Message Title Mrinal Dutta commented on JENKINS-52995 Re: Make Display URL Provider configurable via JCasC Oleg Nenashev Martin d'Anjou I have doubt here with the term ! Standard Global Configuration what does it mean ? Is it yml config file or simple java config file ? And is there any other example like in any another project where I can find use of JCASC and global configs together ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray commented on JENKINS-55722 Re: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection I attached jenkin.png above in attachment section.i provided the remote directory,still same error.please check and let me know. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56131) Redundant installs of a plugin have a terrible ux
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56131 Redundant installs of a plugin have a terrible ux Change By: Oleg Nenashev Labels: ux Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray commented on JENKINS-55722 Re: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection I attached jenkin.png above in attachment section.i provided the remote directory,still same error.please check and let me know. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray commented on JENKINS-55722 Re: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection I attached jenkin.png above in attachment section.i provided the remote directory,still same error.please check and let me know. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56131) Redundant installs of a plugin have a terrible ux
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56131 Redundant installs of a plugin have a terrible ux Change By: Oleg Nenashev Labels: ux Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56131) Redundant installs of a plugin have a terrible ux
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56131 Redundant installs of a plugin have a terrible ux Change By: Oleg Nenashev Labels: ux Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray updated an issue Jenkins / JENKINS-55722 jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Change By: Subhransubala Routray Attachment: jenkin.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray commented on JENKINS-55722 Re: jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection If i fill in remote directory also,still same issue "SFTP channel error".Its something like plug-in problem. please suggest me correct plug-in.All SFTP and FTP related plug-in is there in jerkin. Earlier it was working with whatever i provided in attachment. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title Reinhold Füreder commented on JENKINS-47286 Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view This morning I was positively surprised that according to BlueOcean change log (https://plugins.jenkins.io/blueocean) this issue was solved: Change log 1.11.0 (Feb 13, 2019) ... JENKINS-47286 Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view ... ... "only" to find out that it is still in status reopened, i.e. unresolved and that "only" one aspect was solved: namely the missing translation (https://github.com/jenkinsci/blueocean-plugin/commit/b0bf45c64afbf511971c7e79ff2dd317f1bddfc8) – of course I am happy/grateful about that too. However, this is a bit misleading Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56120) Error installing influx-plugin 1.20.1
Title: Message Title Aleksi Simell closed an issue as Not A Defect Jenkins / JENKINS-56120 Error installing influx-plugin 1.20.1 Change By: Aleksi Simell Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Josh Soref reopened an issue Jenkins / JENKINS-55787 Switch labels from entry to checkbox Change By: Josh Soref Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56119) jumphost not working
Title: Message Title Alex Earl commented on JENKINS-56119 Re: jumphost not working I'm not sure if the test connection takes jump hosts into account. Can you try using the host configuration in a job and see if it works there? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title Gavin Mogan commented on JENKINS-53188 Re: New jobs created from Blue Ocean are tied with username that created them I haven't been able to reproduce this, but I have one more thing to try. What version of blue ocean are you using? what version of jenkins? Could credentials have been tied to that user? Does it happen on run? on view? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56119) jumphost not working
Title: Message Title jesse wen updated an issue Jenkins / JENKINS-56119 jumphost not working Change By: jesse wen I have tested which fw is allowed jenkins directly access is ok to target host.I am trying to use 'jumphost' feature in my env, after test with below error. From linux secure log on jumphost, can not find jenkins host passed ssh tunnel request. Can you help? Thank you.[ my env topology : ] 172.16.4.200(jenkins) --> 172.16.4.201(jumphost, fw allowed) --> 172.16.248.11(target)[ERROR]jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection. Message: [Failed to connect session for config [app]. Message [timeout: socket is not established]] from linux secure log on jumphost, can not find jenkins host passed ssh tunnel request. Can you help? Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56119) jumphost not working
Title: Message Title jesse wen updated an issue Jenkins / JENKINS-56119 jumphost not working Change By: jesse wen I have tested which fw is allowed jenkins directly access is ok to target host.I am trying to use 'jumphost' feature in my env, after test with below error. my env topology:172.16.4.200(jenkins) --> 172.16.4.201(jumphost, fw allowed) --> 172.16.248.11(target)[ERROR]jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection. Message: [Failed to connect session for config [app]. Message [timeout: socket is not established]] from linux secure log on jumphost, can not find jenkins host passed ssh tunnel request. Can you help? Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56119) jumphost not working
Title: Message Title jesse wen commented on JENKINS-56119 Re: jumphost not working thank you for your update, i have updated my issue, can you help? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56120) Error installing influx-plugin 1.20.1
Title: Message Title Ashwin Yaprala commented on JENKINS-56120 Re: Error installing influx-plugin 1.20.1 I was actually following popular answer from here https://stackoverflow.com/a/19588907/1903696. Thank you for directing me in correct path. I have extracted the source and run `mvn install` it generated the hpi file. You can now close this ticket. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55881) Connection error With PTC Integrirty
Title: Message Title Cai Hao closed an issue as Fixed Jenkins / JENKINS-55881 Connection error With PTC Integrirty Change By: Cai Hao Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55880) Connection error With PTC Integrirty
Title: Message Title Cai Hao closed an issue as Fixed Jenkins / JENKINS-55880 Connection error With PTC Integrirty Change By: Cai Hao Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55881) Connection error With PTC Integrirty
Title: Message Title Cai Hao updated an issue Jenkins / JENKINS-55881 Connection error With PTC Integrirty Change By: Cai Hao Priority: Blocker Trivial Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56119) jumphost not working
Title: Message Title jesse wen updated an issue Jenkins / JENKINS-56119 jumphost not working Change By: jesse wen Attachment: issue-new.png I am trying to use 'jumphost' feature in my env, after test with below error. Can you help? my env topology: 172.16.4.200(jenkins) --> 172.16.4.201(jumphost, fw allowed) --> 172.16.248.11(target) [ERROR]jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection. Message: [Failed to connect session for config [app]. Message [ Auth fail timeout: socket is not established ]] from linux secure log on jumphost, can not find jenkins host passed ssh tunnel request. Can you help? Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56119) jumphost not working
Title: Message Title jesse wen updated an issue Jenkins / JENKINS-56119 jumphost not working Change By: jesse wen Attachment: issue.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50643) Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-50643 Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files Change By: Olivier Lamy Comment: SUCCESS: Integrated in Jenkins build foo-fs #10 (See [http://localhost:8080/job/foo-fs/10/])[TEST-112] test olamy JENKINS-50643 (olamy: 14/02/19 12:10 PM [https://github.com/olamy/foo/commit/312499023e05cb0706da84815dfcac96874464c0])* (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50643) Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-50643 Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files Change By: Olivier Lamy Comment: SUCCESS: Integrated in Jenkins build foo-fs #6 (See [http://localhost:8080/job/foo-fs/6/])[TEST-112] test olamy JENKINS-50643 (noreply: 14/02/19 11:49 AM [https://github.com/olamy/foo/commit/24b71825cf63e65c3c7b0b320023d31ba9152c63])* (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50643) Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-50643 Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files Change By: Olivier Lamy Comment: SUCCESS: Integrated in Jenkins build foo-fs #8 (See [http://localhost:8080/job/foo-fs/8/])[TEST-112] test olamy JENKINS-50643 (olamy: 14/02/19 11:56 AM [https://github.com/olamy/foo/commit/ceb0891b4c93af739a2bd9f2c07acf2b2b439db0])* (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50643) Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-50643 Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files Change By: Olivier Lamy Comment: SUCCESS: Integrated in Jenkins build foo-fs #9 (See [http://localhost:8080/job/foo-fs/9/])[TEST-112] test olamy JENKINS-50643 (olamy: 14/02/19 12:08 PM [https://github.com/olamy/foo/commit/cdf3fd5b001e8dcfff1e46b67f76832fcbd53559])* (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50643) Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-50643 Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files Change By: Olivier Lamy Comment: SUCCESS: Integrated in Jenkins build foo-fs #7 (See [http://localhost:8080/job/foo-fs/7/])[TEST-112] test olamy JENKINS-50643 (olamy: 14/02/19 11:51 AM [https://github.com/olamy/foo/commit/f438cb06943c931352b55789b00205ac5acec948])* (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50643) Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files
Title: Message Title Olivier Lamy commented on JENKINS-50643 Re: Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files SUCCESS: Integrated in Jenkins build foo-fs #10 (See http://localhost:8080/job/foo-fs/10/) TEST-112 test olamy JENKINS-50643 (olamy: 14/02/19 12:10 PM https://github.com/olamy/foo/commit/312499023e05cb0706da84815dfcac96874464c0) (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-112) Issue for testing purpose so do not mind
Title: Message Title Olivier Lamy commented on TEST-112 Re: Issue for testing purpose so do not mind SUCCESS: Integrated in Jenkins build foo-fs #10 (See http://localhost:8080/job/foo-fs/10/) TEST-112 test olamy JENKINS-50643 (olamy: 14/02/19 12:10 PM https://github.com/olamy/foo/commit/312499023e05cb0706da84815dfcac96874464c0) (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50643) Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files
Title: Message Title Olivier Lamy commented on JENKINS-50643 Re: Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files SUCCESS: Integrated in Jenkins build foo-fs #9 (See http://localhost:8080/job/foo-fs/9/) TEST-112 test olamy JENKINS-50643 (olamy: 14/02/19 12:08 PM https://github.com/olamy/foo/commit/cdf3fd5b001e8dcfff1e46b67f76832fcbd53559) (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-112) Issue for testing purpose so do not mind
Title: Message Title Olivier Lamy commented on TEST-112 Re: Issue for testing purpose so do not mind SUCCESS: Integrated in Jenkins build foo-fs #9 (See http://localhost:8080/job/foo-fs/9/) TEST-112 test olamy JENKINS-50643 (olamy: 14/02/19 12:08 PM https://github.com/olamy/foo/commit/cdf3fd5b001e8dcfff1e46b67f76832fcbd53559) (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50643) Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files
Title: Message Title Olivier Lamy commented on JENKINS-50643 Re: Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files SUCCESS: Integrated in Jenkins build foo-fs #8 (See http://localhost:8080/job/foo-fs/8/) TEST-112 test olamy JENKINS-50643 (olamy: 14/02/19 11:56 AM https://github.com/olamy/foo/commit/ceb0891b4c93af739a2bd9f2c07acf2b2b439db0) (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-112) Issue for testing purpose so do not mind
Title: Message Title Olivier Lamy commented on TEST-112 Re: Issue for testing purpose so do not mind SUCCESS: Integrated in Jenkins build foo-fs #8 (See http://localhost:8080/job/foo-fs/8/) TEST-112 test olamy JENKINS-50643 (olamy: 14/02/19 11:56 AM https://github.com/olamy/foo/commit/ceb0891b4c93af739a2bd9f2c07acf2b2b439db0) (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-112) Issue for testing purpose so do not mind
Title: Message Title Olivier Lamy commented on TEST-112 Re: Issue for testing purpose so do not mind SUCCESS: Integrated in Jenkins build foo-fs #7 (See http://localhost:8080/job/foo-fs/7/) TEST-112 test olamy JENKINS-50643 (olamy: 14/02/19 11:51 AM https://github.com/olamy/foo/commit/f438cb06943c931352b55789b00205ac5acec948) (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50643) Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files
Title: Message Title Olivier Lamy commented on JENKINS-50643 Re: Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files SUCCESS: Integrated in Jenkins build foo-fs #7 (See http://localhost:8080/job/foo-fs/7/) TEST-112 test olamy JENKINS-50643 (olamy: 14/02/19 11:51 AM https://github.com/olamy/foo/commit/f438cb06943c931352b55789b00205ac5acec948) (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-112) Issue for testing purpose so do not mind
Title: Message Title Olivier Lamy commented on TEST-112 Re: Issue for testing purpose so do not mind SUCCESS: Integrated in Jenkins build foo-fs #6 (See http://localhost:8080/job/foo-fs/6/) TEST-112 test olamy JENKINS-50643 (noreply: 14/02/19 11:49 AM https://github.com/olamy/foo/commit/24b71825cf63e65c3c7b0b320023d31ba9152c63) (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50643) Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files
Title: Message Title Olivier Lamy commented on JENKINS-50643 Re: Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files SUCCESS: Integrated in Jenkins build foo-fs #6 (See http://localhost:8080/job/foo-fs/6/) TEST-112 test olamy JENKINS-50643 (noreply: 14/02/19 11:49 AM https://github.com/olamy/foo/commit/24b71825cf63e65c3c7b0b320023d31ba9152c63) (edit) Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53188) New jobs created from Blue Ocean are tied with username that created them
Title: Message Title Gavin Mogan assigned an issue to Gavin Mogan Jenkins / JENKINS-53188 New jobs created from Blue Ocean are tied with username that created them Change By: Gavin Mogan Assignee: Gavin Mogan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48296) Multibranch pipeline - ignore commits from certain user
Title: Message Title chirs damour edited a comment on JENKINS-48296 Re: Multibranch pipeline - ignore commits from certain user it's not really clear from the help/docs (at least to me) but does the build happen if any of the stategies are met or only if all are met? (and vs or) it seems like it might be an or, which makes the ignore committer strategy not very useful when other strategies are in there too code seems to indicate that's the case [https://github.com/jenkinsci/branch-api-plugin/blob/0ae692141b3ba878b9fd6c774c063fefdd7ff7c2/src/main/java/jenkins/branch/MultiBranchProject.java#L2224] as such these suggestions kinda suck for any custom case Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48296) Multibranch pipeline - ignore commits from certain user
Title: Message Title chirs damour commented on JENKINS-48296 Re: Multibranch pipeline - ignore commits from certain user it's not really clear from the help/docs (at least to me) but does the build happen if any of the stategies are met or only if all are met? (and vs or) it seems like it might be an or, which makes the ignore committer strategy not very useful when other strategies are in there too Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55605) can only click on the first active parallel stage, others running but cannot click
Title: Message Title boris ivan commented on JENKINS-55605 Re: can only click on the first active parallel stage, others running but cannot click some improvement in BO 1.11.1 – I can now click on S1, S2, S3, S5, and context changes accordingly. Prior to BO 1.11.1 I could only see the context of S1 regardless what I clicked. Unfortunately when S5 finishes and the active stages are: S1, S2, S3, S6 ... I cannot click on S6 and have the context switch to S6. The blue active icon gets larger, but the context (logs, etc) doesn't switch. So.. things are a bit better, but still broke. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Connor Yu commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines I am seeing this as well. Upgraded to 2.46.3 yesterday and started seeing this in my simple pipeline. sh: line 1: 27323 Terminated sleep 3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56134) ActiveDirectory Crash During Reconfiguration
Title: Message Title Stephen De Rudder created an issue Jenkins / JENKINS-56134 ActiveDirectory Crash During Reconfiguration Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2019-02-13 21:06 Environment: Windows Server 2008 R2 Ent, Jenkins 2.164, Active Directory plugin 2.12 Labels: plugin Priority: Minor Reporter: Stephen De Rudder The Windows server is part of the domain. Jenkins is running as a service under a local account that is part of the local Administrators group. Here is crash info: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authenticationManager': Cannot resolve reference to bean 'activeDirectory' while setting bean property 'providers' with key [0]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'activeDirectory': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider]: Constructor threw exception; nested exception is java.io.IOException: Failed to connect to Active Directory. Does this machine belong to Active Directory? at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104) at
[JIRA] (JENKINS-51431) Unable to connect to REST service
Title: Message Title Luba Pyat commented on JENKINS-51431 Re: Unable to connect to REST service Was this issue resolved? I have very similar one too.. CC Laszlo Miklosik and Ian Sparkes Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56133) Embed build url of calling job into pod annotations
Title: Message Title Matthew Ludlum created an issue Jenkins / JENKINS-56133 Embed build url of calling job into pod annotations Issue Type: New Feature Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-02-13 20:42 Priority: Minor Reporter: Matthew Ludlum Due to how pod names are constructed and can be freely designed, it is often difficult to tie any single pod back to a build. This is important to do in some cases, such as tracking down the owner of pod, determine the resource usage of a build, or provide feedback if the pod uses non-pullable images. To that end, adding an annotation for the full build URL to the pod metadata will allow us to quickly identify the build server and build responsible for that pod. Add Comment
[JIRA] (JENKINS-51273) Inconsistent Declarative Behavior in Yaml File vs legacy podTemplate
Title: Message Title Matthew Ludlum stopped work on JENKINS-51273 Change By: Matthew Ludlum Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56132) File System SCM should allow passing of build parameters
Title: Message Title Daniel Wamara closed an issue as Duplicate Jenkins / JENKINS-56132 File System SCM should allow passing of build parameters Change By: Daniel Wamara Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56132) File System SCM should allow passing of build parameters
Title: Message Title Daniel Wamara created an issue Jenkins / JENKINS-56132 File System SCM should allow passing of build parameters Issue Type: Improvement Assignee: Unassigned Components: filesystem_scm-plugin Created: 2019-02-13 20:15 Environment: Jenkins ver. 2.150.2 File System SCM Priority: Minor Reporter: Daniel Wamara It should be possible to dynamically set the path of the File system SCM by passing the value of a build parameter. For the moment, following exception is thrown ($SERVICE contains the value of a choice parameter) Building in workspace /Volumes/Data/dwamara/.jenkins/workspace/inzo24-2-docker-build-2 FSSCM.checkout /Volumes/Work/projets/inzo24/$SERVICE to /Volumes/Data/dwamara/.jenkins/workspace/inzo24-2-docker-build-2 FATAL: Parameter 'directory' is not a directory java.lang.IllegalArgumentException: Parameter 'directory' is not a directory at org.apache.commons.io.FileUtils.validateListFilesParameters(FileUtils.java:545) at org.apache.commons.io.FileUtils.listFiles(FileUtils.java:521) at org.apache.commons.io.FileUtils.iterateFiles(FileUtils.java:628) at hudson.plugins.filesystem_scm.FolderDiff.getNewOrModifiedFiles(FolderDiff.java:130) at hudson.plugins.filesystem_scm.RemoteFolderDiff$CheckOut.invoke(RemoteFolderDiff.java:95) at hudson.plugins.filesystem_scm.RemoteFolderDiff$CheckOut.invoke(RemoteFolderDiff.java:88) at hudson.FilePath.act(FilePath.java:1078) at hudson.FilePath.act(FilePath.java:1061) at hudson.plugins.filesystem_scm.FSSCM.checkout(FSSCM.java:215) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at
[JIRA] (JENKINS-56131) Redundant installs of a plugin have a terrible ux
Title: Message Title Josh Soref commented on JENKINS-56131 Re: Redundant installs of a plugin have a terrible ux Downloaded ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55148) Is this plugin abandoned?
Title: Message Title Eric Stein commented on JENKINS-55148 Re: Is this plugin abandoned? Jakub Bochenski - any luck getting your admin permissions going so you can make a release? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54558) Debian package update failed because setup step tries to restart Jenkins service
Title: Message Title
dma_k updated an issue
Jenkins / JENKINS-54558
Debian package update failed because setup step tries to restart Jenkins service
Change By:
dma_k
On Debian stretch I had Jenkins configured to be run under Tomcat 8 server, hence in {{/etc/default/jenkins}} I have specified that:{code}RUN_STANDALONE=false{code}During package update (e.g. via {{apt-get update}}) the following error happened:{code}Setting up jenkins (2.138.2) ...Job for jenkins.service failed because the control process exited with error code.See "systemctl status jenkins.service" and "journalctl -xe" for details.invoke-rc.d: initscript jenkins, action "start" failed.● jenkins.service - LSB: Start Jenkins at boot time Loaded: loaded (/etc/init.d/jenkins; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-11-05 00:31:47 CET; 20ms ago Docs: man:systemd-sysv-generator(8) Process: 29959 ExecStart=/etc/init.d/jenkins start (code=exited, status=1/FAILURE)Nov 05 00:31:47 debian systemd[1]: Starting LSB: Start Jenkins at boot time...Nov 05 00:31:47 debian jenkins[29959]: Not configured to run standaloneNov 05 00:31:47 debian systemd[1]: jenkins.service: Control process exited, code=exited status=1Nov 05 00:31:47 debian systemd[1]: Failed to start LSB: Start Jenkins at boot time.Nov 05 00:31:47 debian systemd[1]: jenkins.service: Unit entered failed state.Nov 05 00:31:47 debian systemd[1]: jenkins.service: Failed with result 'exit-code'.dpkg: error processing package jenkins (--configure): subprocess installed post-installation script returned error exit status 1Errors were encountered while processing: jenkinsE: Sub-process /usr/bin/dpkg returned an error code (1){code}It looks that post-installation script tries to restart Jenkins service and/or check it's status but failed, as it was configured as embedded application.Expected that Jenkins update is possible despite of {{jenkins.service}} status or, in case restart is necessary, it checks that {{RUN_STANDALONE=true}} beforehand. Namely when {{RUN_STANDALONE=false}}, no restart should be performed as otherwise it fails:{code}Unpacking jenkins (2.150.2) over (2.150.1) ...Setting up jenkins (2.150.2) ...Job for jenkins.service failed because the control process exited with error code.See "systemctl status jenkins.service" and "journalctl -xe" for details.invoke-rc.d: initscript jenkins, action "start" failed.● jenkins.service - LSB: Start Jenkins at boot time Loaded: loaded (/etc/init.d/jenkins; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-02-12 14:44:36 CET; 30ms ago Docs: man:systemd-sysv-generator(8) Process: 28490 ExecStart=/etc/init.d/jenkins start (code=exited, status=7)Feb 12 14:44:24 debian systemd[1]: Starting LSB: Start Jenkins at boot time...Feb 12 14:44:29 debian jenkins[28490]: Correct java version foundFeb 12 14:44:34 debian jenkins[28490]: Starting Jenkins Automation Server: jenkinsThe selected http port (8080) on address 0.0.0.0 seems to be in use by another
[JIRA] (JENKINS-56131) Redundant installs of a plugin have a terrible ux
Title: Message Title Daniel Beck commented on JENKINS-56131 Re: Redundant installs of a plugin have a terrible ux Possibly drop the original Download Successfully line entirely. Actually the "Success" is wrong and should be gone. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56131) Redundant installs of a plugin have a terrible ux
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-56131
Redundant installs of a plugin have a terrible ux
Change By:
Josh Soref
# Visit {{/pluginManager/available}} # Select a plugin (e.g. {{spotinst}}) # Click {{Download now and install after restart}} # Then revisit {{/pluginManager/available}} # Select the same plugin (e.g. {{spotinst}}) # Click {{Install without restart}}Actual results: ||...||...|||Spotinst|Downloaded Successfully. Will be activated during the next boot||Spotinst|Success |!image-2019-02-13-13-42-48-518.png!Expected results: * Unclear ** Possibly drop the original {{Download Successfully}} line entirely. ** Or perhaps update its message to {{Downloaded}} and then change the second bullet to {{Activated}}. * All of the text here is wrong: * * {{Successfully}} in {{Download Successfully}} is needlessly capitalized. * * {{boot}} at the end of the second "sentence" should probably be {{launch}}. * * The second "sentence" is missing a period.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56131) Redundant installs of a plugin have a terrible ux
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-56131 Redundant installs of a plugin have a terrible ux Issue Type: Bug Assignee: Unassigned Attachments: image-2019-02-13-13-42-48-518.png Components: core Created: 2019-02-13 18:46 Priority: Minor Reporter: Josh Soref Visit /pluginManager/available Select a plugin (e.g. spotinst) Click Download now and install after restart Then revisit /pluginManager/available Select the same plugin (e.g. spotinst) Click Install without restart Actual results: ... ... Spotinst Downloaded Successfully. Will be activated during the next boot
[JIRA] (JENKINS-56130) java.io.IOException: Process working directory
Title: Message Title Ravi Burra created an issue Jenkins / JENKINS-56130 java.io.IOException: Process working directory Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2019-02-13 18:44 Priority: Minor Reporter: Ravi Burra When I was trying to create a mirror of Gerrit repo then I am getting the below exception error. 13:27:44 java.io.IOException: Process working directory '/home/rburra/workspace/Acura/CI-CD Farm Aggregator Jobs/mapChangesToFeatures/.repo/manifests' doesn't exist!13:27:44 at hudson.Proc$LocalProc.(Proc.java:247)13:27:44 at hudson.Proc$LocalProc.(Proc.java:218)13:27:44 at hudson.Launcher$LocalLauncher.launch(Launcher.java:935)13:27:44 at hudson.Launcher$ProcStarter.start(Launcher.java:454)13:27:44 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1312)13:27:44 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1265)13:27:44 at hudson.remoting.UserRequest.perform(UserRequest.java:212)13:27:44 at hudson.remoting.UserRequest.perform(UserRequest.java:54)13:27:44 at hudson.remoting.Request$2.run(Request.java:369)13:27:44 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)13:27:44 at java.util.concurrent.FutureTask.run(FutureTask.java:264)13:27:44 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)13:27:44 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)13:27:44 at java.lang.Thread.run(Thread.java:834)
[JIRA] (JENKINS-3850) maven installed by tool installer does not set executable flag on unix
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-3850 maven installed by tool installer does not set executable flag on unix Change By: Josh Soref Summary: maven installe installed by tool installer does not set executable flag on unix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12983) Redundant syncs when using matrix jobs
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-12983 Redundant syncs when using matrix jobs Change By: Josh Soref Summary: Redundat Redundant syncs when using matrix jobs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49221) Slave getting disconnected after some idle time.
Title: Message Title Maciek Sroczynski edited a comment on JENKINS-49221 Re: Slave getting disconnected after some idle time. JUST "FIX IT" WHEN MARKING THE NODE AS "OFFLINE" AND PUTTING IT BACK AS "ONLINE" ---case closed-- It seems like when you connect the node and then remove it somehow and want to reconnect it is going into connected/disconnected loop... any ideas? (slave service removed from node as well as cleaning the working dir)STARTING WITH CMD LINE:Both error and output logs will be printed to c:\jenkins\remotinglut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: HPeklut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.lut 13, 2019 5:19:32 PM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.28lut 13, 2019 5:19:32 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFO: Using c:\jenkins\remoting as a remoting work directorylut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://IP:PORT/ |http://ip:PORT/ ]lut 13, 2019 5:19:32 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]lut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: IP Agent port: PORT Identity: IDENTITYlut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Handshakinglut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to IP:PORTlut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectlut 13, 2019 5:19:38 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: IDENTITYlut 13, 2019 5:19:39 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connectedlut 13, 2019 5:19:52 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Terminatedlut 13, 2019 5:20:02 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Performing onReconnect operation.lut 13, 2019 5:20:02 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: onReconnect operation completed.lut 13, 2019 5:20:02 PM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://IP:PORT/|http://ip:PORT/]AND SO ON, and on Add Comment
[JIRA] (JENKINS-49426) parallel steps only show branchname as prefix in console output
Title: Message Title Connor Yu commented on JENKINS-49426 Re: parallel steps only show branchname as prefix in console output I would also like to see this information. I have parallel nodes building each with multiple stages and it's hard to tell which stage contains what output. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56089) Syslog indexer type sends incorrect value for $HOST
Title: Message Title Markus Winter commented on JENKINS-56089 Re: Syslog indexer type sends incorrect value for $HOST makes sense Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56123) JaCoCo Coverage Statistics Grid Portlet reports 100% coverage in case there is no coverage collected at all
Title: Message Title Sergey Zhemzhitsky updated an issue Jenkins / JENKINS-56123 JaCoCo Coverage Statistics Grid Portlet reports 100% coverage in case there is no coverage collected at all Change By: Sergey Zhemzhitsky JaCoCo Coverage Statistics Grid Portlet reports 100% coverage in case there are is no coverage collected at all.Here is the coverage reported by the portlet!image-2019-02-13-16-31-29-943.png|width=600!... and here is the coverage trend as it is shown when clicking and navigating to the corresponding item from the portlet!image-2019-02-13-16-34-36-731.png|width=400! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56123) JaCoCo Coverage Statistics Grid Portlet reports 100% coverage in case there is no coverage collected at all
Title: Message Title Sergey Zhemzhitsky updated an issue Jenkins / JENKINS-56123 JaCoCo Coverage Statistics Grid Portlet reports 100% coverage in case there is no coverage collected at all Change By: Sergey Zhemzhitsky Summary: JaCoCo Coverage Statistics Grid Portlet reports 100% coverage in case there is no coverage collected at all Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56089) Syslog indexer type sends incorrect value for $HOST
Title: Message Title Jakub Bochenski commented on JENKINS-56089 Re: Syslog indexer type sends incorrect value for $HOST This is the line responsible for this https://github.com/jenkinsci/logstash-plugin/blame/master/src/main/java/jenkins/plugins/logstash/persistence/SyslogDao.java#L47 The current behavior has been so since the beginning, but I think we can change it, as sending the target hostname seems useless. Markus Winter WDYT? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title
Jeremy Kam edited a comment on JENKINS-56114
Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Job directory structure was created by Jenkins itself from initial deployment version of 2.73.2. Upgrades through multiple LTS versions to 2.138 worked as expected.Jenkins uses a Docker bind mount into the container to map c:\jenkins to the external bind mount point on the host file system, and all Jenkins files reside within in the Jenkins created directory tree. When starting the container, docker variables and mount point:$HOST_JENKINS_HOME = "d:/data/jenkins"$JENKINS_HOME = "c:/jenkins"--mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME} Directory Jenkins directory listing (from within the container) included in attachment : jenkins_dir_tree_20190213_1 . txt
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title Sean Kline commented on JENKINS-55106 Re: Build stuck on final "exit 0" Thank you very much for pointing this out, Guru. We tried this and are now running 2.150.2 without the delay. Have a great day! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title
Jeremy Kam edited a comment on JENKINS-56114
Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Job directory structure was created by Jenkins itself from initial deployment version of 2.73.2. Upgrades through multiple LTS versions to 2.138 worked as expected.Jenkins uses a Docker bind mount into the container to map c:\jenkins to the external bind mount point on the host file system, and all Jenkins files reside within in the Jenkins created directory tree. When starting the container, docker variables and mount point:$HOST_JENKINS_HOME = "d:/data/jenkins" $JENKINS_HOME = "c:/jenkins"--mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME}Jenkins directory listing (from within the container) included in attachment: jenkins_dir_tree_20190213_1.txt
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title
Jeremy Kam commented on JENKINS-56114
Re: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Job directory structure was created by Jenkins itself from initial deployment version of 2.73.2. Upgrades through multiple LTS versions to 2.138 worked as expected. Jenkins uses a Docker bind mount into the container to map c:\jenkins to the external bind mount point on the host file system, and all Jenkins files reside within in the Jenkins created directory tree. When starting the container, docker variables and mount point: $HOST_JENKINS_HOME = "d:/data/jenkins" $JENKINS_HOME = "c:/jenkins" --mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME} Directory listing included in attachment.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56114) Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
Title: Message Title Jeremy Kam updated an issue Jenkins / JENKINS-56114 Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy) Change By: Jeremy Kam Attachment: jenkins_dir_tree_20190213_1.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52189) GraphListener does not receive FlowStartNode
Title: Message Title Allan Lewis assigned an issue to Sam Van Oort Sorry, Thomas Weißschuh, I did that by mistake! I probably pressed 'i' while this ticket was focused. Jenkins / JENKINS-52189 GraphListener does not receive FlowStartNode Change By: Allan Lewis Assignee: Allan Lewis Sam Van Oort Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52189) GraphListener does not receive FlowStartNode
Title: Message Title Thomas Weißschuh commented on JENKINS-52189 Re: GraphListener does not receive FlowStartNode Allan Lewis you assigned this to yourself, are you planning on working on this? Otherwise I may find the time to take a shot at it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52189) GraphListener does not receive FlowStartNode
Title: Message Title Allan Lewis assigned an issue to Allan Lewis Jenkins / JENKINS-52189 GraphListener does not receive FlowStartNode Change By: Allan Lewis Assignee: Devin Nusbaum Allan Lewis Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52189) GraphListener does not receive FlowStartNode
Title: Message Title Devin Nusbaum commented on JENKINS-52189 Re: GraphListener does not receive FlowStartNode Thomas Weißschuh If you can figure out a clean way to make it work and submit a PR, then I'd be happy to review it. I don't think there is any reason why we wouldn't want it to work, just that the most obvious implementation happens to not work for that use case. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52189) GraphListener does not receive FlowStartNode
Title: Message Title
Thomas Weißschuh commented on JENKINS-52189
Re: GraphListener does not receive FlowStartNode
My current code is nicer to implement with customly created listeners. I can rewrite it to use the global one but wanted to ask before, as maybe it should actually work. My FlowExecutionListener creates a GraphListener for every new Flow (and stores it). The following snippet works around the currently missing functionality by triggering the creation of the GraphListener "manually":
import hudson.Extension;
import org.jenkinsci.plugins.workflow.flow.GraphListener;
import org.jenkinsci.plugins.workflow.graph.FlowNode;
import org.jenkinsci.plugins.workflow.graph.FlowStartNode;
/*
* This class works around https://issues.jenkins-ci.org/browse/JENKINS-52189
* Especially the part where GraphListeners attached during FlowExecutionListener.onRunning() do not receive the FlowStartNode.
* As the per instance logic is nicer to reason about and may work properly in a future version of Jenkins,
* this class will be the bridge until then.
*/
@Extension
public class WorkaroundGraphListener implements GraphListener, GraphListener.Synchronous {
@Override
public void onNewHead(FlowNode node) {
final OTFlowExecutionListener flowExecutionListener = OTFlowExecutionListener.get();
if (node instanceof FlowStartNode) {
flowExecutionListener.getListener(node.getExecution()).onNewHead(node);
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you 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-49221) Slave getting disconnected after some idle time.
Title: Message Title Maciek Sroczynski commented on JENKINS-49221 Re: Slave getting disconnected after some idle time. It seems like when you connect the node and then remove it somehow and want to reconnect it is going into connected/disconnected loop... any ideas? (slave service removed from node as well as cleaning the working dir) STARTING WITH CMD LINE: Both error and output logs will be printed to c:\jenkins\remoting lut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: HPek lut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. lut 13, 2019 5:19:32 PM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.28 lut 13, 2019 5:19:32 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using c:\jenkins\remoting as a remoting work directory lut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among http://IP:PORT/ lut 13, 2019 5:19:32 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] lut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: IP Agent port: PORT Identity: IDENTITY lut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking lut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to IP:PORT lut 13, 2019 5:19:32 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP4-connect lut 13, 2019 5:19:38 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Remote identity confirmed: IDENTITY lut 13, 2019 5:19:39 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected lut 13, 2019 5:19:52 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Terminated lut 13, 2019 5:20:02 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Performing onReconnect operation. lut 13, 2019 5:20:02 PM hudson.remoting.jnlp.Main$CuiListener status INFO: onReconnect operation completed. lut 13, 2019 5:20:02 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among http://IP:PORT/ AND SO ON, and on Add Comment
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Henry Borchers commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I'm running into this more and more. I've put what makes sense into shared libraries and squeeze more and more into ugly "helper functions" outside of the pipeline but it's getting really hard. I really hope there is a better solution coming soon because I'm pretty sure that my coworkers are working with HR to have a talk with me about how much swearing I've been doing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-3404) mix LDAP and local Hudson users
Title: Message Title Mike Machnik edited a comment on JENKINS-3404 Re: mix LDAP and local Hudson users As mentioned in some of the comments above, allowing for both LDAP and local security allows for real users to have access but also allowing for local users to be created for automation. This support would allow us to create an ideal security environment for real users and our automation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56129) Content Replace Plugin - File path doesn't recognise Environment variables
Title: Message Title
Pedro Maia created an issue
Jenkins / JENKINS-56129
Content Replace Plugin - File path doesn't recognise Environment variables
Issue Type:
Bug
Assignee:
mo xun
Components:
content-replace-plugin
Created:
2019-02-13 16:22
Environment:
Jenkins: 2.164 Content Replace Plugin: 1.0.2
Priority:
Major
Reporter:
Pedro Maia
The 'file path' field accepts a hard-coded value like: \\A21-T1-APP074\E$\D2 DMS 1.1.1\Scripts\applySecurityToFilePlan.dql but will not accept environment variables previously injected by the EnvInject Plugin like: \\${CS_SERVER}\E$\D2 DMS 1.1.1\Scripts\applySecurityToFilePlan.dql This makes the Plugin limited as there is no flexibility on the definition of the file to be processed.
Add Comment
[JIRA] (JENKINS-3404) mix LDAP and local Hudson users
Title: Message Title Mike Machnik commented on JENKINS-3404 Re: mix LDAP and local Hudson users As mentioned in some of the comments above, allowing for both LDAP and local security allows for real users to have access but also allowing for local users to be created for automation. This support would allow us to create an ideal security environment for real users and automation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52189) GraphListener does not receive FlowStartNode
Title: Message Title Devin Nusbaum commented on JENKINS-52189 Re: GraphListener does not receive FlowStartNode Thomas Weißschuh I don't know. If you have a use case where you need to use FlowExecutionListener.onRunning to add a listener and cannot use a global extension, then perhaps better to file a separate bug for that specific case. Otherwise, maybe we can just update the docs for FlowExecutionListener#onRunning to mention that if you add a listener in that method it will not see FlowStartNodes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56128) Job import plugin allows credential dumping
Title: Message Title Joshua Ganger updated an issue Jenkins / JENKINS-56128 Job import plugin allows credential dumping Change By: Joshua Ganger Logged into Jenkins with a valid user, no unrestricted credentials assigned/scoped to my user. No permission to view or add credentials assigned to my user. Job import plugin has several users available, appearing in the dropdown as "username/***". If I enter a query URL for an http server that I control and select one of these credentials, the password is transmitted in base64 encoding in the HTTP get request. This essentially allows me to dump any of these stored credentials despite not being allowed to access them through the credentials page. It's possible that I misunderstand this functionality or that we have a misconfiguration, but this seems abuseable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52189) GraphListener does not receive FlowStartNode
Title: Message Title
Thomas Weißschuh edited a comment on JENKINS-52189
Re: GraphListener does not receive FlowStartNode
Another point (also raised on the PR):Should it be possible to use the instantiation based usage of GraphListener (asexplained by its javadoc?Something like the follow following test:{code} @Issue("JENKINS-52189")@Testpublic void notifyFlowStartNodeViaFlowExecutionListener() {story.then(s->{WorkflowJob j = jenkins().createProject(WorkflowJob.class, "bob");j.setDefinition(new CpsFlowDefinition("echo 'I did a thing'", true));WorkflowRun r = story.j.buildAndAssertSuccess(j);FlowStartNodeFlowExectionListener listener = jenkins().getExtensionList(FlowStartNodeFlowExectionListener.class).get(0);assertThat(listener.heads, Matchers.greaterThan(1));assertThat(listener.execNames, Matchers.contains(r.getExecution().toString()));});}@TestExtension("notifyFlowStartNodeViaFlowExecutionListener")public static class FlowStartNodeFlowExectionListener extends FlowExecutionListener {int heads = 0;final List execNames = new ArrayList<>();@Overridepublic void onRunning(@Nonnull FlowExecution execution) {execution.addListener(node -> {heads++;if (node instanceof FlowStartNode) {execNames.add(node.getExecution().toString());}});}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52189) GraphListener does not receive FlowStartNode
Title: Message Title Thomas Weißschuh reopened an issue Jenkins / JENKINS-52189 GraphListener does not receive FlowStartNode Change By: Thomas Weißschuh Resolution: Fixed Status: Resolved Reopened Assignee: Sam Van Oort Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56128) Job import plugin allows credential dumping
Title: Message Title Joshua Ganger created an issue Jenkins / JENKINS-56128 Job import plugin allows credential dumping Issue Type: Bug Assignee: Unassigned Components: job-import-plugin Created: 2019-02-13 15:58 Environment: Jenkins ver. 2.150.2 Priority: Minor Reporter: Joshua Ganger Logged into Jenkins with a valid user, no unrestricted credentials assigned/scoped to my user. Job import plugin has several users available, appearing in the dropdown as "username/***". If I enter a query URL for an http server that I control and select one of these credentials, the password is transmitted in base64 encoding in the HTTP get request. This essentially allows me to dump any of these stored credentials despite not being allowed to access them through the credentials page. It's possible that I misunderstand this functionality or that we have a misconfiguration, but this seems abuseable. Add Comment
[JIRA] (JENKINS-56122) Not able to run UFT Scripts in UFT 14.50 via Jenkins
Title: Message Title Sakthi Isai Bharathi Samundeeswari commented on JENKINS-56122 Re: Not able to run UFT Scripts in UFT 14.50 via Jenkins Daniel Gront Jenkins Version - 2.150 and Micro Focus Application Automation Tools 5.6.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams edited a comment on JENKINS-41102 Re: Job "Changes" do not match "Filter for Poll SCM" * 15/Oct/ 2018 -10-15 update:*Micro Focus internal defect RPI #1115588 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams commented on JENKINS-41102 Re: Job "Changes" do not match "Filter for Poll SCM" 15/Oct/2018 update: Micro Focus internal defect RPI #1115588 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56031) SSH plugin rains intermittently with because of issue with JSch
Title: Message Title Jeff Thompson commented on JENKINS-56031 Re: SSH plugin rains intermittently with because of issue with JSch Matt Sicker, right. I released the jsch-plugin 0.1.55 containing the fix the for this. The ssh-plugin should be updated to reference the new jsch-plugin version. V Kusumanchi might be able to update the jsch-plugin version and test it out. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56126) Jenkins 2.150.2 - Remote Command Execution (Metasploit)
Title: Message Title Daniel Beck edited a comment on JENKINS-56126 Re: Jenkins 2.150.2 - Remote Command Execution (Metasploit) Yes. Someone who has permission to create jobs in Jenkins can run shell commands on noes nodes (master or agents) configured to accept their jobs. That's what Jenkins does. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54143) Cannot create new users in 2.138.2
Title: Message Title Daniel Beck closed an issue as Duplicate https://jenkins.io/security/advisory/2018-05-09/#SECURITY-786 explains the rationale behind the change, and provides a workaround if you need periods in your user names. The lack of form validation bug was fixed in JENKINS-52869, so closing this issue as a duplicate. Jenkins / JENKINS-54143 Cannot create new users in 2.138.2 Change By: Daniel Beck Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56127) vSphere-cloud-plugin RenameSnapshot should support failOnNoExist
Title: Message Title Uwe Hanisch created an issue Jenkins / JENKINS-56127 vSphere-cloud-plugin RenameSnapshot should support failOnNoExist Issue Type: Improvement Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2019-02-13 15:19 Priority: Major Reporter: Uwe Hanisch Before I patch my VM, I want: delete the old snapshot (class DeleteSnapshot) rename the latest/current snapshot to old (class RenameSnapshot) take a new current snapshot (class TakeSnapshot) Since I want it done by a Jenkins Pipeline automatically, I can not predict if there any of the current or old vm snapshot exists. DeleteSnapshot supports failOnNoExist parameter. If is set to false, the build step doesn't fail, if the snapshot does not exists. RenameSnapshot doesn't supports failOnNoExist. If the snapshot to be renamed doesn't exists, the build step fails in any case. Steps to solve it: RenameSnapshot should be extended with boolean failOnNoExist parameter VSphere#renameVmSnapshot should be extended with boolean failOnNoExist parameter and treet a non existing snapshot like the VSphere#deleteSnapshot method To be discussed: default value/behaviour of failOnNoExist
[JIRA] (JENKINS-56031) SSH plugin rains intermittently with because of issue with JSch
Title: Message Title Matt Sicker commented on JENKINS-56031 Re: SSH plugin rains intermittently with because of issue with JSch But the jsch-plugin is already updated to JSCH 0.1.55. You made the release: https://github.com/jenkinsci/jsch-plugin/releases/tag/jsch-0.1.55 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Mark Waite commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ Iurii Mark I would be truly amazed if the Analysis Model API plugin downgrade were the root cause of the problem, especially since this problem was reported before Analysis Model API 2.0 was released. I don't know why the behavior changed when you downgraded. It could be that the downgrade also included a Jenkins restart. It could be that the restart from the downgrade changed some startup ordering or caused the PATH to be initialized differently. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
