[JIRA] (JENKINS-52421) Support PowerShell Core on Windows-Systems
Title: Message Title Michael P edited a comment on JENKINS-52421 Re: Support PowerShell Core on Windows-Systems I feel like a good all around solution would be to provide a dropdown for PowerShell Version Preference. I've thrown together a small POC: !image-2020-04-21-22- 51 52 - 02 03 - 900 562 .png!This solution solves multiple issues: * Running scripts that support both powershell and pwsh but may be run against multiple environments where one or the other may not be present * Running scripts that only support pwsh * Running scripts that only support powershell Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192237.1531060684000.15500.1587534780167%40Atlassian.JIRA.
[JIRA] (JENKINS-52421) Support PowerShell Core on Windows-Systems
Title: Message Title Michael P updated an issue Jenkins / JENKINS-52421 Support PowerShell Core on Windows-Systems Change By: Michael P Attachment: image-2020-04-21-22-51-02-900.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192237.1531060684000.15490.1587534720540%40Atlassian.JIRA.
[JIRA] (JENKINS-52421) Support PowerShell Core on Windows-Systems
Title: Message Title Michael P updated an issue Jenkins / JENKINS-52421 Support PowerShell Core on Windows-Systems Change By: Michael P Attachment: image-2020-04-21-22-51-02-900.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192237.1531060684000.15494.1587534720603%40Atlassian.JIRA.
[JIRA] (JENKINS-52421) Support PowerShell Core on Windows-Systems
Title: Message Title Michael P commented on JENKINS-52421 Re: Support PowerShell Core on Windows-Systems I feel like a good all around solution would be to provide a dropdown for PowerShell Version Preference. I've thrown together a small POC: This solution solves multiple issues: Running scripts that support both powershell and pwsh but may be run against multiple environments where one or the other may not be present Running scripts that only support pwsh Running scripts that only support powershell Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192237.1531060684000.15496.1587534720627%40Atlassian.JIRA.
[JIRA] (JENKINS-49349) git scm plugin attempts to checkout stale SHAs
Title: Message Title Mark Waite updated JENKINS-49349 May be due to not having configured the job to prune stale branches. If prune stale branches is not enabled in the job, then the local workspace will retain branches that no longer exist on the master. Jenkins / JENKINS-49349 git scm plugin attempts to checkout stale SHAs Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-49349) git scm plugin attempts to checkout stale SHAs
Title: Message Title Mark Waite updated JENKINS-49349 Jenkins / JENKINS-49349 git scm plugin attempts to checkout stale SHAs Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188214.1517595371000.15477.1587529860951%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) ItemGroupMixing#createProject() does not call Jenkins#checkGoodName
Title: Message Title Calvin Park commented on JENKINS-61956 Re: ItemGroupMixing#createProject() does not call Jenkins#checkGoodName I've tried to contribute to the cloudbees-folder-plugin git repo but mvn hpi:run fails. cloudbees-folder-plugin master$ mvn hpi:run [INFO] Scanning for projects... [INFO] [INFO] --< org.jenkins-ci.plugins:cloudbees-folder >--- [INFO] Building Folders Plugin 6.13-SNAPSHOT [INFO] [ hpi ]- [INFO] [INFO] >>> maven-hpi-plugin:3.10:run (default-cli) > compile @ cloudbees-folder >>> [...] [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ cloudbees-folder --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 45 source files to /Users/calvin/GitRepos/cloudbees-folder-plugin/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] java.nio.file.NoSuchFileException: /Users/calvin/GitRepos/cloudbees-folder-plugin/target/classes/META-INF/annotations/hudson.Extension [INFO] 1 error [...] The github page didn't enable Issues feature so I can't ask for help there https://github.com/jenkinsci/cloudbees-folder-plugin Any ideas on how to fix the compilation error? Thank you Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-52889) new lines in secret is substituted by spaces when reading via Vault plugin
Title: Message Title Joseph Petersen closed an issue as Cannot Reproduce Jenkins / JENKINS-52889 new lines in secret is substituted by spaces when reading via Vault plugin Change By: Joseph Petersen Status: Open Closed Assignee: Peter Tierno Joseph Petersen Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192828.1533446727000.15467.1587529080673%40Atlassian.JIRA.
[JIRA] (JENKINS-60091) HashiCorp Vault plugin using approle is not working since v3.0.0
Title: Message Title Joseph Petersen resolved as Fixed Fixed in v3.1.1 Jenkins / JENKINS-60091 HashiCorp Vault plugin using approle is not working since v3.0.0 Change By: Joseph Petersen Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/hashicorp-vault-plugin/releases/tag/hashicorp-vault-plugin-3.1.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60091) HashiCorp Vault plugin using approle is not working since v3.0.0
Title: Message Title Joseph Petersen assigned an issue to Joseph Petersen Jenkins / JENKINS-60091 HashiCorp Vault plugin using approle is not working since v3.0.0 Change By: Joseph Petersen Assignee: Peter Tierno Joseph Petersen Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202936.1573144964000.15458.1587528720478%40Atlassian.JIRA.
[JIRA] (JENKINS-45650) CLI known_hosts support fails on non-standard SSH ports
Title: Message Title Karthick Prabu Ponnusamy commented on JENKINS-45650 Re: CLI known_hosts support fails on non-standard SSH ports Hi guys, We are seeing this issue on: Jenkins v2.176.3 Running on CentOS 7.5 and SSH Plugin. Jenkins CLI adds the SSH key to known_hosts without port, so the entry is conflicting with regular SSH key Any fix for this issue other than removing `.ssh/known_hosts`? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183843.1500471216000.15446.1587527820283%40Atlassian.JIRA.
[JIRA] (JENKINS-62003) Add build trigger creation to Multibranch Pipeline projects
Title: Message Title Martin Henschke created an issue Jenkins / JENKINS-62003 Add build trigger creation to Multibranch Pipeline projects Issue Type: Improvement Assignee: Atlassian Bitbucket Server Components: atlassian-bitbucket-server-integration-plugin Created: 2020-04-22 03:38 Labels: tracked-by-atlassian Priority: Major Reporter: Martin Henschke There is currently no way to register a build trigger in Bitbucket using a multibranch pipeline project. A UI trigger should be added to the configuration page in the same manner as Freestyle and Pipeline projects. Workaround: Until this feature is added, you can still create a webhook in your Bitbucket Server instance manually: Go to your Bitbucket instance, and navigate to the affected repository Go to Settings -> Webhooks -> create Fill in the name and base URL for your Jenkins instance Check the Repository "Push" event
[JIRA] (JENKINS-48019) Bitbucket branch source fail randomly
Title: Message Title Jordi Miguel edited a comment on JENKINS-48019 Re: Bitbucket branch source fail randomly Without more context it's hard to know where is the problem you're facing. At first glance it doesn't look like the same error that this ticket was tracking. From my point of view it look more like a network problem in your infrastructure.I would suggest that you try to discard that it's not something related to another part of the stack aside of this jenkins pluign, some ideas to look at: network connectivity, OS limits, DNS resolution, ...If you still think that the problem is on the jenkins plugin I recommend that you open a new ticket and show up also on the GitHub [repo|[https://github.com/jenkinsci/bitbucket-branch-source-plugin/]] and have a look at the open issues there. Also you can try to ask for help through the "issues" section. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186558.1510738478000.15423.1587511080404%40Atlassian.JIRA.
[JIRA] (JENKINS-48019) Bitbucket branch source fail randomly
Title: Message Title Jordi Miguel commented on JENKINS-48019 Re: Bitbucket branch source fail randomly Without more context it's hard to know where is the problem you're facing. At first glance it doesn't look like the same error that this ticket was tracking. From my point of view it look more like a network problem in your infrastructure. I would suggest that you try to discard that it's not something related to another part of the stack aside of this jenkins pluign, some ideas to look at: network connectivity, OS limits, DNS resolution, ... If you still think that the problem is on the jenkins plugin I recommend that you open a new ticket and show up also on the GitHub [repo|https://github.com/jenkinsci/bitbucket-branch-source-plugin/] and look at the open issues there. Also you can try to ask for help through the "issues" section. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186558.1510738478000.15406.1587510960446%40Atlassian.JIRA.
[JIRA] (JENKINS-61912) Clicking failure cause link on build page does not highlight location in console output
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61912 Clicking failure cause link on build page does not highlight location in console output Change By: Daniel Beck Labels: jenkinsfile multi-branch regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205784.158694671.15404.1587510240224%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Ranky Lau commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Is there anyone working at this issue right now? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.15368.1587508080659%40Atlassian.JIRA.
[JIRA] (JENKINS-62002) SCM API 2.0 support for Bitbucket Server Integration
Title: Message Title Steven Terrana created an issue Jenkins / JENKINS-62002 SCM API 2.0 support for Bitbucket Server Integration Issue Type: Task Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2020-04-21 21:12 Priority: Minor Reporter: Steven Terrana It would be great if this plugin implemented the SCM API 2.0 spec similarly to how the git-branch source and bitbucket-branch-source plugins do. For other plugins that interact with SCM, it becomes very difficult to integrate with arbitrary SCM plugins if this common interface is not supported. Is this on the roadmap currently? Add Comment
[JIRA] (JENKINS-48019) Bitbucket branch source fail randomly
Title: Message Title Karan Mehta updated an issue Jenkins / JENKINS-48019 Bitbucket branch source fail randomly Change By: Karan Mehta Summary: Bitbucket branch source fail randomically randomly Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186558.1510738478000.15299.1587502081279%40Atlassian.JIRA.
[JIRA] (JENKINS-48019) Bitbucket branch source fail randomically
Title: Message Title Karan Mehta updated an issue Jenkins / JENKINS-48019 Bitbucket branch source fail randomically Change By: Karan Mehta Comment: Still facing this issue. Please tag the fix version for this. !image-2020-04-22-02-16-10-563.png|width=822,height=170! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186558.1510738478000.15282.1587502081016%40Atlassian.JIRA.
[JIRA] (JENKINS-48019) Bitbucket branch source fail randomically
Title: Message Title Karan Mehta reopened an issue Still facing this issue. Please tag the fix version for this. Jenkins / JENKINS-48019 Bitbucket branch source fail randomically Change By: Karan Mehta Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-48019) Bitbucket branch source fail randomically
Title: Message Title Karan Mehta edited a comment on JENKINS-48019 Re: Bitbucket branch source fail randomically Still facing this issue. Can you help us with the fix version for of this? !image-2020-04-22-02-14-56-680.png|width=804,height=166! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186558.1510738478000.15262.1587501960791%40Atlassian.JIRA.
[JIRA] (JENKINS-48019) Bitbucket branch source fail randomically
Title: Message Title Karan Mehta commented on JENKINS-48019 Re: Bitbucket branch source fail randomically Still facing this issue. Can you help us with the fix version for this? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186558.1510738478000.15231.1587501720443%40Atlassian.JIRA.
[JIRA] (JENKINS-62000) HTTP ERROR 403 No valid crumb was included in the request
Title: Message Title Daniel Beck closed an issue as Not A Defect This is an issue tracker, not a support site. Please ask on the users mailing list or on IRC or Gitter. Jenkins / JENKINS-62000 HTTP ERROR 403 No valid crumb was included in the request Change By: Daniel Beck Status: In Progress Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-61758) Test Result Summary in logs is incorrect.
Title: Message Title Barrie Sager updated JENKINS-61758 We upgraded to the latest version of the plug-in and that resolved the issue. Jenkins / JENKINS-61758 Test Result Summary in logs is incorrect. Change By: Barrie Sager Status: In Review Closed Resolution: Fixed Released As: Latest plug-in version was installed; resolved the issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-49664) ThinBackup Multi-Branch Branches Directory and SSH Key
Title: Message Title Jon Tancer commented on JENKINS-49664 Re: ThinBackup Multi-Branch Branches Directory and SSH Key Jakob Fahrner The PR has been merged to master but it doesn't appear that a new version of the plugin has been released yet. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188593.1519181272000.15219.1587501060261%40Atlassian.JIRA.
[JIRA] (JENKINS-62001) Autocompletion dropdown UI looks broken
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-62001 Autocompletion dropdown UI looks broken Change By: Daniel Beck Environment: Jenkins 2.233 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205893.1587500364000.15216.1587501000186%40Atlassian.JIRA.
[JIRA] (JENKINS-62001) Autocompletion dropdown UI looks broken
Title: Message Title Daniel Beck commented on JENKINS-62001 Re: Autocompletion dropdown UI looks broken Looks correctin 2.232, so this is a regression in 2.233 specifically. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205893.1587500364000.15214.1587500700152%40Atlassian.JIRA.
[JIRA] (JENKINS-62001) Autocompletion dropdown UI looks broken
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-62001 Autocompletion dropdown UI looks broken Issue Type: Bug Assignee: Unassigned Attachments: 2.222.1.png, 2.233.png Components: core Created: 2020-04-21 20:19 Labels: regression ui ux Priority: Minor Reporter: Daniel Beck Attached screenshots of the "Logger" configuration autocompletion UI in 2.222.1 and 2.233. It looks like one of the recent redesign PRs messed this up. Add Comment
[JIRA] (JENKINS-43820) Stage name must be a string literal
Title: Message Title Brian J Murrell commented on JENKINS-43820 Re: Stage name must be a string literal This gets really, super ugly in the context of matrix. Surely you can see how not being able to substitute a variable into the stage name makes this a much less-than-useful representation of the job: I have no idea what any of those stages are without hovering over the "Matrix" text for each combination. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181338.1493122184000.15166.1587499740777%40Atlassian.JIRA.
[JIRA] (JENKINS-43820) Stage name must be a string literal
Title: Message Title Brian J Murrell updated an issue Jenkins / JENKINS-43820 Stage name must be a string literal Change By: Brian J Murrell Attachment: screenshot-matrix.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181338.1493122184000.15128.1587499681330%40Atlassian.JIRA.
[JIRA] (JENKINS-62000) HTTP ERROR 403 No valid crumb was included in the request
Title: Message Title
carlos RUIZ JIMENEZ updated an issue
Jenkins / JENKINS-62000
HTTP ERROR 403 No valid crumb was included in the request
Change By:
carlos RUIZ JIMENEZ
Buenas tardes, Soy nuevo con Jenkins la verdad y tengo un Jenkins que se ha actualizado a version 2.232 y la llamada a los jobs desde fuera no funciona dando un error: {color:#cc}HTTP ERROR 403 No valid crumb was included in the request<{color} Este es el script que realizaba la llamada y funciona en version antigua: {color:#0037da}#!/bin/bash {color}{color:#3a96dd}crumb{color}{color:#cc}={color}{color:#881798}$(curl -u {color}{color:#af5f00}"{color}{color:#c50f1f}jenkins2:1234{color}{color:#af5f00}" {color}{color:#881798}-s {color}{color:#af5f00}'{color}{color:#c50f1f} [ http://jenkins.local:8080/crumbIssuer/api/xml?xpath=concat(//crumbRequestField ] ,":",//crumb){color}{color:#af5f00}'{color}{color:#881798}) {color} {color:#af5f00}echo {color}{color:#881798}$crumb {color} {color:#cc}curl {color}{color:#881798}-u {color}{color:#af5f00}"{color}{color:#c50f1f}jenkins2:1234{color}{color:#af5f00}" {color}{color:#881798}-H {color}{color:#af5f00}"{color}{color:#881798}$crumb{color}{color:#af5f00}" {color}{color:#881798}-X {color}{color:#cc}POST [ http://jenkins.local: |http://jenkins.local/] {color}{color:#c50f1f}8080{color}{color:#cc}/job/sencillo/build?{color}{color:#3a96dd}delay{color}{color:#cc}=0sec{color}{color:#cc}Por favor, ¿me podrían ayudar?.{color} {color:#cc}Gracias{color}
Add Comment
This
[JIRA] (JENKINS-62000) HTTP ERROR 403 No valid crumb was included in the request
Title: Message Title carlos RUIZ JIMENEZ started work on JENKINS-62000 Change By: carlos RUIZ JIMENEZ Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205892.1587498514000.15121.1587498900186%40Atlassian.JIRA.
[JIRA] (JENKINS-62000) HTTP ERROR 403 No valid crumb was included in the request
Title: Message Title carlos RUIZ JIMENEZ created an issue Jenkins / JENKINS-62000 HTTP ERROR 403 No valid crumb was included in the request Issue Type: Bug Assignee: Andras Nemes Components: apica-loadtest-plugin Created: 2020-04-21 19:48 Environment: Version: Jenkins 2.232 Centos 7 Docker-compose Priority: Major Reporter: carlos RUIZ JIMENEZ Buenas tardes, Soy nuevo con Jenkins la verdad y tengo un Jenkins que se ha actualizado a version 2.232 y la llamada a los jobs desde fuera no funciona dando un error: HTTP ERROR 403 No valid crumb was included in the request< Este es el script que realizaba la llamada y funciona en version antigua: #!/bin/bashcrumb=$(curl -u "jenkins2:1234" -s 'http://jenkins.local:8080/crumbIssuer/api/xml?xpath=concat(//crumbRequestField,":",//crumb)')echo $crumbcurl -u "jenkins2:1234" -H "$crumb" -X POST http://jenkins.local:8080/job/sencillo/build?delay=0sec Por favor, ¿me podrían ayudar?. Gracias Add Comment
[JIRA] (JENKINS-61995) P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long
Title: Message Title ling fu commented on JENKINS-61995 Re: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long I can only see this in jenkins log: Apr 21, 2020 2:36:04 PM INFO org.jenkinsci.plugins.p4.tasks.CheckoutTask getBuildChange getBuildChange:return:2100587 Server version: P4D/LINUX26X86_64/2013.2/938876 (2014/09/23) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205886.1587487073000.15117.1587497880161%40Atlassian.JIRA.
[JIRA] (JENKINS-61999) If scm fails, credentials are not populated in post-build steps
Title: Message Title o viana created an issue Jenkins / JENKINS-61999 If scm fails, credentials are not populated in post-build steps Issue Type: Bug Assignee: Unassigned Components: credentials-binding-plugin Created: 2020-04-21 19:26 Environment: Jenkins ver. 2.176.3 & Jenkins ver. 2.222.1 Priority: Major Reporter: o viana Searched high-and-low for this, but couldn't find anything. How to reproduce: 1. Create a freestyle project. 2. Set the project to check out from a bogus github repo that you can never reach. 3. Add a credentials binding for the job (in my case, Separated Username and Password). 4. Add a simple post-build step via the PostBuildScript Plugin to use the credentials defined in #3 (such as echo-ing the credentials). 5. Execute the job. 6. Set the project to check out from a legitimate github repo that you can access. 7. Re-execute the job. Actual: 5. Post-build step can't use the credentials as they're empty. 7. Post-build step can use the credentials as they're not empty. Expected: Post-build step should still have access to the credentials, even if the scm step fails.
[JIRA] (JENKINS-1878) Ability to move job to top of queue
Title: Message Title Ronny Borchert commented on JENKINS-1878 Re: Ability to move job to top of queue The plugin this not working anymore. The menu entry is missing. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.131951.1213683192000.15038.1587496141237%40Atlassian.JIRA.
[JIRA] (JENKINS-61998) Jenkins upgrade fails on CentOS - Public key is not installed
Title: Message Title
Constantin Bugneac updated an issue
Jenkins / JENKINS-61998
Jenkins upgrade fails on CentOS - Public key is not installed
Change By:
Constantin Bugneac
It looks like since version 232 the Jenkins rpm package is not signed anymore with the published GPG key and it fails to install on CentOS using yum/rpm.{code:java}# yum -y update jenkinsLoaded plugins: fastestmirrorLoading mirror speeds from cached hostfile * base: anorien.csc.warwick.ac.uk * elrepo: lon.mirror.rackspace.com * elrepo-kernel: lon.mirror.rackspace.com * epel: mirror.serverion.com * extras: anorien.csc.warwick.ac.uk * updates: mirrors.coreix.netResolving Dependencies--> Running transaction check---> Package jenkins.noarch 0:2.232-1.1 will be updated---> Package jenkins.noarch 0:2.233-1.1 will be an update--> Finished Dependency ResolutionDependencies Resolved== Package Arch Version Repository Size==Updating: jenkins noarch 2.233-1.1 jenkins 63 MTransaction Summary==Upgrade 1 PackageTotal size: 63 MDownloading packages:warning: /var/cache/yum/x86_64/7/jenkins/packages/jenkins-2.233-1.1.noarch.rpm: Header V4 RSA/SHA512 Signature, key ID 45f2c3d5: NOKEYPublic key for jenkins-2.233-1.1.noarch.rpm is not installed{code}PS: I've followed this guide [https://wiki.jenkins.io/display/JENKINS/Installing+Jenkins+on+Red+Hat+distributions] Using `{{yum install jenkins --nogpgcheck}}` is not a good idea as it breaks the trust to origin of software.
Add Comment
[JIRA] (JENKINS-61998) Jenkins upgrade fails on CentOS - Public key is not installed
Title: Message Title
Constantin Bugneac updated an issue
Jenkins / JENKINS-61998
Jenkins upgrade fails on CentOS - Public key is not installed
Change By:
Constantin Bugneac
It looks like since version 232 the Jenkins rpm package is not signed anymore with the published GPG key and it fails to install on CentOS using yum/rpm.{code:java}# yum -y update jenkinsLoaded plugins: fastestmirrorLoading mirror speeds from cached hostfile * base: anorien.csc.warwick.ac.uk * elrepo: lon.mirror.rackspace.com * elrepo-kernel: lon.mirror.rackspace.com * epel: mirror.serverion.com * extras: anorien.csc.warwick.ac.uk * updates: mirrors.coreix.netResolving Dependencies--> Running transaction check---> Package jenkins.noarch 0:2.232-1.1 will be updated---> Package jenkins.noarch 0:2.233-1.1 will be an update--> Finished Dependency ResolutionDependencies Resolved== Package Arch Version Repository Size==Updating: jenkins noarch 2.233-1.1 jenkins 63 MTransaction Summary==Upgrade 1 PackageTotal size: 63 MDownloading packages:warning: /var/cache/yum/x86_64/7/jenkins/packages/jenkins-2.233-1.1.noarch.rpm: Header V4 RSA/SHA512 Signature, key ID 45f2c3d5: NOKEYPublic key for jenkins-2.233-1.1.noarch.rpm is not installed{code}PS: I've followed this guide [https://wiki.jenkins.io/display/JENKINS/Installing+Jenkins+on+Red+Hat+distributions] Using `{{yum install jenkins --nogpgcheck}}` is not good idea as it breaks the trust to origin of software.
Add Comment
[JIRA] (JENKINS-61998) Jenkins upgrade fails on CentOS - Public key is not installed
Title: Message Title Constantin Bugneac created an issue Jenkins / JENKINS-61998 Jenkins upgrade fails on CentOS - Public key is not installed Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-21 18:52 Labels: jenkins Priority: Blocker Reporter: Constantin Bugneac It looks like since version 232 the Jenkins rpm package is not signed anymore with the published GPG key and it fails to install on CentOS using yum/rpm. # yum -y update jenkins Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: anorien.csc.warwick.ac.uk * elrepo: lon.mirror.rackspace.com * elrepo-kernel: lon.mirror.rackspace.com * epel: mirror.serverion.com * extras: anorien.csc.warwick.ac.uk * updates: mirrors.coreix.net Resolving Dependencies --> Running transaction check ---> Package jenkins.noarch 0:2.232-1.1 will be updated ---> Package jenkins.noarch 0:2.233-1.1 will be an update --> Finished Dependency ResolutionDependencies Resolved== PackageArch VersionRepository Size == Updating: jenkinsnoarch2.233-1.1 jenkins
[JIRA] (JENKINS-61995) P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long
Title: Message Title Joel Brown edited a comment on JENKINS-61995 Re: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long Hi [~fulingstar], do you have a stack trace in your *jenkins* log file ? Also, what's you your p4d/helix server exact version? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205886.1587487073000.15029.1587495120105%40Atlassian.JIRA.
[JIRA] (JENKINS-61995) P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long
Title: Message Title Joel Brown commented on JENKINS-61995 Re: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long Hi ling fu, do you have a stack trace in your jenkins log file ? Also, what's you p4d/helix server exact version? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205886.1587487073000.15027.1587494760295%40Atlassian.JIRA.
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Henry Xu commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification Jesse Glick Actually I don't think the idea of one job per branch and the multi-branch pipeline is feasible for a large project. I think Jenkins 2.0 pipeline already grants us the ability to handle the multi-branch scenario and merge requests in a single pipeline script. Multi-branch pipeline may looks good if everything works ideally. But in the real world, we have already had to apply some global change to work around unexpected problems several times. And by using the one job per branch strategy, we still have to distinguish push events and merge events to do different things. Then why not just handle all of those conditions in a single pipeline script. It's hard for me to switch to multi-branch pipeline without any strong reason. On the other hand, by providing a namespace mechanism for milestone, just as what we already had in `lock`, can be very useful and flexible in many cases. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187125.1513079616000.15019.1587494100320%40Atlassian.JIRA.
[JIRA] (JENKINS-61997) EmptyStackException from CpsFlowExecution.onProgramEnd
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-61997 EmptyStackException from CpsFlowExecution.onProgramEnd Change By: Jesse Glick Environment: CloudBees Core 2.222.2.1-rolling (I think) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205888.1587492081000.15015.1587492180061%40Atlassian.JIRA.
[JIRA] (JENKINS-61997) EmptyStackException from CpsFlowExecution.onProgramEnd
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-61997 EmptyStackException from CpsFlowExecution.onProgramEnd Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2020-04-21 18:01 Priority: Minor Reporter: Jesse Glick No idea how to reproduce; saw this after startup about a possibly stuck/broken build: ... WARNING org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService reportProblem Unexpected exception in CPS VM thread: CpsFlowExecution[Owner[...]] java.util.EmptyStackException at java.util.Stack.peek(Stack.java:102) at java.util.Stack.pop(Stack.java:84) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onProgramEnd(CpsFlowExecution.java:1236) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:423) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$400(CpsThreadGroup.java:96) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:312) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:276) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:67) Not entirely obvious what the most graceful response is here. Call createPlaceholderNodes?
[JIRA] (JENKINS-61969) Support websocket connection in swarm
Title: Message Title Basil Crow commented on JENKINS-61969 Re: Support websocket connection in swarm Hey Patrick Ruckstuhl, thanks for the feature request. I'd love to have WebSocket support in Swarm. Pull requests are welcome! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205858.1587374835000.15013.1587490560121%40Atlassian.JIRA.
[JIRA] (JENKINS-30341) jenkins maven release not releasing , uploading only snapshots
Title: Message Title Mehdi Mahmoud commented on JENKINS-30341 Re: jenkins maven release not releasing , uploading only snapshots Is that issue still opened, fixed or abandoned? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164934.1441713144000.15011.1587490260188%40Atlassian.JIRA.
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Jesse Glick commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification Our pipeline is triggered by GitLab's Merge Request events. Note that an alternate solution in this case is to use the GitLab branch source plugin, so that each MR corresponds to a distinct job. Obviously that is a big change with other impacts. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187125.1513079616000.15001.1587488520348%40Atlassian.JIRA.
[JIRA] (JENKINS-61996) Gitea organization with SSH checkout has ssh:/// in address
Title: Message Title Martin Zemek created an issue Jenkins / JENKINS-61996 Gitea organization with SSH checkout has ssh:/// in address Issue Type: Bug Assignee: Unassigned Attachments: 2020-04-21-log.txt, image-2020-04-21-18-40-08-741.png Components: gitea-plugin Created: 2020-04-21 16:43 Environment: Jenkins 2.232 Credentials 2.3.7 Gitea Plugin 1.2.0 Gitea 1.11.4 Priority: Minor Reporter: Martin Zemek Job fails to checkout over SSH. When created with Gitea organization and scanned for jenkinsfile. The problem seems to be in ssh url: git.exe config remote.origin.url ssh:///g...@gitea.f.cz:-1/F/3.git # timeout=10 notice the ssh:///git@ Because of this the "/git" user is used. The correct user should be "git" When using the git plugin and Multibranch pipeline, checkout proceeds correctly.
[JIRA] (JENKINS-61995) P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long
Title: Message Title ling fu created an issue Jenkins / JENKINS-61995 P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long Issue Type: Task Assignee: Unassigned Components: p4-plugin Created: 2020-04-21 16:37 Environment: Jenkins ver. 2.176.2 p4-plugin 1.10.3 windows 10 java.runtime.version 1.8.0_161-b12 Priority: Minor Reporter: ling fu I created a very simple freestyle job to use Perforce in SCM: Manual(custom view) view: (xxx) is the path on our P4 server //depot//... //jenkins-test_sync//... Force clean and sync (autoclean and sync has the same issue) At last, in the log, I saw the failure: P4 Task: syncing files at change: 2100529 ... p4 sync -p c:\jenkins\workspace\test_sync/...@2100529 -p4 sync -p c:\jenkins\workspace\test_sync/...@2100529 ... totalFileSize 69169 ... totalFileCount 4 .. //the files P4 Task: attempt: 1 ERROR: P4: Task Exception: com.perforce.p4java.exception.ConnectionException: Unmarshalable value in RpcStreamConnection.marshal; type: java.lang.Long Finished: FAILURE All the files are synced from P4 server on the local machine, but it reported the failure and failed the job.
[JIRA] (JENKINS-61867) Calendar Plugin should have options to show/hide polling
Title: Message Title Roland Asmann commented on JENKINS-61867 Re: Calendar Plugin should have options to show/hide polling Pull Request added: https://github.com/jenkinsci/calendar-view-plugin/pull/22 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205731.1586525088000.14992.1587486600126%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title
David Rodriguez edited a comment on JENKINS-61943
Re: Jenkins2, P4 Plugin: Error must create client ' to access local files
Hi Karl,The P4 command below is executed within maven {code:java}/bin/sh -c p4 -d /data/jenkins_home/workspace/admin-ui-4.2 changes -m1 ...{code}Why doesn't the P4CLIENT persist throughout the job like it does with Jenkins1. This way it's backward compatible when upgrading from jenkin1 to jenkins2. Otherwise the P4 Plugin it's not backward compatible.I modified the job on both jenkins1 and jenkin2 job by removing the maven step and adding adding only the shell step to execute the above command. The jenkins job config.xml and console logs are attached. * [^jenkins1-job-config.xml][^jenkins1-job-console.log][^jenkins2-job-config.xml][^jenkins2-job-console.log]!/jira/images/icons/link_attachment_7.gif|width=7,height=7,align=absmiddle!Note on Jenkin1, the P4 command below in the log returns an expected change from the perforce repo. Is it possible for the the P4 plugin in Jenkins2 to do the same? If so, how?Jenkin1 shell:{code:java}echo "P4CLIENT = $P4CLIENT"echo "P4_CLIENT = $P4_CLIENT"echo "PWD = `pwd`"cmd="/usr/bin/p4 -d /data/builds/workspace/drod-test-1.6 changes -m1 ..."`$cmd`{code}{panel:title=Jenkin1 console log}Sync complete, took 1003 ms [drod-test-1.6] $ /bin/sh -xe /tmp/hudson1085421712960825854.sh + echo P4CLIENT = ci-drod-test-1.6-1091564373 P4CLIENT = ci-drod-test-1.6-1091564373 + echo P4_CLIENT = P4_CLIENT = + pwd + echo PWD = /data/builds/workspace/drod-test-1.6 PWD = /data/builds/workspace/drod-test-1.6 + cmd=/usr/bin/p4 -d /data/builds/workspace/drod-test-1.6 changes -m1 ... + /usr/bin/p4 -d /data/builds/workspace/drod-test-1.6 changes -m1 ... *{color:#4c9aff}+ Change 290033 on 2018/11/16 by davidt@FR-NBSPT6 ' IT test fail'{color}* /tmp/hudson1085421712960825854.sh: 8: /tmp/hudson1085421712960825854.sh: Change: not found Build step 'Execute shell' marked build as failure Finished: FAILURE{panel} Jenkin2 shell:{code:java}echo "P4CLIENT = $P4CLIENT"echo "P4_CLIENT = $P4_CLIENT"echo "PWD = `pwd`"cmd="/usr/bin/p4 -d /data/jenkins_home/workspace/drod-test-2.222 changes -m1 ..."`$cmd`{code}{panel:title=Jenkin2 console log}[drod-test-2.222] $ /bin/sh -xe /tmp/jenkins7634372390604735818.sh + echo P4CLIENT = P4CLIENT = + echo P4_CLIENT = ci-drod-test-2.222 P4_CLIENT = ci-drod-test-2.222 + pwd + echo PWD = /data/jenkins_home/workspace/drod-test-2.222 PWD = /data/jenkins_home/workspace/drod-test-2.222 + cmd=/usr/bin/p4 -d /data/jenkins_home/workspace/drod-test-2.222 changes -m1 ... + /usr/bin/p4 -d /data/jenkins_home/workspace/drod-test-2.222 changes -m1 ... *{color:#de350b}... - must create client 'ip-10-21-2-84' to access local files.{color}* + Build step 'Execute shell'{panel}
Add Comment
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title David Rodriguez commented on JENKINS-61943 Re: Jenkins2, P4 Plugin: Error must create client ' to access local files Karl, you're awesome! Really appreciate your help with this. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.14988.1587485940198%40Atlassian.JIRA.
[JIRA] (JENKINS-60868) Calender View Plugin is not working with Parameterized Scheduler Plugin
Title: Message Title Roland Asmann commented on JENKINS-60868 Re: Calender View Plugin is not working with Parameterized Scheduler Plugin Pull Request added: https://github.com/jenkinsci/calendar-view-plugin/pull/21 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204244.1579997793000.14986.1587485760151%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth commented on JENKINS-61943 Re: Jenkins2, P4 Plugin: Error must create client ' to access local files Hi David Rodriguez - Not ignoring you but dont know the answer yet. Checking with the developers and will let you know when I have something. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.14979.1587484260129%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4_CLIENT environment variable non-reentrant
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60213 P4_CLIENT environment variable non-reentrant Change By: Karl Wirth Summary: P4CLIENT P4_CLIENT environment variable non-reentrant Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.14975.1587483180229%40Atlassian.JIRA.
[JIRA] (JENKINS-61994) kubernetes pipeline hangs forever when pod creation is rejected by kubernetes
Title: Message Title
Flemming Frandsen created an issue
Jenkins / JENKINS-61994
kubernetes pipeline hangs forever when pod creation is rejected by kubernetes
Issue Type:
Bug
Assignee:
Ioannis Canellos
Components:
kubernetes-pipeline-plugin, kubernetes-plugin
Created:
2020-04-21 15:28
Priority:
Critical
Reporter:
Flemming Frandsen
We use OPA gatekeeper to restrict which images can be used by our kubernetes builds. This means that if a non-whitelisted image is used, the k8s API server will reject the creation of the pod. If I manually apply the yaml from jenkins, then the rejection looks like this:
> kubectl apply -f hest.yaml
Error from server ([denied by image-constraint] container has an invalid image repo , allowed repos are ["jenkins/jnlp-slave:", "gitlab/gitlab-runner-helper:", "gitlab/gitlab-runner:", "foo.example.com:5501/", "gradle:", "alpine:", "golang:"]): error when creating "hest.yaml": admission webhook "validation.gatekeeper.sh" denied the request: [denied by image-constraint] container has an invalid image repo , allowed repos are ["jenkins/jnlp-slave:", "gitlab/gitlab-runner-helper:", "gitlab/gitlab-runner:", "foo.example.com:5501/", "gradle:", "alpine:", "golang:"]
In jenkins the build hangs at "Created Pod" until aborted.
Obtained Jenkinsfile from 259e54efd09055268dbe4e56f9f9738c4607ad1b
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] podTemplate
[Pipeline] {
[Pipeline] node
Still waiting to schedule task
All nodes of label
[JIRA] (JENKINS-61993) Test Results Aggregator - HTML report displays first row with black text on black background?
Title: Message Title
SON T DANG updated an issue
Jenkins / JENKINS-61993
Test Results Aggregator - HTML report displays first row with black text on black background?
Change By:
SON T DANG
HTML report displays OK via email notification. But if we view it on Jenkins URL, the first row displays Black text on Black background, see attached imageIf we download the html report (via Zip button), and view it using browser, it displays OK. Update: Error log from console: {code:java}index.html:1 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-Lc4aCLVicdnYsGslfePKymo8QsEMz6ZWfXmSYkS88BE='), or a nonce ('nonce-...') is required to enable inline execution. {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-61993) Test Results Aggregator - HTML report displays first row with black text on black background?
Title: Message Title SON T DANG updated an issue Jenkins / JENKINS-61993 Test Results Aggregator - HTML report displays first row with black text on black background? Change By: SON T DANG Summary: Test Results Aggregator - HTML report display displays first column row with black text on black background? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205884.1587481979000.14960.1587482280148%40Atlassian.JIRA.
[JIRA] (JENKINS-61993) Test Results Aggregator - HTML report display first column with black text on black background?
Title: Message Title SON T DANG updated an issue Jenkins / JENKINS-61993 Test Results Aggregator - HTML report display first column with black text on black background? Change By: SON T DANG HTML report displays OK via email notification. But if we view it on Jenkins URL, the first row displays Black text on Black background, see attached image If we download the html report (via Zip button), and view it using browser, it displays OK. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205884.1587481979000.14958.1587482160148%40Atlassian.JIRA.
[JIRA] (JENKINS-61993) Test Results Aggregator - HTML report display first column with black text on black background?
Title: Message Title SON T DANG updated an issue Jenkins / JENKINS-61993 Test Results Aggregator - HTML report display first column with black text on black background? Change By: SON T DANG Attachment: html_report.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205884.1587481979000.14956.1587482100282%40Atlassian.JIRA.
[JIRA] (JENKINS-61993) Test Results Aggregator - HTML report display first column with black text on black background?
Title: Message Title SON T DANG updated an issue Jenkins / JENKINS-61993 Test Results Aggregator - HTML report display first column with black text on black background? Change By: SON T DANG **If a job name contains special characters, must specify job name with characters in UTF-8 HTML report displays OK via email notification . Otherwise, But if we view it produces "Job Not found"For example on Jenkins URL , if job's name is "Some Test" the first row displays Black text on Black background , I must specify "Some%20Test"Need an improvement to avoid requiring filling in special characters in UTF-8 see attached image Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-61993) Test Results Aggregator - HTML report display first column with black text on black background?
Title: Message Title SON T DANG created an issue Jenkins / JENKINS-61993 Test Results Aggregator - HTML report display first column with black text on black background? Issue Type: Improvement Assignee: Socrates Sidereas Components: test-results-aggregator-plugin Created: 2020-04-21 15:12 Environment: Jenkins 2.231, Test Results Aggregator 1.0.7 Priority: Minor Reporter: SON T DANG **If a job name contains special characters, must specify job name with characters in UTF-8. Otherwise, it produces "Job Not found" For example, if job's name is "Some Test", I must specify "Some%20Test" Need an improvement to avoid requiring filling in special characters in UTF-8 Add Comment
[JIRA] (JENKINS-61992) Adding Veracode Scan to Veracode Jenkins Open source project
Title: Message Title Shihaaz Buhary assigned an issue to Shihaaz Buhary Jenkins / JENKINS-61992 Adding Veracode Scan to Veracode Jenkins Open source project Change By: Shihaaz Buhary Assignee: Dennis Gu Shihaaz Buhary Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205883.1587480871000.14950.1587481320153%40Atlassian.JIRA.
[JIRA] (JENKINS-61992) Adding Veracode Scan to Veracode Jenkins Open source project
Title: Message Title Shihaaz Buhary created an issue Jenkins / JENKINS-61992 Adding Veracode Scan to Veracode Jenkins Open source project Issue Type: Story Assignee: Dennis Gu Components: veracode-scan-plugin Created: 2020-04-21 14:54 Priority: Minor Reporter: Shihaaz Buhary Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to
[JIRA] (JENKINS-61988) The plugin default Java_opts
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-61988 The plugin default Java_opts Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205878.1587466129000.14941.1587480660413%40Atlassian.JIRA.
[JIRA] (JENKINS-61990) StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Title: Message Title
Sir Tumbleweed edited a comment on JENKINS-61990
Re: StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
One more thing that points me in this direction (or this 'other' plugin's direction):I thought moving out my init.groovy fixed the issue for me, but after next reboot the stackoverflow returned. So I continued digging and disabled the following block from an organization folder config brought the actual relief.{noformat}hudson.model.Item.Discover:myldapgroup hudson.model.Item.Read:myldapgroup hudson.model.Item.Workspace:myldapgroup hudson.model.View.Read:myldapgroup{noformat} There seems to be a circle in this per-project authorization configuration. But it's not clear to me why. After disabling this, my init.groovy also started working again, so I'll remove that hint from the original issue description. Edit: I think I narrowed it down to the Discover permission, which is implied by Item.Read and the validator in the frontend disallows selecting Discover when Item.Read is selected. Would be nice if there was a more tolerant handling to avoid this stack overflow of Jenkins though.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205880.1587466781000.14903.1587477960056%40Atlassian.JIRA.
[JIRA] (JENKINS-61520) At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error.
Title: Message Title Govind Sureka commented on JENKINS-61520 Re: At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error. Thanks Anda, currently I don't have access to the Lab options mentioned in doc that you shared. Could you please provide solution for the JNLP-4 error which is major hinderance now from Jenkins execution. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205217.1584601273000.14902.1587476460246%40Atlassian.JIRA.
[JIRA] (JENKINS-61375) Cannot disable CSRF
Title: Message Title John Rocha commented on JENKINS-61375 Re: Cannot disable CSRF For those of you that stumble upon this issue. It is resolved with a Jenkins configuration change. There may be other ways to resolve this, but this is how I resolved it. Configure remote machine remote machine to add a token Log on to Jenkins as the user that will execute the job (i.e. build user) Select People Select your user ID (i.e. build user). Select Configure Find the section titled API Token to add a token Select Add new Token Select Generate Copy the token and keep it. This is the only time the token will be in plain text for you to copy. Select [Save] to save the token with the user Configure calling machine's remote parameterized interface to use this token Log on to Jenkins on the calling machine Select Manage Jenkins. Select Configure System. Scroll down to the the section Parameterized Remote Trigger Configuration and find the entry for the remote machine you added a token to in the previous step. Change Authentication to Token Authentication. Set the User Name to the correct user (i.e. build user) Paste the copied token from the previous configuration into the API Token_ field. Select [Save] This should fix the remote parameter calls. It should now work even with CSRF enabled.
[JIRA] (JENKINS-61985) MyViewsProperty support for configuration-as-code
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-61985 MyViewsProperty support for configuration-as-code Change By: Tim Jacomb Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205875.1587459604000.14898.1587474540195%40Atlassian.JIRA.
[JIRA] (JENKINS-61985) MyViewsProperty support for configuration-as-code
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-61985 MyViewsProperty support for configuration-as-code Change By: Tim Jacomb Summary: NPE when saving MyViewsProperty support for configuration-as-code Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205875.1587459604000.14896.1587474480164%40Atlassian.JIRA.
[JIRA] (JENKINS-61991) Support for pull request builds
Title: Message Title Marco van Munster created an issue Jenkins / JENKINS-61991 Support for pull request builds Issue Type: Improvement Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2020-04-21 12:21 Priority: Minor Reporter: Marco van Munster **I would like to have support for jenkins build trigger on new pull request or updated pull request in bitbucket. Now I merge the feature branch with the develop branch before te build, ( with the feature "Merge before build" from Additional Behaviours from Bitbucket Server SCM) the problem is that no new build is triggered when the target branch/develop is updated. But the build status in Bitbucket pull request is then gone. Add Comment
[JIRA] (JENKINS-61985) NPE when saving MyViewsProperty
Title: Message Title
Evaristo Gutierrez updated an issue
Jenkins / JENKINS-61985
NPE when saving MyViewsProperty
Change By:
Evaristo Gutierrez
When applying a configuration, a NPE is raised because of the MyViewsProperty class.{code:java}java.lang.NullPointerException at hudson.model.MyViewsProperty.save(MyViewsProperty.java:138) at hudson.BulkChange.commit(BulkChange.java:98) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:271) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.configure(DataBoundConfigurator.java:83) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$doConfigure$16668e2$1(HeteroDescribableConfigurator.java:277) at io.vavr.CheckedFunction0.lambda$unchecked$52349c75$1(CheckedFunction0.java:247) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.doConfigure(HeteroDescribableConfigurator.java:277) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$null$2(HeteroDescribableConfigurator.java:86) at io.vavr.control.Option.map(Option.java:392) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$configure$3(HeteroDescribableConfigurator.java:86) at io.vavr.Tuple2.apply(Tuple2.java:238) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.configure(HeteroDescribableConfigurator.java:83) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.configure(HeteroDescribableConfigurator.java:55) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:345) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:276) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.configure(DataBoundConfigurator.java:83) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:345) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:276) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.configure(DataBoundConfigurator.java:83) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$doConfigure$16668e2$1(HeteroDescribableConfigurator.java:277) at io.vavr.CheckedFunction0.lambda$unchecked$52349c75$1(CheckedFunction0.java:247) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.doConfigure(HeteroDescribableConfigurator.java:277) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$null$2(HeteroDescribableConfigurator.java:86) at io.vavr.control.Option.map(Option.java:392) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$configure$3(HeteroDescribableConfigurator.java:86) at io.vavr.Tuple2.apply(Tuple2.java:238) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.configure(HeteroDescribableConfigurator.java:83) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.check(HeteroDescribableConfigurator.java:92) at
[JIRA] (JENKINS-61985) NPE when saving MyViewsProperty
Title: Message Title Evaristo Gutierrez commented on JENKINS-61985 Re: NPE when saving MyViewsProperty Tim Jacomb sorry, I have added it to the description. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205875.1587459604000.14891.1587470100256%40Atlassian.JIRA.
[JIRA] (JENKINS-61985) NPE when saving MyViewsProperty
Title: Message Title Tim Jacomb commented on JENKINS-61985 Re: NPE when saving MyViewsProperty What’s the configuration being applied? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205875.1587459604000.14888.1587469320177%40Atlassian.JIRA.
[JIRA] (JENKINS-61990) StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Title: Message Title
Sir Tumbleweed updated an issue
Jenkins / JENKINS-61990
StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Change By:
Sir Tumbleweed
After latest container (LTS) and plugin updates, booting the jenkins results in huge stacktraces caused by a stackoverflow error. The result is that the Jenkins seems available, the queue is filled but items cannot be worked on, because a class has not been properly loaded on boot:{noformat}java.lang.IllegalStateException: The class jenkins.security.QueueItemAuthenticatorConfiguration was not found, potentially not yet loadedjava.lang.IllegalStateException: The class jenkins.security.QueueItemAuthenticatorConfiguration was not found, potentially not yet loaded at hudson.ExtensionList.getInstance(ExtensionList.java:166) at jenkins.security.QueueItemAuthenticatorConfiguration.get(QueueItemAuthenticatorConfiguration.java:61) at jenkins.security.QueueItemAuthenticatorConfiguration$ProviderImpl.getAuthenticators(QueueItemAuthenticatorConfiguration.java:70) at jenkins.security.QueueItemAuthenticatorProvider$IteratorImpl.hasNext(QueueItemAuthenticatorProvider.java:44) at hudson.model.Queue$Item.authenticate(Queue.java:2332) {noformat}The relevant source of evil is the following stacktrace which I will attach in full as a file.To make this pop up in searches I paste an excerpt of the stack trace here.{noformat}at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:66) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:268) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:390) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:328) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:267) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:197) at hudson.util.DescribableList$ConverterImpl.unmarshal(DescribableList.java:275) at
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Roman Pickl edited a comment on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
I used [~ext3h]'s solution:https://issues.jenkins-ci.org/browse/JENKINS-9104?focusedCommentId=360603=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-360603 we solved it like this in a jenkins github multi-branch setup with jenkinsfiles: {code:java} bat """ mkdir tmp set _MSPDBSRV_ENDPOINT_= ${BUILD_TAG} set TMP=${Workspace}\\tmp set TEMP=${Workspace}\\tmp set TMPDIR=${Workspace}\\tmp build.bat """ {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.139260.1300499644000.14795.1587468902158%40Atlassian.JIRA.
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title
Roman Pickl commented on JENKINS-9104
Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
I used Andreas Ringlstetter's solution: https://issues.jenkins-ci.org/browse/JENKINS-9104?focusedCommentId=360603=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-360603 we solved it like this in a jenkins github multi-branch setup with jenkinsfiles: bat """ mkdir tmp set MSPDBSRV_ENDPOINT= ${BUILD_TAG} set TMP=${Workspace}tmp set TEMP=${Workspace}tmp set TMPDIR=${Workspace}tmp build.bat """
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.139260.1300499644000.14702.1587468841800%40Atlassian.JIRA.
[JIRA] (JENKINS-61990) StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Title: Message Title Sir Tumbleweed commented on JENKINS-61990 Re: StackOverflowError on boot related to QueueItemAuthenticatorConfiguration One more thing that points me in this direction (or this 'other' plugin's direction): I thought moving out my init.groovy fixed the issue for me, but after next reboot the stackoverflow returned. So I continued digging and disabled the following block from an organization folder config brought the actual relief. hudson.model.Item.Discover:myldapgroup hudson.model.Item.Read:myldapgroup hudson.model.Item.Workspace:myldapgroup hudson.model.View.Read:myldapgroup There seems to be a circle in this per-project authorization configuration. But it's not clear to me why. After disabling this, my init.groovy also started working again, so I'll remove that hint from the original issue description. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205880.1587466781000.14699.1587468780049%40Atlassian.JIRA.
[JIRA] (JENKINS-61990) StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Title: Message Title Daniel Beck assigned an issue to Unassigned That's yet another plugin, but likely unrelated too. Jenkins / JENKINS-61990 StackOverflowError on boot related to QueueItemAuthenticatorConfiguration Change By: Daniel Beck Component/s: core Component/s: matrix-auth-plugin Component/s: matrix-project-plugin Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61990) StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Title: Message Title Sir Tumbleweed commented on JENKINS-61990 Re: StackOverflowError on boot related to QueueItemAuthenticatorConfiguration I assumed a connetion due to at jenkins.security.QueueItemAuthenticatorConfiguration.get(QueueItemAuthenticatorConfiguration.java:61) at org.jenkinsci.plugins.authorizeproject.ProjectQueueItemAuthenticator.getConfigured(ProjectQueueItemAuthenticator.java:178) at org.jenkinsci.plugins.authorizeproject.ProjectQueueItemAuthenticator.isConfigured(ProjectQueueItemAuthenticator.java:190) at org.jenkinsci.plugins.authorizeproject.AuthorizeProjectStrategy.checkUnsecuredConfiguration(AuthorizeProjectStrategy.java:186) at org.jenkinsci.plugins.authorizeproject.AuthorizeProjectStrategy.readResolve(AuthorizeProjectStrategy.java:176) but I might be wrong. I am not familiar with the numerous components. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205880.1587466781000.14695.1587468360119%40Atlassian.JIRA.
[JIRA] (JENKINS-61602) Passing script parameters containing "|" works on Linux but fails on Windows
Title: Message Title Dirk Heinrichs commented on JENKINS-61602 Re: Passing script parameters containing "|" works on Linux but fails on Windows Any news on this? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205301.158471799.14691.1587468300160%40Atlassian.JIRA.
[JIRA] (JENKINS-61694) Groovy Hooks may run before or after JOB_CONFIG_ADAPTED
Title: Message Title Daniel Beck commented on JENKINS-61694 Re: Groovy Hooks may run before or after JOB_CONFIG_ADAPTED Would this address JENKINS-61694? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205519.1585231269000.14693.1587468300188%40Atlassian.JIRA.
[JIRA] (JENKINS-61990) StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Title: Message Title Daniel Beck commented on JENKINS-61990 Re: StackOverflowError on boot related to QueueItemAuthenticatorConfiguration What does this have to do with matrix-auth plugin and/or matrix-project plugin? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205880.1587466781000.14688.1587468240177%40Atlassian.JIRA.
[JIRA] (JENKINS-61990) StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Title: Message Title
Sir Tumbleweed updated an issue
Jenkins / JENKINS-61990
StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Change By:
Sir Tumbleweed
After latest container (LTS) and plugin updates, booting the jenkins results in huge stacktraces caused by a stackoverflow error. The result is that the Jenkins seems available, the queue is filled but items cannot be worked on, because a class has not been properly loaded on boot:{noformat}java.lang.IllegalStateException: The class jenkins.security.QueueItemAuthenticatorConfiguration was not found, potentially not yet loadedjava.lang.IllegalStateException: The class jenkins.security.QueueItemAuthenticatorConfiguration was not found, potentially not yet loaded at hudson.ExtensionList.getInstance(ExtensionList.java:166) at jenkins.security.QueueItemAuthenticatorConfiguration.get(QueueItemAuthenticatorConfiguration.java:61) at jenkins.security.QueueItemAuthenticatorConfiguration$ProviderImpl.getAuthenticators(QueueItemAuthenticatorConfiguration.java:70) at jenkins.security.QueueItemAuthenticatorProvider$IteratorImpl.hasNext(QueueItemAuthenticatorProvider.java:44) at hudson.model.Queue$Item.authenticate(Queue.java:2332) {noformat}The relevant source of evil is the following stacktrace which I will attach in full as a file.To make this pop up in searches I paste an excerpt of the stack trace here.{noformat}at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:66) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:268) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:390) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:328) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:267) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:197) at hudson.util.DescribableList$ConverterImpl.unmarshal(DescribableList.java:275) at
[JIRA] (JENKINS-61990) StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Title: Message Title
Sir Tumbleweed updated an issue
Jenkins / JENKINS-61990
StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Change By:
Sir Tumbleweed
After latest container (LTS) and plugin updates, booting the jenkins results in huge stacktraces caused by a stackoverflow error. The result is that the Jenkins seems available, the queue is filled but items cannot be worked on, because a class has not been properly loaded on boot:{noformat}java.lang.IllegalStateException: The class jenkins.security.QueueItemAuthenticatorConfiguration was not found, potentially not yet loadedjava.lang.IllegalStateException: The class jenkins.security.QueueItemAuthenticatorConfiguration was not found, potentially not yet loaded at hudson.ExtensionList.getInstance(ExtensionList.java:166) at jenkins.security.QueueItemAuthenticatorConfiguration.get(QueueItemAuthenticatorConfiguration.java:61) at jenkins.security.QueueItemAuthenticatorConfiguration$ProviderImpl.getAuthenticators(QueueItemAuthenticatorConfiguration.java:70) at jenkins.security.QueueItemAuthenticatorProvider$IteratorImpl.hasNext(QueueItemAuthenticatorProvider.java:44) at hudson.model.Queue$Item.authenticate(Queue.java:2332) {noformat}The relevant source of evil is the following stacktrace which I will attach in full as a file.To make this pop up in searches I paste an excerpt of the stack trace here.{noformat}at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:66) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:268) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:390) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:328) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:267) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:197) at hudson.util.DescribableList$ConverterImpl.unmarshal(DescribableList.java:275) at
[JIRA] (JENKINS-61990) StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Title: Message Title Sir Tumbleweed updated an issue Jenkins / JENKINS-61990 StackOverflowError on boot related to QueueItemAuthenticatorConfiguration Change By: Sir Tumbleweed Summary: StackOverflowError on boot related toQueueItemAuthenticatorConfiguration Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205880.1587466781000.14681.1587466860132%40Atlassian.JIRA.
[JIRA] (JENKINS-61990) StackOverflowError on boot related to
Title: Message Title Sir Tumbleweed created an issue Jenkins / JENKINS-61990 StackOverflowError on boot related to Issue Type: Bug Assignee: Daniel Beck Attachments: jenkins_stackoverflow.txt Components: matrix-auth-plugin, matrix-project-plugin Created: 2020-04-21 10:59 Environment: Jenkins version 2.222.1 matrix-auth 2.5 matrix-project 1.14 Priority: Minor Reporter: Sir Tumbleweed After latest container (LTS) and plugin updates, booting the jenkins results in huge stacktraces caused by a stackoverflow error. The result is that the Jenkins seems available, the queue is filled but items cannot be worked on, because a class has not been properly loaded on boot: java.lang.IllegalStateException: The class jenkins.security.QueueItemAuthenticatorConfiguration was not found, potentially not yet loadedjava.lang.IllegalStateException: The class jenkins.security.QueueItemAuthenticatorConfiguration was not found, potentially not yet loaded at hudson.ExtensionList.getInstance(ExtensionList.java:166) at jenkins.security.QueueItemAuthenticatorConfiguration.get(QueueItemAuthenticatorConfiguration.java:61) at jenkins.security.QueueItemAuthenticatorConfiguration$ProviderImpl.getAuthenticators(QueueItemAuthenticatorConfiguration.java:70) at jenkins.security.QueueItemAuthenticatorProvider$IteratorImpl.hasNext(QueueItemAuthenticatorProvider.java:44) at
[JIRA] (JENKINS-61989) Office-365-Connector Plugin no option to set proxy configuration
Title: Message Title Devaraja Somaiah created an issue Jenkins / JENKINS-61989 Office-365-Connector Plugin no option to set proxy configuration Issue Type: Bug Assignee: Srivardhan Hebbar Components: office-365-connector-plugin Created: 2020-04-21 10:56 Priority: Minor Reporter: Devaraja Somaiah Hi, We are trying do MSTeams server Integration with our Jenkins CI Server to send status notifications for the Build Jobs, for this we used Jenkins Plugin O*ffice-365-Connector(4.12.4)*.The issue we are facing is we have a proxy server in between Jenkins & MSTeams server and we observed there is no option of defining proxy configuration in the Office-365-Connector plugin setup.Please let me know how to set proxy server details in this Plugin so that it sends messages using proxy to the MSTEAM Server. Thanks Devaraj Add Comment
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Henry Xu commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification I think this is an essential feature that needs to be implemented in milestone. Our pipeline is triggered by GitLab's Merge Request events. Whenever there are code updated or special comments, the job will be triggered. It is very common to have multiple builds that triggered by the same Merge Request in our pipeline. In this case, we would hope that old builds should be aborted if there are a new build of same Merge Request. If milestone can support classification, then we can simply write milestone(groupLable: env.gitlab_merge_request_id) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187125.1513079616000.14669.1587466320316%40Atlassian.JIRA.
[JIRA] (JENKINS-61988) The plugin default Java_opts
Title: Message Title Владислав Ненашев created an issue Jenkins / JENKINS-61988 The plugin default Java_opts Issue Type: Task Assignee: Devin Nusbaum Components: jdk-tool-plugin Created: 2020-04-21 10:48 Environment: Jenkins ver. 2.204.2 Priority: Major Reporter: Владислав Ненашев The plugin generates Java_opts when unpacking the portable version from the archive with the-d64 option that causes a problem when installing java 11, please add the Java_opts setting to the plugin settings Unrecognized option: -d64 Add Comment
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Timo Sand commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification Use case: We have a single job which does PR deployments. It is triggered by each PR's own build job, but with different params, like which branch to deploy etc. We would like to ensure that only the latest build gets deployed as it would be unnecessary to deploy older builds. Milestones and inverse locks seemed to offer a great solution to this, but milestones don't take parameters into account at all and thus it cancels jobs which have different parameters. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187125.1513079616000.14659.1587466020265%40Atlassian.JIRA.
[JIRA] (JENKINS-61987) Update default value of job parameter after change in Jenkinsfile
Title: Message Title Piotr Krukowiecki closed an issue as Not A Defect Closing Jenkins / JENKINS-61987 Update default value of job parameter after change in Jenkinsfile Change By: Piotr Krukowiecki Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-61987) Update default value of job parameter after change in Jenkinsfile
Title: Message Title Piotr Krukowiecki commented on JENKINS-61987 Re: Update default value of job parameter after change in Jenkinsfile I'm sorry. It looks like I had a syntax error in my Jenkinsfile. After fixing it, Jenkins is picking up my changes in defaultValue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205877.1587465343000.14655.1587465720060%40Atlassian.JIRA.
[JIRA] (JENKINS-61987) Update default value of job parameter after change in Jenkinsfile
Title: Message Title
Piotr Krukowiecki updated an issue
Jenkins / JENKINS-61987
Update default value of job parameter after change in Jenkinsfile
Change By:
Piotr Krukowiecki
Changes to the parameter *defaultValue* in Jenkinsfile are not reflected in existing Jenkins job after executing the job. * use following parameter definition:{code:java}properties([parameters([string(name: 'EXCLUDE', defaultValue: 'pattern', description: ' Exclude jobs that match this regexp description '),]),]) {code} * add new job and run it for the first time, go to job configuration - the job should now have this parameter with "pattern' default value * change in the Jenkinsfile pattern to "pattern2" * run the job again and go to job configuration - the job will still have the old value "pattern"
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] (JENKINS-61987) Update default value of job parameter after change in Jenkinsfile
Title: Message Title Piotr Krukowiecki created an issue Jenkins / JENKINS-61987 Update default value of job parameter after change in Jenkinsfile Issue Type: New Feature Assignee: Unassigned Components: pipeline-model-definition-plugin Created: 2020-04-21 10:35 Priority: Minor Reporter: Piotr Krukowiecki Changes to the parameter defaultValue in Jenkinsfile are not reflected in existing Jenkins job after executing the job. use following parameter definition: properties([ parameters([ string(name: 'EXCLUDE', defaultValue: 'pattern', description: 'Exclude jobs that match this regexp'), ]), ]) add new job and run it for the first time, go to job configuration - the job should now have this parameter with "pattern' default value change in the Jenkinsfile pattern to "pattern2" run the job again and go to job configuration - the job will still have the old value "pattern"
[JIRA] (JENKINS-61414) ERROR: No item named xxx/yyy found
Title: Message Title prakash raj assigned an issue to Unassigned Jenkins / JENKINS-61414 ERROR: No item named xxx/yyy found Change By: prakash raj Assignee: prakash raj Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205074.1583851284000.14652.1587464760117%40Atlassian.JIRA.
[JIRA] (JENKINS-61414) ERROR: No item named xxx/yyy found
Title: Message Title prakash raj assigned an issue to prakash raj Jenkins / JENKINS-61414 ERROR: No item named xxx/yyy found Change By: prakash raj Assignee: prakash raj Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205074.1583851284000.14650.1587464700124%40Atlassian.JIRA.
[JIRA] (JENKINS-61974) Test Results Aggregator - Special character in Job name
Title: Message Title SON T DANG commented on JENKINS-61974 Re: Test Results Aggregator - Special character in Job name Update: The job name with special characters should be displayed "without UTF-8" as well in Report page: /reports/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205863.158738195.14619.1587461220129%40Atlassian.JIRA.
[JIRA] (JENKINS-61974) Test Results Aggregator - Special character in Job name
Title: Message Title Socrates Sidereas started work on JENKINS-61974 Change By: Socrates Sidereas Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205863.158738195.14591.1587460620433%40Atlassian.JIRA.
[JIRA] (JENKINS-61974) Test Results Aggregator - Special character in Job name
Title: Message Title Socrates Sidereas updated JENKINS-61974 Jenkins / JENKINS-61974 Test Results Aggregator - Special character in Job name Change By: Socrates Sidereas Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205863.158738195.14593.1587460620459%40Atlassian.JIRA.
