[JIRA] (JENKINS-57240) Only last stage data is sent to influx db from jenkins pipeline
Title: Message Title z cloud commented on JENKINS-57240 Re: Only last stage data is sent to influx db from jenkins pipeline Aleksi Simell ，Thank you for your reply and look forward to this feature. The customDataMap and customDataMapTags support list(map) will be great. For example: stageDataMapTagsList = [] stageDataMapTags = [:] stageDataMapTagsList.add(stageDataMapTags) customDataMapTags['stage'] = stageDataMapTagsList Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199003.1556612056000.5293.1567494420157%40Atlassian.JIRA.
[JIRA] (JENKINS-58856) No Authorization Header for WinRM connection
Title: Message Title
Christoph Niehoff commented on JENKINS-58856
Re: No Authorization Header for WinRM connection
Yes, I use the Administrator as I read that domain users do not work. Using the packer the following powershell script is given to the Instances user_data:
write-output "Running User Data Script" write-host "(host) Running User Data Script"
Set-ExecutionPolicy Unrestricted -Scope LocalMachine -Force -ErrorAction Ignore
net user Administrator {{ user `administrator_password` }}
Don't set this before Set-ExecutionPolicy as it throws an error $ErrorActionPreference = "stop"
Remove HTTP listener Remove-Item -Path WSMan:\\Localhost\\listenerlistener* -Recurse
$Cert = New-SelfSignedCertificate -CertstoreLocation Cert:\\LocalMachineMy -DnsName "packer" New-Item -Path WSMan:\\LocalHostListener -Transport HTTPS -Address * -CertificateThumbPrint $Cert.Thumbprint -Force
WinRM write-output "Setting up WinRM" write-host "(host) setting up WinRM"
cmd.exe /c winrm quickconfig -q cmd.exe /c winrm set "winrm/config" '@{MaxTimeoutms="180"}' cmd.exe /c winrm set "winrm/config/winrs" '@{MaxMemoryPerShellMB="1024"}' cmd.exe /c winrm set "winrm/config/service" '@{AllowUnencrypted="true"}' cmd.exe /c winrm set "winrm/config/client" '@{AllowUnencrypted="true"}' cmd.exe /c winrm set "winrm/config/service/auth" '@{Basic="true"}' cmd.exe /c winrm set "winrm/config/client/auth" '@{Basic="true"}' cmd.exe /c winrm set "winrm/config/service/auth" '@{CredSSP="true"}' cmd.exe /c winrm set "winrm/config/listener?Address=*+Transport=HTTPS" "@{Port=`"5986`";Hostname=`"packer`";CertificateThumbprint=`"$($Cert.Thumbprint)`"}" cmd.exe /c netsh advfirewall firewall set rule group="remote administration" new enable=yes cmd.exe /c netsh firewall add portopening TCP 5986 "Port 5986" cmd.exe /c net stop winrm cmd.exe /c sc config winrm start= auto cmd.exe /c net start winrm
[JIRA] (JENKINS-58856) No Authorization Header for WinRM connection
Title: Message Title
Christoph Niehoff edited a comment on JENKINS-58856
Re: No Authorization Header for WinRM connection
Yes, I use the Administrator as I read that domain users do not work.Using the packer the following powershell script is given to the Instances user_data:{quote} write-output "Running User Data Script"write-host "(host) Running User Data Script"Set-ExecutionPolicy Unrestricted -Scope LocalMachine -Force -ErrorAction Ignorenet user Administrator \{{ user `administrator_password` }} # Don't set this before Set-ExecutionPolicy as it throws an error $ErrorActionPreference = "stop" # Remove HTTP listenerRemove -Item -Path WSMan:\\Localhost\\listener \\ listener* -Recurse$Cert = New-SelfSignedCertificate -CertstoreLocation Cert:\\LocalMachine \\ My -DnsName "packer"New-Item -Path WSMan:\\LocalHost \\ Listener -Transport HTTPS -Address * -CertificateThumbPrint $Cert.Thumbprint -Force # WinRM write-output "Setting up WinRM"write-host "(host) setting up WinRM"cmd.exe /c winrm quickconfig -qcmd.exe /c winrm set "winrm/config" '@\{MaxTimeoutms="180"}'cmd.exe /c winrm set "winrm/config/winrs" '@\{MaxMemoryPerShellMB="1024"}'cmd.exe /c winrm set "winrm/config/service" '@\{AllowUnencrypted="true"}'cmd.exe /c winrm set "winrm/config/client" '@\{AllowUnencrypted="true"}'cmd.exe /c winrm set "winrm/config/service/auth" '@\{Basic="true"}'cmd.exe /c winrm set "winrm/config/client/auth" '@\{Basic="true"}'cmd.exe /c winrm set "winrm/config/service/auth" '@\{CredSSP="true"}'cmd.exe /c winrm set "winrm/config/listener?Address=*+Transport=HTTPS" "@\{Port=`"5986`";Hostname=`"packer`";CertificateThumbprint=`"$($Cert.Thumbprint)`"}"cmd.exe /c netsh advfirewall firewall set rule group="remote administration" new enable=yescmd.exe /c netsh firewall add portopening TCP 5986 "Port 5986"cmd.exe /c net stop winrmcmd.exe /c sc config winrm start= autocmd.exe /c net start winrm{quote}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are s
[JIRA] (JENKINS-58856) No Authorization Header for WinRM connection
Title: Message Title
Christoph Niehoff edited a comment on JENKINS-58856
Re: No Authorization Header for WinRM connection
Yes, I use the Administrator as I read that domain users do not work.Using the packer the following powershell script is given to the Instances user_data:{quote} write-output "Running User Data Script" write-host "(host) Running User Data Script"Set-ExecutionPolicy Unrestricted -Scope LocalMachine -Force -ErrorAction Ignorenet user Administrator \{{ user `administrator_password` }}$ErrorActionPreference = "stop"Remove-Item -Path WSMan:\\Localhost\\listener \\ listener* -Recurse$Cert = New-SelfSignedCertificate -CertstoreLocation Cert:\\LocalMachine \\ My -DnsName "packer" New-Item -Path WSMan:\\LocalHost \\ Listener -Transport HTTPS -Address * -CertificateThumbPrint $Cert.Thumbprint -Forcewrite-output "Setting up WinRM" write-host "(host) setting up WinRM"cmd.exe /c winrm quickconfig -q cmd.exe /c winrm set "winrm/config" '@\{MaxTimeoutms="180"}' cmd.exe /c winrm set "winrm/config/winrs" '@\{MaxMemoryPerShellMB="1024"}' cmd.exe /c winrm set "winrm/config/service" '@\{AllowUnencrypted="true"}' cmd.exe /c winrm set "winrm/config/client" '@\{AllowUnencrypted="true"}' cmd.exe /c winrm set "winrm/config/service/auth" '@\{Basic="true"}' cmd.exe /c winrm set "winrm/config/client/auth" '@\{Basic="true"}' cmd.exe /c winrm set "winrm/config/service/auth" '@\{CredSSP="true"}' cmd.exe /c winrm set "winrm/config/listener?Address=*+Transport=HTTPS" "@\{Port=`"5986`";Hostname=`"packer`";CertificateThumbprint=`"$($Cert.Thumbprint)`"}" cmd.exe /c netsh advfirewall firewall set rule group="remote administration" new enable=yes cmd.exe /c netsh firewall add portopening TCP 5986 "Port 5986" cmd.exe /c net stop winrm cmd.exe /c sc config winrm start= auto cmd.exe /c net start winrm{quote}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group
[JIRA] (JENKINS-58856) No Authorization Header for WinRM connection
Title: Message Title
Christoph Niehoff edited a comment on JENKINS-58856
Re: No Authorization Header for WinRM connection
Yes, I use the Administrator as I read that domain users do not work.Using the packer the following powershell script is given to the Instances user_data:{quote} write-output "Running User Data Script" write-host "(host) Running User Data Script"Set-ExecutionPolicy Unrestricted -Scope LocalMachine -Force -ErrorAction Ignorenet user Administrator \{{ user `administrator_password` }}$ErrorActionPreference = "stop"Remove-Item -Path WSMan:\\Localhost\\listener \\ listener* -Recurse$Cert = New-SelfSignedCertificate -CertstoreLocation Cert:\\LocalMachine \\ My -DnsName "packer" New-Item -Path WSMan:\\LocalHost\\Listener -Transport HTTPS -Address * -CertificateThumbPrint $Cert.Thumbprint -Forcewrite-output "Setting up WinRM" write-host "(host) setting up WinRM"cmd.exe /c winrm quickconfig -q cmd.exe /c winrm set "winrm/config" '@\{MaxTimeoutms="180"}' cmd.exe /c winrm set "winrm/config/winrs" '@\{MaxMemoryPerShellMB="1024"}' cmd.exe /c winrm set "winrm/config/service" '@\{AllowUnencrypted="true"}' cmd.exe /c winrm set "winrm/config/client" '@\{AllowUnencrypted="true"}' cmd.exe /c winrm set "winrm/config/service/auth" '@\{Basic="true"}' cmd.exe /c winrm set "winrm/config/client/auth" '@\{Basic="true"}' cmd.exe /c winrm set "winrm/config/service/auth" '@\{CredSSP="true"}' cmd.exe /c winrm set "winrm/config/listener?Address=*+Transport=HTTPS" "@\{Port=`"5986`";Hostname=`"packer`";CertificateThumbprint=`"$($Cert.Thumbprint)`"}" cmd.exe /c netsh advfirewall firewall set rule group="remote administration" new enable=yes cmd.exe /c netsh firewall add portopening TCP 5986 "Port 5986" cmd.exe /c net stop winrm cmd.exe /c sc config winrm start= auto cmd.exe /c net start winrm{quote}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and
[JIRA] (JENKINS-52923) Error Signal Description not displayed in Blue Ocean
Title: Message Title
Melvin Won commented on JENKINS-52923
Re: Error Signal Description not displayed in Blue Ocean
It happens to me when the variable to be interpolated is larger than 104 characters. Example, when metaDataFilePath is larger than 104 characters, the entire error description is not displayed on blue ocean. error signal is still displayed.
error ("[ERROR] Metadata missing for ${bundleName} : Unable to find ${metaDataFilePath}. Please make sure the file exists.")
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192882.1533661843000.5308.1567495020347%40Atlassian.JIRA.
[JIRA] (JENKINS-59165) It reports null pointer exception when clicking test configuraiton button on email configuration
Title: Message Title Tommy Sparber commented on JENKINS-59165 Re: It reports null pointer exception when clicking test configuraiton button on email configuration This should be fixed with PR60. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201602.1567254832000.5316.1567495200158%40Atlassian.JIRA.
[JIRA] (JENKINS-59165) It reports null pointer exception when clicking test configuraiton button on email configuration
Title: Message Title Tommy Sparber edited a comment on JENKINS-59165 Re: It reports null pointer exception when clicking test configuraiton button on email configuration This should be fixed with [PR60|https://github.com/jenkinsci/mailer-plugin/pull/60]. Only the "Send Test E-Mail" feature is affected by this bug, if the server is configured correctly, the notification e-mails should be send successfully. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201602.1567254832000.5320.1567495380294%40Atlassian.JIRA.
[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Dominik Bartholdi commented on JENKINS-59192 Re: configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines As the config-file-provider did not change, this seems more an issue caused on the kubernetes site. As I never worked with kubernetes, this will definitely need to be fixed by someone who does know how k8 works. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201633.1567448335000.5326.1567495680223%40Atlassian.JIRA.
[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Dominik Bartholdi assigned an issue to Carlos Sanchez Jenkins / JENKINS-59192 configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201633.1567448335000.5330.1567495740197%40Atlassian.JIRA.
[JIRA] (JENKINS-58822) Failed to send out e-mail
Title: Message Title Tommy Sparber commented on JENKINS-58822 Re: Failed to send out e-mail If everything is configured correctly, and you are using the Mailer-Plugin version >=1.24 you a probaly affected by JENKINS-58768. The bug described there, only affects the send test email function, but task notifications should be sent successfully. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201134.1565077475000.5334.1567496040445%40Atlassian.JIRA.
[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Carlos Sanchez assigned an issue to Unassigned Jenkins / JENKINS-59192 configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines Change By: Carlos Sanchez Assignee: Dominik Bartholdi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201633.1567448335000.5349.1567496520539%40Atlassian.JIRA.
[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Carlos Sanchez assigned an issue to Dominik Bartholdi Jenkins / JENKINS-59192 configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines Change By: Carlos Sanchez Assignee: Carlos Sanchez Dominik Bartholdi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201633.1567448335000.5345.1567496520493%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title Tommy Sparber commented on JENKINS-59161 Re: ERROR: 530 Authentication required According to https://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-connect.html you need to use SSL (check Use SSL). For the "send Test E-Mail" feature there is currently a bug, but with the correct confugration task notification emails should be sent. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201598.1567204978000.5353.1567496940193%40Atlassian.JIRA.
[JIRA] (JENKINS-48791) Cannot open Job configuration
Title: Message Title Slavomir Kundrik updated JENKINS-48791 Jenkins / JENKINS-48791 Cannot open Job configuration Change By: Slavomir Kundrik Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187568.1515067009000.5357.1567497180327%40Atlassian.JIRA.
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title James Nord commented on JENKINS-44085 Re: have a simple way to limit the number of parallel branches that run concurrently take is not going to work as it will block the cps thread. I should have known that yesterday Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181710.1494001199000.5402.1567498264290%40Atlassian.JIRA.
[JIRA] (JENKINS-59200) Multiple Dependency-check links created when upgrading
Title: Message Title Kent Granström created an issue Jenkins / JENKINS-59200 Multiple Dependency-check links created when upgrading Issue Type: Bug Assignee: Unassigned Attachments: jenkins.png Components: dependency-check-jenkins-plugin Created: 2019-09-03 08:23 Environment: Jenkins 2.189, dependency-check-plugin-jenkins 5.02 Windows 2016 server, Maven 3.5.4, executing dependency-check 5.2.1 (upgraded from 4.0.2) Priority: Major Reporter: Kent Granström After upgrading dep-check I see a large number of links on the build's frontpage and they all point to the same directory but all show the same information. Add Comment
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde commented on JENKINS-59137 Re: Connectivity issues with ec2 slaves Found the culprit. From the documentation for the Amazon Linux (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-ami-basics.html#security-updates) it states: Amazon Linux is configured to download and install security updates at launch time.[...] The default setting for repo_upgrade is security. That is, if you don't specify a different value in your user data, by default, Amazon Linux performs the security upgrades at launch for any packages installed at that time Since I had pre-installed the java library, after some days/weeks there was probably an update, and the security updates kicked in messing everything up!!! So this is not something this plugin can prevent, but maybe we can have some FAQ or some "Known Issues" section? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201569.1567062958000.5405.1567499280242%40Atlassian.JIRA.
[JIRA] (JENKINS-59201) jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Title: Message Title Vassilena Treneva created an issue Jenkins / JENKINS-59201 jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed] Issue Type: Bug Assignee: Ivan Fernandez Calvo Attachments: consoleFull.txt, Jenkinsfile.txt Components: pipeline, subversion-plugin Created: 2019-09-03 08:31 Environment: Jenkins ver. 2.140 Subversion plugin 2.12.1 Other plugins: Pipeline: API Plugin that defines Pipeline API. 2.33Pipeline: Basic Steps Commonly used steps for Pipelines. 2.13Pipeline: Build Step Adds the Pipeline step build to trigger builds of other jobs. 2.7 Pipeline: Declarative An opinionated, declarative Pipeline. 1.3.3 Pipeline: Declarative Agent API Replaced by Pipeline: Declarative Extension Points API plugin. 1.1.1 Pipeline: Declarative Extension Points API APIs for extension points used in Declarative Pipelines. 1.3.3Pipeline: Groovy Pipeline execution engine based on continuation passing style transformation of Groovy scripts. 2.61Pipeline: Input Step Adds the Pipeline step input to wait for human input or approval. 2.8 Pipeline: Job Defines a new job type for pipelines and provides their generic user interface. 2.29Pipeline: Milestone Step Plugin that provides the milestone step 1.3.1 Pipeline: Model API Model API for Declarative Pipeline. 1.3.3Pipeline: Multibranch Enhances Pipeline plugin to handle branches better by automatically grouping builds from different branches. 2.20 Pipeline: Multibranch with defaults Enhances Pipeline plugin to handle branches better by automatically grouping builds from different branches. Supports enable one default pipeline 2.0 Pipeline: Nodes and Processes Pipeline steps locking agents and workspaces, and running external processes that may survive a Jenkins restart or slave reconnection. 2.26Pipeline: REST API Provides a REST API to access pipeline and pipeline run data. 2.10 Pipeline: SCM Step Adds a Pipeline step to check out or update working sources from various SCMs (version control). 2.7Pipeline: Shared Groovy Libraries Shared libraries for Pipeline scripts. 2.12 Pipeline: Stage Step Adds the Pipeline step stage to delineate portions of a build. 2.3 Pipeline: Stage Tags Metadata Library plugin for Pipeline stage tag metadata. 1.3.3Pipeline: Stage View Pipeline Stage View Plugin. 2.10 Pipeline: Step API API for a
[JIRA] (JENKINS-59201) jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-59201 jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed] Change By: Vassilena Treneva Every now and then, we get errors like the one below: Started by upstream project "10.5_release_pipeline" build number 266Started by upstream project "10.5_release_pipeline" build number 266originally caused by: Started by timerChecking out svn [http://svndae.apama.com:80/um/branches/rel/10.5.0.x//build/change-management/jenkinsfiles/sonar_cpp|http://svndae.apama.com/um/branches/rel/10.5.0.x//build/change-management/jenkinsfiles/sonar_cpp] into /FS/fslocal/jenkinsWorkspace/jobs/10.5_sonar_cpp/workspace@script to read JenkinsfileChecking out a fresh workspace because the workspace is not http://:80/um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cppCleaning local Directory .Checking out http://:80/um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cpp at revision '2019-09-03T03:36:12.694 +0200'A JenkinsfileAt revision 123796 No changes for http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cpp since the previous buildRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] properties[Pipeline] echoJenkins template functions will check out revision: @123796[Pipeline] libraryLoading library templates@branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates@123796Opening connection to http:///um/Updating http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates@123796 at revision 123796U vars/pipelineBuilder.groovyAt revision 123796 ERROR: Checkout failedorg.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled 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 org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:353) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1003) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1041) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239) at
[JIRA] (JENKINS-59201) jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Title: Message Title Vassilena Treneva updated an issue Jenkins / JENKINS-59201 jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed] Change By: Vassilena Treneva Every now and then, we get errors like the one below: Started by upstream project "10.5_release_pipeline" build number 266Started by upstream project "10.5_release_pipeline" build number 266originally caused by: Started by timerChecking out svn [ http://svndae.apama.com:80/um/branches/rel/10.5.0.x//build/change-management/jenkinsfiles/sonar_cpp |http://svndae.apama.com/um/branches/rel/10.5.0.x//build/change-management/jenkinsfiles/sonar_cpp] into /FS/fslocal/jenkinsWorkspace/jobs/10.5_sonar_cpp/workspace@script to read JenkinsfileChecking out a fresh workspace because the workspace is not http://:80/um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cppCleaning local Directory .Checking out http://:80/um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cpp at revision '2019-09-03T03:36:12.694 +0200'A JenkinsfileAt revision 123796No changes for http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cpp since the previous buildRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] properties[Pipeline] echoJenkins template functions will check out revision: @123796[Pipeline] libraryLoading library templates@branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates@123796Opening connection to http:///um/Updating http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates@123796 at revision 123796U vars/pipelineBuilder.groovyAt revision 123796ERROR: Checkout failedorg.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled 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 org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:353) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1003) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1041) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239)
[JIRA] (JENKINS-59201) jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Title: Message Title
Vassilena Treneva updated an issue
Jenkins / JENKINS-59201
jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Change By:
Vassilena Treneva
Every now and then, we get errors like the one below: {{ Started by upstream project "10.5_release_pipeline" build number 266Started by upstream project "10.5_release_pipeline" build number 266originally caused by: Started by timerChecking out svn [http://svndae.apama.com:80/um/branches/rel/10.5.0.x//build/change-management/jenkinsfiles/sonar_cpp|http://svndae.apama.com/um/branches/rel/10.5.0.x//build/change-management/jenkinsfiles/sonar_cpp] into /FS/fslocal/jenkinsWorkspace/jobs/10.5_sonar_cpp/workspace@script to read JenkinsfileChecking out a fresh workspace because the workspace is not http://:80/um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cppCleaning local Directory .Checking out http://:80/um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cpp at revision '2019-09-03T03:36:12.694 +0200'A JenkinsfileAt revision 123796 No changes for http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/sonar_cpp since the previous buildRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] properties[Pipeline] echoJenkins template functions will check out revision: @123796[Pipeline] libraryLoading library templates@branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates@123796Opening connection to http:///um/Updating http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates@123796 at revision 123796U vars/pipelineBuilder.groovyAt revision 123796 ERROR: Checkout failedERROR: Checkout failedorg.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled 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 org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:353) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1003) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1041) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnO
[JIRA] (JENKINS-59200) Multiple Dependency-check links created when upgrading
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-59200 Multiple Dependency-check links created when upgrading Change By: Kent Granström After upgrading dep-check I see a large number of links on the build's frontpage and they all point to the same directory but all show the same information. It appears to be one per module in the job. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201644.1567498992000.5415.1567499700369%40Atlassian.JIRA.
[JIRA] (JENKINS-59201) jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Title: Message Title
Vassilena Treneva updated an issue
Jenkins / JENKINS-59201
jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Change By:
Vassilena Treneva
Every now and then, we get errors like the one below:{{ ERROR: Checkout failedERROR: Checkout failedorg.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled 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 org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:353) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1003) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1041) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1239) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:190)Caused: hudson.util.IOException2: revision check failed on http:///um/branches/rel/10.5.0.x/build/change-management/jenkinsfiles/templates at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:204) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:898) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.doRetrieve(SCMSourceRetriever.java:116) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:86) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:157) at org.jenkinsci.plugins.workflow.libs.LibraryStep$Execution.run(LibraryStep.java:207) at org.jenkinsci.plugins.workflow.libs.LibraryStep$Execution.run(LibraryStep.java:156) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingS
[JIRA] (JENKINS-59200) Multiple Dependency-check links created when upgrading
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-59200 Multiple Dependency-check links created when upgrading Change By: Kent Granström After upgrading dep-check I see a large number of links on the build's frontpage and they all point to the same directory but all show the same information. It appears to be one per module in the job. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201644.1567498992000.5418.1567500060653%40Atlassian.JIRA.
[JIRA] (JENKINS-59201) jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed]
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-59201 jenkins shared libarry checkout causes [hudson.util.IOException2: revision check failed] Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201645.1567499505000.5420.1567500600154%40Atlassian.JIRA.
[JIRA] (JENKINS-44789) docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom
Title: Message Title Michael Brunner commented on JENKINS-44789 Re: docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom Hi, I have docker pipeline plugin version 1.19 running and still have the same issue. Is it really resolved? Or am I doing something wrong here. [Bitbucket] Build result notified 11:02:05 java.io.IOException: Cannot retrieve .Id from 'docker inspect nginx:stable-alpine as prod' 11:02:05 at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:220) 11:02:05 at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:118) 11:02:05 at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:88) 11:02:05 at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) 11:02:05 at hudson.security.ACL.impersonate(ACL.java:290) 11:02:05 at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) 11:02:05 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 11:02:05 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 11:02:05 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 11:02:05 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 11:02:05 at java.lang.Thread.run(Thread.java:748) 11:02:05 Finished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" grou
[JIRA] (JENKINS-59187) node-sharing-plugin: fails to use crumb correctly since Jenkins 2.176
Title: Message Title James Dingwall updated an issue Jenkins / JENKINS-59187 node-sharing-plugin: fails to use crumb correctly since Jenkins 2.176 Change By: James Dingwall In the jenkins log:WARNING: No valid crumb was included in request for /cloud/NodeSharing-/api/reportUsage by nsp-user. Returning 403.I believe this is being triggered by [ https://jenkins.io/doc/upgrade-guide/2.176/#SECURITY-626 ] The crumb that is issued can only be used in a single session but no session handling is present in the nsp code. This also affects the 'Test connection' from the executor to the orchestrator. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201625.1567431531000.5443.1567501980370%40Atlassian.JIRA.
[JIRA] (JENKINS-59202) updated changelog?
Title: Message Title Jon Bendtsen created an issue Jenkins / JENKINS-59202 updated changelog? Issue Type: Improvement Assignee: Srivardhan Hebbar Components: office-365-connector-plugin Created: 2019-09-03 09:28 Priority: Minor Reporter: Jon Bendtsen I really wish that the changelog would be kept uptodate. No matter where I've looked I've been unable to find any changelog newer than revision 4.5 of the office-365-connector plugin, and it is revision 4.12 now :-/ I've looked: https://plugins.jenkins.io/Office-365-Connector https://wiki.jenkins.io/display/JENKINS/Office+365+Connector+Plugin https://github.com/jenkinsci/office-365-connector-plugin https://github.com/jenkinsci/office-365-connector-plugin/releases https://docs.microsoft.com/en-us/outlook/actionable-messages/ Add Comment
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Raihaan Shouhell commented on JENKINS-59137 Re: Connectivity issues with ec2 slaves Awesome, yeah I'll add that into some documentation somewhere or you might be able to edit our wiki page Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201569.1567062958000.5450.1567503960572%40Atlassian.JIRA.
[JIRA] (JENKINS-58856) No Authorization Header for WinRM connection
Title: Message Title Raihaan Shouhell commented on JENKINS-58856 Re: No Authorization Header for WinRM connection For my own I do not have credssp enabled but our user data scripts look identical. My setup does work with that script. Note group policies override anything you attempt to set on the command line. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201171.1565246564000.5453.1567504200706%40Atlassian.JIRA.
[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title junaid mukhtar commented on JENKINS-52593 Re: Support EKS authentication, or specifying a kubeconfig directly Carlos Sanchez do you have any howto or a guide on how to do it? I am struggling to connect Jenkins with EKS cluster via the kubernetes plugin. Any help would be highly appreciated Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192436.1531774635000.5456.1567504800356%40Atlassian.JIRA.
[JIRA] (JENKINS-39976) pipeline build failed mail - missing line break
Title: Message Title Oleg Nenashev reopened an issue Jenkins / JENKINS-39976 pipeline build failed mail - missing line break Change By: Oleg Nenashev Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176600.1479914126000.5465.1567505520515%40Atlassian.JIRA.
[JIRA] (JENKINS-39976) pipeline build failed mail - missing line break
Title: Message Title Oleg Nenashev commented on JENKINS-39976 Re: pipeline build failed mail - missing line break I do not see changes which would have fixed that. The PR is trivial, so probably we should integrate it and move on Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176600.1479914126000.5472.1567505640180%40Atlassian.JIRA.
[JIRA] (JENKINS-54683) Pods entering error state due to ConnectionRefusalException: Unknown client name
Title: Message Title Jakub Vavrik commented on JENKINS-54683 Re: Pods entering error state due to ConnectionRefusalException: Unknown client name This behaviour occurs when your job is running with Slave spawned in k8s and some job in the background calls Jenkins.instance.reload(). Jenkins instance forgets that it has a slave of such name and this exception occurs. I'd say either do not call Jenkins.instance.reload() or reload function should be able to not forget running slaves it has created. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195475.1542484359000.5479.1567506663270%40Atlassian.JIRA.
[JIRA] (JENKINS-54683) Pods entering error state due to ConnectionRefusalException: Unknown client name
Title: Message Title
Jakub Vavrik edited a comment on JENKINS-54683
Re: Pods entering error state due to ConnectionRefusalException: Unknown client name
This behaviour occurs when your job is running with Slave spawned in k8s and some job in the background calls Jenkins.instance.reload(). Jenkins instance forgets that it has a slave of such name and this exception occurs. I'd say either do not call Jenkins.instance.reload() or reload function should be able to not forget running slaves it has created. Partial log from master:{code:java}Sep 03, 2019 9:49:05 AM io.fabric8.jenkins.openshiftsync.BuildConfigWatcher$3 callINFO: Updated job web2-bc-admin from BuildConfig NamespaceName{web2:bc-admin} with revision: 356707991Sep 03, 2019 9:49:05 AM io.fabric8.jenkins.openshiftsync.CredentialsUtils upsertCredentialINFO: Updated credential web2-jenkins-secret-bitbucket from Secret NamespaceName{web2:jenkins-secret-bitbucket} with revision: 171272636Sep 03, 2019 9:49:05 AM io.fabric8.jenkins.openshiftsync.BuildSyncRunListener onStartedINFO: starting polling build job/web2/job/web2-bc-admin/3/Sep 03, 2019 9:49:08 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Kubernetes agents: 1Sep 03, 2019 9:49:08 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Template for label java11-maven35-nodejs8-boosted: Kubernetes Pod TemplateSep 03, 2019 9:49:08 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl applyINFO: Started provisioning Kubernetes Pod Template from openshift with 1 executors. Remaining excess workload: 0Sep 03, 2019 9:49:18 AM hudson.slaves.NodeProvisioner$2 runINFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s)Sep 03, 2019 9:49:18 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Created Pod: web2/java11-maven35-nodejs8-boosted-m3tvbSep 03, 2019 9:49:18 AM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?Sep 03, 2019 9:49:22 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Pod is running: web2/java11-maven35-nodejs8-boosted-m3tvbSep 03, 2019 9:49:22 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (0/100): java11-maven35-nodejs8-boosted-m3tvbSep 03, 2019 9:49:23 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (1/100): java11-maven35-nodejs8-boosted-m3tvbSep 03, 2019 9:49:24 AM hudson.TcpSlaveAgentListener$ConnectionHandler runINFO: Accepted JNLP4-connect connection #12 from /10.38.49.11:56832Sep 03, 2019 9:49:24 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (2/100): java11-maven35-nodejs8-boosted-m3tvbSep 03, 2019 9:49:25 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (3/100): java11-maven35-nodejs8-boosted-m3tvbSep 03, 2019 9:49:26 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (4/100): java11-maven35-nodejs8-boosted-m3tvbSep 03, 2019 9:49:27 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launchINFO: Waiting for agent to connect (5/100): java11-maven35-nodejs8-boosted-m3tvbINFO: Terminating Kubernetes instance for agent java11-maven35-nodejs8-boosted-m3tvbSep 03, 2019 9:58:26 AM okhttp3.internal.platform.Platform logINFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?FATAL: Computer for agent is null: java11-maven35-nodejs8-boosted-m3tvbSep 03, 2019 9:58:26 AM org.csa
[JIRA] (JENKINS-59200) Multiple Dependency-check links created when upgrading
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-59200 Multiple Dependency-check links created when upgrading Change By: Kent Granström Environment: Windows 2016 server, Jenkins 2. 189 193 , dependency-check-plugin-jenkins 5.02 Windows 2016 server, Maven 3.5.4, executing dependency-check 5.2.1 (upgraded from 4.0.2) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201644.1567498992000.5505.1567508280078%40Atlassian.JIRA.
[JIRA] (JENKINS-59178) Nullpointer exception in IssuesAggregator.updateMap
Title: Message Title Kent Granström commented on JENKINS-59178 Re: Nullpointer exception in IssuesAggregator.updateMap Does anyone know if there is a workaround for this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201615.1567417828000.5511.1567509540259%40Atlassian.JIRA.
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde commented on JENKINS-59137 Re: Connectivity issues with ec2 slaves Raihaan Shouhell I will update the wiki. Cheers Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201569.1567062958000.5513.1567509780258%40Atlassian.JIRA.
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde resolved as Not A Defect Jenkins / JENKINS-59137 Connectivity issues with ec2 slaves Change By: Toni Van de Voorde Status: Open Resolved Assignee: FABRIZIO MANFREDI Raihaan Shouhell Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201569.1567062958000.5517.1567509840935%40Atlassian.JIRA.
[JIRA] (JENKINS-45055) Make EnvInject FindBugs-clean
Title: Message Title Oleg Nenashev commented on JENKINS-45055 Re: Make EnvInject FindBugs-clean Current state: [INFO] --- spotbugs-maven-plugin:3.1.12:check (spotbugs) @ envinject --- [INFO] BugInstance size is 21 [INFO] Error size is 0 [INFO] Total bugs: 21 [ERROR] hudson.plugins.envfile.EnvFileBuildWrapper$DescriptorImpl.getDisplayName() may return null, but is declared @Nonnull [hudson.plugins.envfile.EnvFileBuildWrapper$DescriptorImpl] At EnvFileBuildWrapper.java:[line 43] NP_NONNULL_RETURN_VIOLATION [ERROR] hudson.plugins.setenv.SetEnvBuildWrapper$DescriptorImpl.getDisplayName() may return null, but is declared @Nonnull [hudson.plugins.setenv.SetEnvBuildWrapper$DescriptorImpl] At SetEnvBuildWrapper.java:[line 52] NP_NONNULL_RETURN_VIOLATION [ERROR] Unused field: org.jenkinsci.plugins.envinject.EnvInjectBuilder$1.val$resultVariables [org.jenkinsci.plugins.envinject.EnvInjectBuilder$1] In EnvInjectBuilder$1.java UUF_UNUSED_FIELD [ERROR] org.jenkinsci.plugins.envinject.EnvInjectGlobalPasswordWrapper$DescriptorImpl.getDisplayName() may return null, but is declared @Nonnull [org.jenkinsci.plugins.envinject.EnvInjectGlobalPasswordWrapper$DescriptorImpl] At EnvInjectGlobalPasswordWrapper.java:[line 42] NP_NONNULL_RETURN_VIOLATION [ERROR] org.jenkinsci.plugins.envinject.EnvInjectInfo is Serializable; consider declaring a serialVersionUID [org.jenkinsci.plugins.envinject.EnvInjectInfo] At EnvInjectInfo.java:[lines 27-86] SE_NO_SERIALVERSIONID [ERROR] org.jenkinsci.plugins.envinject.EnvInjectJobProperty.getPasswordEntries() may expose internal representation by returning EnvInjectJobProperty.passwordEntries [org.jenkinsci.plugins.envinject.EnvInjectJobProperty] At EnvInjectJobProperty.java:[line 227] EI_EXPOSE_REP [ERROR] org.jenkinsci.plugins.envinject.EnvInjectJobProperty.setContributors(EnvInjectJobPropertyContributor[]) may expose internal representation by storing an externally mutable object into EnvInjectJobProperty.contributors [org.jenkinsci.plugins.envinject.EnvInjectJobProperty] At EnvInjectJobProperty.java:[line 158] EI_EXPOSE_REP2 [ERROR] Class org.jenkinsci.plugins.envinject.EnvInjectJobPropertyInfo defines non-transient non-serializable instance field secureGroovyScript [org.jenkinsci.plugins.envinject.EnvInjectJobPropertyInfo] In EnvInjectJobPropertyInfo.java SE_BAD_FIELD [ERROR] org.jenkinsci.plugins.envinject.EnvInjectJobPropertyInfo is Serializable; consider declaring a serialVersionUID [org.jenkinsci.plugins.envinject.EnvInjectJobPropertyInfo] At EnvInjectJobPropertyInfo.java:[lines 35-123] SE_NO_SERIALVERSIONID [ERROR] org.jenkinsci.plugins.envinject.EnvInjectPasswordWrapper.setPasswordEntries(EnvInjectPasswordEntry[]) may expose internal representation by storing an externally mutable object into EnvInjectPasswordWrapper.passwordEntries [org.jenkinsci.plugins.envinject.EnvInjectPasswordWrapper] At EnvInjectPasswordWrapper.java:[line 114] EI_EXPOSE_REP2 [ERROR] envInjectPasswordEntry must be non-null but is marked as nullable [org.jenkinsci.plugins.envinject.EnvInjectPasswordWrapper$1] At EnvInjectPasswordWrapper.java:[lines 43-46] NP_PARAMETER_MUST_BE_NONNULL_BUT_MARKED_AS_NULLABLE [ERROR] envInjectPasswordEntry must be non-null but is marked as nullable [org.jenkinsci.plugins.envinject.EnvInjectPasswordWrapper$2] At EnvInjectPasswordWrapper.java:[lines 53-56] NP_PARAMETER_MUST_BE_NONNULL_BUT_MARKED_AS_NULLABLE [ERROR] req must be non-null but is marked as nullable [org.jenkinsci.plugins.envinject.EnvInjectPasswordWrapper$D
[JIRA] (JENKINS-45055) Make EnvInject SpotBugs-clean
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-45055 Make EnvInject SpotBugs-clean Change By: Oleg Nenashev Summary: Make EnvInject FindBugs SpotBugs -clean Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183146.1498117592000.5521.1567510440281%40Atlassian.JIRA.
[JIRA] (JENKINS-45055) Make EnvInject SpotBugs-clean
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-45055 Make EnvInject SpotBugs-clean Change By: Oleg Nenashev Labels: findbugs newbie-friendly spotbugs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183146.1498117592000.5522.1567510440300%40Atlassian.JIRA.
[JIRA] (JENKINS-59168) Variable is not resolved in "Runtime Settings" of "LoadRunner-specific settings" of build-step "Execute Microfocus tests from file system"
Title: Message Title Aliaksandr Kavaliou commented on JENKINS-59168 Re: Variable is not resolved in "Runtime Settings" of "LoadRunner-specific settings" of build-step "Execute Microfocus tests from file system" Hello, have seen the issue since 5.6.2 version. And at all haven't experienced expected result (variable evaluation) since started using the plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201605.1567267759000.5529.1567511100298%40Atlassian.JIRA.
[JIRA] (JENKINS-39403) Path separators in nested variables are not being escaped correctly when parsing the property file
Title: Message Title Oleg Nenashev resolved as Fixed Taking the feedback, I have released it in 2.2.1. https://github.com/jenkinsci/envinject-plugin/releases/tag/envinject-2.2.1 Thanks Alex Taylor and Raihaan Shouhell for your patches! Jenkins / JENKINS-39403 Path separators in nested variables are not being escaped correctly when parsing the property file Change By: Oleg Nenashev Status: Reopened Resolved Resolution: Fixed Released As: EnvInject 2.2.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-59137) Connectivity issues with ec2 slaves
Title: Message Title Toni Van de Voorde commented on JENKINS-59137 Re: Connectivity issues with ec2 slaves Raihaan Shouhell Updated the wiki => https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin#AmazonEC2Plugin-KnownIssues Cheers Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201569.1567062958000.5541.1567511700095%40Atlassian.JIRA.
[JIRA] (JENKINS-57182) When configuring a Jira steps site in casc yaml file. If the Jenkins service is restarted, the site is duplicated in Jenkins config
Title: Message Title Jim D commented on JENKINS-57182 Re: When configuring a Jira steps site in casc yaml file. If the Jenkins service is restarted, the site is duplicated in Jenkins config Thank you! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198934.1556196877000.5544.1567511820264%40Atlassian.JIRA.
[JIRA] (JENKINS-59203) Upgrading Jenkins to 2.176.3 breaks service hooks integration with Visualstudio.com
Title: Message Title Even Juberg created an issue Jenkins / JENKINS-59203 Upgrading Jenkins to 2.176.3 breaks service hooks integration with Visualstudio.com Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-03 12:00 Environment: Jenins 2.176.3, TFS, Strict Crumb Issuer Priority: Minor Reporter: Even Juberg This issue was introduced when upgrading from Jenkins version 2.176.2 to 2.176.3. I believe this is related to the change referred https://jenkins.io/security/advisory/2019-08-28/, under CSRF protection [...]. Our development team is using visualstudio.com and have up til now used service hooks there, to trigger builds in jenkins. When upgrading to the latest version of jenkins these service hooks fail, referring to an invalid crumb. I have tried installing and using the "strict crumb issuer" plugin, but that does not seem to work at all with the service hooks from VS. Disabling CSRF seem to "fix the problem", but that is obviously not an option. Please advice. Add Comment
[JIRA] (JENKINS-56057) UpdateSiteWarningsConfiguration should be confirgurable via JCasC
Title: Message Title Simon Wydooghe commented on JENKINS-56057 Re: UpdateSiteWarningsConfiguration should be confirgurable via JCasC It would be great to be able to suppress certain warnings via JSasC. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197480.1549643829000.5553.1567513020360%40Atlassian.JIRA.
[JIRA] (JENKINS-59200) Multiple Dependency-check links created when upgrading
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-59200 Multiple Dependency-check links created when upgrading Change By: Kent Granström After upgrading dep-check I see a large number of links on the build's frontpage and they all point to the same directory but all show the same information. Also, noticed that there are similar issues out there:https://issues.jenkins-ci.org/browse/JENKINS-58523https://issues.jenkins-ci.org/browse/JENKINS-58610https://issues.jenkins-ci.org/browse/JENKINS-59076 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201644.1567498992000.5560.1567513080403%40Atlassian.JIRA.
[JIRA] (JENKINS-56057) UpdateSiteWarningsConfiguration should be confirgurable via JCasC
Title: Message Title Daniel Estermann commented on JENKINS-56057 Re: UpdateSiteWarningsConfiguration should be confirgurable via JCasC I would like to see this feature as well Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197480.1549643829000.5562.1567513260536%40Atlassian.JIRA.
[JIRA] (JENKINS-59204) NPE when trying to use claim plugin after upgrading to jenkins 2.191
Title: Message Title Olivier Vernin moved an issue Jenkins / JENKINS-59204 NPE when trying to use claim plugin after upgrading to jenkins 2.191 Change By: Olivier Vernin Project: Infrastructure Jenkins Key: INFRA JENKINS - 2234 59204 Workflow: classic default workflow JNJira + In-Review Component/s: build-failure-analyzer-plugin Component/s: jenkins.io Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201470.1566815964000.5571.1
[JIRA] (JENKINS-59204) NPE when trying to use claim plugin after upgrading to jenkins 2.191
Title: Message Title Christian Ertl updated an issue Jenkins / JENKINS-59204 NPE when trying to use claim plugin after upgrading to jenkins 2.191 Change By: Christian Ertl Component/s: claim-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201470.1566815964000.5575.1567513620260%40Atlassian.JIRA.
[JIRA] (JENKINS-58950) When trying to deploy with v2.0.0 of this plugin got error unable to find valid certification path to requested target.
Title: Message Title Mikhail K. resolved as Fixed Jenkins / JENKINS-58950 When trying to deploy with v2.0.0 of this plugin got error unable to find valid certification path to requested target. Change By: Mikhail K. Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201297.1565877004000.5585.156751464%40Atlassian.JIRA.
[JIRA] (JENKINS-58950) When trying to deploy with v2.0.0 of this plugin got error unable to find valid certification path to requested target.
Title: Message Title Mikhail K. closed an issue as Fixed Jenkins / JENKINS-58950 When trying to deploy with v2.0.0 of this plugin got error unable to find valid certification path to requested target. Change By: Mikhail K. Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201297.1565877004000.5586.1567514222477%40Atlassian.JIRA.
[JIRA] (JENKINS-59095) useAuth is set to false even when 'Use SMTP Authentication' is enabled and configured
Title: Message Title Tommy Sparber commented on JENKINS-59095 Re: useAuth is set to false even when 'Use SMTP Authentication' is enabled and configured This should be fixed with the release 1.26 of the mailer-plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201515.1566890549000.5589.1567514342037%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title Tommy Sparber commented on JENKINS-59161 Re: ERROR: 530 Authentication required The "send Test E-Mail" feature is fixed in the recently released version 1.26. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201598.1567204978000.5607.1567515420215%40Atlassian.JIRA.
[JIRA] (JENKINS-59117) Add support for WorkflowPipelineView to JobDSL
Title: Message Title Daniel Spilker started work on JENKINS-59117 Change By: Daniel Spilker Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201546.1566985699000.5611.1567516440195%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title Paul Cosma commented on JENKINS-59161 Re: ERROR: 530 Authentication required Works fine now. Thanks a lot Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201598.1567204978000.5614.1567516500360%40Atlassian.JIRA.
[JIRA] (JENKINS-59117) Add support for WorkflowPipelineView to JobDSL
Title: Message Title
Daniel Spilker commented on JENKINS-59117
Re: Add support for WorkflowPipelineView to JobDSL
https://github.com/Diabol/delivery-pipeline-plugin/pull/304 https://github.com/jenkinsci/job-dsl-plugin/pull/1200 These two pull requests will enable Dynamic DSL support:
folder('example-folder') {
views {
workflowPipelineView {
name('example-view')
allowAbort(true)
allowPipelineStart(true)
description('test')
linkToConsoleLog(true)
maxNumberOfVisiblePipelines(8)
noOfColumns(12)
noOfPipelines(7)
showAbsoluteDateTime(true)
showChanges(true)
sorting('se.diabol.jenkins.pipeline.sort.NameComparator')
updateInterval(100)
componentSpecs {
componentSpec {
name('example')
job('example-pipeline')
}
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201546.1566985699000.5618.1567516620107%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title Adrien Lecharpentier resolved as Fixed Jenkins / JENKINS-59161 ERROR: 530 Authentication required Change By: Adrien Lecharpentier Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/mailer-plugin/releases/tag/mailer-1.26 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201598.1567204978000.5621.1567516681238%40Atlassian.JIRA.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Marat Radchenko commented on JENKINS-47496 Re: No automatic builds for tags Stephen Connolly R. Tyler Croy This article clearly states that if we add "Discover tags" to multibranch pipeline, Jenkins will trigger builds when tags are pushed into repo. But this bug ( JENKINS-47496 ) says that tags are not supposed to trigger a build automatically. Could you please decide somehow which one of you is right? As a Jenkins user, I +1 for tag triggering. We want to use this to build/publish releases whenever Git tag is created. This is the way all other major CI systems work: Travis CI, CircleCI, AppVeyour. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.5627.1567516740485%40Atlassian.JIRA.
[JIRA] (JENKINS-59198) jenkisn配置发送测试邮件失败，报空指针异常
Title: Message Title Alex Earl commented on JENKINS-59198 Re: jenkisn配置发送测试邮件失败，报空指针异常 I don't see anything in the stack trace that points to email-ext. You'll have to provide a lot more information about your configuration. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201641.1567478279000.5639.1567516740879%40Atlassian.JIRA.
[JIRA] (JENKINS-44789) docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom
Title: Message Title
Devin Nusbaum commented on JENKINS-44789
Re: docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom
Michael Brunner We need to see how you are using the Docker Pipeline Plugin in your Jenkinsfile/shared library to know for sure. If you have a Declarative Pipeline using "agent { docker ... }", your problem should be fixed by https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/350, which has not yet been released.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182845.1496978044000.5643.1567517160544%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Wen Zhou commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines if the bug is really introduced by the workflow-job plugin, can we expect a fix in the new release? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000.5672.1567517522105%40Atlassian.JIRA.
[JIRA] (JENKINS-54937) java.lang.IllegalStateException: Cannot delete last view
Title: Message Title Daniel Spilker commented on JENKINS-54937 Re: java.lang.IllegalStateException: Cannot delete last view It's not possible to replace the "All" view by another view in one step, see https://wiki.jenkins.io/display/JENKINS/Editing+or+Replacing+the+All+View. What should be the expected behavior? A nicer error message? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195946.154348716.5716.1567517760133%40Atlassian.JIRA.
[JIRA] (JENKINS-59099) Environment variables with '$' in their content get corrupted in the container step in declerative pipeline
Title: Message Title Marcell Lipusz updated an issue Jenkins / JENKINS-59099 Environment variables with '$' in their content get corrupted in the container step in declerative pipeline Change By: Marcell Lipusz Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201519.1566900392000.5717.1567518120128%40Atlassian.JIRA.
[JIRA] (JENKINS-39976) pipeline build failed mail - missing line break
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-39976 pipeline build failed mail - missing line break Change By: Jesse Glick Status: Reopened Resolved Resolution: Fixed Released As: 1.26 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176600.1479914126000.5719.1567518422205%40Atlassian.JIRA.
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
jerry wiltse commented on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
This naive code seems to work fine, can you think of any issue with using it?
while(true) {
thing = latch.pollFirst();
if (thing != null){
break;
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181710.1494001199000.5761.1567520220971%40Atlassian.JIRA.
[JIRA] (JENKINS-59205) GUI doesn't display updated parameters after multiple runs
Title: Message Title David Williams created an issue Jenkins / JENKINS-59205 GUI doesn't display updated parameters after multiple runs Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-03 14:18 Environment: Linux 3.10.0-957.5.1.el7.x86_64 Java 1.8.0_222-b10 Jenkins 2.176.3 Plugins ace-editor 1.1 amazon-ecr 1.6 amazon-ecs 1.19 anchore-container-scanner 1.0.18 ansible 1.0 ansicolor 0.6.2 ant 1.9 antisamy-markup-formatter 1.5 apache-httpcomponents-client-4-api 4.5.5-3.0 authentication-tokens 1.3 aws-credentials 1.26 aws-java-sdk 1.11.594 aws-lambda 0.5.10 aws-parameter-store 1.2.1 basic-branch-build-strategies 1.3.2 blueocean 1.17.0 blueocean-autofavorite 1.2.3 blueocean-bitbucket-pipeline 1.17.0 blueocean-commons 1.17.0 blueocean-config 1.17.0 blueocean-core-js 1.17.0 blueocean-dashboard 1.17.0 blueocean-display-url 2.2.0 blueocean-events 1.17.0 blueocean-git-pipeline 1.17.0 blueocean-github-pipeline 1.17.0 blueocean-i18n 1.17.0 blueocean-jira 1.17.0 blueocean-jwt 1.17.0 blueocean-personalization 1.17.0 blueocean-pipeline-api-impl 1.17.0 blueocean-pipeline-editor 1.17.0 blueocean-pipeline-scm-api 1.17.0 blueocean-rest 1.17.0 blueocean-rest-impl 1.17.0 blueocean-web 1.17.0 bouncycastle-api 2.17 branch-api 2.5.2 build-timeout 1.19 cloudbees-bitbucket-branch-source 2.4.4 cloudbees-folder 6.9 command-launcher 1.3 credentials 2.3.0 credentials-binding 1.18 display-url-api 2.3.0 docker-build-publish 1.3.2 docker-commons 1.13 docker-workflow 1.17 durable-task 1.29 ec2 1.45 embeddable-build-status 2.0.2 envinject 2.1.6 envinject-api 1.5 external-monitor-job 1.7 favorite 2.3.2 file-operations 1.7 git 3.10.0 git-client 2.7.7 git-server 1.7 github 1.29.4 github-api 1.95 github-branch-source 2.5.3 golang 1.2 google-login 1.4 graphiteIntegrator 1.3-SNAPSHOT (private-06/11/2018 15:08-mitalpotey) greenballs 1.15 handlebars 1.1.1 handy-uri-templates-2-api 2.1.7-1.0 htmlpublisher 1.18 http_request 1.8.22 jackson2-api 2.9.9 javadoc 1.4 jdk-tool 1.2 jenkins-design-language 1.17.0 jira 3.0.5 job-dsl 1.76 jquery-detached 1.2.1 jsch 0.1.55 junit 1.27 ldap 1.20 lockable-resources 2.5 mailer 1.23 matrix-auth 2.4.2 matrix-project 1.14 mercurial 2.5 momentjs 1.1.1 monitoring 1.76.0 node-iterator-api 1.5.0 pam-auth 1.5.1 pipeline-aws 1.38 pipeline-build-step 2.9 pipeline-graph-analysis 1.10 pipeline-input-step 2.11 pipeline-milestone-step 1.3.1 pipeline-model-api 1.3.9 pipeline-model-declarative-agent 1.1.1 pipeline-model-definition 1.3.9 pipeline-model-extensions 1.3.9 pipeline-rest-api 2.12 pipeline-stage-
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Liam Newman commented on JENKINS-47496 Re: No automatic builds for tags Marat Radchenko Please use the Basic Branch Build Strategies plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.5816.1567520520658%40Atlassian.JIRA.
[JIRA] (JENKINS-59205) GUI doesn't display updated parameters after multiple runs
Title: Message Title David Williams updated an issue Jenkins / JENKINS-59205 GUI doesn't display updated parameters after multiple runs Change By: David Williams Attachment: Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201652.1567520338000.5817.1567521060158%40Atlassian.JIRA.
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title James Nord commented on JENKINS-44085 Re: have a simple way to limit the number of parallel branches that run concurrently This naive code seems to work fine, can you think of any issue with using it? CPU usage as you are in a tight spin loop whilst waiting that will spin the CPS thread causing other issues.. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181710.1494001199000.5860.1567521121719%40Atlassian.JIRA.
[JIRA] (JENKINS-44789) docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom
Title: Message Title Michael Brunner commented on JENKINS-44789 Re: docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom Thank you for your hint. I'm actually using it in a declarative pipeline manner. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182845.1496978044000.5862.1567521606812%40Atlassian.JIRA.
[JIRA] (JENKINS-59152) Jenkins fails to properly abort "bat" step
Title: Message Title Marat Radchenko updated an issue Jenkins / JENKINS-59152 Jenkins fails to properly abort "bat" step Change By: Marat Radchenko Component/s: durable-task-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201589.1567181048000.5897.1567523040074%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Paulius Bulotas commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Small update... While it's little inconvenience with configuring pipeline text or pipeline scm source, I just noticed that configuring Folder (which has shared pipeline, vault info configured), shared pipeline and vault info is also not displayed and if you save folder config, those things are lost from config. I was a bit surprised that after modifying folder description, shared pipeline and vault info disappeared (config-history plugin is great) and all jobs in folder started failing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.5899.1567523220752%40Atlassian.JIRA.
[JIRA] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title Sebastien TANIERE updated an issue Jenkins / JENKINS-53745 Multiple JUnit reports recordings analyses at the same time Change By: Sebastien TANIERE Attachment: jenkins_parameters.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194250.1537790514000.5910.1567523520298%40Atlassian.JIRA.
[JIRA] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title Sebastien TANIERE updated an issue Jenkins / JENKINS-53745 Multiple JUnit reports recordings analyses at the same time Change By: Sebastien TANIERE Attachment: artefacts_files.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194250.1537790514000.5913.1567523641649%40Atlassian.JIRA.
[JIRA] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title Sebastien TANIERE commented on JENKINS-53745 Re: Multiple JUnit reports recordings analyses at the same time Hello, I have similar issue when using performance plugin with 2 xml files in each of 7 subfolders : It generate 196 lines "Performance: File PTB-Menu_Mission_junit.xml reported 0.0% of errors [SUCCESS]. Build status is: SUCCESS" I noticed that performance plugin search for xml files in both folders workspace & jobs : D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165038\CPE-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\jobs\ReflexReactiviteEveryServers\builds\15\performance-reports\JUnit\CPE-Menu_Mission_junit.xml, but he should only search in workspace as my "source data files" field is set to : "ReflexFmTests/Reports/PROD/sReactiviteMenuEtEcran/*/.xml" I also use saving artefacts in jenkins parameters, perhaps it is linked to incompatibility between saving artefacts and performance plugin ? extract of my jenkins parameters : here is my artefact folder structure : (I do not know what creates dashboard_* files as I do not generate it myself) say me if you need more elements to analyse here is end of jenkins console : New run name is '#15 3/9-16:50' Archiving artifacts Recording test results Creating parser with percentiles:'0,50,90,100,' filterRegex: Performance: Recording JUnit reports 'ReflexFmTests/Reports/PROD/sReactiviteMenuEtEcran/**/*.xml' Performance: JUnit copying reports to master, files '[D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165038\CPE-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165038\CPE-Menu_Mission_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165039\CPN-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165039\CPN-Menu_Mission_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165040\ENT-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165040\ENT-Menu_Mission_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165041\FCE-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165041\FCE-Menu_Mission_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165042\LPO-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165042\LPO-Menu_Mission_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165043\MAN-Ecran_HFQ300_junit.xml, D:\Integra
[JIRA] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title
Sebastien TANIERE edited a comment on JENKINS-53745
Re: Multiple JUnit reports recordings analyses at the same time
Hello, I have similar issue when using performance plugin with 2 xml files in each of 7 subfolders : It generate generates 196 lines "Performance: File PTB-Menu_Mission_junit.xml reported 0.0% of errors [SUCCESS]. Build status is: SUCCESS" I noticed that performance plugin search for xml files in both folders workspace & jobs : * D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165038\CPE-Ecran_HFQ300_junit.xml, * D:\Integration\Jenkins\jobs\ReflexReactiviteEveryServers\builds\15\performance-reports\JUnit\CPE-Menu_Mission_junit.xml, but he should only search in workspace as my "source data files" field is set to : "ReflexFmTests/Reports/PROD/sReactiviteMenuEtEcran/**/*.xml" I also use saving artefacts in jenkins parameters, perhaps it is linked to incompatibility between saving artefacts and performance plugin ?extract of my jenkins parameters : !jenkins_parameters.png|thumbnail!here is my artefact folder structure : (I do not know what creates dashboard_* files as I do not generate it myself) !artefacts_files.png|thumbnail! say me if you need more elements to analysehere is end of jenkins console : {code:java}New run name is '#15 3/9-16:50' Archiving artifacts Recording test results Creating parser with percentiles:'0,50,90,100,' filterRegex: Performance: Recording JUnit reports 'ReflexFmTests/Reports/PROD/sReactiviteMenuEtEcran/**/*.xml' Performance: JUnit copying reports to master, files '[D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165038\CPE-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165038\CPE-Menu_Mission_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165039\CPN-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165039\CPN-Menu_Mission_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165040\ENT-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165040\ENT-Menu_Mission_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165041\FCE-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165041\FCE-Menu_Mission_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165042\LPO-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165042\LPO-Menu_Mission_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165043\MAN-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165043\MAN-Menu_Mission_junit.xml, D:\Integration\Jenkins\workspace\ReflexReactiviteEveryServers\ReflexFmTests\Reports\PROD\sReactiviteMenuEtEcran\20190903_165044\PTB-Ecran_HFQ300_junit.xml, D:\Integration\Jenkins\worksp
[JIRA] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title Sebastien TANIERE commented on JENKINS-53745 Re: Multiple JUnit reports recordings analyses at the same time and here is end of performance plugin log : console_jenkins_job15.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194250.1537790514000.5943.1567524720224%40Atlassian.JIRA.
[JIRA] (JENKINS-53745) Multiple JUnit reports recordings analyses at the same time
Title: Message Title Sebastien TANIERE commented on JENKINS-53745 Re: Multiple JUnit reports recordings analyses at the same time another thing which may cause the loop, my junit report files are self made generated and have same name in testssuites, testsuite, and testcase. Ecran_HFQ300_junit.xml : name="Ecran HFQ300" time="7986" timestamp="2019-09-03 10:08:12" hostname="HOSTNAME inconnu" id="Ecran HFQ300" tests="1" failures="0" errors="0"> name="Ecran HFQ300" time="7986" tests="1" failures="0" errors="0"> name="Ecran HFQ300" classname="Ecran HFQ300" time="7986" status="PASSED"> Menu_Mission_HFQ300_junit.xml : Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194250.1537790514000.5946.1567525320157%40Atlassian.JIRA.
[JIRA] (JENKINS-59206) Environment variables tag name and branch name set incorrectly
Title: Message Title MICHAEL PERZEL created an issue Jenkins / JENKINS-59206 Environment variables tag name and branch name set incorrectly Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2019-09-03 16:22 Environment: Jenkins jenkins-2.187-1.1 Git-plugin 4.0.0-rc Priority: Minor Reporter: MICHAEL PERZEL In a multi-branch pipeline, if you commit to the master branch and print out the values of the environments variables you will see: BRANCH_NAME = master GIT_BRANCH = master If you trigger a build via committing a tag to the same repository and print out the variables (where the tag name is 4.1.0): BRANCH_NAME = 4.1.0 GIT_BRANCH = 4.1.0 TAG_NAME = 4.1.0 I believe the correct values for the tagged build should be: BRANCH_NAME = master GIT_BRANCH = master TAG_NAME = 4.1.0 Add Comment
[JIRA] (JENKINS-59206) Environment variables tag name and branch name set incorrectly
Title: Message Title
Mark Waite edited a comment on JENKINS-59206
Re: Environment variables tag name and branch name set incorrectly
I disagree. A tag does not reliably have an association to a branch. A tag is a "a pointer to a specific commit". It identifies a specific commit by providing a simplified name to describe that commit.A branch is a " lightweight movable pointer".Depending on the state of the repository, a tag may be on no branch, one branch, or many branches. Attempting to assign a branch name which is not the name of the tag is hard or impossible to do reliably.Output from the command {{git log --graph --pretty=oneline --abbrev-commit --decorate}}:{noformat}* dd46d51 (HEAD -> master) More information added* f6db255 Add another date* dacdad4 (tag: v2.0) Another new change* c4825db Add comment about v1.1| * ec23f88 (branch-1.x) Another README change| * 8c5c32a New change on branch-1.x| | * a6a83ee (tag: orphan-v1.1) Orphan change, no branch| |/| * 1df4892 A newer change on branch-1.x| * 3990059 (tag: v1.0) A change on branch-1.x|/* a693bf7 Add comment about tag* 183db1f Add README{noformat}In that case, the tag {{orphan-1.1}} is not directly associated with any branch, while the tag {{v1.0}} might be associated with {{branch-1x}}. However, if branch-1.x is merged into master, then the tag {{v1.0}} might be associated with both {{branch-1.x}} and {{master}}.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201655.1567527731000.5980.1567532880309%40Atlassian.JIRA.
[JIRA] (JENKINS-59206) Environment variables tag name and branch name set incorrectly
Title: Message Title Mark Waite commented on JENKINS-59206 Re: Environment variables tag name and branch name set incorrectly I disagree. A tag does not reliably have an association to a branch. A tag is a "a pointer to a specific commit". It identifies a specific commit by providing a simplified name to describe that commit. A branch is a " lightweight movable pointer". Depending on the state of the repository, a tag may be on no branch, one branch, or many branches. Attempting to assign a branch name which is not the name of the tag is hard or impossible to do reliably. Output from the command git log --graph --pretty=oneline --abbrev-commit --decorate: * dd46d51 (HEAD -> master) More information added * f6db255 Add another date * dacdad4 (tag: v2.0) Another new change * c4825db Add comment about v1.1 | * ec23f88 (branch-1.x) Another README change | * 8c5c32a New change on branch-1.x | | * a6a83ee (tag: orphan-v1.1) Orphan change, no branch | |/ | * 1df4892 A newer change on branch-1.x | * 3990059 (tag: v1.0) A change on branch-1.x |/ * a693bf7 Add comment about tag * 183db1f Add README In that case, the tag orphan-1.1 is not directly associated with any branch, while the tag v1.0 might be associated with branch-1x. However, if branch-1.x is merged into master, then the tag v1.0 might be associated with both branch-1.x and master. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/
[JIRA] (JENKINS-59206) Environment variables tag name and branch name set incorrectly
Title: Message Title
Mark Waite edited a comment on JENKINS-59206
Re: Environment variables tag name and branch name set incorrectly
I disagree. A tag does not reliably have an association to a branch. A tag is a "a pointer to a specific commit". It identifies a specific commit by providing a simplified name to describe that commit.A branch is a " lightweight movable pointer".Depending on the state of the repository, a tag may be on no branch, one branch, or many branches. Attempting to assign a branch name which is not the name of the tag is hard or impossible to do reliably.Output from {{git log --graph --pretty=oneline --abbrev-commit --decorate}}:{noformat}* dd46d51 (HEAD -> master) More information added* f6db255 Add another date* dacdad4 (tag: v2.0) Another new change* c4825db Add comment about v1.1| * ec23f88 (branch-1.x) Another README change| * 8c5c32a New change on branch-1.x| | * a6a83ee (tag: orphan-v1.1) Orphan change, no branch| |/| * 1df4892 A newer change on branch-1.x| * 3990059 (tag: v1.0) A change on branch-1.x|/* a693bf7 Add comment about tag* 183db1f Add README{noformat}In that case, the tag {{orphan-1.1}} is not directly associated with any branch, while the tag {{v1.0}} might be associated with {{branch- 1x 1.x }}. However, if branch-1.x is merged into master, then the tag {{v1.0}} might be associated with both {{branch-1.x}} and {{master}}.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201655.1567527731000.5982.1567532940109%40Atlassian.JIRA.
[JIRA] (JENKINS-59206) Environment variables tag name and branch name set incorrectly
Title: Message Title
Mark Waite edited a comment on JENKINS-59206
Re: Environment variables tag name and branch name set incorrectly
I disagree. A tag does not reliably have an association to a branch. A tag is a "a pointer to a specific commit". It identifies a specific commit by providing a simplified name to describe that commit.A branch is a " lightweight movable pointer".Depending on the state of the repository, a tag may be on no branch, one branch, or many branches. Attempting to assign a branch name which is not the name of the tag is hard or impossible to do reliably.Output from {{git log --graph --pretty=oneline --abbrev-commit --decorate}}:{noformat}* dd46d51 (HEAD -> master) More information added* f6db255 Add another date* dacdad4 (tag: v2.0) Another new change* c4825db Add comment about v1.1| * ec23f88 (branch-1.x) Another README change| * 8c5c32a New change on branch-1.x| | * a6a83ee (tag: orphan-v1.1) Orphan change, no branch| |/| * 1df4892 A newer change on branch-1.x| * 3990059 (tag: v1.0) A change on branch-1.x|/* a693bf7 Add comment about tag* 183db1f Add README{noformat}In that case, the tag {{orphan-1.1}} is not directly associated with any branch, while the tag {{v1.0}} might be associated with {{branch-1.x}}. However, if branch-1.x is merged into master, then the tag {{v1.0}} might be associated with both {{branch-1.x}} and {{master}}. After merging branch-1.x into master:{noformat}* 7a7ce4d (HEAD -> master) Merge branch 'branch-1.x'|\| * ec23f88 (branch-1.x) Another README change| * 8c5c32a New change on branch-1.x* | dd46d51 More information added* | f6db255 Add another date* | dacdad4 (tag: v2.0) Another new change* | c4825db Add comment about v1.1| | * a6a83ee (tag: orphan-v1.1) Orphan change, no branch| |/| * 1df4892 A newer change on branch-1.x| * 3990059 (tag: v1.0) A change on branch-1.x|/* a693bf7 Add comment about tag* 183db1f Add README{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because
[JIRA] (JENKINS-59121) Multibranch build strategy extension plugin throws BitbucketSCMSource cannot be cast to AbstractGitSCMSource
Title: Message Title Igal Gluh commented on JENKINS-59121 Re: Multibranch build strategy extension plugin throws BitbucketSCMSource cannot be cast to AbstractGitSCMSource Benjamin Hi, Can you please share yours job configuration ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201550.1566997231000.5986.1567533660133%40Atlassian.JIRA.
[JIRA] (JENKINS-59207) READONLY autoclean sync fails on reconcile
Title: Message Title Dave Miller created an issue Jenkins / JENKINS-59207 READONLY autoclean sync fails on reconcile Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-09-03 18:16 Environment: Jenkins ver. 2.150.2 Plugin ver. 1.10.3 Priority: Major Reporter: Dave Miller When a READONLY client is synced with the "Auto cleanup and sync" option, the reconcile throws an innocuous "Client of type 'readonly' cannot modify files." error. In 1.10, this error is ignored. In 1.10.3, this error causes the build to fail. This may be a consequence of a modification to src/main/java/org/jenkinsci/plugins/p4/client/ClientHelper.java in Change 25759, which added an exception when a reconcile fails. Unfortunately, in the above scenario, reconcile shouldn't even be called, so the fact that it fails should be ignored. Add Comment
[JIRA] (JENKINS-59208) OneDataScan
Title: Message Title Purushotham Reddy created an issue Jenkins / JENKINS-59208 OneDataScan Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2019-09-03 18:44 Priority: Minor Reporter: Purushotham Reddy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201658.1567536256000.5992.1567536300096%40Atlassian.JIRA.
[JIRA] (JENKINS-59198) jenkisn配置发送测试邮件失败，报空指针异常
Title: Message Title Purushotham Reddy started work on JENKINS-59198 Change By: Purushotham Reddy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201641.1567478279000.5997.1567536360328%40Atlassian.JIRA.
[JIRA] (JENKINS-59209) README supported versions needs to distinguish On-Prem vs Cloud
Title: Message Title Ian Williams created an issue Jenkins / JENKINS-59209 README supported versions needs to distinguish On-Prem vs Cloud Issue Type: Improvement Assignee: Kellie Jos Components: tfs-plugin Created: 2019-09-03 18:46 Environment: N/A Priority: Minor Reporter: Ian Williams The Supported Versions has been updated to reflect MS name change choice: VSTS -> Azure DevOps. But now it's even more confusing since Azure DevOps (cloud) is different to Azure DevOps Server (on-prem). Given the REST API take a while to trickle down to the on-prem, it's possible the Supported capabilities differ between the two (assuming there are more tfs-plugin updates to come). "Azure DevOps (cloud)" and "Azure DevOps Server (on-prem)" should be shown separately. Add Comment
[JIRA] (JENKINS-59209) README supported versions needs to distinguish On-Prem vs Cloud
Title: Message Title Ian Williams commented on JENKINS-59209 Re: README supported versions needs to distinguish On-Prem vs Cloud No harm in pulling Fixed typos in README.md as well. Would be nice to see some actual updates to the plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201659.1567536407000.6001.1567536540110%40Atlassian.JIRA.
[JIRA] (JENKINS-47597) Jenkins UI wording for removing a GitHub-based multibranch Pipeline project is very misleading
Title: Message Title Cliff Meyers commented on JENKINS-47597 Re: Jenkins UI wording for removing a GitHub-based multibranch Pipeline project is very misleading Agree that it's really misleading. Even on a recent version of Jenkins, it says "Delete Repository" on both the context menu and on the detail page for the job itself. I think "Delete Pipeline" would also work and is a bit briefer. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186010.1508474112000.6003.1567536780254%40Atlassian.JIRA.
[JIRA] (JENKINS-59178) Nullpointer exception in IssuesAggregator.updateMap
Title: Message Title Ulli Hafner commented on JENKINS-59178 Re: Nullpointer exception in IssuesAggregator.updateMap Since I can't reproduce this bug yet I just can guess: you can try to enable the warnings plugin for all configurations. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201615.1567417828000.6005.1567536900344%40Atlassian.JIRA.
[JIRA] (JENKINS-59178) Nullpointer exception in IssuesAggregator.updateMap
Title: Message Title Kent Granström commented on JENKINS-59178 Re: Nullpointer exception in IssuesAggregator.updateMap Will do that tomorrow morning. Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201615.1567417828000.6007.1567537500134%40Atlassian.JIRA.
[JIRA] (JENKINS-59206) Environment variables tag name and branch name set incorrectly
Title: Message Title MICHAEL PERZEL commented on JENKINS-59206 Re: Environment variables tag name and branch name set incorrectly Okay, I agree with your explanation. With that in mind should git_branch and branch_name be set to the tag name when the build was triggered by a tag commit? I'm trying to accomplish being able to differentiate between builds triggered from a commit to a branch and from tagging a commit. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201655.1567527731000.6009.1567537800105%40Atlassian.JIRA.
[JIRA] (JENKINS-59210) Extract commit SHA of Jenkinsfile
Title: Message Title Oleg Varshavsky created an issue Jenkins / JENKINS-59210 Extract commit SHA of Jenkinsfile Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-09-03 19:10 Environment: Jenkins ver. 2.121.3 - [git, '3.8.0'] - [git-client, '2.7.1'] - [git-server, '1.7'] - [github, '1.29.0'] - [github-api, '1.90'] - [github-branch-source, '2.3.3'] - [github-organization-folder, '1.6'] Priority: Major Reporter: Oleg Varshavsky We need to make sure that commit SHA that triggered the build via webhook is the same SHA that the repo is being checkout out. Use case: Dev-1 merges changes to repo 'a'. Within seconds, Dev-2 merges changes to repo 'a'. Expectation: Each commit triggers a separate build based on the webhook SHA that triggered the build. Current result: SHA of Jenkinsfile might be not the same as checkout code, since the merges might happen within seconds of each other. Add Comment
[JIRA] (JENKINS-59206) Environment variables tag name and branch name set incorrectly
Title: Message Title
Mark Waite edited a comment on JENKINS-59206
Re: Environment variables tag name and branch name set incorrectly
I disagree. A tag does not reliably have an association to a branch. A tag is a "a pointer to a specific commit". It identifies a specific commit by providing a simplified name to describe that commit.A branch is a " lightweight movable pointer".Depending on the state of the repository, a tag may be on no branch, one branch, or many branches. Attempting to assign a branch name which is not the name of the tag is hard or impossible to do reliably.Output from {{git log --graph --pretty=oneline --abbrev-commit --decorate}}:{noformat}* dd46d51 (HEAD -> master) More information added* f6db255 Add another date* dacdad4 (tag: v2.0) Another new change* c4825db Add comment about v1.1| * ec23f88 (branch-1.x) Another README change| * 8c5c32a New change on branch-1.x| | * a6a83ee (tag: orphan-v1.1) Orphan change, no branch| |/| * 1df4892 A newer change on branch-1.x| * 3990059 (tag: v1.0) A change on branch-1.x|/* a693bf7 Add comment about tag* 183db1f Add README{noformat}In that case, the tag {{orphan-1.1}} is not directly associated with any branch, while the tag {{v1.0}} might be associated with {{branch-1.x}}. However, if branch-1.x is merged into master, then the tag {{v1.0}} might be associated with both {{branch-1.x}} and {{master}}.After merging branch-1.x into master:{noformat}* 7a7ce4d (HEAD -> master) Merge branch 'branch-1.x'|\| * ec23f88 (branch-1.x) Another README change| * 8c5c32a New change on branch-1.x* | dd46d51 More information added* | f6db255 Add another date* | dacdad4 (tag: v2.0) Another new change* | c4825db Add comment about v1.1| | * a6a83ee (tag: orphan-v1.1) Orphan change, no branch| |/| * 1df4892 A newer change on branch-1.x| * 3990059 (tag: v1.0) A change on branch-1.x|/* a693bf7 Add comment about tag* 183db1f Add README{noformat} In this case, after merging, the tag {{v1.0}} is now on both branch-1.x and on master.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-59206) Environment variables tag name and branch name set incorrectly
Title: Message Title Mark Waite commented on JENKINS-59206 Re: Environment variables tag name and branch name set incorrectly In declarative Pipeline, there is the condition (see Pipeline syntax) when buildingTag A stage with that directive will only be built when a tag is being built. I suspect something similar could be done with scripted Pipeline, checking for the existence or non-existence of the environment variable TAG_NAME. I don't know of a way to do anything like that in Freestyle, Maven, or Matrix job types. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201655.1567527731000.6015.1567538340111%40Atlassian.JIRA.
