[JIRA] (JENKINS-57269) Declarative pipeline with ssh-steps-plugin
Title: Message Title
Davide F commented on JENKINS-57269
Re: Declarative pipeline with ssh-steps-plugin
Hello Naresh Rayapati, Thanks for your quick feedback. Here's how I've tried to use script block in a declarative pipeline pipeline { agent any stages { stage ('Main Stage') { steps { script { stage ('nothing but display a message') { echo 'First stage' {{ }}} stage ('ssh') { def remote = [:] remote.name = "hostname" remote.host = "fqdn-hostname" remote.port = custom-port remote.allowAnyHosts = true withCredentials([sshUserPrivateKey(credentialsId: '', keyFileVariable: 'key', passphraseVariable: 'passphrase', usernameVariable: 'username')]) { remote.passphrase = passphrase sshGet(remote: remote, from: 'abc.sh', into: 'abc.sh', override: true) {{ }}} {{ }}} {{ }}} {{ }}} {{ }}} } } The job is "stuck" at sshGet step and I have to terminate the step manually to get the job finish. But if I use the example below (using sshagent), the job works just fine. pipeline { agent any stages { stage ('Main Stage') { steps { script { stage ('nothing but display a message') { echo 'First stage' {{ }}} stage ('ssh') { withCredentials([sshUserPrivateKey(credentialsId: '}}{{x}}{{', keyFileVariable: 'key', passphraseVariable: 'passphrase', usernameVariable: 'username')]) { {{ remote.passphrase = passphrase}} sshagent(['x']) { sh 'scp -o StrictHostKeyChecking=no $username@hostname:~/abc.sh .' {{ }}} {{ }}} {{ }}} {{ }}} {{ }}} {{ }}} {{ }}} } Any idea ? Thanks for your help Davide
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribe
[JIRA] (JENKINS-57269) Declarative pipeline with ssh-steps-plugin
Title: Message Title
Davide F edited a comment on JENKINS-57269
Re: Declarative pipeline with ssh-steps-plugin
Hello [~nrayapati],Thanks for your quick feedback.Here's how I've tried to use script block in a declarative pipeline{{pipeline {}}{{ agent any}}{{ stages {}}{{ stage ('Main Stage') {}}{{ steps {}}{{ script {}}{{ stage ('nothing but display a message') {}}{{ echo 'First stage'}} {{ } }} {{ stage ('ssh') {}}{{ def remote = [:]}}{{ remote.name = "hostname"}}{{ remote.host = "fqdn-hostname"}}{{ remote.port = custom-port}}{{ remote.allowAnyHosts = true}}{{ withCredentials([sshUserPrivateKey(credentialsId: '', keyFileVariable: 'key', passphraseVariable: 'passphrase', usernameVariable: 'username')]) {}}{{ remote.passphrase = passphrase}}{{ sshGet(remote: remote, from: 'abc.sh', into: 'abc.sh', override: true)}} {{ } }} {{ } }} {{ } }} {{ } }} {{ } }} {{ }}}{{}}}The job is "stuck" at sshGet step and I have to terminate the step manually to get the job finish.But if I use the example below (using sshagent), the job works just fine.{{pipeline {}}{{ agent any}}{{ stages {}}{{ stage ('Main Stage') {}}{{ steps {}}{{ script {}}{{ stage ('nothing but display a message') {}}{{ echo 'First stage'}} {{ } }} {{ stage ('ssh') {}}{{ withCredentials([sshUserPrivateKey(credentialsId: ' }}{{ x }}{{ ', keyFileVariable: 'key', passphraseVariable: 'passphrase', usernameVariable: 'username')]) {}} \ {{ remote.passphrase = passphrase}}{{ sshagent(['x']) {}}{{ sh 'scp -o StrictHostKeyChecking=no $username@hostname:~/abc.sh .'}} {{ } }} {{ } }} {{ } }} {{ } }} {{ } }} {{ } }} {{ } }} {{}}}Any idea ?Thanks for your helpDavide
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56666) maven-git-versioning-extension causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml'
Title: Message Title Michael Düsterhus reopened an issue Sorry hat no time before to test. I tried version 3.6.11 and the error is still the same. Did you consider that this plugin modifies the pom.xml to target/.git-versioned.pom.xml So its not in the same directory. Jenkins / JENKINS-5 maven-git-versioning-extension causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml' Change By: Michael Düsterhus 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-57300) Blue Ocean wrong log display
Title: Message Title Loïc Collignon created an issue Jenkins / JENKINS-57300 Blue Ocean wrong log display Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-05-02 08:14 Environment: Jenkins: 1.15.1 - Core 2.175 - 43483b9 Client Browser: Chromium 74.0.3729.108 Client Os: Arch Linux (64 bits) Priority: Minor Reporter: Loïc Collignon Step 1: I received a mail with a URL like this: http:///job//53/display/redirect?page=changes This is showing only a table of commits, but no log. The run is on a success state (green top-bar) Step 2: If I click on "previous run", on the top left corner, it goes back to the previous run, which was failing (red top-bar). This time a log is displayed, showing what was on error. Step 3: Now I click on "next run", going back to the run displayed on step 1, but this time there is a log. But the log is the one from step 2. So the log report errors, while there is a green top-bar and the real log is error free. You can close the view, using the top right corner close button, to go back to the run list. Then if you click on the right run, you get the right log, error free.
[JIRA] (JENKINS-54782) Change Subversion plugin version over JCASC
Title: Message Title Michael Düsterhus reopened an issue This is a valid issue as the subversion plugin does not allow to configure its setting with Jcasc Jenkins / JENKINS-54782 Change Subversion plugin version over JCASC Change By: Michael Düsterhus Resolution: Not A Defect 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-54782) Change Subversion plugin version over JCASC
Title: Message Title Michael Düsterhus updated an issue Jenkins / JENKINS-54782 Change Subversion plugin version over JCASC Change By: Michael Düsterhus Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43693) multibranchPipelineJob overrides old branch indexing sources
Title: Message Title J Knurek commented on JENKINS-43693 Re: multibranchPipelineJob overrides old branch indexing sources I'm with Ray Kivisto on this. I don't think this issue should be "Closed/Fix" if the default functionality still doesn't work as expected. The ability to set the `id` does solve the problem, but in my opinion this is a workaround. And if a workaround is required, this should be clearly documented. Or even better, the default functionality should be the expected functionality. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35158) search box provides 404 and duplicates results for jobs in folders
Title: Message Title Philip Johnson resolved as Fixed I reopened this issue as it was reproducible in v2.150.3 with Folders plugin 6.8, but having updated to v2.164.1, the issue is resolved, so marking it as resolved again. Jenkins / JENKINS-35158 search box provides 404 and duplicates results for jobs in folders Change By: Philip Johnson Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57214) NPE on getYaml when using Config-as-code
Title: Message Title Carlos Sanchez updated JENKINS-57214 Jenkins / JENKINS-57214 NPE on getYaml when using Config-as-code Change By: Carlos Sanchez Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57301) Blue Ocean Plugin does not support INPUT_PARAMS
Title: Message Title Ahmed Itman created an issue Jenkins / JENKINS-57301 Blue Ocean Plugin does not support INPUT_PARAMS Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-05-02 08:59 Priority: Critical Reporter: Ahmed Itman I was using INPUT_PARAMS to get inputs from user Now, I am trying to use blue ocean,SO : I installed Blue Ocean in Plugins in Jenkins Built the Job , their is a problem that ==> Error This pipeline uses input types that are unsupported. Use Jenkins Classic to resolve this input step. Resolve Input 4. When cliking on Reslove Inputs, It will redirect to the old Gui for INPUT_PARAMS Any Recommendation to solve that Issue ? OR their is an alternative option instead of INPUT_PARAMS in Blue Ocean Thanks in advance Add Comment
[JIRA] (JENKINS-57301) Blue Ocean Plugin does not support INPUT_PARAMS
Title: Message Title Ahmed Itman updated an issue Jenkins / JENKINS-57301 Blue Ocean Plugin does not support INPUT_PARAMS Change By: Ahmed Itman I was using *INPUT_PARAMS* to get inputs from user Now, I am trying to use blue ocean,SO : # I installed Blue Ocean in Plugins in Jenkins # Built the Job , their is a problem that ==> ErrorThis pipeline uses input types that are unsupported. Use Jenkins Classic to resolve this input step. [ Resolve Input |http://localhost:8080/job/TestParametersGroovy/91/input] 4. When cliking on Reslove Inputs, It will redirect to the old *Gui* for *INPUT_PARAMS* Any Recommendation to solve that Issue ?OR their is an alternative option instead of *INPUT_PARAMS* in Blue Ocean Thanks in advance Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57301) Blue Ocean Plugin does not support INPUT_PARAMS
Title: Message Title Ahmed Itman assigned an issue to Thorsten Scherler Jenkins / JENKINS-57301 Blue Ocean Plugin does not support INPUT_PARAMS Change By: Ahmed Itman Assignee: Thorsten Scherler Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57302) Running out of inodes on jenkins server
Title: Message Title mor san created an issue Jenkins / JENKINS-57302 Running out of inodes on jenkins server Issue Type: Bug Assignee: Craig Rodrigues Components: scm-sync-configuration-plugin Created: 2019-05-02 09:25 Priority: Minor Reporter: mor san Hi, We are running out of free indoes on our jenkins server. Must of the inodes are taken by the many files under "/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/.git/objects" - there are many files there. some of the are 3 years old. is is safe to delete them? if so, how can we prevent it from fulling up again? Add Comment
[JIRA] (JENKINS-57301) Blue Ocean Plugin does not support INPUT_PARAMS
Title: Message Title Ahmed Itman updated an issue Jenkins / JENKINS-57301 Blue Ocean Plugin does not support INPUT_PARAMS Change By: Ahmed Itman Component/s: jenkinsfile-runner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57301) Blue Ocean Plugin does not support INPUT_PARAMS
Title: Message Title Ahmed Itman commented on JENKINS-57301 Re: Blue Ocean Plugin does not support INPUT_PARAMS I think the problem is with Dynamic ==> for example if you are using Active choices parameter which use groovy script to get data and fill the parameter Those ERROR Message will raise If you are using Pipeline script get data dynamically this ERROR Message will raise So, Any Recommendations ? Thanks a million Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57246) "Git LFS pull after checkout" has no effect on build node
Title: Message Title Przemysław Czechowski commented on JENKINS-57246 Re: "Git LFS pull after checkout" has no effect on build node It was just a silly mistake on my side: I was adding LFS Pull option to wrong SCM. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title Andrei Costescu commented on JENKINS-33843 Re: It's not possible to disable/uninstall optional dependencies Great news that this is resolved. Which version will have this fixed? (I see it in Jenkins ver. 2.164.2 where I can't uninstall Static Analysis Utilities 1.96 (which has a security warning and is end-of-life) due to an optional dependency to it from Email Extension Plugin 2.66 which I still use) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57303) Duplicate builds triggered from webhook (push) on branch pipelines
Title: Message Title Mads Navntoft Noe created an issue Jenkins / JENKINS-57303 Duplicate builds triggered from webhook (push) on branch pipelines Issue Type: Bug Assignee: Kirill Merkushev Attachments: Screenshot 2019-05-02 at 12.16.19.png Components: github-branch-source-plugin, github-plugin Created: 2019-05-02 10:29 Environment: OS: 16.04.6 LTS 4.4.0-1081-aws OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_212-b03) OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.212-b03, mixed mode) Jenkins ver. 2.150.2 GitHub plugin 1.29.4 GitHub Branch Source Plugin 2.5.1 Jenkins is accessed through reverse proxy (nginx via proxy_pass). Priority: Minor Reporter: Mads Navntoft Noe Occasionally, a push to a branch triggers two builds on the corresponding branch in a multibranch pipeline. We are using the GitHub as branch source, and have added a organization wide GitHub webhook on push only. I am not sure about the relationship between the GitHub plugin and the GitHub branch source plugin. On normal builds we see the following two lines: Started by GitHub push by (author) Push event to branch master at 9:31:27 AM on May 2, 2019 Each of the builds that are triggered twice has just one of the above lines, i.e. Started by GitHub push by (author)
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title Ionut Balutoiu commented on JENKINS-57154 Re: HTTP ERROR 403 This issue affects me as well. Considering that version 0.31 is affected by a CSRF vulnerability (https://jenkins.io/security/advisory/2019-04-30/#SECURITY-443), do you guys have any ETA for fixing this, so we can update to 0.32 as soon as possible ? Without any workaround for this issue, it's hard to maintain a Matrix-based security authorization using 0.32, since you'll get error 403 for every user present there. Thank-you, Ionut Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title Daniel Beck commented on JENKINS-33843 Re: It's not possible to disable/uninstall optional dependencies Are you sure? analysis-core 1.96 should not have a security warning, we fixed that 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-54782) Change Subversion plugin version over JCASC
Title: Message Title Michael Düsterhus updated an issue Jenkins / JENKINS-54782 Change Subversion plugin version over JCASC Change By: Michael Düsterhus How can I change this parameter? It doesn't seem available.I want Please allow to change it to 1 configure subversion plugin settings like workspace format by the casc plugin . 8. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54782) Change Subversion plugin version over JCASC
Title: Message Title Michael Düsterhus updated an issue Jenkins / JENKINS-54782 Change Subversion plugin version over JCASC Change By: Michael Düsterhus How can I change this parameter? It doesn't seem available.I want Please allow to change it to 1 configure subversion plugin settings like workspace format by the casc plugin . 8. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57275) Bitbucket Hook to Jenkins URL parameters
Title: Message Title Mark Waite updated JENKINS-57275 Jenkins / JENKINS-57275 Bitbucket Hook to Jenkins URL parameters Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57275) Bitbucket Hook to Jenkins URL parameters
Title: Message Title Mark Waite updated JENKINS-57275 Thanks. That means you've accepted the risks from keeping undefined parameters. The risks seemed significant enough to the Jenkins project that it was included in a security advisory. Be sure that the webhook is an authenticated web hook so that you safeguard yourself from unauthenticated calls passing parameters to jobs. Jenkins / JENKINS-57275 Bitbucket Hook to Jenkins URL parameters Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49332) Jenkins unable to manage webhooks of Github organization
Title: Message Title Tarjei Huse commented on JENKINS-49332 Re: Jenkins unable to manage webhooks of Github organization Any news here? I have tried very hard to find a place in Jenkins to set the username for the secret key, but have failed and thus Jenkins reports my ORGNAME as the username when connecting to GitHub. Is there a way to configure this in Jenkins I'm not seeing? In the comments above I see some references to "Projects->GitHub Organization->Owner under your Jenkins GitHub organisation" but I cannot find any such link in my Jenkins install. Regards, Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57301) Blue Ocean Plugin does not support INPUT_PARAMS
Title: Message Title Ahmed Itman commented on JENKINS-57301 Re: Blue Ocean Plugin does not support INPUT_PARAMS Blue Ocean does not support Interactive Inputs, Right ? If yes please Find a solution Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57301) Blue Ocean Plugin does not support INPUT_PARAMS
Title: Message Title Ahmed Itman commented on JENKINS-57301 Re: Blue Ocean Plugin does not support INPUT_PARAMS Thorsten Scherler Aaron Jenkins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Patrick Rose created an issue Jenkins / JENKINS-57304 Multiple "idle" entries on Build Executor Status for non-existant executors Issue Type: Bug Assignee: Unassigned Attachments: Screenshot_2019-05-02_12-14-44.png Components: core Created: 2019-05-02 11:19 Environment: Jenkins 2.175 Web browser: Chrome 73 Priority: Trivial Reporter: Patrick Rose We have a jenkins environment where we have a single server with multiple executors (4). Sometimes the display has multiple idles, even though all executors are in use: Add Comment
[JIRA] (JENKINS-57233) Support "shortest timeout"parameter at TimeoutContext build stuck plugin
Title: Message Title
Bernhard M updated JENKINS-57233
Thank you for the example. Not sure why I didn't find it myself even when browsing the dynamic documentation on my jenkins. Addition: It will only work if you add
timeoutEnvVar('BUILD_TIMEOUT_OCCURED')
because for some reason this is mandatory.
Jenkins / JENKINS-57233
Support "shortest timeout"parameter at TimeoutContext build stuck plugin
Change By:
Bernhard M
Status:
Fixed but Unreleased Closed
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57218) NPE from SymbolLookup after job-dsl update without configuration-as-code
Title: Message Title Ivan Dimitrov commented on JENKINS-57218 Re: NPE from SymbolLookup after job-dsl update without configuration-as-code I can confirm that the issue still exists. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57219) Parallel Pipeline stages on multiple nodes require n+1 executors
Title: Message Title
Christian Poessinger commented on JENKINS-57219
Re: Parallel Pipeline stages on multiple nodes require n+1 executors
I think I resolved the issue by replacing the top most agent definition from "label Docker" to "none" This does not require the additional (+1) executor as all is handled on the master itself. pipeline { agent none }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54782) Change Subversion plugin version over JCASC
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-54782 Change Subversion plugin version over JCASC Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57301) Blue Ocean Plugin does not support INPUT_PARAMS
Title: Message Title Thorsten Scherler assigned an issue to Unassigned Jenkins / JENKINS-57301 Blue Ocean Plugin does not support INPUT_PARAMS Change By: Thorsten Scherler Assignee: Thorsten Scherler Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56786) Safe restart is not safe when some jobs are running
Title: Message Title kutzi commented on JENKINS-56786 Re: Safe restart is not safe when some jobs are running In my experience pipeline jobs often don't survive a master restart. Even though they 'should' I know, but I don't know what we could have done wrong in all of our pipelines so that all of them tend to fail a lot, when restarting master. At the very least the description of safeRestart is wrong, as James Withers said: `Are you sure you want to restart Jenkins? Jenkins will restart once all running jobs are finished.` For pipeline jobs it only - if at all - waits for the current stage to finish Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57305) Copy/Paste from logs adds an extra blank line after every line
Title: Message Title Mike Parker created an issue Jenkins / JENKINS-57305 Copy/Paste from logs adds an extra blank line after every line Issue Type: Bug Assignee: Unassigned Attachments: image-2019-05-02-13-44-43-012.png Components: blueocean-plugin Created: 2019-05-02 12:47 Priority: Minor Reporter: Mike Parker When copying output from the log file into another place such as Slack, JIRA, Github, Jenkins adds extra blank lines which need manually removing which is very tedious and annoying. For example if I highlight some text like this Pasting into this window in Jira gives me: [2019-05-02T10:46:40.961Z] running [git clean -xdf win\src\Resources] [2019-05-02T10:46:40.961Z] Removing win/src/Resources/CHANGELOG [2019-05-02T10:46:40.961Z] Removing win/src/Resources/LICENSE.rtf [2019-05-02T10:46:40.961Z] Removing win/src/Resources/UpdateChannel It'd be great if there was no extra lines. Thanks!
[JIRA] (JENKINS-54782) Change Subversion plugin version over JCASC
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54782 Re: Change Subversion plugin version over JCASC the origin issue description is completely different, so now it is a new issue, I've unassigned me because I am no longer the maintainer of the plugin, and keep the issue open in case someone wants to take 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-54782) Change Subversion plugin version over JCASC
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-54782 Change By: Ivan Fernandez Calvo Status: Reopened 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-54782) Change Subversion plugin version over JCASC
Title: Message Title Ivan Fernandez Calvo stopped work on JENKINS-54782 Change By: Ivan Fernandez Calvo 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-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah commented on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" Bernd Wanko The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names. See comment 28 in 259131: HPI: Expose RTC Build properties in the Jenkins build environment Having said that since '' can be included in the name of the environment variables, if the build property name contains '' it should be retained. '_' in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have _ in the property names in the build definition and ignores _ when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix. In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to _ by the teamconcert plugin when creating the corresponding environment variables in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com / ].See comment 28 in[259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131]Having said that since ' _ __ ' can be included in the name of the environment variables, if the build property name contains ' _ __ ' it should be retained. '_' in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have _ in the property names in the build definition and ignores _ when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to _ by the teamconcert plugin when creating the corresponding environment variables in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/].See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__' _ can be included in the name of the environment variables, if the build property name contains _ ' __ ___ ' _ it should be retained retained_ . '_' in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have _ in the property names in the build definition and ignores _ when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to _ by the teamconcert plugin when creating the corresponding environment variables in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/].See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained_ retained . '_' in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have ' _ ' in the property names in the build definition and ignores ' _ ' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to _ by the teamconcert plugin when creating the corresponding environment variables in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/].See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. ' _ __ ' _ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have '_' in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to ' _ ' by the teamconcert plugin when creating the corresponding environment variables in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/].See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. '__'_ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have ' _ __ ' _ in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to '_' by the teamconcert plugin when creating the corresponding environment variables in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [ [ https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names| | http://example.com/] [https://stackoverflow . com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/] []|http://example.com/]. See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. '__'_ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have '__'_ in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to '_' by the teamconcert plugin when creating the corresponding environment variables in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving email
[JIRA] (JENKINS-57219) Parallel Pipeline stages on multiple nodes require n+1 executors
Title: Message Title Christian Poessinger assigned an issue to Christian Poessinger Jenkins / JENKINS-57219 Parallel Pipeline stages on multiple nodes require n+1 executors Change By: Christian Poessinger Assignee: Christian Poessinger Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [ [ https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names| | http://example.com/] [https://stackoverflow . com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/] []|http://example.com/]. See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. '__'_ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have '__'_ in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to '_' by the teamconcert plugin when creating the corresponding environment variables in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving email
[JIRA] (JENKINS-56786) Safe restart is not safe when some jobs are running
Title: Message Title Rick commented on JENKINS-56786 Re: Safe restart is not safe when some jobs are running For some situations, a pipeline job is an atom unit. And a stage is just a part of the pipeline job. I still think that the restart action should wait the whole pipeline job is finished. Or leave an option for that at least. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [ [|http://example.com/] [ https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/] [||http://example . com/] [https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/] []|http://example.com/]. See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. '__'_ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have '__'_ in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to '_' by the teamconcert plugin when creating the corresponding environment variables in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscr
[JIRA] (JENKINS-57219) Parallel Pipeline stages on multiple nodes require n+1 executors
Title: Message Title Christian Poessinger updated JENKINS-57219 Jenkins / JENKINS-57219 Parallel Pipeline stages on multiple nodes require n+1 executors Change By: Christian Poessinger Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in [ [|http://example.com/] [https://stackoverflow.com/questions/2821043/allowed- Allowed characters - in -linux- Linux environment - variable - names| http://example.com/] [ ||http://example.com/] [ https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/] [ ] |http://example.com/]. See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. '__'_ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have '__'_ in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to '_' by the teamconcert plugin when creating the corresponding environment variables in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-57220) RTC build property names: Underscore chars "swallowed"
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-57220 Re: RTC build property names: Underscore chars "swallowed" [~bernddasbrot]The current behavior when exporting the build properties from RTC build definition to environment variables in Jenkins build is to keep only alpha-numeric characters, change '.' to '_' and ignore the rest. If the result is empty or begins with a digit then no environment variable is created for that property. This is because of the restrictions on the characters allowed in environment variable names in some operating systems as described in[Allowed characters in Linux environment variable names| [ https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names|http://example.com/] ] See comment 28 in [259131: HPI: Expose RTC Build properties in the Jenkins build environment|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/259131] Having said that since '__'_ can be included in the name of the environment variables, if the build property name contains _'___'_ it should be retained. '__'_ in the property names being ignored is a defect in the teamconcert plugin. Though it is unlikely that there are existing builds which have '__'_ in the property names in the build definition and ignores '_' when referring to them in Jenkins build, otherwise this issue would have been reported earlier, this scenario can't be ruled out while making the fix.In the mean time would it be possible for you to use '.' in the name of the properties added in the build definition which would then be converted to '_' by the teamconcert plugin when creating the corresponding environment variables in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, vis
[JIRA] (JENKINS-57306) Can't check "Disable the host SSH key check" in Ansible plugin through JobDSL
Title: Message Title
bouke b created an issue
Jenkins / JENKINS-57306
Can't check "Disable the host SSH key check" in Ansible plugin through JobDSL
Issue Type:
Bug
Assignee:
Jean-Christophe Sirot
Components:
ansible-plugin
Created:
2019-05-02 13:08
Environment:
Jenkins 2.164.1, Job DSL 1.72, Ansible plugin 1.0. Jenkins runs on Linux Redhat.
Priority:
Minor
Reporter:
bouke b
Given a Jenkins installation with the latest Job DSL and Ansible plugin, as far as I understand the following DSL code should generate a Jenkins job with two 'Invoke Ansible Playbook' build steps. But it doesn't: it creates the two steps just fine, but the 'Invoke Ansible Playbook' checkbox remains disabled for both generated steps. Note that all other supported chechboxes and fields work just fine.
job('reproducer-job') {
description('Reproducer dsl seed job')
steps {
ansiblePlaybook('test-host-key-checking-false.yml') {
inventoryPath('test-inventory.ini')
hostKeyChecking(false)
}
ansiblePlaybook('test-host-key-checking-true.yml') {
inventoryPath('test-inventory.ini')
hostKeyChecking(true)
}
}
}
[JIRA] (JENKINS-57307) Job Sidepanel Favorite Task item shows up half-rendered when user is not logged in.
Title: Message Title
Flemming Steffensen created an issue
Jenkins / JENKINS-57307
Job Sidepanel Favorite Task item shows up half-rendered when user is not logged in.
Issue Type:
Bug
Assignee:
James Dumay
Components:
favorite-plugin
Created:
2019-05-02 13:10
Environment:
Jenkins 2.172 Favorite plugin 2.3.2
Priority:
Major
Reporter:
Flemming Steffensen
We have an issue where an invalid 'task' is shown in (any) jobs side-panel whenever the user is not logged in. It appear to be a half rendition of the favorite task. Looking at the html, this is what I find:
"task">
function postRequest_id7642(a) {
new Ajax.Request(a.href);
hoverNotification('Done.', a.parentNode);
return false;
}
"return postRequest_id7642(this)" href="" class="code-quote" style="color: #009100">"/" class="task-icon-link">
"/" alt="" style="width: 24px; height: 24px; margin: 2px;">
"return postRequest_id7642(this)" href="" class="code-quote" style="color: #009100">"/" class="task-link">
Whenever I log in, the above has it's proper data (project path, user name etc.) filled in as this:
[JIRA] (JENKINS-56443) EC2 plugin doesn't take into account 'shutdown mode' of Jenkins
Title: Message Title FABRIZIO MANFREDI started work on JENKINS-56443 Change By: FABRIZIO MANFREDI 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-56927) Request: EC2 plugin should use SSH keys via credentials plugin
Title: Message Title FABRIZIO MANFREDI started work on JENKINS-56927 Change By: FABRIZIO MANFREDI 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Dax Games commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 No problem, just trying to help. That fixes it! May 02, 2019 1:18:54 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Kubernetes agents: 1 May 02, 2019 1:18:54 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Template for label pd-slave: Kubernetes Pod Template May 02, 2019 1:18:54 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider createClient INFO: Created new Kubernetes client: kubernetes io.fabric8.kubernetes.client.DefaultKubernetesClient@5339d085 May 02, 2019 1:18:54 PM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? May 02, 2019 1:18:54 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0 May 02, 2019 1:19:04 PM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s) May 02, 2019 1:19:04 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Created Pod: pd-pipedream/pd-slave-g6cwh May 02, 2019 1:19:04 PM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? May 02, 2019 1:19:07 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Pod is running: pd-pipedream/pd-slave-g6cwh May 02, 2019 1:19:07 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (0/250): pd-slave-g6cwh May 02, 2019 1:19:08 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (1/250): pd-slave-g6cwh May 02, 2019 1:19:09 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Waiting for agent to connect (2/250): pd-slave-g6cwh Add Comment
[JIRA] (JENKINS-56443) EC2 plugin doesn't take into account 'shutdown mode' of Jenkins
Title: Message Title FABRIZIO MANFREDI updated an issue Jenkins / JENKINS-56443 EC2 plugin doesn't take into account 'shutdown mode' of Jenkins merged, it will part of the 1.43 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title
Dax Games edited a comment on JENKINS-56347
Re: Kubernetes plugin provisioning pods twice in 1.14.6
No problem, just trying to help.That fixes it!{code:java}May 02, 2019 1:18:54 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1May 02, 2019 1:18:54 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label pd-slave: Kubernetes Pod TemplateMay 02, 2019 1:18:54 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesClientProvider createClientINFO: Created new Kubernetes client: kubernetes io.fabric8.kubernetes.client.DefaultKubernetesClient@5339d085May 02, 2019 1:18:54 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?May 02, 2019 1:18:54 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl applyINFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors. Remaining excess workload: 0May 02, 2019 1:19:04 PM hudson.slaves.NodeProvisioner$2 runINFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s)May 02, 2019 1:19:04 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Created Pod: pd-pipedream/pd-slave-g6cwhMay 02, 2019 1:19:04 PM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?May 02, 2019 1:19:07 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Pod is running: pd-pipedream/pd-slave-g6cwhMay 02, 2019 1:19:07 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (0/250): pd-slave-g6cwhMay 02, 2019 1:19:08 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (1/250): pd-slave-g6cwhMay 02, 2019 1:19:09 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (2/250): pd-slave-g6cwh{code} Any idea how long before a new version is released?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56836) Support multiple instance types for one AMI
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-56836 Re: Support multiple instance types for one AMI With the new API of Amazon and the new fleet service, unfortunately it requires deep change Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55618) When using spot instances, requests 3-4 nodes when one is needed
Title: Message Title Rinat Khairullin updated an issue Jenkins / JENKINS-55618 When using spot instances, requests 3-4 nodes when one is needed Change By: Rinat Khairullin Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-55075 Pipeline: If job fails it will run again on next poll. Change By: Karl Wirth Assignee: Paul Allen Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55618) When using spot instances, requests 3-4 nodes when one is needed
Title: Message Title Rinat Khairullin commented on JENKINS-55618 Re: When using spot instances, requests 3-4 nodes when one is needed We are experiencing the same issue, totally unable to use spot instances as plugin creates huge amount of instances that is only limited by cap value. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54461) Grant Job Rerun in a Pipeline as a Individual Permission
Title: Message Title Jed Jacobs commented on JENKINS-54461 Re: Grant Job Rerun in a Pipeline as a Individual Permission We resolved this by granting "build" access to jobs which may require a restart. This is not ideal because this gives ability for people to run the job off-pipeline instead of limiting them to rerun a job only in the context of a pipeline. However, lacking any other solution at this time, that is how we are handling this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54461) Grant Job Rerun in a Pipeline as a Individual Permission
Title: Message Title Jed Jacobs updated JENKINS-54461 Jenkins / JENKINS-54461 Grant Job Rerun in a Pipeline as a Individual Permission Change By: Jed Jacobs Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56685) Stash Pullrequest Builder modify cookie handling
Title: Message Title Brandon Johnson edited a comment on JENKINS-56685 Re: Stash Pullrequest Builder modify cookie handling Jakub, having that in the global configuration would work great. I'm not too good with java, i've been trying to follow it along to see where best to change it but I haven't found it. I do see where I believe I could just change it so it only does BROWSER_COMPATIBILITY but I didn't know if that would be on an ok PR to make. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56685) Stash Pullrequest Builder modify cookie handling
Title: Message Title Brandon Johnson commented on JENKINS-56685 Re: Stash Pullrequest Builder modify cookie handling Jakub Bochenski If you have a link to a branch or some commits that have the global configuration stuff I can take a look at it and see if I can't make a PR for adding this part. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57301) Blue Ocean Plugin does not support INPUT_PARAMS
Title: Message Title Thorsten Scherler commented on JENKINS-57301 Re: Blue Ocean Plugin does not support INPUT_PARAMS https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-core-js/src/js/parameter/index.js#L20 are the ones BO supports ATM Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57218) NPE from SymbolLookup after job-dsl update without configuration-as-code
Title: Message Title Jesse Glick commented on JENKINS-57218 Re: NPE from SymbolLookup after job-dsl update without configuration-as-code Ivan Dimitrov update the Structs plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title Jesse Glick commented on JENKINS-33843 Re: It's not possible to disable/uninstall optional dependencies Andrei Costescu the fix is still open for review. If and when the fix is merged, this issue will be closed with details. In the meantime, see the *.disabled workaround above. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56838) pipeline job hangs forever at checkout GitSCM
Title: Message Title Tsvi Mostovicz commented on JENKINS-56838 Re: pipeline job hangs forever at checkout GitSCM This appears to be due to the fact that Git SCM parses through all of the older builds when checking out. (See https://github.com/jenkinsci/git-plugin/blob/34fa174566716c8c6a1ab392a0cf3b5c05fc4d41/src/main/java/hudson/plugins/git/GitSCM.java#L1136) As we were not clearing out old builds, over time the performance hit caused by parsing over all the older builds became so huge, checkout would timeout after 1 hour. Clearing out old builds resolved the issue for us. Note that the File variable passed to the function was set to null, as the scm step function calling it had updateChanges set to false. This might be a possible enhancement to the GitSCM plugin to eventually skip calculation of the history if the changelog file passed to checkout is null. As I'm not really sure about how this might affect other parts of the code, I'm weary of implementing 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-56838) pipeline job hangs forever at checkout GitSCM
Title: Message Title Tsvi Mostovicz assigned an issue to Mark Waite Jenkins / JENKINS-56838 pipeline job hangs forever at checkout GitSCM Change By: Tsvi Mostovicz Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57264) accessing file credential in pipeline causes nullPointerException
Title: Message Title Sydney Satchwill commented on JENKINS-57264 Re: accessing file credential in pipeline causes nullPointerException I had the same plugin versions and issue. I was able to fix by updating Structs plugin 1.18 -> 1.19 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56838) pipeline job hangs forever at checkout GitSCM
Title: Message Title Tsvi Mostovicz commented on JENKINS-56838 Re: pipeline job hangs forever at checkout GitSCM Mark Waite please see the comment I added. I solved the issue for us, I wonder though who should I tag for the enhancement I proposed. (I don't mind putting in a PR myself, but I have never developed for Jenkins so I'll need some handholding) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57301) Blue Ocean Plugin does not support INPUT_PARAMS
Title: Message Title Ahmed Itman commented on JENKINS-57301 Re: Blue Ocean Plugin does not support INPUT_PARAMS Hi Thorsten Scherler is it the solution, i see the link for .js Should i modify bluocean*.js in my Jenkins ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Oleg Nenashev commented on JENKINS-57304 Re: Multiple "idle" entries on Build Executor Status for non-existant executors It is for flyweight executors, I believe (e.g. for Pipeline). They may be indicated as idle in Web UI for a while. Do they disappear automatically after some time? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Patrick Rose commented on JENKINS-57304 Re: Multiple "idle" entries on Build Executor Status for non-existant executors I've just checked again now - there's still the same number of extra idles. I can check again tomorrow morning? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman edited a comment on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub [~synalogik][~amirbarkal] [~dbsanfte] If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3. https://drive.google.com/file/d/1VreeBlIG0RCbSI80wW2BBOmcVT9ZySNW/view?usp=sharingIf you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade. The code can be seen at https://github.com/jenkinsci/github-branch-source-plugin/pull/223 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman edited a comment on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub [~synalogik][~amirbarkal] If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3. https://drive.google.com/file/d/1VreeBlIG0RCbSI80wW2BBOmcVT9ZySNW/view?usp=sharingIf you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade. The code can be seen at https://github.com/jenkinsci/github-branch-source-plugin/pull/223 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman edited a comment on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub [~synalogik][~amirbarkal][~dbsanfte] [~soar] If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3. https://drive.google.com/file/d/1VreeBlIG0RCbSI80wW2BBOmcVT9ZySNW/view?usp=sharingIf you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade. The code can be seen at https://github.com/jenkinsci/github-branch-source-plugin/pull/223 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56838) pipeline job hangs forever at checkout GitSCM
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-56838 pipeline job hangs forever at checkout GitSCM Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Jesse Glick commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Liam Newman maybe we can run this at least temporarily on ci.jenkins.io? I know R. Tyler Croy has a strict “no experimental code” rule for this server, but the current situation is badly broken to begin with. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56838) pipeline job hangs forever at checkout GitSCM
Title: Message Title Mark Waite commented on JENKINS-56838 Re: pipeline job hangs forever at checkout GitSCM I suspect this is related to JENKINS-19022, git plugin mistakenly retains list of SHA1's of all preceding builds in later builds, bloating memory use. We've attempted at least 3 different times to resolve JENKINS-19022, each time abandoning due to incompatibilities that are introduced by the proposed changes. Reducing the number of builds retained in history is the most direct workaround for the problem. Other workarounds exist as well, like groovy scripts that will remove old BuildData records. Unless you're ready for months and months of work to implement the fix without causing compatibility problems, I'd recommend you prefer retaining fewer builds rather than attempting to make a code change in the git plugin for this 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-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman edited a comment on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub [~synalogik] , [~amirbarkal] , [~dbsanfte] , [~soar]If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3. https://drive.google.com/file/d/1VreeBlIG0RCbSI80wW2BBOmcVT9ZySNW/view?usp=sharingIf you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade. The code can be seen at https://github.com/jenkinsci/github-branch-source-plugin/pull/223 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56685) Stash Pullrequest Builder modify cookie handling
Title: Message Title Jakub Bochenski commented on JENKINS-56685 Re: Stash Pullrequest Builder modify cookie handling The work on global configuration is only planned still. What can be done now is: create a PR changing this directly. This build will then be available through the Experimental Update Center Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title William F commented on JENKINS-56890 Re: IOException: "cannot find current thread" Again, based on a perfunctory glance at the proximal code (and, admittedly, with absolutely no understanding of the codebase as a whole), I suspect this issue could be fixed by simply synchronizing all access to the underlying "threads" TreeMap. One potential approach would be to follow the advice given in the TreeMap documentation: Note that this implementation is not synchronized. If multiple threads access a map concurrently, and at least one of the threads modifies the map structurally, it must be synchronized externally. (A structural modification is any operation that adds or deletes one or more mappings; merely changing the value associated with an existing key is not a structural modification.) This is typically accomplished by synchronizing on some object that naturally encapsulates the map. If no such object exists, the map should be "wrapped" using the Collections.synchronizedSortedMap method. This is best done at creation time, to prevent accidental unsynchronized access to the map: SortedMap m = Collections.synchronizedSortedMap(new TreeMap(...)); I get the impression that the authors of the code hoped to avoid the need for explicit synchronization by forcing all write operations to execute in a single thread...but, as noted in the javadoc excerpt above, that's not good enough. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title Leandro Lucarella commented on JENKINS-57154 Re: HTTP ERROR 403 Also affected, same description, first user is retrieved correctly, all the following are errors, and any attempt to save the configuration for the security page ends in a "No valid crumb was included in the request" 403 error. Ddowngrading to version 0.31 fixed it for me too, but then I'm exposed to the CSRF vulnerability Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32087) Configure JIRA credentials at the Job configuration level
Title: Message Title Mathieu Delrocq commented on JENKINS-32087 Re: Configure JIRA credentials at the Job configuration level A pull request has been opened for this : https://github.com/jenkinsci/jira-plugin/pull/188 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57308) Update for Sonar 6 LTS (icons, links)
Title: Message Title Georg Henzler created an issue Jenkins / JENKINS-57308 Update for Sonar 6 LTS (icons, links) Issue Type: Improvement Assignee: Georg Henzler Components: mashup-portlets-plugin Created: 2019-05-02 15:11 Priority: Minor Reporter: Georg Henzler Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57309) Ensure Generic JS portlet does not XSS-encode JS
Title: Message Title Georg Henzler created an issue Jenkins / JENKINS-57309 Ensure Generic JS portlet does not XSS-encode JS Issue Type: Bug Assignee: Georg Henzler Components: mashup-portlets-plugin Created: 2019-05-02 15:13 Priority: Minor Reporter: Georg Henzler Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title
Dan Ebert edited a comment on JENKINS-57244
Re: java.io.NotSerializableException: The calling thread Thread has no associated channel
I'm seeing a similar problem. Here's the stack trace from the build log:{{ }}{{ }} *07:53:56* hudson.remoting.ProxyException: java.io.NotSerializableException: The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56* at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67)*07:53:56* at hudson.FilePath.writeObject(FilePath.java:2989)*07:53:56* at sun.reflect.GeneratedMethodAccessor188.invoke(Unknown Source)*07:53:56* at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*07:53:56* at java.lang.reflect.Method.invoke(Method.java:498)*07:53:56* at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135)*07:53:56* Caused: hudson.remoting.ProxyException: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56* Debugging information *07:53:56* message : Could not call hudson.FilePath.writeObject()*07:53:56* cause-exception : java.io.NotSerializableException*07:53:56* cause-message : The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56* ---*07:53:56* at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141)*07:53:56* at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259)*07:53:56* at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83)*07:53:56* at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)*07:53:56* at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)*07:53:56* at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)*07:53:56* at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:263)*07:53:56* at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:250)*07:53:56* Caused: hudson.remoting.ProxyException: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.scoverage.ScoverageBuildAction#buildPath for class org.jenkinsci.plugins.scoverage.ScoverageBuildAction*07:53:56* at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:254)*07:53:56* at hudson.util.RobustReflectionConver
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title
Dan Ebert edited a comment on JENKINS-57244
Re: java.io.NotSerializableException: The calling thread Thread has no associated channel
I'm seeing a similar problem. Here's the stack trace from the build log: {{ }} {{}} *07:53:56* hudson.remoting.ProxyException: java.io.NotSerializableException: The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56* at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67)*07:53:56* at hudson.FilePath.writeObject(FilePath.java:2989)*07:53:56* at sun.reflect.GeneratedMethodAccessor188.invoke(Unknown Source)*07:53:56* at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*07:53:56* at java.lang.reflect.Method.invoke(Method.java:498)*07:53:56* at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135)*07:53:56* Caused: hudson.remoting.ProxyException: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56* Debugging information *07:53:56* message : Could not call hudson.FilePath.writeObject()*07:53:56* cause-exception : java.io.NotSerializableException*07:53:56* cause-message : The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56* ---*07:53:56* at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141)*07:53:56* at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259)*07:53:56* at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83)*07:53:56* at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)*07:53:56* at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)*07:53:56* at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)*07:53:56* at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:263)*07:53:56* at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:250)*07:53:56* Caused: hudson.remoting.ProxyException: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.scoverage.ScoverageBuildAction#buildPath for class org.jenkinsci.plugins.scoverage.ScoverageBuildAction*07:53:56* at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:254)*07:53:56* at hudson.util.RobustReflectionCo
[JIRA] (JENKINS-57258) Lost builds historical data after updating to Jenkins v2.175
Title: Message Title Daniel Beck commented on JENKINS-57258 Re: Lost builds historical data after updating to Jenkins v2.175 Did you also update any plugins? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57311) Pipeline script from SCM - fetch for every single stage
Title: Message Title nima nima created an issue Jenkins / JENKINS-57311 Pipeline script from SCM - fetch for every single stage Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-05-02 15:26 Priority: Minor Reporter: nima nima Hello Everyone, Due to size of pipeline scripts (more than 700 lines ), it is not easy for me to update/edit the pipeline inside the default pipeline editor ( very simple and small space to write script ). So i uploaded the scripts to Bitbucket and reconfigured the pipeline to use "Pipeline script from SCM". but I encountered 2 issues which are kind of blocker item for me at this moment: 1) i realized that for each stage, the jenkins tries to check out from Bitbucket which slows down the entire pipeline ( because in each pipeline, there are more than 10 stages ). I can not consider it as a major problem or blocker item. but at least it can be considered as performance issue 2) a few stages ( section ) in my pipeline should be run only on remote node ( slave node ) to complete the code installation/release ( let's say yum install MyPackage), the issue is that these remote nodes do NOT have access to Bitbucket (technically they should NOT have access to internet or vice versa) and the jenkins can not check out and eventually the stage would fail. I can't seem to find any options to configure the jenkins so it can only fetch/checkout the pipeline script only on Master. any idea on how to resolve this issue ?
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Dan Ebert commented on JENKINS-57244 Re: java.io.NotSerializableException: The calling thread Thread has no associated channel I'm seeing a similar problem. Here's the stack trace from the build log: 07:53:56 hudson.remoting.ProxyException: java.io.NotSerializableException: The calling thread Threadorg.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56* at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67)07:53:56 at hudson.FilePath.writeObject(FilePath.java:2989)07:53:56 at sun.reflect.GeneratedMethodAccessor188.invoke(Unknown Source)07:53:56 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)07:53:56 at java.lang.reflect.Method.invoke(Method.java:498)07:53:56 at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135)07:53:56 Caused: hudson.remoting.ProxyException: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Threadorg.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56* Debugging information 07:53:56 message : Could not call hudson.FilePath.writeObject()07:53:56 cause-exception : java.io.NotSerializableException*07:53:56* cause-message : The calling thread Threadorg.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel*07:53:56* ---07:53:56 at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141)07:53:56 at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259)07:53:56 at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83)07:53:56 at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)07:53:56 at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)07:53:56 at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)07:53:56 at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:263)07:53:56 at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:250)07:53:56 Caused: hudson.remoting.ProxyException: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.scoverage.ScoverageBuildAction#buildPath for class org.jenkinsci.plugins.scoverage.ScoverageBuildAction*07:53:56* at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:254)07:53:56 at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:222)07:53:56 at com.thoughtworks.xstream.converters.reflection.PureJavaReflect
[JIRA] (JENKINS-57310) Publish Over SSH can't connect when PasswordAuthentication is set to "NO"
Title: Message Title Jed Jacobs created an issue Jenkins / JENKINS-57310 Publish Over SSH can't connect when PasswordAuthentication is set to "NO" Issue Type: Improvement Assignee: Alex Earl Components: publish-over-ssh-plugin Created: 2019-05-02 15:25 Environment: Jenkins 2.150.2 running on Redhat Linux 6.9 Publish Over SSH plugin version 1.19.1 Target servers are Linux as well. Priority: Major Reporter: Jed Jacobs Our security office is implementing Multi-factor authentication (MFA). The are strictly enforcing the PasswordAuthentication parameter to a value of "no" in the sshd_config file in every server. The Publish_Over_SSH plugin connection fails with the message "Auth Cancel", which means it can't connect to the server to validate the credentials. This is different than "Authorization Failed", which means there is a credential issue. This renders our ability to send files to target servers using this plugin. As a result, we will have to set up public keys on all our build agents and target servers (of which there are over 200 and growing) and write explicit SSH commands to transfer the files. The SSH Plugin is unaffected by this change. However, that plugin does not transfer files. Is it possible to look at the connection methodology of the SSH Plugin and apply this to the Publish Over SSH plugin so it can still connect regardless of the PasswordAuthentication setting to "no"?
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: Daniel Beck Labels: regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title
Dan Ebert edited a comment on JENKINS-57244
Re: java.io.NotSerializableException: The calling thread Thread has no associated channel
I'm seeing a similar problem. Here's the stack trace from the build log:{{ }} {{* 07:53:56 * hudson.remoting.ProxyException: java.io.NotSerializableException: The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel * 07:53:56 * at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67) * 07:53:56 * at hudson.FilePath.writeObject(FilePath.java:2989) * 07:53:56 * at sun.reflect.GeneratedMethodAccessor188.invoke(Unknown Source) * 07:53:56 * at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) * 07:53:56 * at java.lang.reflect.Method.invoke(Method.java:498) * 07:53:56 * at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135) * 07:53:56 * Caused: hudson.remoting.ProxyException: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel * 07:53:56 * Debugging information * 07:53:56 * message : Could not call hudson.FilePath.writeObject() * 07:53:56 * cause-exception : java.io.NotSerializableException * 07:53:56 * cause-message : The calling thread Thread[org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution [#354],5,main] has no associated channel. The current object /var/lib/jenkins/jobs/ci-platform-numbers-api/builds/452 is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel * 07:53:56 * --- * 07:53:56 * at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141) * 07:53:56 * at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259) * 07:53:56 * at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83) * 07:53:56 * at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) * 07:53:56 * at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) * 07:53:56 * at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) * 07:53:56 * at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:263) * 07:53:56 * at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:250) * 07:53:56 * Caused: hudson.remoting.ProxyException: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.scoverage.ScoverageBuildAction#buildPath for class org.jenkinsci.plugins.scoverage.ScoverageBuildAction * 07:53:56 * at hudson.util.RobustReflect
[JIRA] (JENKINS-56996) null permission lookup when pull-request's origin repo/branch is deleted on github
Title: Message Title Liam Newman assigned an issue to Unassigned Jenkins / JENKINS-56996 null permission lookup when pull-request's origin repo/branch is deleted on github Change By: Liam Newman Assignee: Liam Newman Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57278) Console Log View
Title: Message Title Veronika Zwickenpflug assigned an issue to Veronika Zwickenpflug Jenkins / JENKINS-57278 Console Log View Change By: Veronika Zwickenpflug Assignee: Veronika Zwickenpflug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
