[JIRA] (JENKINS-59529) Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Title: Message Title
Brent Zeiss commented on JENKINS-59529
Re: Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Alright, just discovered some odd behavior. If the Stdout is returned, then the script will fail as expected... I would expect both to return a postive exit code! The downside of using returnStdout is that none of that output will be displayed in the logs.
pipeline {
agent any
stages {
stage('gobbledygook - will pass') {
steps{
powershell script: 'gobbledygook'
}
}
stage('gobbledygook - will fail') {
steps{
powershell returnStdout: true, script: 'gobbledygook'
}
}
}
}
And this is the output:
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in C:\jenkins_workspace\Jenkins Playground\PowershellErrorExample
[Pipeline] {
[Pipeline] stage
[Pipeline] { (gobbledygook - will pass)
[Pipeline] powershell
powershell.exe : gobbledygook : The term 'gobbledygook' is not recognized as the name of a cmdlet, function, script file, or operable
At C:\jenkins_workspace\Jenkins Playground\PowershellErrorExample@tmp\durable-805172ca\powershellWrapper.ps1:3 char:1
+ & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ...
+ ~
+ CategoryInfo : NotSpecified: (gobbledygook : ...e, or operable :String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\jenkins_workspace\Jenkins Playground\PowershellErrorExample@tmp\durable-805172ca\powershellScript.ps1:1 char:1
+ gobbledygook
+
+ CategoryInfo : ObjectNotFound: (gobbledygook:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (gobbledygook - will fail)
[Pipeline] powershell
gobbledygook : The term 'gobbledygook' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify
that the path is correct and try again.
At C:\jenkins_workspace\Jenkins Playground\PowershellErrorExample@tmp\durable-bf7e742d\powershellScript.ps1:1 char:1
+ gobbledygook
+
+ CategoryInfo : ObjectNotFound: (gobbledygook:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE
[JIRA] (JENKINS-59512) I am getting Connection timed out while testing HP ALM connection throu Jenkins
Title: Message Title Roy Lu commented on JENKINS-59512 Re: I am getting Connection timed out while testing HP ALM connection throu Jenkins Hi Which build step were you using? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202135.1569336332000.5670.1569462660230%40Atlassian.JIRA.
[JIRA] (JENKINS-59537) Test open PR's
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59537 Test open PR's Issue Type: Task Assignee: Marky Jackson Components: prometheus-plugin Created: 2019-09-26 01:23 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59536) Triage open issues
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59536 Triage open issues Issue Type: Task Assignee: Marky Jackson Components: prometheus-plugin Created: 2019-09-26 01:22 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59535) Document setting up development environment for the plugin
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59535 Document setting up development environment for the plugin Issue Type: Task Assignee: Marky Jackson Components: prometheus-plugin Created: 2019-09-26 01:22 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59534) Document setting up the plugin and use cases
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59534 Document setting up the plugin and use cases Issue Type: Task Assignee: Marky Jackson Components: prometheus-plugin Created: 2019-09-26 01:21 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59533) Document setting up development environment for the plugin
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59533 Document setting up development environment for the plugin Issue Type: Task Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-09-26 01:21 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59532) Document the setup to use the plugin for the wiki
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59532 Document the setup to use the plugin for the wiki Issue Type: Task Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-09-26 01:20 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59531) Triage all open issues
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59531 Triage all open issues Issue Type: Task Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-09-26 01:19 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59530) Manually test all open PR's
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59530 Manually test all open PR's Issue Type: Task Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-09-26 01:19 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56307) Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time
Title: Message Title Rick updated JENKINS-56307 https://github.com/jenkinsci/kubernetes-plugin/releases/tag/kubernetes-1.19.1 Jenkins / JENKINS-56307 Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time Change By: Rick Status: Fixed but Unreleased Resolved Released As: kubernetes-1.19.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-59529) Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Title: Message Title
Brent Zeiss edited a comment on JENKINS-59529
Re: Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
{{ According to [ }}{{ this answer on SO }}{{ | }}{{[ https://stackoverflow.com/a/34853488/848668] }}{{] , the script should be exiting with an exit code of 1 when the {{ -NonInteractive }} flag is used. At least in the case of {{ MissingMandatoryParameter . }} .
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202158.1569456687000.5641.1569458340042%40Atlassian.JIRA.
[JIRA] (JENKINS-59529) Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Title: Message Title
Brent Zeiss edited a comment on JENKINS-59529
Re: Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
{{According to [ }}{{ this answer on SO }}{{ | }}{{ [https://stackoverflow.com/a/34853488/848668] }}{{ ], the script should be exiting with an exit code of 1 when the -NonInteractive flag is used. At least in the case of MissingMandatoryParameter.}}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202158.1569456687000.5640.1569458280122%40Atlassian.JIRA.
[JIRA] (JENKINS-59529) Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Title: Message Title
Brent Zeiss edited a comment on JENKINS-59529
Re: Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
{{According to [this answer on SO|[https://stackoverflow.com/a/34853488/848668] , ] , the script should be exiting with an exit code of 1 when the -NonInteractive flag is used. At least in the case of MissingMandatoryParameter.}}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202158.1569456687000.5639.1569458280070%40Atlassian.JIRA.
[JIRA] (JENKINS-59529) Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Title: Message Title Brent Zeiss commented on JENKINS-59529 Re: Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException" According to [this answer on SO|https://stackoverflow.com/a/34853488/848668,] the script should be exiting with an exit code of 1 when the -NonInteractive flag is used. At least in the case of MissingMandatoryParameter. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202158.1569456687000.5638.1569458160064%40Atlassian.JIRA.
[JIRA] (JENKINS-59529) Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Title: Message Title
Brent Zeiss updated an issue
Jenkins / JENKINS-59529
Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Change By:
Brent Zeiss
A build will not fail when a powershell script encounters an error "MissingMandatoryParameter" or "CommandNotFoundException".I would expect an error code other than 0, or, for the script to fail.Here are some examples:{code:java}powershell "gobbledygook"{code}Results in something similar to:{noformat}[Pipeline] echoRunning powershell command:gobbledygook [Pipeline] powershellpowershell.exe : gobbledygook : The term 'gobbledygook' is not recognized as the name of a cmdlet, function, script file, or operable At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable-25a0caf8\powershellWrapper.ps1:3 char:1+ & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ...+ ~+ CategoryInfo : NotSpecified: (gobbledygook : ...e, or operable :String) [], RemoteException+ FullyQualifiedErrorId : NativeCommandError program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable-25a0caf8\powershellScript.ps1:3 char:5+ gobbledygook+ + CategoryInfo : ObjectNotFound: (gobbledygook:String) [], CommandNotFoundException+ FullyQualifiedErrorId : CommandNotFoundException [Pipeline] echoPowershell exit status: 0{noformat}and{code:java}powershell "buildVS 'Release' -nuget $true"{code}Results in something similar to:{noformat}[Pipeline] echo Running powershell command: buildVS 'Release' -nuget $true [Pipeline] powershellpowershell powershellpowershell .exe : buildVS : Cannot process command because of one or more missing mandatory parameters: config. At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable- d4ee0605 9137f721 \powershellWrapper.ps1:3 char:1 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ... + ~ + CategoryInfo : NotSpecified: (buildVS : Canno...meters: config.:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable- d4ee0605 9137f721 \powershellScript.ps1:3 char:5 + buildVS 'Release' -nuget $true + ~~~ + CategoryInfo : InvalidArgument: ( :) [buildVS], ParameterBindingException + FullyQualifiedErrorId : MissingMandatoryParameter,buildVS [Pipeline] echoPowershell exit status: 0 {noformat}
[JIRA] (JENKINS-59529) Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Title: Message Title
Brent Zeiss updated an issue
Jenkins / JENKINS-59529
Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Change By:
Brent Zeiss
A build will not fail when a powershell script encounters an error "MissingMandatoryParameter" or "CommandNotFoundException".I would expect an error code other than 0, or, for the script to fail.Here are some examples:{code:java}powershell " buildVS 'Release' -nuget $true gobbledygook "{code} Results in something similar to:{noformat}[Pipeline] echo Running powershell command: buildVS 'Release' -nuget $true gobbledygook [Pipeline] powershellpowershell powershellpowershell .exe : buildVS gobbledygook : Cannot process command because The term 'gobbledygook' is not recognized as the name of one a cmdlet, function, script file, or more missing mandatory parameters: config. operable At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable- d4ee0605 25a0caf8 \powershellWrapper.ps1:3 char:1 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ... + ~ + CategoryInfo : NotSpecified: ( buildVS gobbledygook : Canno ... meters e, or operable : config.: String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable- d4ee0605 25a0caf8 \powershellScript.ps1:3 char:5+ buildVS 'Release' -nuget $true gobbledygook + ~~~ + CategoryInfo : InvalidArgument ObjectNotFound : ( gobbledygook:String) [ buildVS ], ParameterBindingException CommandNotFoundException + FullyQualifiedErrorId : MissingMandatoryParameter,buildVS CommandNotFoundException [Pipeline] echoPowershell exit status: 0 {noformat}and{code:java}powershell " gobbledygook buildVS 'Release' -nuget $true "{code}Results in something similar to:{noformat}[Pipeline] echo Running powershell command: gobbledygook buildVS 'Release' -nuget $true [Pipeline] powershellpowershell powershellpowershell .exe : gobbledygook buildVS : The term 'gobbledygook' is not recognized as the name Cannot process command because of a cmdlet, function, script file, one or operable more missing mandatory parameters: config. At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable- 25a0caf8 d4ee0605 \powershellWrapper.ps1:3 char:1+ & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ...+ ~+ CategoryInfo : NotSpecified: ( gobbledygook buildVS : Canno ... e, or operable meters : config.: String) [], RemoteException+ FullyQualifiedErrorId : NativeCommandError program. Check the spelling of the name, or if a
[JIRA] (JENKINS-59529) Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Title: Message Title
Brent Zeiss updated an issue
Jenkins / JENKINS-59529
Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Change By:
Brent Zeiss
A build will not fail when a powershell script encounters an error "MissingMandatoryParameter" or "CommandNotFoundException". I would expect an error code other than 0, or, for the script to fail.Here are some examples:{code:java}powershell "buildVS 'Release' -nuget $true"{code} Results in something similar to:{noformat} [Pipeline] echo Running powershell command: buildVS 'Release' -nuget $true [Pipeline] powershellpowershell.exe : buildVS : Cannot process command because of one or more missing mandatory parameters: config. At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable-d4ee0605\powershellWrapper.ps1:3 char:1 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ... + ~ + CategoryInfo : NotSpecified: (buildVS : Canno...meters: config.:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable-d4ee0605\powershellScript.ps1:3 char:5 + buildVS 'Release' -nuget $true + ~~~ + CategoryInfo : InvalidArgument: ( :) [buildVS], ParameterBindingException + FullyQualifiedErrorId : MissingMandatoryParameter,buildVS {noformat}and{code:java}powershell "gobbledygook"{code}Results in something similar to:{noformat}[Pipeline] echoRunning powershell command:gobbledygook [Pipeline] powershellpowershell.exe : gobbledygook : The term 'gobbledygook' is not recognized as the name of a cmdlet, function, script file, or operable At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable-25a0caf8\powershellWrapper.ps1:3 char:1+ & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ...+ ~+ CategoryInfo : NotSpecified: (gobbledygook : ...e, or operable :String) [], RemoteException+ FullyQualifiedErrorId : NativeCommandError program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable-25a0caf8\powershellScript.ps1:3 char:5+ gobbledygook+ + CategoryInfo : ObjectNotFound: (gobbledygook:String) [], CommandNotFoundException+ FullyQualifiedErrorId : CommandNotFoundException [Pipeline] echoPowershell exit status: 0{noformat}
[JIRA] (JENKINS-59529) Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Title: Message Title Brent Zeiss updated an issue Jenkins / JENKINS-59529 Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException" Change By: Brent Zeiss The powershell command is: buildVS 'Release' -nuget $true [Pipeline] echoRunning powershell command:buildVS 'Release' -nuget $true [Pipeline] powershellpowershell.exe : buildVS : Cannot process command because of one or more missing mandatory parameters: config.At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable-d4ee0605\powershellWrapper.ps1:3 char:1+ & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ...+ ~+ CategoryInfo : NotSpecified: (buildVS : Canno...meters: config.:String) [], RemoteException+ FullyQualifiedErrorId : NativeCommandErrorAt C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable-d4ee0605\powershellScript.ps1:3 char:5+ buildVS 'Release' -nuget $true+ ~~~+ CategoryInfo : InvalidArgument: (:) [buildVS], ParameterBindingException+ FullyQualifiedErrorId : MissingMandatoryParameter,buildVS Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59529) Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException"
Title: Message Title Brent Zeiss created an issue Jenkins / JENKINS-59529 Build is not failing when powershell script exits with "MissingMandatoryParameter" or "CommandNotFoundException" Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2019-09-26 00:11 Priority: Minor Reporter: Brent Zeiss The powershell command is: buildVS 'Release' -nuget $true [Pipeline] echo Running powershell command: buildVS 'Release' -nuget $true [Pipeline] powershellpowershell.exe : buildVS : Cannot process command because of one or more missing mandatory parameters: config. At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable-d4ee0605\powershellWrapper.ps1:3 char:1 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ... + ~ + CategoryInfo : NotSpecified: (buildVS : Canno...meters: config.:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError At C:\jenkins_workspace\Jenkins Playground\WebAppTest - Deploy from Git branch@tmp\durable-d4ee0605\powershellScript.ps1:3 char:5 + buildVS 'Release' -nuget $true + ~~~ + CategoryInfo : InvalidArgument: ( [buildVS], ParameterBindingException + FullyQualifiedErrorId : MissingMandatoryParameter,buildVS
[JIRA] (JENKINS-59505) Minor typo fix to the pluginSetupWizard.properties file
Title: Message Title Mike Ajala updated JENKINS-59505 Jenkins / JENKINS-59505 Minor typo fix to the pluginSetupWizard.properties file Change By: Mike Ajala Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202127.1569317932000.5632.1569454380373%40Atlassian.JIRA.
[JIRA] (JENKINS-39374) Add ability to get SCM authentication tokens from Vault
Title: Message Title Nick Sanborn commented on JENKINS-39374 Re: Add ability to get SCM authentication tokens from Vault We wouldn't be able to put effort towards this for at least a month but if you pushed up your branch with whatever you have that would be helpful for estimation. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175898.1477892147000.5626.1569451080330%40Atlassian.JIRA.
[JIRA] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
matt matthews edited a comment on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Suggesting to just use shared/trusted libraries is not enough IMHO, we need a switch to turn this stuff off. as an example, today I have a basic Jenkinsfile that's throwing errors with [].tail(): Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods tail java.lang.Object[]. Job console offers a link to go to the ScriptApproval URL to approve, but then it does not remember the approval.. I return to the job generating the error and then it happens again in exactly the same way, telling me to approve. There's nothing further I can even do here to debug that problem (which is just another distraction from the work I really want to do), so I get forced into rewrite `[].tail()` as different-but-equivalent groovy, something with `[].findAll{}`, which just works. So why is Jenkins not remembering the approvals? Why is `findAll` safer than `tail`? Why does this plugin exist in the ecosystem if it doesn't work and can't work? [https://wiki.jenkins.io/display/JENKINS/Permissive+Script+Security+Plugin] Like other users, our Jenkins is behind a VPN, and we have multiple Jenkins instances so that we don't have to deal with all the complexity of highly granular user/job/credential permissioning. Since all people who can login to a given instance are admins on that instance.. our experience is that none of script-security stuff adds security, it just degrades our stability. Please, can we just get a config option to just turn this off everywhere?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Albert Jankowski commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Tomasz Kurcz how were you able to modify the payload coming from JIRA? I didn't think we can control that. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201336.1566200967000.5518.1569448140190%40Atlassian.JIRA.
[JIRA] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
matt matthews edited a comment on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Suggestign Suggesting to just use shared/trusted libraries is not enough IMHO, we need a switch to turn this stuff off. as an example, today I have a basic Jenkinsfile that's throwing errors with [].tail():Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods tail java.lang.Object[]. Job console offers a link to go to the ScriptApproval URL to approve, but then it does not remember the approval.. I return to the job generating the error and then it happens again in exactly the same way, telling me to approve. There's nothing further I can even do here to debug that problem (which is just another distraction from the work I really want to do), so I get forced into rewrite `[].tail()` as different-but-equivalent groovy, something with `[].findAll{}`, which just works. So why is Jenkins not remembering the approvals? Why is `findAll` safer than `tail`? Why does this plugin exist in the ecosystem if it doesn't work and can't work? [https://wiki.jenkins.io/display/JENKINS/Permissive+Script+Security+Plugin]Like other users, our Jenkins is behind a VPN, and we have multiple Jenkins instances so that we don't have to deal with all the complexity of highly granular user/job/credential permissioning. Since all people who can login to a given instance are admins on that instance.. our experience is that none of script-security stuff adds security, it just degrades our stability.Please, can we just get a config option to just turn this off everywhere?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title
matt matthews commented on JENKINS-28178
Re: Option to disable sandbox in CpsScmFlowDefinition
Suggestign to just use shared/trusted libraries is not enough IMHO, we need a switch to turn this stuff off. as an example, today I have a basic Jenkinsfile that's throwing errors with [].tail(): Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods tail java.lang.Object[]. Job console offers a link to go to the ScriptApproval URL to approve, but then it does not remember the approval.. I return to the job generating the error and then it happens again in exactly the same way, telling me to approve. There's nothing further I can even do here to debug that problem (which is just another distraction from the work I really want to do), so I get forced into rewrite `[].tail()` as different-but-equivalent groovy, something with `[].findAll{}`, which just works. So why is Jenkins not remembering the approvals? Why is `findAll` safer than `tail`? Why does this plugin exist in the ecosystem if it doesn't work and can't work? https://wiki.jenkins.io/display/JENKINS/Permissive+Script+Security+Plugin Like other users, our Jenkins is behind a VPN, and we have multiple Jenkins instances so that we don't have to deal with all the complexity of highly granular user/job/credential permissioning. Since all people who can login to a given instance are admins on that instance.. our experience is that none of script-security stuff adds security, it just degrades our stability. Please, can we just get a config option to just turn this off everywhere?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58054) Support release notes
Title: Message Title Mez Pahlan commented on JENKINS-58054 Re: Support release notes Not at this time, no. With JENKINS-59462 I am looking to support uploading a file containing release notes for a similar use case but I'm not planning to support getting the changelog from Jenkins just yet. Perhaps in the future. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200075.1560793667000.5317.1569447780160%40Atlassian.JIRA.
[JIRA] (JENKINS-58054) Support release notes
Title: Message Title Nithin Reddy commented on JENKINS-58054 Re: Support release notes HockeyApp had an option something like this. Guess it is not being implemented for this plugin if I am not wrong. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200075.1560793667000.5315.1569445920123%40Atlassian.JIRA.
[JIRA] (JENKINS-58054) Support release notes
Title: Message Title Nithin Reddy updated an issue Jenkins / JENKINS-58054 Support release notes Change By: Nithin Reddy Attachment: Screen Shot 2019-09-25 at 2.09.50 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200075.1560793667000.5313.1569445860145%40Atlassian.JIRA.
[JIRA] (JENKINS-58054) Support release notes
Title: Message Title Mez Pahlan commented on JENKINS-58054 Re: Support release notes Nithin Reddy The syntax is described in the pipeline syntax generator. There is a new field introduced in 0.6.0 called releaseNotes that is a free text field. AppCenter interprets this as Markdown. So something like this would work: appCenter apiToken: APPCENTER_API_TOKEN, ownerName: 'owner', appName: 'app-name', pathToApp: 'path/to/app.apk', distributionGroups: 'distribution', releaseNotes: 'Describe what has changed' Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200075.1560793667000.5304.1569444000199%40Atlassian.JIRA.
[JIRA] (JENKINS-59466) Nested Views are incompatible with Config as Code
Title: Message Title Alex Taylor commented on JENKINS-59466 Re: Nested Views are incompatible with Config as Code So I created this PR which does fix the error but I am not confident that this is the best fix since it would set the owner of all your nested views to the SYSTEM user or Jenkins user. That may be bad practice and make things break... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202064.1569007172000.5295.1569443400185%40Atlassian.JIRA.
[JIRA] (JENKINS-58054) Support release notes
Title: Message Title Nithin Reddy commented on JENKINS-58054 Re: Support release notes Mez Pahlan is there a way to append ChangeLog to the release notes? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200075.1560793667000.5293.1569443280189%40Atlassian.JIRA.
[JIRA] (JENKINS-58296) Projects are triggered twice when using File Parameter and Firefox 67
Title: Message Title Alejandro Jurado Walls updated an issue Jenkins / JENKINS-58296 Projects are triggered twice when using File Parameter and Firefox 67 Change By: Alejandro Jurado Walls Labels: firefox Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200361.1562053852000.5283.1569439980342%40Atlassian.JIRA.
[JIRA] (JENKINS-58296) Projects are triggered twice when using File Parameter and Firefox 67
Title: Message Title Alejandro Jurado Walls updated an issue Jenkins / JENKINS-58296 Projects are triggered twice when using File Parameter and Firefox 67 Change By: Alejandro Jurado Walls Environment: Jenkins 2.176.1, Paramized Parameterized Trigger Plugin 2.35.2, Firefox 67.0.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200361.1562053852000.5273.1569439860464%40Atlassian.JIRA.
[JIRA] (JENKINS-58296) Projects are triggered twice when using File Parameter and Firefox 67
Title: Message Title Alejandro Jurado Walls updated an issue Jenkins / JENKINS-58296 Projects are triggered twice when using File Parameter and Firefox 67 Change By: Alejandro Jurado Walls Component/s: parameterized-trigger-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200361.1562053852000.5263.1569439800427%40Atlassian.JIRA.
[JIRA] (JENKINS-56573) pipeline scripts to git clone a LFS project from github
Title: Message Title Mark Waite updated JENKINS-56573 Jenkins / JENKINS-56573 pipeline scripts to git clone a LFS project from github Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198188.1552624779000.5261.1569438420296%40Atlassian.JIRA.
[JIRA] (JENKINS-56573) pipeline scripts to git clone a LFS project from github
Title: Message Title Mark Waite updated JENKINS-56573 If the command line git version you are using does not support git large files (git LFS), then the git plugin and the Jenkins pipeline cannot make it support them. Upgrade to a more recent version of command line git. If you didn't need LFS support, you could also enable JGit on your Jenkins installation and use JGit. However, the git client plugin JGit implementation does not support git LFS. Jenkins / JENKINS-56573 pipeline scripts to git clone a LFS project from github Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-57710) Git checkout fails when using "Git LFS pull after checkout"
Title: Message Title Mark Waite updated JENKINS-57710 Please don't use bug reports as a way to ask for help. In this case, the bug report was assigned to the wrong plugin, so was not seen until now. It should have been assigned to the git plugin and the question and related discussion should be in the Jenkins users mailing list or in one of the chat channels. Jenkins / JENKINS-57710 Git checkout fails when using "Git LFS pull after checkout" Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-57710) Git checkout fails when using "Git LFS pull after checkout"
Title: Message Title Mark Waite updated JENKINS-57710 Jenkins / JENKINS-57710 Git checkout fails when using "Git LFS pull after checkout" Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199651.1559040483000.5257.1569438180438%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-41891 Serve static files from second domain as an alternative to setting CSP Change By: Daniel Beck Assignee: Matt Sicker Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178741.1486645144000.5246.1569437280282%40Atlassian.JIRA.
[JIRA] (JENKINS-59528) Support Ant style file paths
Title: Message Title Mez Pahlan started work on JENKINS-59528 Change By: Mez Pahlan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202157.1569433535000.5243.1569436140068%40Atlassian.JIRA.
[JIRA] (JENKINS-59438) Log output is misleading
Title: Message Title Mez Pahlan updated JENKINS-59438 Jenkins / JENKINS-59438 Log output is misleading Change By: Mez Pahlan Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202022.1568835926000.5242.1569436080105%40Atlassian.JIRA.
[JIRA] (JENKINS-59438) Log output is misleading
Title: Message Title Mez Pahlan updated JENKINS-59438 Jenkins / JENKINS-59438 Log output is misleading Change By: Mez Pahlan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202022.1568835926000.5237.1569434400294%40Atlassian.JIRA.
[JIRA] (JENKINS-59527) Trim white space from pipeline library name and version field
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59527 Trim white space from pipeline library name and version field Change By: Mark Waite Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202156.1569432268000.5236.1569433980165%40Atlassian.JIRA.
[JIRA] (JENKINS-43820) Stage name must be a string literal
Title: Message Title Larry West commented on JENKINS-43820 Re: Stage name must be a string literal Andrew Bayer - a "design decision" that neither satisfies the customer nor addresses some inherent constraint is indistinguishable from a design flaw. Please have someone else in your organization – who is not invested in this "design decision" – re-evaluate this. Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181338.1493122184000.5209.1569433740488%40Atlassian.JIRA.
[JIRA] (JENKINS-59528) Support Ant style file paths
Title: Message Title Mez Pahlan created an issue Jenkins / JENKINS-59528 Support Ant style file paths Issue Type: Improvement Assignee: Mez Pahlan Components: appcenter-plugin Created: 2019-09-25 17:45 Priority: Minor Reporter: Mez Pahlan We need the ability to pass in an Ant style syntax for path parameters. For example: path/to/*.apk Acceptance Criteria: All parameters that accept file paths also support Ant style glob syntax Add Comment
[JIRA] (JENKINS-59527) Trim white space from pipeline library name and version field
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-59527 Trim white space from pipeline library name and version field Issue Type: Improvement Assignee: Darin Pope Components: workflow-cps-global-lib-plugin Created: 2019-09-25 17:24 Priority: Minor Reporter: Mark Waite When an administrator enters the name and version of a pipeline shared library, leading and trailing white space seems to be preserved. That confuses them because they don't see the white space in the field Add Comment
[JIRA] (JENKINS-52219) Deploy Plugin Fails to deploy an ear file properly in WebSphere
Title: Message Title Morsi Tlili commented on JENKINS-52219 Re: Deploy Plugin Fails to deploy an ear file properly in WebSphere Hi, I'm still facing the same issue. Any fix please? Regards, Morsi Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191983.1530131714000.5199.1569432120088%40Atlassian.JIRA.
[JIRA] (JENKINS-52219) Deploy Plugin Fails to deploy an ear file properly in WebSphere
Title: Message Title Morsi Tlili assigned an issue to Greg horvath Jenkins / JENKINS-52219 Deploy Plugin Fails to deploy an ear file properly in WebSphere Change By: Morsi Tlili Assignee: Greg horvath Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191983.1530131714000.5194.1569432060189%40Atlassian.JIRA.
[JIRA] (JENKINS-52219) Deploy Plugin Fails to deploy an ear file properly in WebSphere
Title: Message Title Morsi Tlili assigned an issue to Siraj Sayeed Jenkins / JENKINS-52219 Deploy Plugin Fails to deploy an ear file properly in WebSphere Change By: Morsi Tlili Assignee: Greg horvath Siraj Sayeed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191983.1530131714000.5197.1569432060344%40Atlassian.JIRA.
[JIRA] (JENKINS-52219) Deploy Plugin Fails to deploy an ear file properly in WebSphere
Title: Message Title Morsi Tlili updated an issue Jenkins / JENKINS-52219 Deploy Plugin Fails to deploy an ear file properly in WebSphere Change By: Morsi Tlili Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191983.1530131714000.5191.1569431700308%40Atlassian.JIRA.
[JIRA] (JENKINS-59403) agent fails immediately when started in a docker-compose cluster
Title: Message Title Jeff Thompson commented on JENKINS-59403 Re: agent fails immediately when started in a docker-compose cluster We've had a couple of attempts to augment or change the startup process lately, some which were eventually successful and some which failed. The key to success has been a clearly defined use case and flow. If we can figure that out for this scenario, this could be a nice enhancement. I'm always a little concerned about approaches that just wait for some arbitrary amount of time, which may work but not always. Though, if the alternative is to just wait forever, a timeout may not be a bad idea. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201960.156870580.5189.1569430860118%40Atlassian.JIRA.
[JIRA] (JENKINS-54163) Email-Ext 2.63: brokenBuildSuspects recipient provider is not working for pipeline builds
Title: Message Title Amit Dar commented on JENKINS-54163 Re: Email-Ext 2.63: brokenBuildSuspects recipient provider is not working for pipeline builds Is this fix going to be released soon? this problem is killing us and we are trying to avoid a downgrade of the server... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194792.1539944186000.5181.1569429840194%40Atlassian.JIRA.
[JIRA] (JENKINS-58724) Add a log to know wich Run is executed on a pod
Title: Message Title Mathieu Delrocq updated JENKINS-58724 Jenkins / JENKINS-58724 Add a log to know wich Run is executed on a pod Change By: Mathieu Delrocq Status: Fixed but Unreleased Resolved Released As: 1.18.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201017.1564478302000.5175.1569427920196%40Atlassian.JIRA.
[JIRA] (JENKINS-58207) 2.181 JNA update breaks NegotiateSSO
Title: Message Title Tim Postler commented on JENKINS-58207 Re: 2.181 JNA update breaks NegotiateSSO I ran into the same problem today while upgrading from LTS 2.176.3 to 190.1 (automatic upgrade), and I guess others will follow. Fortunately 2.176.4 does still work. Any news when this will be fixed? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200266.1561541748000.5166.1569427740934%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Karl Wirth commented on JENKINS-54472 Re: Pin build at Perforce Label does not support variable expansion Correct label behavior is not described. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195237.154144342.5159.1569424380136%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Karl Wirth commented on JENKINS-54472 Re: Pin build at Perforce Label does not support variable expansion Hi John Rocha - Have you tried this on P4-Plugin 10.1.3? For us the label expansion works. For example my variable is defined as 'SV_P4_CHANGELOG' in the job and I set the parameter to 'karl_label' when I manually ran the build: Started by user unknown or anonymous Running as SYSTEM [EnvInject] - Loading node environment variables. Building on master in workspace /var/lib/jenkins/workspace/JENKINS-54472-PinBuildFreestyle ... p4 client -o jenkins-master-JENKINS-54472-PinBuildFreestyle-7 +... p4 info +... p4 info +... p4 client -o jenkins-master-JENKINS-54472-PinBuildFreestyle-7 +... p4 counter change +... p4 changes -m1 -ssubmitted //jenkins-master-JENKINS-54472-PinBuildFreestyle-7/... +... p4 label -o karl_label +... p4 label -o karl_label This also was the behavior we saw with pipeline. However it is important to note that P4-Plugin can only sync to automatic labels. This is due to a limitation in Jenkins. This does not seem to be documented so I have created JENKINS-59526. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-59526) Clearly document automatic vs static label usage
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-59526 Clearly document automatic vs static label usage Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-09-25 15:08 Environment: 1.10.13 Labels: P4_VERIFY Priority: Critical Reporter: Karl Wirth It is not document that P4-Jenkins will not work with static labels. If this is correct it should be included in the 'pin' tooltip and documentation: https://www.perforce.com/manuals/jenkins/Content/P4Jenkins/Home-p4jenkins.html Add Comment
[JIRA] (JENKINS-59525) SVN update Failure;unable to create file in Jenkins(Docker)
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-59525 Re: SVN update Failure;unable to create file in Jenkins(Docker) I'd suggest you to cleanup the workspace before or after the build Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202151.156941586.5140.1569423900224%40Atlassian.JIRA.
[JIRA] (JENKINS-59525) SVN update Failure;unable to create file in Jenkins(Docker)
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-59525 SVN update Failure;unable to create file in Jenkins(Docker) Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202151.156941586.5138.1569423840346%40Atlassian.JIRA.
[JIRA] (JENKINS-54163) Email-Ext 2.63: brokenBuildSuspects recipient provider is not working for pipeline builds
Title: Message Title Amit Dar assigned an issue to Alex Earl Jenkins / JENKINS-54163 Email-Ext 2.63: brokenBuildSuspects recipient provider is not working for pipeline builds Change By: Amit Dar Assignee: Amit Dar Alex Earl Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194792.1539944186000.5020.1569417960299%40Atlassian.JIRA.
[JIRA] (JENKINS-55998) recordIssues cannot see /workspace within docker.image.inside
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55998 recordIssues cannot see /workspace within docker.image.inside Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/219 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197415.1549479959000.5007.1569417000223%40Atlassian.JIRA.
[JIRA] (JENKINS-48802) Possibility to add/change the path that used to display source files
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-48802 Possibility to add/change the path that used to display source files Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/219 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187580.1515085477000.5005.1569416940522%40Atlassian.JIRA.
[JIRA] (JENKINS-57312) Provide tokens for new and fixed warnings
Title: Message Title Ulli Hafner updated JENKINS-57312 Jenkins / JENKINS-57312 Provide tokens for new and fixed warnings Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199081.1556811582000.4994.1569416220450%40Atlassian.JIRA.
[JIRA] (JENKINS-59525) SVN update Failure;unable to create file in Jenkins(Docker)
Title: Message Title
Sriram Arvind created an issue
Jenkins / JENKINS-59525
SVN update Failure;unable to create file in Jenkins(Docker)
Issue Type:
Bug
Assignee:
Ivan Fernandez Calvo
Components:
subversion-plugin
Created:
2019-09-25 12:51
Environment:
Jenkins:2.195(DOCKER) Subversion:1.8 Subversion Plugin:2.12.1
Priority:
Major
Reporter:
Sriram Arvind
Hi, i am running Jenkins Pipeline with SCM using SVN.It is a Maven based CI and CD. The pipeline project ran successfully at first time,but it is failing after the first success. my stack trace: it is not able to create a particular file {{}}
org.tmatesoft.svn.core.SVNException: svn: E204899: Cannot create new file '/var/jenkins_home/workspace/pipeline-testing-1/console/wc-content-notification/target/.svn/lock' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:70) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:760) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:340) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:910) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:363) at
[JIRA] (JENKINS-59522) Takes long time to deploy custom extentions only for windows 10 custome managed image
Title: Message Title
Muhammad Faizan ul haq commented on JENKINS-59522
Re: Takes long time to deploy custom extentions only for windows 10 custome managed image
I created a fresh image using packer, using the following code: { "builders": [{ "type": "azure-arm", "client_id": "", "client_secret": "", "tenant_id": "", "subscription_id": "", "managed_image_resource_group_name": "", "managed_image_name": "", "os_type": "Windows", "image_publisher": "MicrosoftWindowsDesktop", "image_offer": "Windows-10", "image_sku": "RS5-PRO", "communicator": "winrm", "winrm_use_ssl": true, "winrm_insecure": true, "winrm_timeout": "5m", "winrm_username": "packer", "azure_tags": { "dept": "", "task": "" } , "location": "North Europe", "vm_size": "Standard_DS2_v2" }], "provisioners": [ { "type": "powershell", "inline": [ "Set-Service RdAgent -StartupType Disabled", "Set-Service WindowsAzureTelemetryService -StartupType Disabled", "Set-Service WindowsAzureGuestAgent -StartupType Disabled", "remove-itemproperty -Path 'HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Setup\\SysPrepExternal\\Generalize' -Name '*'", "if( Test-Path $Env:SystemRoot\\windows\\system32\\Sysprep\\unattend.xml )\{ rm $Env:SystemRoot\\windows\\system32\\Sysprep\\unattend.xml -Force} ", "& $env:SystemRoot\\System32\\SysprepSysprep.exe /oobe /generalize /quiet /quit", "while($true) { $imageState = Get-ItemProperty HKLM:\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\SetupState | Select ImageState; if($imageState.ImageState -ne 'IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE') { Write-Output $imageState.ImageState; Start-Sleep -s 10 } else { break } }" ] }] } ~ and it took 9 minutes for deployment. Kindly suggest if we are doing something wrong. this is only for windows-10 Desktop
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59524) sendBuildInfo should also be able to send buildName/buildDescription to JIRA
Title: Message Title Martin Pruefer created an issue Jenkins / JENKINS-59524 sendBuildInfo should also be able to send buildName/buildDescription to JIRA Issue Type: New Feature Assignee: Rafal Myslek Components: atlassian-jira-software-cloud-plugin Created: 2019-09-25 12:05 Priority: Minor Reporter: Martin Pruefer I would like to see in a Jira issue, which version of the built project contains the resolution. Therefore I would like to store Jenkins' buildName (or perhaps some more interesting Jenkins data) in the according Jira issue. Since the Jira Software Cloud plugin already performs similar tasks for deployment information, it would be a good place for that build information, too. Add Comment
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Markus Winter edited a comment on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat The plugin has a dependecy tocom.atlassianant-filesystem-taskswhich has a dependency to a very old jna and org.jruby.ext.posix.jna-posixI guess the LocalCopy class needs to be reimplemented without the Atlassian stuff to be able to fix it. Or shade the dependency to jna as proposed in JENKINS-58207Staying on old jna in Jenkins core is causing issues when trying to connect AIX machines with certain JDKs (see JENKINS-57515) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.4967.1569409920425%40Atlassian.JIRA.
[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat
Title: Message Title Markus Winter commented on JENKINS-58211 Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat The plugin has a dependecy to com.atlassian ant-filesystem-tasks which has a dependency to a very old jna and org.jruby.ext.posix.jna-posix I guess the LocalCopy class needs to be reimplemented without the Atlassian stuff to be able to fix it. Staying on old jna in Jenkins core is causing issues when trying to connect AIX machines with certain JDKs (see JENKINS-57515) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200271.1561558166000.4957.1569409680285%40Atlassian.JIRA.
[JIRA] (JENKINS-59523) NPE while reading valid Xcode project with v. 2.0.12
Title: Message Title Alexander Pogulyaka created an issue Jenkins / JENKINS-59523 NPE while reading valid Xcode project with v. 2.0.12 Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 2019-09-25 10:40 Priority: Blocker Reporter: Alexander Pogulyaka This problem appeared after updating Mac OS X to 10.14.6 and appears only for Xcode 10.3 (with Xcode 11 works fine). After downgrading Xcode plugin to 2.0.8 works fine. Stackowerflow issue: https://stackoverflow.com/questions/58061101/exception-when-building-project-with-jenkins-xcode-plugin/58078516#58078516 13:11:44 Also setting CFBundleVersion key (assuming it exists)13:11:44 13:11:44 Updating CFBundleVersion in Info.plist(s)...13:11:44 13:11:44 Updated CFBundleVersion in "OTP.xcodeproj/../iFOBS-Info.plist" to 1.3.17.190*13:11:44* 13:11:44 13:11:44 Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 1.3.17*13:11:44* Technical version (CFBundleVersion) used by Jenkins to produce the IPA: 1.3.17.190*13:11:44* Read signing information from Xcode Project.13:11:44 Read information from workspace OTP*13:11:44* ERROR: Build step failed with exception*13:11:44* java.lang.NullPointerException*13:11:44* at au.com.rayh.XCodeBuilder._perform(XCodeBuilder.java:1289)13:11:44 at au.com.rayh.XCodeBuilder.perform(XCodeBuilder.java:1085)13:11:44 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)13:11:44 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)13:11:44 at hudson.model.Build$BuildExecution.build(Build.java:206)13:11:44 at hudson.model.Build$BuildExecution.doRun(Build.java:163)13:11:44 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)13:11:44 at hudson.model.Run.execute(Run.java:1835)13:11:44 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)13:11:44 at hudson.model.ResourceController.execute(ResourceController.java:97)13:11:44 at hudson.model.Executor.run(Executor.java:429)13:11:44 Build
[JIRA] (JENKINS-59512) I am getting Connection timed out while testing HP ALM connection throu Jenkins
Title: Message Title Maria Narcisa Galan updated an issue Jenkins / JENKINS-59512 I am getting Connection timed out while testing HP ALM connection throu Jenkins Change By: Maria Narcisa Galan Summary: I am getting timedout error Connection timed out while testing HP ALM connection throu Jenkins Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202135.1569336332000.4953.1569407640205%40Atlassian.JIRA.
[JIRA] (JENKINS-59512) I am getting timedout error while testing HP ALM connection throu Jenkins
Title: Message Title Maria Narcisa Galan updated an issue Jenkins / JENKINS-59512 I am getting timedout error while testing HP ALM connection throu Jenkins Change By: Maria Narcisa Galan Labels: ALM Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202135.1569336332000.4950.1569407580268%40Atlassian.JIRA.
[JIRA] (JENKINS-59512) I am getting timedout error while testing HP ALM connection throu Jenkins
Title: Message Title Maria Narcisa Galan assigned an issue to Roy Lu Jenkins / JENKINS-59512 I am getting timedout error while testing HP ALM connection throu Jenkins Change By: Maria Narcisa Galan Assignee: Maria Narcisa Galan Roy Lu Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202135.1569336332000.4947.1569407220198%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Richard Bywater resolved as Fixed 1.20 is released which should be available in the next few hours. This puts the logic back to 1.18 style handling. Jenkins / JENKINS-59511 Error opening report with HTML Publisher Change By: Richard Bywater Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/htmlpublisher-plugin/releases/tag/htmlpublisher-1.20 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-7139) HtmlPublisher should be able to handle wildcard paths to find multiple html files
Title: Message Title Richard Bywater commented on JENKINS-7139 Re: HtmlPublisher should be able to handle wildcard paths to find multiple html files Unfortunately once again this change has had to be backed out as it breaks people who don't run the jobs on the Jenkins master. It will be reintroduced soon hopefully once the code is tweaked to pick up the file from the right place so please hang tight Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137236.1280999333000.4913.1569405903101%40Atlassian.JIRA.
[JIRA] (JENKINS-7139) HtmlPublisher should be able to handle wildcard paths to find multiple html files
Title: Message Title Richard Bywater reopened an issue Jenkins / JENKINS-7139 HtmlPublisher should be able to handle wildcard paths to find multiple html files Change By: Richard Bywater Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137236.1280999333000.4915.1569405903151%40Atlassian.JIRA.
[JIRA] (JENKINS-59512) I am getting timedout error while testing HP ALM connection throu Jenkins
Title: Message Title Maria Narcisa Galan updated an issue Jenkins / JENKINS-59512 I am getting timedout error while testing HP ALM connection throu Jenkins Change By: Maria Narcisa Galan Environment: I am getting while testing HP ALM connectivity with Jenkins while configaration. Please let me know what could be the reason?url: http://alm-da.***.***.com/qcbin/java.net.ConnectException: Connection timed out (Connection timed out) at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.net.NetworkClient.doConnect(NetworkClient.java:175) at sun.net.www.http.HttpClient.openServer(HttpClient.java:463) at sun.net.www.http.HttpClient.openServer(HttpClient.java:558) at sun.net.www.http.HttpClient.(HttpClient.java:242) at sun.net.www.http.HttpClient.New(HttpClient.java:339) at sun.net.www.http.HttpClient.New(HttpClient.java:357) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220) at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at org.glassfish.jersey.client.HttpUrlConnector._apply(HttpUrlConnector.java:321) at org.glassfish.jersey.client.HttpUrlConnector.apply(HttpUrlConnector.java:227)Caused: javax.ws.rs.ProcessingException Add Comment
[JIRA] (JENKINS-59512) I am getting timedout error while testing HP ALM connection throu Jenkins
Title: Message Title Maria Narcisa Galan updated an issue Jenkins / JENKINS-59512 I am getting timedout error while testing HP ALM connection throu Jenkins Change By: Maria Narcisa Galan I am getting while testing HP ALM connectivity with Jenkins while configaration. Please let me know what could be the reason?url: [http://alm-da.***.***.com/qcbin/|http://alm-da.%2A%2A%2A.%2A%2A%2A%2A%2A%2A%2A.com/qcbin/]java.net.ConnectException: Connection timed out (Connection timed out)at java.net.PlainSocketImpl.socketConnect(Native Method)at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)at java.net.Socket.connect(Socket.java:589)at sun.net.NetworkClient.doConnect(NetworkClient.java:175)at sun.net.[www.http.HttpClient.openServer(HttpClient.java:463)|http://www.http.httpclient.openserver%28httpclient.java:463)/]at sun.net.[www.http.HttpClient.openServer(HttpClient.java:558)|http://www.http.httpclient.openserver%28httpclient.java:558)/]at sun.net.[www.http.HttpClient.init(HttpClient.java:242)|http://www.http.httpclient.%3Cinit%3E%28httpclient.java:242)/]at sun.net.[www.http.HttpClient.New(HttpClient.java:339)|http://www.http.httpclient.new%28httpclient.java:339)/]at sun.net.[www.http.HttpClient.New(HttpClient.java:357)|http://www.http.httpclient.new%28httpclient.java:357)/]at sun.net.[www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1220)|http://www.protocol.http.httpurlconnection.getnewhttpclient%28httpurlconnection.java:1220)/]at sun.net.[www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156)|http://www.protocol.http.httpurlconnection.plainconnect0%28httpurlconnection.java:1156)/]at sun.net.[www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050)|http://www.protocol.http.httpurlconnection.plainconnect%28httpurlconnection.java:1050)/]at sun.net.[www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:984)|http://www.protocol.http.httpurlconnection.connect%28httpurlconnection.java:984)/]at sun.net.[www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)|http://www.protocol.http.httpurlconnection.getinputstream0%28httpurlconnection.java:1564)/]at sun.net.[www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)|http://www.protocol.http.httpurlconnection.getinputstream%28httpurlconnection.java:1492)/]at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)at org.glassfish.jersey.client.HttpUrlConnector._apply(HttpUrlConnector.java:321)at org.glassfish.jersey.client.HttpUrlConnector.apply(HttpUrlConnector.java:227)Caused: javax.ws.rs.ProcessingException
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title
Georgi Georgiev updated an issue
Jenkins / JENKINS-59511
Error opening report with HTML Publisher
Change By:
Georgi Georgiev
Comment:
My input dir(reportDir) structure:{code:java}attachments/bullet_point.pngcollapseall.gifemailable-report.htmlfailed.pngfiles/index.htmljquery-1.7.1.min.jsjunitreports/Maven/navigator-bullet.pngold/passed.pngreport-0.htmlscreenshots/skipped.pngtestng.csstestng-failed.xmltestng-reports.csstestng-reports.jstestng-results.xmlTestSuite.txtTEST-TestSuite.xml{code}Log:{code:java}[htmlpublisher] Archiving at BUILD level /opt/jenkins/workspace/Mask/Mask1/Mask2@3/791/Mask3/Mask4/test-output to /opt/jenkins/jobs/Mask/jobs/Mask1/jobs/Mask2/builds/791/htmlreports/MyReport {code}Please note that for the log, I have replaced real directories names with tokens("Mask", "Mask1"...), but values are still 1:1 matching in the source and target dir paths(example "Mask1" value in source dir is the same as "Mask1" value in target)
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58826) "Aggregated Analysis Results" does not get updated after a few dozen builds
Title: Message Title Marc Würth commented on JENKINS-58826 Re: "Aggregated Analysis Results" does not get updated after a few dozen builds Yes, it is still a problem. The diagram hasn't changed, even though we use 6.0.4 now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201139.1565095677000.4875.1569405120296%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Richard Bywater commented on JENKINS-59511 Re: Error opening report with HTML Publisher Thanks that reconciles my theory. Taking another look at the code it will only work currently if the job is run on the same machine as the Jenkins master. As its going to take a little while to solve that, I'm reverting the change and will be pushing out 1.20 soon which will revert the functionality back to the way 1.18 is working. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4870.1569405060222%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title
Georgi Georgiev commented on JENKINS-59511
Re: Error opening report with HTML Publisher
My input dir(reportDir) structure:
attachments/
bullet_point.png
collapseall.gif
emailable-report.html
failed.png
files/
index.html
jquery-1.7.1.min.js
junitreports/
Maven/
navigator-bullet.png
old/
passed.png
report-0.html
screenshots/
skipped.png
testng.css
testng-failed.xml
testng-reports.css
testng-reports.js
testng-results.xml
TestSuite.txt
TEST-TestSuite.xml
Log:
[htmlpublisher] Archiving at BUILD level /opt/jenkins/workspace/Mask/Mask1/Mask2@3/791/Mask3/Mask4/test-output to /opt/jenkins/jobs/Mask/jobs/Mask1/jobs/Mask2/builds/791/htmlreports/MyReport
Please note that for the log, I have replaced real directories names with tokens("Mask", "Mask1"...), but values are still 1:1 matching in the source and target dir paths(example "Mask1" value in source dir is the same as "Mask1" value in target)
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Thomas Gimpel commented on JENKINS-59511 Re: Error opening report with HTML Publisher Also here: publishHTML was called on a node other than master. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4867.1569404940166%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-54472 Pin build at Perforce Label does not support variable expansion Change By: Karl Wirth Labels: P4_B P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195237.154144342.4856.1569404700316%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Henry Wilson commented on JENKINS-59511 Re: Error opening report with HTML Publisher My log output looks exactly the same as that from Thomas above. I've also compared between a build on 1.19 and one on 1.18, log output is identical. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4860.1569404700393%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Henry Wilson commented on JENKINS-59511 Re: Error opening report with HTML Publisher Richard Bywater yes our agents are separate from Master Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4862.1569404700418%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Richard Bywater edited a comment on JENKINS-59511 Re: Error opening report with HTML Publisher Ok I think I might have found where the issue lies - are all your you three running pipelines on an agent or similar that *isn't* the Jenkins master? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4850.1569404641258%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Richard Bywater commented on JENKINS-59511 Re: Error opening report with HTML Publisher Ok I think I might have found where the issue lies - are all your three running pipelines on an agent or similar that isn't the Jenkins master? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4846.1569404640649%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-54472 Pin build at Perforce Label does not support variable expansion Change By: Karl Wirth Assignee: Charusheela Bopardikar Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195237.154144342.4853.1569404641821%40Atlassian.JIRA.
[JIRA] (JENKINS-59522) Takes long time to deploy custom extentions only for windows 10 custome managed image
Title: Message Title
Muhammad Faizan ul haq commented on JENKINS-59522
Re: Takes long time to deploy custom extentions only for windows 10 custome managed image
If the Custom Managed Image has "windows test mode" enabled, the deployment takes 25 minutes and then fails with an error: { "status": "Canceled", "error": { "code": "ResourceDeploymentFailure", "message": "The resource operation completed with terminal provisioning state 'Canceled'.", "details": [ { "code": "OperationPreempted", "message": "The operation has been preempted by a more recent operation." } ] } }
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202146.1569398711000.4842.1569404520126%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Thomas Gimpel commented on JENKINS-59511 Re: Error opening report with HTML Publisher [2019-09-25T04:05:46.934Z] [htmlpublisher] Archiving HTML reports... [2019-09-25T04:05:46.935Z] [htmlpublisher] Archiving at BUILD level /jenkins/workspace/Project_Project_feature_develop5.0/testresults/smoketest to /var/lib/jenkins/jobs/Project/jobs/Project/branches/feature-develop5-0.8a6oo2/builds/881/htmlreports/Smoke_20test_20result Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4839.1569404400241%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Richard Bywater commented on JENKINS-59511 Re: Error opening report with HTML Publisher Also if anyone can share the portion of the log that relates to HTML publisher that would be great (The section should start along the lines of "[htmlpublisher] Archiving at...") Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4834.1569404040211%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Henry Wilson commented on JENKINS-59511 Re: Error opening report with HTML Publisher Just downgraded to 1.18 and can confirm it's working again Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4827.1569403560167%40Atlassian.JIRA.
[JIRA] (JENKINS-36720) Investigate/cleanup medium-severity FindBugs issues in the Jenkins core
Title: Message Title Stefan Spieker commented on JENKINS-36720 Re: Investigate/cleanup medium-severity FindBugs issues in the Jenkins core There are several PRs done for this and there are more to come. This is a quite huge task. I think we would be down to 400 spotbugs issues if all PRs would be merged. So I guess this will be in progress for a longer while Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172755.1468600777000.4825.1569403500274%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Richard Bywater commented on JENKINS-59511 Re: Error opening report with HTML Publisher I've tried to reproduce locally but unfortunately as of yet haven't been able to. I'll keep on trying but in the meantime if you are having the issue are you able to produce a directory listing of your the directory in the workspace represented by reportDir (and subdirectories if applicable) just so I can get a feeling for what is present to see if there's anything different to what I'm testing. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4819.1569402960227%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Richard Bywater commented on JENKINS-59511 Re: Error opening report with HTML Publisher Henry Wilson if you go to Manage Jenkins / Manage Plugins and go to the Installed plugins tab, there hopefully is a Downgrade button there to take you back to 1.18. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4815.1569402900175%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Henry Wilson commented on JENKINS-59511 Re: Error opening report with HTML Publisher Georgi Georgiev is there an easy way to roll back to the previous version? Annoyingly the Jenkins UI only ever presents the latest version to install... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4811.1569402840179%40Atlassian.JIRA.
[JIRA] (JENKINS-24767) Role-based Authorization Strategy not working with sub-folders
Title: Message Title Raúl Salinas-Monteagudo commented on JENKINS-24767 Re: Role-based Authorization Strategy not working with sub-folders It also cost me a while to find out how to make job folders work. Documentation should be improved. It works nicely with: FOLDERNAME(/.*)? Which means: the folder name alone, and anything starting by the folder name followed a slash. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.157403.1411065421000.4807.1569402660299%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Henry Wilson commented on JENKINS-59511 Re: Error opening report with HTML Publisher Richard Bywater as per other comments I'm using pipeline configuration as below. Was definitely working with the previous version. publishHTML([ allowMissing: true, alwaysLinkToLastBuild: false, keepAll: true, reportDir: 'packages/assistant-client-core/coverage/lcov-report', reportFiles: 'index.html', reportName: 'CodeCoverage', reportTitles: '']) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4802.1569402540226%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title
Georgi Georgiev edited a comment on JENKINS-59511
Re: Error opening report with HTML Publisher
I had the same issue with 1.19. Just switched to previous version and everything works fine again.Here is my configuration for the plugin(I am using pipeline jobs):{code:java}publishHTML(target: [allowMissing : false,alwaysLinkToLastBuild: true,keepAll : true,reportDir: "test-output",reportFiles : "report-0.html, rerun-0.html",reportName : "MyReport"]) {code} Unfortunately, I have no special background info - the plugin got updated yesterday and this issue appeared immediately. Btw, I want to mention that this issue is *not* related only to pipeline scripts as I reproduced it with standard matrix job with same configuration.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202133.1569334207000.4784.1569401760180%40Atlassian.JIRA.
