[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Federico Pellegrin edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
What you are trying to do is to tell your tool (OpenCover ?) to filter them and that totally depends on your tool. I sincerely don't know much about OpenCover and never used it, but looking at the [usage page|https://github.com/opencover/opencover/wiki/Usage] I don't see an {code:java} --exclude {code} option as by your example but see some { { code:java} - - excludebyfile . {code } } . Maybe that is what you are looking for! On the other side, on Jenkins coverage plugin side, such a filtering feature right now is not present. You may in case try to request it at the plugin page, but given that usually the tools generating the reports can do this it is maybe not something very interesting for the plugin itself.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.6732.1578718080200%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Federico Pellegrin commented on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
What you are trying to do is to tell your tool (OpenCover ?) to filter them and that totally depends on your tool. I sincerely don't know much about OpenCover and never used it, but looking at the usage page I don't see an --exclude option as by your example but see some {{-excludebyfile.}}Maybe that is what you are looking for! On the other side, on Jenkins coverage plugin side, such a filtering feature right now is not present. You may in case try to request it at the plugin page, but given that usually the tools generating the reports can do this it is maybe not something very interesting for the plugin itself.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.6728.1578718020265%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
hi FYI [~fedepell], [~stephenconnolly] Hi mate [~fedepell] hope you doing good?I just want one thing to make sure. I wanted to exclude some dlls (eg: dapper.dll) from including to this code-coverage reports; Such as in my source code their are dlls I don't want to use for use as packages for Code-Coverage reports. So when generating my unit tests Code-Coverage reports how can I exclude those dll files?Is their any code to exclude dll files in here? Such as when I running my RunTests.ps1 script for unit testing can I add some code to exclude dapper.dll file in below code ? {color:#ff} This example is not worked. :(.{color}{color:#172b4d} Existing Code:{color}{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code} example: Code I want for Exclude dapper.dll:{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --exclude dapper.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this m
[JIRA] (JENKINS-6957) Windows slave fails to find java
Title: Message Title Ilguiz Latypov edited a comment on JENKINS-6957 Re: Windows slave fails to find java The "system cannot find the file specified" error results from the poor service wrapper architecture that freezes the java.exe location in the "executable" XML tag inside its jenkins-slave.xml.[https://mohitgoyal.co/2016/12/18/failed-to-start-jenkins-after-updating-java/] I also found that it helps to comment out the other tag enabling a live update of the slave JAR. When this update is enabled, the service fails to start silently trying . The wrapper log shows an attempt to download the file and timing out without giving a verbose reason for this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137054.1278976025000.6714.1578706920285%40Atlassian.JIRA.
[JIRA] (JENKINS-6957) Windows slave fails to find java
Title: Message Title Ilguiz Latypov edited a comment on JENKINS-6957 Re: Windows slave fails to find java The "system cannot find the file specified" error results from the poor service wrapper architecture that freezes the java.exe location in the "executable" XML tag inside its jenkins-slave.xml. [ https://mohitgoyal.co/2016/12/18/failed-to-start-jenkins-after-updating-java/ ] I also found that it helps to comment out the other tag enabling a live update of the slave JAR. When this update is enabled, the service fails to start silently trying to download the file and timing out without giving a verbose reason for this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137054.1278976025000.6705.1578706860276%40Atlassian.JIRA.
[JIRA] (JENKINS-6957) Windows slave fails to find java
Title: Message Title Ilguiz Latypov commented on JENKINS-6957 Re: Windows slave fails to find java The "system cannot find the file specified" results from the poor service wrapper architecture that freezes the java.exe location in the "executable" XML tag inside its jenkins-slave.xml. https://mohitgoyal.co/2016/12/18/failed-to-start-jenkins-after-updating-java/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137054.1278976025000.6696.1578706740326%40Atlassian.JIRA.
[JIRA] (JENKINS-60353) Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404
Title: Message Title Karl Shultz commented on JENKINS-60353 Re: Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404 For the record, converting the plugin to use okhttp3 did not solve this problem. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203370.1575386738000.6694.1578705480182%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
hi [~fedepell], Hi mate hope you doing good?I just want one thing to make sure. I wanted to exclude some dlls (eg: dapper.dll) from including to this code-coverage reports; Such as in my source code their are dlls I don't want to use for use as packages for Code-Coverage reports. So when generating my unit tests Code-Coverage reports how can I exclude those dll files?Is their any code to exclude dll files in here? Such as when I running my RunTests.ps1 script for unit testing can I add some code to exclude dapper.dll file in below code ? {color:#ff} {color:#172b4d} This example is not worked. :(.{color} {color:#172b4d} Existing Code:{color} {color} {code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code} example: Code I want for Exclude dapper.dll:{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --exclude dapper.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message becau
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
hi [~fedepell], Hi mate hope you doing good?I just want one thing to make sure. I wanted to exclude some dlls (eg: dapper.dll) from including to this code-coverage reports; Such as in my source code their are dlls I don't want to use for use as packages for Code-Coverage reports. So when generating my unit tests Code-Coverage reports how can I exclude those dll files?Is their any code to exclude dll files in here? Such as when I running my RunTests.ps1 script for unit testing can I add some code to exclude dapper.dll file in below code ? {color:#ff} {color:#172b4d} This example is not worked. :(. {color} {color:#172b4d} Existing Code:{color}{color}{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code} Code I want for Exclude dapper.dll:{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --exclude dapper.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
hi [~fedepell], Hi mate hope you doing good?I just want one thing to make sure. I wanted to exclude some dlls (eg: dapper.dll) from including to this code-coverage reports; Such as in my source code their are dlls I don't want to use for use as packages for Code-Coverage reports. So when generating my unit tests Code-Coverage reports how can I exclude those dll files?Is their any code to exclude dll files in here? Such as when I running my RunTests.ps1 script for unit testing can I add some code to exclude dapper.dll file in below code ? {color:#ff} This example is not worked. :( . {color:#172b4d}Existing Code:{color}{color}{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code} Code I want for Exclude dapper.dll: {code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --exclude dapper.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
hi [~fedepell], Hi mate hope you doing good?I just want one thing to make sure. I wanted to exclude some dlls (eg: dapper.dll) from including to this code-coverage reports; Such as in my source code their are dlls I don't want to use for use as packages for Code-Coverage reports. So when generating my unit tests Code-Coverage reports how can I exclude those dll files?Is their any code to exclude dll files in here? Such as when I running my RunTests.ps1 script for unit testing can I add some code to exclude dapper.dll file in below code ? {color:#ff} This example is not worked. :( {color:#172b4d} Normal Existing Code:{color}{color}{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code} Code I want for Exclude dapper.dll: {code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --exclude dapper.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are s
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
hi [~fedepell], Hi mate hope you doing good?I just want one thing to make sure. I wanted to exclude some dlls (eg: dapper.dll) from including to this code-coverage reports; Such as in my source code their are dlls I don't want to use for use as packages for Code-Coverage reports. So when generating my unit tests Code-Coverage reports how can I exclude those dll files?Is their any code to exclude dll files in here? Such as when I running my RunTests.ps1 script for unit testing can I add some code to exclude dapper.dll file in below code ? {color:#ff} This example is not worked. :( {color:#172b4d} Normal Code:{color}{color}{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code} {color:#172b4d} Code I want for Exclude dapper.dll: {color} {code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --exclude dapper.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
hi [~fedepell], Hi mate hope you doing good?I just want one thing to make sure. I wanted to exclude some dlls (eg: dapper.dll) from including to this code-coverage reports; Such as in my source code their are dlls I don't want to use for use as packages for Code-Coverage reports. So when generating my unit tests Code-Coverage reports how can I exclude those dll files?Is their any code to exclude dll files in here? Such as when I running my RunTests.ps1 script for unit testing can I add some code to exclude dapper.dll file in below code ? {color:#ff} This example is not worked. :({color:#172b4d}Normal Code:{color} {color}{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code} {color:#ff} {color} {color:#172b4d}Code I want for Exclude dapper.dll:{color}{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --exclude dapper.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this mes
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
hi [~fedepell], Hi mate hope you doing good?I just want one thing to make sure. I wanted to exclude some dlls (eg: dapper.dll) from including to this code-coverage reports; Such as in my source code their are dlls I don't want to use for use as packages for Code-Coverage reports. So when generating my unit tests Code-Coverage reports how can I exclude those dll files?Is their any code to exclude dll files in here? Such as when I running my RunTests.ps1 script for unit testing can I add some code to exclude dapper.dll file in below code ? {color:#ff} This example is not worked. :( {color :#172b4d } Normal Code:{color} { color}{ code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll -- result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code}{color:#ff} {color}{color:#172b4d}Code I want for Exclude dapper.dll:{color}{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll -- exclude dapper.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
hi [~fedepell], Hi mate hope you doing good?I just want one thing to make sure. I wanted to exclude some dlls (eg: dapper.dll) from including to this code-coverage reports; Such as in my source code their are dlls I don't want to use for use as packages for Code-Coverage reports. So when generating my unit tests Code-Coverage reports how can I exclude those dll files?Is their any code to exclude dll files in here? Such as when I running my RunTests.ps1 script for unit testing can I add some code to exclude dapper.dll file in below code ? {color:#ff} This example is not worked. :({color}{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --exclude dapper.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.6662.1578704041743%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
hi [~fedepell], Hi mate hope you doing good?I just want one thing to make sure. I wanted to exclude some dlls (eg: dapper.dll) from including to this code-coverage reports; Such as in my source code their are dlls I don't want to use for use as packages for Code-Coverage reports. So when generating my unit tests Code-Coverage reports how can I exclude those dll files?Is their any code to exclude dll files in here? Such as when I running my RunTests.ps1 script for unit testing can I add some code to exclude dapper.dll file in below code ? {color:# FF ff } This example is not worked. :({color} {code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --exclude dapper.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.6658.1578703980369%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-59308
Re: Cobertura Code coverage all reports are showing in similar
hi [~fedepell], Hi mate hope you doing good?I just want one thing to make sure. I wanted to exclude some dlls (eg: dapper.dll) from including to this code-coverage reports , such ; Such as in my source code their are dlls I don't want to use for use as packages for Code-Coverage reports . So when generating my unit tests Code-Coverage reports how can I exclude those dll files?Is their any code to exclude dll files in here . ? Such as when I changed running my code for as below RunTests . But it doesn't work ps1 script for me unit testing can I add some code to exclude the packages dapper . dll file in below code ? {color:#FF} This example is not worked. :({color}{code:java}.$Opencover\OpenCover.Console.exe -target:"$NUNIT\nunit3-console.exe" -targetargs:".\Tests\NunitFast\NUnitTestsFast\$CONFIGURATION\net47\ServiceTestFast.dll --exclude dapper.dll --result=.\Tests\NunitFast\upstream-corewebservice-nunit-result.xml" -output:".\Tests\NunitFast\opencover-upstream-corewebservice-nunit-result.xml" -register:"user" {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.6656.1578703980331%40Atlassian.JIRA.
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Amila Gunathilake commented on JENKINS-59308 Re: Cobertura Code coverage all reports are showing in similar hi Federico Pellegrin, Hi mate hope you doing good? I just want one thing to make sure. I wanted to exclude some dlls from including to this code-coverage reports, such as in my source code their are dlls I don't want to use for use as packages for Code-Coverage. So when generating my unit tests Code-Coverage reports how can I exclude those dll files? Is their any code to exclude dll files in here. Such I changed my code for as below. But it doesn't work for me to exclude the packages. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201856.1568169015000.6650.1578703320248%40Atlassian.JIRA.
[JIRA] (JENKINS-60712) Copied managed config file should be removed when block ends
Title: Message Title Nikolas Falco commented on JENKINS-60712 Re: Copied managed config file should be removed when block ends It was so, this is a regression after update the config file provider plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203960.157858259.6648.1578702660173%40Atlassian.JIRA.
[JIRA] (JENKINS-60736) Add posibility to obtain SAML assertion after login using SAML plugin
Title: Message Title Seweryn Habdank-Wojewodzki edited a comment on JENKINS-60736 Re: Add posibility to obtain SAML assertion after login using SAML plugin OK. I understand see your opinion, but I do not understand it.We saw all tokens in logs on the server, so I am not sure, why it cannot be visible in form of environment variable.SVN plugin exposes SVN credentials in this ways as well - there is variable, which contains them. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203989.1578680312000.6646.1578698100114%40Atlassian.JIRA.
[JIRA] (JENKINS-60736) Add posibility to obtain SAML assertion after login using SAML plugin
Title: Message Title Seweryn Habdank-Wojewodzki commented on JENKINS-60736 Re: Add posibility to obtain SAML assertion after login using SAML plugin OK. I understand your opinion, but I do not understand it. We saw all tokens in logs on the server, so I am not sure, why it cannot be visible in form of environment variable. SVN plugin exposes SVN credentials in this ways as well - there is variable, which contains them. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203989.1578680312000.6644.1578698040127%40Atlassian.JIRA.
[JIRA] (JENKINS-60737) EC2 ASG Slave taken offline in middle of a job for no diskspace left when multiple executors given to a slave
Title: Message Title Arindom Sarkar created an issue Jenkins / JENKINS-60737 EC2 ASG Slave taken offline in middle of a job for no diskspace left when multiple executors given to a slave Issue Type: Bug Assignee: Chad Schmutzer Components: ec2-fleet-plugin Created: 2020-01-10 22:38 Priority: Minor Reporter: Arindom Sarkar slaves spawned off by EC2 fleet plugin were taken offline with this message. This happens when multiple executors assigned to the slave, and jobs are allotted to them concurrently and every jobs checkout a git repository. Is there a way to avoid this? 13:31:12 nonprodslave2 i-0dd32 was marked offline: Node is being removed Receiving objects: 79% (88346/111053), 179.52 MiB | 2.03 MiB/s fatal: write error: No space left on device*13:30:29* fatal: index-pack failed*13:30:29* Add Comment
[JIRA] (JENKINS-60736) Add posibility to obtain SAML assertion after login using SAML plugin
Title: Message Title Ivan Fernandez Calvo closed an issue as Won't Do Jenkins / JENKINS-60736 Add posibility to obtain SAML assertion after login using SAML plugin Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203989.1578680312000.6640.1578694320431%40Atlassian.JIRA.
[JIRA] (JENKINS-60736) Add posibility to obtain SAML assertion after login using SAML plugin
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-60736 Re: Add posibility to obtain SAML assertion after login using SAML plugin SAML plugin does not manage anything on builds, it only makes the authentication and authorization part, that's it. The token provided by the IdP is in the browser of the user, expose it directly as an environment variable is a security issue. So the only implementation for your use case is a plugin that grabs the token from the browser and creates a credential in the user namespace with the value, then you can select this credential as a parameter for your jobs, thus this something that does not fit on the SAML plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203989.1578680312000.6638.1578694320389%40Atlassian.JIRA.
[JIRA] (JENKINS-23601) Modify Audit Trail plugin to log information based on user type
Title: Message Title Pierre Beitz closed an issue as Incomplete Jenkins / JENKINS-23601 Modify Audit Trail plugin to log information based on user type Change By: Pierre Beitz Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155983.1403863263000.6635.1578688860357%40Atlassian.JIRA.
[JIRA] (JENKINS-23601) Modify Audit Trail plugin to log information based on user type
Title: Message Title Pierre Beitz commented on JENKINS-23601 Re: Modify Audit Trail plugin to log information based on user type Closing for now please reopen if you still need the feature and have more details. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155983.1403863263000.6633.1578688860327%40Atlassian.JIRA.
[JIRA] (JENKINS-49499) Jenkins admin logs through Logger List not getting captured
Title: Message Title Pierre Beitz commented on JENKINS-49499 Re: Jenkins admin logs through Logger List not getting captured Closing for now, please reopen if you still lack the events. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188390.1518428802000.6629.1578688680260%40Atlassian.JIRA.
[JIRA] (JENKINS-49499) Jenkins admin logs through Logger List not getting captured
Title: Message Title Pierre Beitz closed an issue as Incomplete Jenkins / JENKINS-49499 Jenkins admin logs through Logger List not getting captured Change By: Pierre Beitz Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188390.1518428802000.6631.1578688680288%40Atlassian.JIRA.
[JIRA] (JENKINS-40517) Allow changing delimiter in log output
Title: Message Title Pierre Beitz updated JENKINS-40517 Jenkins / JENKINS-40517 Allow changing delimiter in log output Change By: Pierre Beitz Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177193.1481911536000.6619.1578688500727%40Atlassian.JIRA.
[JIRA] (JENKINS-12848) Log parameters used for a build
Title: Message Title Pierre Beitz started work on JENKINS-12848 Change By: Pierre Beitz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.143306.1329845988000.6622.1578688500776%40Atlassian.JIRA.
[JIRA] (JENKINS-12848) Log parameters used for a build
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-12848 Log parameters used for a build Change By: Pierre Beitz Assignee: Alan Harder Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.143306.1329845988000.6625.1578688500827%40Atlassian.JIRA.
[JIRA] (JENKINS-12848) Log parameters used for a build
Title: Message Title Pierre Beitz updated JENKINS-12848 Jenkins / JENKINS-12848 Log parameters used for a build Change By: Pierre Beitz Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.143306.1329845988000.6627.1578688500848%40Atlassian.JIRA.
[JIRA] (JENKINS-60621) unable to add sonar project key in the jenkins.
Title: Message Title Michael Svendsen commented on JENKINS-60621 Re: unable to add sonar project key in the jenkins. We just ran into this error today and discovered that the issue was a trailing `/` in our sonarqube instance url configuration. So under "Manage Jenkins" -> "Configure System" make sure you don't have a trailing `/` on your instance url under the "Quality Gates - Sonarqube" section. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203852.1577958715000.6617.1578687480169%40Atlassian.JIRA.
[JIRA] (JENKINS-60723) Github PR from jenkins
Title: Message Title Brian Saville commented on JENKINS-60723 Re: Github PR from jenkins reddi sekhara, I own the GitHub Pull Request Comment Build Plugin, which is very different from the GHPRB plugin you are trying to configure. I've reassigned components, good luck. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203972.1578646189000.6614.1578686460192%40Atlassian.JIRA.
[JIRA] (JENKINS-60723) Github PR from jenkins
Title: Message Title Brian Saville updated an issue Jenkins / JENKINS-60723 Github PR from jenkins Change By: Brian Saville Component/s: ghprb-plugin Component/s: github-pr-comment-build-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203972.1578646189000.6610.1578686400306%40Atlassian.JIRA.
[JIRA] (JENKINS-60723) Github PR from jenkins
Title: Message Title Brian Saville assigned an issue to Unassigned Jenkins / JENKINS-60723 Github PR from jenkins Change By: Brian Saville Assignee: Brian Saville Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203972.1578646189000.6612.1578686400358%40Atlassian.JIRA.
[JIRA] (JENKINS-54748) Memory leak in test-results-analyzer causes Jenkins to crash
Title: Message Title Adam Grant commented on JENKINS-54748 Re: Memory leak in test-results-analyzer causes Jenkins to crash This is an urgent issue for my Jenkins service. Any updates? Can we make a bounty? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195552.1542794187000.6603.1578685200266%40Atlassian.JIRA.
[JIRA] (JENKINS-60725) "Added a missed class for missing class telemetry" on AdoptOpenJDK 11
Title: Message Title ethorsa updated an issue Jenkins / JENKINS-60725 "Added a missed class for missing class telemetry" on AdoptOpenJDK 11 Change By: ethorsa Issue Type: New Feature Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203974.1578649121000.6600.1578681360399%40Atlassian.JIRA.
[JIRA] (JENKINS-60736) Add posibility to obtain SAML assertion after login using SAML plugin
Title: Message Title Seweryn Habdank-Wojewodzki created an issue Jenkins / JENKINS-60736 Add posibility to obtain SAML assertion after login using SAML plugin Issue Type: New Feature Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2020-01-10 18:18 Environment: Linux RedHat, SAML Plugin 1.1.4, Jenkins 2.204.1. Priority: Major Reporter: Seweryn Habdank-Wojewodzki Dears, After login to Jenkins using SAML plugin user may perform some actions like preparing automatic deployment after build or calling some other tools over the REST APIs, but those actions (tools) require authentication (e.g. in form of valid SAML assertion). The feature would be to give build tasks access to SAML assertion e.g. via temporary created environment variable, how it is done for build name or build ID and bunch of others. How it would be possible to implement? Perhaps we can provide some implementation proposal, but we shall agree on feature design. Best regards, Seweryn. Add Comment
[JIRA] (JENKINS-42811) Vsphere Cloud plugin stops working after a number of builds
Title: Message Title pjdarton commented on JENKINS-42811 Re: Vsphere Cloud plugin stops working after a number of builds According to that log message, you've set a max=10 for instances from that template. So, unless you've got other templates defined on that cloud, you're never going to reach 50 as that template is capped at 10 - that's why it's saying it's 100% full when it's got 10 instances provisioned with max=10. You either need to allow that template to spawn an unlimited number of instances (capped only by the cloud instance cap), or to spawn a larger number of instances, or to define other templates such that the sum of all templates' max fields comes to at least the cloud's instance cap. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179810.1489595244000.6594.1578678060182%40Atlassian.JIRA.
[JIRA] (JENKINS-60685) Kubernetes plugin crashes from v1.22.4
Title: Message Title MARY Olivier commented on JENKINS-60685 Re: Kubernetes plugin crashes from v1.22.4 Fixed for me since 1.22.5 on kubernetes 1.15.6 will try in 1.16.3 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203929.1578472634000.6592.1578677580228%40Atlassian.JIRA.
[JIRA] (JENKINS-60735) No more trim on kubernetes labels
Title: Message Title
MARY Olivier updated an issue
Jenkins / JENKINS-60735
No more trim on kubernetes labels
Change By:
MARY Olivier
HimI switched 1.21.3 to 1.22.5 Kubernetes Plugin versionSince switch I had this error : {code:java}Failed to count the # of live instances on Kubernetesio.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://kubernetes.default/api/v1/namespaces/prod-jenkins/pods?labelSelector=jenkins%3Dslave%2Cjenkins%2Flabel%3Dlinux_alpine_openjdk_jdk8_4g_. Message: unable to parse requirement: invalid label value: "linux_alpine_openjdk_jdk8_4g_": at key: "jenkins/label": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue', or 'my_value', or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?'). Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=unable to parse requirement: invalid label value: "linux_alpine_openjdk_jdk8_4g_": at key: "jenkins/label": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue', or 'my_value', or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?'), metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}). at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:510) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:449) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:413) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:372) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:354) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.listRequestHelper(BaseOperation.java:153) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:620) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:69) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.getActiveSlavePods(KubernetesCloud.java:608) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:593) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:535) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:725) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:332) at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:63) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:819) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:70) at jenkins.security.ImpersonatingScheduledExecutorService$1.ru
[JIRA] (JENKINS-60735) No more trim on kubernetes labels
Title: Message Title
MARY Olivier updated an issue
Jenkins / JENKINS-60735
No more trim on kubernetes labels
Change By:
MARY Olivier
HimI switched 1.21.3 to 1.22.5 Kubernetes Plugin versionSince switch I had this error : {quote}Failed to count the # of live instances on Kubernetes io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://kubernetes.default/api/v1/namespaces/prod-jenkins/pods?labelSelector=jenkins%3Dslave%2Cjenkins%2Flabel%3Dlinux_alpine_openjdk_jdk8_4g_. Message: unable to parse requirement: invalid label value: "linux_alpine_openjdk_jdk8_4g_": at key: "jenkins/label": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue', or 'my_value', or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?'). Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=unable to parse requirement: invalid label value: "linux_alpine_openjdk_jdk8_4g_": at key: "jenkins/label": a valid label must be an empty string or consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue', or 'my_value', or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])?'), metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}). at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:510) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:449) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java {code : 413) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport. java :372) } at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:354) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.listRequestHelper(BaseOperation.java:153) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:620) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:69) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.getActiveSlavePods(KubernetesCloud.java:608) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:593) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:535) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:725) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:332) at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:63) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:819) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:70) at jenkins.security.ImpersonatingSchedule
[JIRA] (JENKINS-60735) No more trim on kubernetes labels
Title: Message Title MARY Olivier created an issue Jenkins / JENKINS-60735 No more trim on kubernetes labels Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2020-01-10 17:27 Environment: Kubernetes 1.15.6 Kubernetes-plugin 1.22.5 Jenkins LTS 1.204.1 Labels: plugin jenkins kubernetes kubernetes-plugin Priority: Major Reporter: MARY Olivier Him I switched 1.21.3 to 1.22.5 Kubernetes Plugin version Since switch I had this error : Failed to count the # of live instances on Kubernetes io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://kubernetes.default/api/v1/namespaces/prod-jenkins/pods?labelSelector=jenkins%3Dslave%2Cjenkins%2Flabel%3Dlinux_alpine_openjdk_jdk8_4g_. Message: unable to parse requirement: invalid label value: "linux_alpine_openjdk_jdk8_4g_": at key: "jenkins/label": a valid label must be an empty string or consist of alphanumeric characters, '', '' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue', or 'my_value', or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9_.])?[A-Za-z0-9])?'). Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=unable to parse requirement: invalid label value: "linux_alpine_openjdk_jdk8_4g": at key: "jenkins/label": a valid label must be an empty string or consist of alphanumeric characters, '', '_' or '.', and must start and end with an alphanumeric character (e.g. '
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title Vipul Madaan commented on JENKINS-54502 Re: Jenkins crashed when a running build was aborted. Hello My issue got resolved . I downloaded the Executable of Jenkins and instead of running an upgrade from UI Or replacing a jar file Idid use newly downloaded executable to do a fresh install of newer version on top of my previous version . So now I have newer version and don’t have any crashes . I have tested it for a while and I am not able to reproduce the crash . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195272.1541539669000.6572.1578677160456%40Atlassian.JIRA.
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title ingolfur Thorisson commented on JENKINS-54502 Re: Jenkins crashed when a running build was aborted. Is this still an issue? I'm also seeing this behaviour on 2.204.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195272.1541539669000.6557.1578676440328%40Atlassian.JIRA.
[JIRA] (JENKINS-60216) Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible
Title: Message Title Devin Nusbaum commented on JENKINS-60216 Re: Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible Bogomil Vasilev If your builds were working before the change, then you should be able to just change the type of the parameter on the downstream job to a string parameter so that no conversion happens, since that is what the previous behavior would have been (there was no conversion previously, so you were just passing a string parameter, which the downstream job apparently handles correctly, so I don't think the triggered builds were actually using the Node and Label Parameter Plugin, you just thought they were (this doesn't apply if you were also building the downstream job via the UI, since I think node and label parameters would work in that context)). If you want to keep use the Node and Label Parameter Plugin, then I would start watching and vote on JENKINS-43720 and JENKINS-47571. Max Matissek I think the Extensible Choice Parameter Plugin is a special case, and we should still convert the parameters for them but not log a warning, similarly to what is done now for regular Choice Parameters. Can you please file a new bug for that issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203189.1574194043000.6555.1578
[JIRA] (JENKINS-59259) sshAgent step does not survive agent disconnect/reconnect
Title: Message Title Jesse Glick updated JENKINS-59259 Jenkins / JENKINS-59259 sshAgent step does not survive agent disconnect/reconnect Change By: Jesse Glick Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201727.1567754679000.6552.1578675180180%40Atlassian.JIRA.
[JIRA] (JENKINS-59259) sshAgent step does not survive agent disconnect/reconnect
Title: Message Title Jesse Glick updated JENKINS-59259 Jenkins / JENKINS-59259 sshAgent step does not survive agent disconnect/reconnect Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 1.18 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201727.1567754679000.6550.1578674820617%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title
Dominik Bartholdi edited a comment on JENKINS-60407
Re: Launched instances cannot reach public internet (regression)
I was able to fix the issue by adding this to the JasC Config of the ec2 plugin: {code:java} associatePublicIp: true { { code } }
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.6548.1578673920280%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title
Dominik Bartholdi commented on JENKINS-60407
Re: Launched instances cannot reach public internet (regression)
I was able to fix the issue by adding this to the JasC Config of the ec2 plugin: associatePublicIp: true {{}}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.6545.1578673860283%40Atlassian.JIRA.
[JIRA] (JENKINS-60734) Replace js-builder with webpack
Title: Message Title Félix Queiruga Balado updated an issue Jenkins / JENKINS-60734 Replace js-builder with webpack Change By: Félix Queiruga Balado Right now Jenkins uses a combination of [js-builder|https://github.com/jenkinsci/js-builder] and gulp as the toolchain to build the frontend assets.There are many reasons to replace js-builder with a modern, industry-standard tool: * It does not support many new technologies and techniques commonly used nowadays, like post-css. * It is not being actively maintained. * It is a tool used only within the Jenkins project. This and the lack of comprehensive documentation makes it difficult for developers to modify or extend the toolchain. * It is based on outdated tools (i.e. browserify) and uses a module system that is incompatible with modern JS build tools.I propose basing the new frontend toolchain on [webpack|https://webpack.js.org/]. It is the tool that has the more usage, support and customizability.h3. The js-builder ecosystemjs-builder offers the possibility, using some sibling libraries ([js-modules|https://github.com/jenkinsci/js-modules], [js-libs|https://github.com/jenkinsci/js-libs]), to have shared libraries across multiple projects running on the same window. For example, if both Jenkins core and a plugin use the same version of jquery, it would only be loaded once.While this can seem like a great idea, having this behaviour on Core can be problematic. Having core load its own libraries would only add an extra 50-100KB of JS code. It introduces a huge maintainability burden and locks the project into using js-builder & friends.h3. Planned changesThe goal of this improvement is to replace js-builder with webpack, and use NPM versions of the js-libs used on the project (handlebars, jquery, bootstrap). Add Comment
[JIRA] (JENKINS-60734) Replace js-builder with webpack
Title: Message Title Félix Queiruga Balado created an issue Jenkins / JENKINS-60734 Replace js-builder with webpack Issue Type: Improvement Assignee: Unassigned Components: core Created: 2020-01-10 16:08 Priority: Minor Reporter: Félix Queiruga Balado Right now Jenkins uses a combination of js-builder and gulp as the toolchain to build the frontend assets. There are many reasons to replace js-builder with a modern, industry-standard tool: It does not support many new technologies and techniques commonly used nowadays, like post-css. It is a tool used only within the Jenkins project. This and the lack of comprehensive documentation makes it difficult for developers to modify or extend the toolchain. It is based on outdated tools (i.e. browserify) and uses a module system that is incompatible with modern JS build tools. I propose basing the new frontend toolchain on webpack. It is the tool that has the more usage, support and customizability. The js-builder ecosystem js-builder offers the possibility, using some sibling libraries (js-modules, js-libs), to have shared libraries across multiple projects running on the same window. For example, if both Jenkins core and a plugin use the same version of jquery, it would only be loaded once. While this can seem like a great idea, having this behaviour on Core can be problematic. Having core load its own libraries would only add an extra 50-100KB of JS code. It introduces a huge maintainability burden and locks the project into using js-builder & friends. Planned changes The goal of this improvement is to replace js-builder with webpack, and use NPM versions of the js-libs used on the project (handlebars, jquery, bootstrap).
[JIRA] (JENKINS-60733) Collapse by defaults kubernetes sections in Jenkins Global Configuration
Title: Message Title Mathieu Delrocq created an issue Jenkins / JENKINS-60733 Collapse by defaults kubernetes sections in Jenkins Global Configuration Issue Type: Improvement Assignee: Unassigned Components: kubernetes-plugin Created: 2020-01-10 15:28 Labels: plugin jenkins Priority: Minor Reporter: Mathieu Delrocq I purpose to add a default collapse to kubernetes cloud sections in the global configuration of Jenkins. In fact, we have a lot of kubernetes clouds and templates configured and it become difficult to navigate in the global configuration. You can take inspiration of docker-plugin wich implements it. Add Comment
[JIRA] (JENKINS-39559) Job Config History Plugin saving config for a node other than the one being edited
Title: Message Title Robin Schulz commented on JENKINS-39559 Re: Job Config History Plugin saving config for a node other than the one being edited The problem here is that ComputerListener's methods don't provide information on which node's config has changed. So every node's config is persisted. Having activated the option to not save duplicates, this should still only save the config of the node for which you changed something unless you haven't altered other config.xmls manually or in another way that has not triggered the Saveable listener. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176111.1478531414000.6536.1578669780415%40Atlassian.JIRA.
[JIRA] (JENKINS-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Raphael Pionke updated JENKINS-55202 PR with a proper fix: https://github.com/jenkinsci/performance-signature-dynatrace-plugin/pull/81 Jenkins / JENKINS-55202 Performance Signature Plugin: JAXB API is missing with Java 11 Change By: Raphael Pionke Status: Reopened Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+un
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title Dominik Bartholdi commented on JENKINS-60407 Re: Launched instances cannot reach public internet (regression) we have the exact same issue, I think this is caused by JENKINS-58578 I did some manual testing and setting a public IP on the agent solves the issue - this IP is set automatically on an agent launched with ec2-plugin:1.45 -> we had to go back to 1.45 too Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.6508.1578668220220%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title László Kovács commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI It seems like a recurring problem with security plugins no matter what Jenkins versions we are using. With 2.138.3 Jenkins version after updating script-security plugin to version to 1.68 and permissive-script-security plugin is 0.5. We don't use Prometheus plugin, but the issue is still the same. As I see new permissive-script-security plugin version (0.5) has complications with several other plugin and there is no fix for it currently. So you have to downgrade plugins to solve the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.6493.1578667740670%40Atlassian.JIRA.
[JIRA] (JENKINS-1877) Explanatory message at prepare for shutdown
Title: Message Title jpena updated an issue Jenkins / JENKINS-1877 Explanatory message at prepare for shutdown Change By: jpena Comment: +1. It would be super useful Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.131950.1213676576000.6491.1578667141554%40Atlassian.JIRA.
[JIRA] (JENKINS-42811) Vsphere Cloud plugin stops working after a number of builds
Title: Message Title
Jorge Peña commented on JENKINS-42811
Re: Vsphere Cloud plugin stops working after a number of builds
Hi pjdarton thank you for replying. Yes, when I wrote error I refered to the warning printed on the post above. After creating the issue I realised that having the value 2147483647 is just cosmetic. We are relying on this plugin for creating and destroying jenkins agents on demand. This issue keeps happening with newer versions of the plugin so we are running a job recurrently in our Jenkins instance to avoid this issue. We didn't experience issues of memory. We had issues of VMs with duplicated names but I am not sure it was related with this workaround. We developed a small script that would destroy the virtual machines on vmware that weren't present in Jenkins, after all these are linked clones and were re-created again. Currently we are running Jenkins version: 2.150.3 vsphere-cloud plugin: 2.21 This is a piece of the log where it should create a new jenkins agent (the last one since we set up a hard limit of 50 agents) but it didn't create it
Jan 10, 2020 3:11:32 PM INFO org.jenkinsci.plugins.vSphereCloud provision
provision(xcode-10.1,20): Provisioning 0 new =[]
Jan 10, 2020 3:11:32 PM INFO org.jenkinsci.plugins.vSphereCloud calculateMaxAdditionalSlavesPermitted
There are 49 VMs in this cloud. The instance cap for the cloud is 50, so we have room for more
Jan 10, 2020 3:11:32 PM INFO org.jenkinsci.plugins.vSphereCloud provision
provision(xcode-11.1,6): 0 existing slaves (=0 executors), templates available are [Template[prefix=sod-xxx-01, provisioned=[sod-xxx-011, sod-xxx-0110, sod-xxx-012, sod-xxx-013, sod-xxx-014, sod-xxx-015, sod-xxx-016, sod-xxx-017, sod-xxx-018, sod-xxx-019], planned=[], unwanted={}, max=10, fullness=100.000%]]
That piece of log just keeps repeating over and over. After running the job with the mentioned workaround it starts creating agents again. Regards,
Add Comment
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title Karolina Arancibia Valuskova updated an issue Jenkins / JENKINS-59431 When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node Change By: Karolina Arancibia Valuskova Component/s: parameterized-trigger-plugin Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202015.1568813775000.6453.1578666781051%40Atlassian.JIRA.
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title Karolina Arancibia Valuskova updated an issue Jenkins / JENKINS-59431 When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node Change By: Karolina Arancibia Valuskova Priority: Critical Blocker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202015.1568813775000.6455.1578666781160%40Atlassian.JIRA.
[JIRA] (JENKINS-60732) Node is repeated in execution
Title: Message Title Karolina Arancibia Valuskova created an issue Jenkins / JENKINS-60732 Node is repeated in execution Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin, parameterized-trigger-plugin Created: 2020-01-10 14:31 Labels: nodelabelparameter parameterized-trigger Priority: Blocker Reporter: Karolina Arancibia Valuskova When using All Nodes For Label Factory, the nodes in the execution are detected correctly (per log under job//build#) but the nodes that the triggered job actually runs in are not right, and a Node is used more than once (usually the first discovered). Add Comment
[JIRA] (JENKINS-56764) Pipeline fails on some AMI images / node types because of Broken Pipe
Title: Message Title Alexander Bachmeier commented on JENKINS-56764 Re: Pipeline fails on some AMI images / node types because of Broken Pipe We are also encountering this issue (EKS v1.14.9). Has anyone been able to make progress on this issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198407.1553610802000.6446.1578666540588%40Atlassian.JIRA.
[JIRA] (JENKINS-60716) Loss of exception detail in LogRotator failures
Title: Message Title Jesse Glick commented on JENKINS-60716 Re: Loss of exception detail in LogRotator failures Yes, the regression was detected in 2.204.1. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203964.1578599933000.6422.1578665940220%40Atlassian.JIRA.
[JIRA] (JENKINS-60539) Make build history timeline limit configurable (BuildTimelineWidget)
Title: Message Title Guillaume MAHIEUX commented on JENKINS-60539 Re: Make build history timeline limit configurable (BuildTimelineWidget) Hi, any news on this? Thank you! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203642.1576755244000.6413.1578665340057%40Atlassian.JIRA.
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title Karolina Arancibia Valuskova updated an issue Jenkins / JENKINS-59431 When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node Change By: Karolina Arancibia Valuskova Comment: There is a similar problem when there are two groups of nodes : 6 nodes with TESTPC label and 6 nodes with PRODPC label. The plugin would send the run call to all of them regardless of the label they have, this is a big issue of broken functionality. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202015.1568813775000.6406.1578664860589%40Atlassian.JIRA.
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title
Karolina Arancibia Valuskova updated an issue
Jenkins / JENKINS-59431
When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Change By:
Karolina Arancibia Valuskova
I've 6 similar nodes, that share a label "TESTPC" when I configure the job to trigger with that label the plugin works fine as it triggers on all 6 nodes.{{I have added the label "TESTPC1", "TESTPC2", and so on in each node since every now and then we want to run the job on only one specific node, however what ends up happening is that the job is run in any of the computers that have the "TESTPC" label and only in one (most usually not the intended one). I also tried putting a label that doesn't share the any letter with the other labels on my node ("banana") but the problem still persists.}}{{-The same applies when I have groups of different nodes with a single label. }}{{-There is the same problem with the Node - Factory part of the plugin.}}{{Here is the log of a build that should have run on TESTPC1,2 and 3, but instead run on TESPC 5 (twice) and PRODPC6 (PC with different label)}}{code:java}Started by user [8mha:4GcLNmTz8oi6tKjMMjxnTRRbUCKLrip2lyOZlKIRHdypmx+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAyuEgZ+/dLi1CL94syUktTiktQiAKFXgYvE [0m Running as SYSTEM Building remotely on [8mha:4JNmtgR2g18637CcH5OrJjPvakAXl1al6Pij6HjPxIbMnR+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz2EgZB/eT83ILSktQi/WBnR78AZzMAOdpwt8Y= [0mTESTPC6 (TESTPC) in workspace C:/jenkins/workspace/ define: [LabelParameterValue: NODELABEL=TESTPC1] define: [LabelParameterValue: NODELABEL=TESTPC2] define: [LabelParameterValue: NODELABEL=TESTPC3] Triggering projects: [8mha:4GEYBZuNUHdwWOzB3SOyspk29pTLutRnS9YcoIxnTpKWlx+LCP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMgQKGEQ08/KT9J3zSvLLMrPy03NKwlOLSkt0AcArVNUhJs= [0mFinished: SUCCESS{code}Which seems to indicate that the job was send to build before the nodes were selected.
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title
Karolina Arancibia Valuskova updated an issue
Jenkins / JENKINS-59431
When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Change By:
Karolina Arancibia Valuskova
I've 6 similar nodes, that share a label "TESTPC" when I configure the job to trigger with that label the plugin works fine as it triggers on all 6 nodes.{{I have added the label "TESTPC1", "TESTPC2", and so on in each node since every now and then we want to run the job on only one specific node, however what ends up happening is that the job is run in any of the computers that have the "TESTPC" label and only in one (most usually not the intended one). I also tried putting a label that doesn't share the any letter with the other labels on my node ("banana") but the problem still persists.}}{{-The same applies when I have groups of different nodes with a single label. i.e. 12 nodes 6 with TESTPC and 6 with PRODPC }} {{-There is the same problem with the Node - Factory part of the plugin.}}{{Here is the log of a build that should have run on TESTPC1,2 and 3, but instead run on TESPC 5 (twice) and PRODPC6 (PC with different label)}}{code:java}Started by user [8mha:4GcLNmTz8oi6tKjMMjxnTRRbUCKLrip2lyOZlKIRHdypmx+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAyuEgZ+/dLi1CL94syUktTiktQiAKFXgYvE [0m Running as SYSTEM Building remotely on [8mha:4JNmtgR2g18637CcH5OrJjPvakAXl1al6Pij6HjPxIbMnR+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz2EgZB/eT83ILSktQi/WBnR78AZzMAOdpwt8Y= [0mTESTPC6 (TESTPC) in workspace C:/jenkins/workspace/ define: [LabelParameterValue: NODELABEL=TESTPC1] define: [LabelParameterValue: NODELABEL=TESTPC2] define: [LabelParameterValue: NODELABEL=TESTPC3] Triggering projects: [8mha:4GEYBZuNUHdwWOzB3SOyspk29pTLutRnS9YcoIxnTpKWlx+LCP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMgQKGEQ08/KT9J3zSvLLMrPy03NKwlOLSkt0AcArVNUhJs= [0mFinished: SUCCESS{code}Which seems to indicate that the job was send to build before the nodes were selected.
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title
Karolina Arancibia Valuskova updated an issue
Jenkins / JENKINS-59431
When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Change By:
Karolina Arancibia Valuskova
I've 6 similar nodes, that share a label "TESTPC" when I configure the job to trigger with that label the plugin works fine as it triggers on all 6 nodes. {{ I have added the label "TESTPC1", "TESTPC2", and so on in each node since every now and then we want to run the job on only one specific node, however what ends up happening is that the job is run in any of the computers that have the "TESTPC" label and only in one (most usually not the intended one). I also tried putting a label that doesn't share the any letter with the other labels on my node ("banana") but the problem still persists. }}{{-The same applies when I have groups of different nodes with a single label. }}{{-There is the same problem with the Node - Factory part of the plugin.}}{{Here is the log of a build that should have run on TESTPC1,2 and 3, but instead run on TESPC 5 (twice) and PRODPC6 (PC with different label)}}{code:java}Started by user [8mha:4GcLNmTz8oi6tKjMMjxnTRRbUCKLrip2lyOZlKIRHdypmx+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAyuEgZ+/dLi1CL94syUktTiktQiAKFXgYvE [0m Running as SYSTEM Building remotely on [8mha:4JNmtgR2g18637CcH5OrJjPvakAXl1al6Pij6HjPxIbMnR+LCP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAz2EgZB/eT83ILSktQi/WBnR78AZzMAOdpwt8Y= [0mTESTPC6 (TESTPC) in workspace C:/jenkins/workspace/ define: [LabelParameterValue: NODELABEL=TESTPC1] define: [LabelParameterValue: NODELABEL=TESTPC2] define: [LabelParameterValue: NODELABEL=TESTPC3] Triggering projects: [8mha:4GEYBZuNUHdwWOzB3SOyspk29pTLutRnS9YcoIxnTpKWlx+LCP9b85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMgQKGEQ08/KT9J3zSvLLMrPy03NKwlOLSkt0AcArVNUhJs= [0mFinished: SUCCESS{code}Which seems to indicate that the job was send to build before the nodes were selected.
[JIRA] (JENKINS-60731) Review return values in the Computer API being used by node monitors
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60731 Review return values in the Computer API being used by node monitors Change By: Oleg Nenashev Issue Type: Improvement Task Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203982.1578663465000.6398.1578663480218%40Atlassian.JIRA.
[JIRA] (JENKINS-60731) Review return values in the Computer API being used by node monitors
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-60731 Review return values in the Computer API being used by node monitors Issue Type: Improvement Assignee: Oleg Nenashev Components: core Created: 2020-01-10 13:37 Priority: Minor Reporter: Oleg Nenashev We could probably generalize the API a bit. See https://github.com/jenkinsci/jenkins/pull/4271#pullrequestreview-341032013 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60507) Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled
Title: Message Title Konstantin Demenkov edited a comment on JENKINS-60507 Re: Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled I have the same issue on latest 2. 201 204.1 LTS. It appears pretty often (10% of jobs) in working with proxmox slaves over proxmox cloud plugin and jnlp. I suspect some incompatibility in timeouts/ connection's logic between master and proxmox slaves, but really don't know, why it happens. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203598.157651039.6394.1578660540277%40Atlassian.JIRA.
[JIRA] (JENKINS-60687) Extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB
Title: Message Title Aleksi Simell commented on JENKINS-60687 Re: Extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB Make a fork from the plugin repository and create a new file for the generator. Pretty good guidelines can be found from other generators. You will most probably need the `buildAction` from the plugin and then it's just looking at the Serenity plugin code to get the correct data. Finally, you will need to call the generator inside `InfluxDbPublicationService.java` to actually use the generator. Additionally, unit tests for the generator would be nice I know the plugin lacks sufficient unit tests, but there should be some tests for other generators you can use as a base. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203931.1578474488000.6392.1578660300144%40Atlassian.JIRA.
[JIRA] (JENKINS-59431) When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node
Title: Message Title Karolina Arancibia Valuskova commented on JENKINS-59431 Re: When using node label's "All Nodes for Label Factory" on single label node, it runs job on wrong node There is a similar problem when there are two groups of nodes : 6 nodes with TESTPC label and 6 nodes with PRODPC label. The plugin would send the run call to all of them regardless of the label they have, this is a big issue of broken functionality. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202015.1568813775000.6389.1578659700107%40Atlassian.JIRA.
[JIRA] (JENKINS-58207) 2.181 JNA update breaks NegotiateSSO
Title: Message Title Stefan Rademacher commented on JENKINS-58207 Re: 2.181 JNA update breaks NegotiateSSO I checked it on our two jenkins servers. Metadata is up-to-date on both, but none shows the 1.4 version. I am going to upgrade manually, if no one else has this issue. Thx Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200266.1561541748000.6377.1578659640519%40Atlassian.JIRA.
[JIRA] (JENKINS-58194) Unsatisfied dependencies gitlab-hook
Title: Message Title Elek Akos commented on JENKINS-58194 Re: Unsatisfied dependencies gitlab-hook Install Java 8 java version "1.8.0_231" Java(TM) SE Runtime Environment (build 1.8.0_231-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.231-b11, mixed mode) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200249.156149246.6361.1578658980409%40Atlassian.JIRA.
[JIRA] (JENKINS-60730) Add possibility to exclude branches and tags older than X days
Title: Message Title Daniel Steiert created an issue Jenkins / JENKINS-60730 Add possibility to exclude branches and tags older than X days Issue Type: New Feature Assignee: Unassigned Components: github-branch-source-plugin Created: 2020-01-10 12:20 Priority: Major Reporter: Daniel Steiert Problem Statement We have had problems with anything that reacts to multiple branches or tags for quite some time now. Any form of multibranch plugin or plugins that check for tags, Pull Requests or anything like it. They all cause issues as soon as there is either an upgrade in which there are no logs from previous builds, after a disaster with data-loss or when re-running certain seed-jobs that modify (e.g. multibranch-) configurations. The issue presents itself in the form of complications due to rebuilds of every single branch, PR and tag for every single repository, at the same time. This might not be a problem for small and very short builds, but it becomes a huge issue for anything that runs longer than 5 minutes. Firstly, this blocks the ability to build current and urgent jobs (since all slaves are busy building old branches/tags/PRs). Secondly, it requires immense amounts of resources (often times all of them, even if that means 120+ x 16 GB with 4 cores slaves) that wouldn't have to be used necessarily. Thirdly, the Jenkins Master almost always suffers from further crashes or erratic behaviour, since a lot of jobs are queueing up, all slaves are engaged and there is in general a lot of load on the system (unnecessarily so). This kind of behaviour can not only be experienced on older environments with static slaves and everything running on VMs, but more specifically on more modern setups in which the Jenkins is created and runs stateless in a Kubernetes cluster. If there was a way to restrict or ignore old/stale branches/tags/PRs, basically all of the above mentioned problems could be solved. Feature Proposal The github-branch-source-plugin is one of the plugins that caus
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Gregory Zussa commented on JENKINS-55787 Re: Switch labels from entry to checkbox Regarding the Datadog Plugin, we should be good with our latest release 1.0.0. Let us know if this is not the case. - https://github.com/jenkinsci/datadog-plugin/blob/master/src/main/resources/org/datadog/jenkins/plugins/datadog/DatadogGlobalConfiguration/config.jelly#L77-L81 - https://github.com/jenkinsci/datadog-plugin/blob/master/src/main/resources/org/datadog/jenkins/plugins/datadog/DatadogJobProperty/config.jelly#L19 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197176.1548453513000.6348.1578658500200%40Atlassian.JIRA.
[JIRA] (JENKINS-60507) Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled
Title: Message Title Konstantin Demenkov updated an issue Jenkins / JENKINS-60507 Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled Change By: Konstantin Demenkov Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203598.157651039.6344.1578658260325%40Atlassian.JIRA.
[JIRA] (JENKINS-60640) Support rename job and sync it in pipeline module in ALM Octane
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-60640 Support rename job and sync it in pipeline module in ALM Octane Change By: Radi Berkovich Labels: 6.0.4-BETA Octane Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203878.1578238949000.6345.1578658260346%40Atlassian.JIRA.
[JIRA] (JENKINS-60670) StackOverflowError due to the HP ALM implementation of GraphListener
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-60670 StackOverflowError due to the HP ALM implementation of GraphListener Change By: Radi Berkovich Labels: Octane Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203913.1578384494000.6342.1578658260293%40Atlassian.JIRA.
[JIRA] (JENKINS-60640) Support rename job and sync it in pipeline module in ALM Octane
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-60640 Support rename job and sync it in pipeline module in ALM Octane Change By: Radi Berkovich Labels: 6.0.4-BETA Octane Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203878.1578238949000.6340.1578658200069%40Atlassian.JIRA.
[JIRA] (JENKINS-60670) StackOverflowError due to the HP ALM implementation of GraphListener
Title: Message Title Radi Berkovich commented on JENKINS-60670 Re: StackOverflowError due to the HP ALM implementation of GraphListener Hi I see that you use 5.6.2 version of plugin. We did many improvements in the area. And now latest version is 6.0 . If its possible , can you please check if the issue is reproducible on more updated version. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203913.1578384494000.6339.1578657900838%40Atlassian.JIRA.
[JIRA] (JENKINS-60507) Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled
Title: Message Title Konstantin Demenkov commented on JENKINS-60507 Re: Pipeline stuck when allocating machine | node block appears to be neither running nor scheduled I have the same issue on latest 2.201 LTS. It appears pretty often (10% of jobs) in working with proxmox slaves over proxmox cloud plugin and jnlp. I suspect some incompatibility in timeouts/ connection's logic between master and proxmox slaves, but really don't know, why it happens. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203598.157651039.6337.1578657840136%40Atlassian.JIRA.
[JIRA] (JENKINS-60727) Add capability to clean submodules' submodules
Title: Message Title Bill Collins commented on JENKINS-60727 Re: Add capability to clean submodules' submodules git-client-plugin PR: https://github.com/jenkinsci/git-client-plugin/pull/489 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203976.1578651595000.6327.1578656040309%40Atlassian.JIRA.
[JIRA] (JENKINS-60727) Add capability to clean submodules' submodules
Title: Message Title Bill Collins started work on JENKINS-60727 Change By: Bill Collins Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203976.1578651595000.6326.1578656040298%40Atlassian.JIRA.
[JIRA] (JENKINS-60727) Add capability to clean submodules' submodules
Title: Message Title Bill Collins assigned an issue to Bill Collins Jenkins / JENKINS-60727 Add capability to clean submodules' submodules Change By: Bill Collins Assignee: Mark Waite Bill Collins Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203976.1578651595000.6325.1578656040260%40Atlassian.JIRA.
[JIRA] (JENKINS-60712) Copied managed config file should be removed when block ends
Title: Message Title Anders Hammar updated an issue Jenkins / JENKINS-60712 Copied managed config file should be removed when block ends Change By: Anders Hammar Environment: nodejs-plugin Jenkins 2.190.3 (on RHEL7 with openJDK 1.8.0)Token Macro Plugin v2.10Config FIle Provider Plugin v3.6.2NodeJS Plugin v1.3.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203960.157858259.6323.1578655860225%40Atlassian.JIRA.
[JIRA] (JENKINS-60720) Possibility to specify if env variables should be filtered or not in npm config file
Title: Message Title Anders Hammar updated an issue Jenkins / JENKINS-60720 Possibility to specify if env variables should be filtered or not in npm config file Change By: Anders Hammar Environment: Jenkins 2.190.3 (on RHEL7 with openJDK 1.8.0)Token Macro Plugin v2.10Config FIle Provider Plugin v3.6.2NodeJS Plugin 1.3.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203969.157864169.6321.1578655800059%40Atlassian.JIRA.
[JIRA] (JENKINS-60381) Remove old, deprecated remoting protocols
Title: Message Title Oleg Nenashev commented on JENKINS-60381 Re: Remove old, deprecated remoting protocols Also created https://github.com/jenkins-infra/jenkins.io/pull/2757 for the Administrative Monitors update Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203430.1575564508000.6314.1578655500210%40Atlassian.JIRA.
[JIRA] (JENKINS-60381) Remove old, deprecated remoting protocols
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60381 Remove old, deprecated remoting protocols Change By: Oleg Nenashev Released As: remoting 3.40, Jenkins 2.214 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203430.1575564508000.6316.1578655500237%40Atlassian.JIRA.
[JIRA] (JENKINS-60381) Remove old, deprecated remoting protocols
Title: Message Title Oleg Nenashev commented on JENKINS-60381 Re: Remove old, deprecated remoting protocols Jeff Thompson Docker packaging will also need to be updated to close this story Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203430.1575564508000.6305.1578654900568%40Atlassian.JIRA.
[JIRA] (JENKINS-60381) Remove old, deprecated remoting protocols
Title: Message Title Oleg Nenashev started work on JENKINS-60381 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203430.1575564508000.6301.1578654840454%40Atlassian.JIRA.
[JIRA] (JENKINS-60381) Remove old, deprecated remoting protocols
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60381 Remove old, deprecated remoting protocols Change By: Oleg Nenashev Component/s: docker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203430.1575564508000.6303.1578654840506%40Atlassian.JIRA.
[JIRA] (JENKINS-60381) Remove old, deprecated remoting protocols
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60381 Remove old, deprecated remoting protocols Change By: Oleg Nenashev Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203430.1575564508000.6299.1578654840407%40Atlassian.JIRA.
[JIRA] (JENKINS-59671) Support storing multiple Jenkins credentials in a single Secrets Manager secret
Title: Message Title Chris Kilding resolved as Won't Do Jenkins / JENKINS-59671 Support storing multiple Jenkins credentials in a single Secrets Manager secret Change By: Chris Kilding Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202363.1570221511000.6297.1578654600093%40Atlassian.JIRA.
[JIRA] (JENKINS-60729) Calender View Plugin not showing past builds data
Title: Message Title prashanth kasoju updated an issue Jenkins / JENKINS-60729 Calender View Plugin not showing past builds data Change By: prashanth kasoju Hi Team,We have installed Calender View Plugin(0.3.1) and till dec29 it was working fine and on 30 and 31st dec 2019 the data is not shown. Data is showing again from 1st jan . we have seen 2 days scheduled data missing.can some one please help me the below issue.Just curious to understand is there any issue with plugin? attached is the screenshot Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203978.1578654206000.6296.1578654420156%40Atlassian.JIRA.
[JIRA] (JENKINS-60675) An automated ant build called from Jenkins fails
Title: Message Title Karl Wirth commented on JENKINS-60675 Re: An automated ant build called from Jenkins fails Hi Peeush Trikha - I just wanted to check if you had seen my previous comment. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203918.1578391928000.6294.1578654300238%40Atlassian.JIRA.
[JIRA] (JENKINS-60729) Calender View Plugin not showing past builds data
Title: Message Title prashanth kasoju created an issue Jenkins / JENKINS-60729 Calender View Plugin not showing past builds data Issue Type: Bug Assignee: Sven Schoenung Attachments: calenderview (1).png Components: calendar-view-plugin Created: 2020-01-10 11:03 Priority: Minor Reporter: prashanth kasoju Hi Team, We have installed Calender View Plugin(0.3.1) and till dec29 it was working fine and on 30 and 31st dec the data is not shown. Data is showing again from 1st jan . we have seen 2 days scheduled data missing. can some one please help me the below issue.Just curious to understand is there any issue with plugin? attached is the screenshot Add Comment
