[JIRA] (JENKINS-59837) java.lang.OutOfMemoryError: Compressed class space
Title: Message Title Dennis Tran created an issue Jenkins / JENKINS-59837 java.lang.OutOfMemoryError: Compressed class space Issue Type: Story Assignee: Unassigned Components: _unsorted Created: 2019-10-18 06:45 Environment: Jenkins 2.164.2 java version "1.8.0_201 Priority: Minor Reporter: Dennis Tran Apparently, my build job failed unit test, this issue happening randomly in every slave node. [INFO] Running ch.crdw.task.service.CrdhwayDraftTaskServiceTest [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.798 s - in ch.crdw.task.service.CrdhwayDraftTaskServiceTest [INFO] Running ch.crdw.cloning.service.DossierTaskServiceTest [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.173 s - in ch.crdw.cloning.service.DossierTaskServiceTest [INFO] Running ch.crdw.helper.DossierOperationHelperTest [INFO] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.829 s - in ch.crdw.helper.DossierOperationHelperTest [INFO] Running ch.crdw.helper.AbstractCockpitBuilderTest [INFO] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5 s - in ch.crdw.helper.AbstractCockpitBuilderTest [INFO] Running ch.crdw.helper.CompetenceLevelHelperTest [INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.341 s - in ch.crdw.helper.CompetenceLevelHelperTest [INFO] Running ch.crdw.helper.PropertyHelperTest [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.728 s - in ch.crdw.helper.PropertyHelperTest [INFO] Running ch.crdw.helper.ClientOnBoardingViewBeanHelperTest [ERROR] Tests run: 2, Failures: 0, Errors: 1, S
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Tomas Westling commented on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. That is weird, but seems it has to be a problem on your end, since 1.23.1 is visible from all our Jenkins instances. When was the last "update information obtained" ? It has been in the update site for quite a while now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202251.1569939008000.10120.1571381100403%40Atlassian.JIRA.
[JIRA] (JENKINS-59836) HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects
Title: Message Title
Kalana Samaraweera updated an issue
Jenkins / JENKINS-59836
HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects
Change By:
Kalana Samaraweera
We've enabled Vault plugin (version 3.0.0) configuration for our Jenkins free-style project. Following error appears when we save the build job configurations. Somehow it allows us to configure plugin from Jenkins configuration (i.e. Configure-System) . Our Jenkins version is 2.150.3 {code:java}java.lang.UnsupportedOperationException: Refusing to marshal com.bettercloud.vault.VaultConfig for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize com.datapipe.jenkins.vault.VaultAccessor#config for class com.datapipe.jenkins.vault.VaultAccessor at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize com.datapipe.jenkins.vault.VaultBuildWrapper#vaultAccessor for class com.datapipe.jenkins.vault.VaultBuildWrapper at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractRefere
[JIRA] (JENKINS-59836) HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects
Title: Message Title Kalana Samaraweera updated an issue Jenkins / JENKINS-59836 HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects Change By: Kalana Samaraweera Summary: HashiCorp Vault plugin configuration cannot be enabled for Free-style Freestyle projects 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.202571.1571380365000.10113.1571380500333%40Atlassian.JIRA.
[JIRA] (JENKINS-59836) HashiCorp Vault plugin configuration cannot be enabled for Free-style projects
Title: Message Title
Kalana Samaraweera updated an issue
Jenkins / JENKINS-59836
HashiCorp Vault plugin configuration cannot be enabled for Free-style projects
Change By:
Kalana Samaraweera
We've enabled Vault plugin (version 3.0.0) configuration for our Jenkins free-style project. Following error appears when we save the build job configurations. Somehow it allows us to configure plugin from Jenkins configuration (i.e. Configure-System) configuration . {code:java}java.lang.UnsupportedOperationException: Refusing to marshal com.bettercloud.vault.VaultConfig for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize com.datapipe.jenkins.vault.VaultAccessor#config for class com.datapipe.jenkins.vault.VaultAccessor at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize com.datapipe.jenkins.vault.VaultBuildWrapper#vaultAccessor for class com.datapipe.jenkins.vault.VaultBuildWrapper at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.co
[JIRA] (JENKINS-59836) HashiCorp Vault plugin configuration cannot be enabled for Free-style projects
Title: Message Title Kalana Samaraweera created an issue Jenkins / JENKINS-59836 HashiCorp Vault plugin configuration cannot be enabled for Free-style projects Issue Type: Bug Assignee: Peter Tierno Components: hashicorp-vault-plugin Created: 2019-10-18 06:32 Priority: Major Reporter: Kalana Samaraweera We've enabled Vault plugin (version 3.0.0) configuration for our Jenkins free-style project. Following error appears when we save the build job configurations. Somehow it allows us to configure plugin from Jenkins (i.e. Configure-System) configuration. java.lang.UnsupportedOperationException: Refusing to marshal com.bettercloud.vault.VaultConfig for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) Caused: java.lang.RuntimeException: Failed to serialize com.datapipe.jenkins.vault.VaultAccessor#config for class com.datapipe.jenkins.vault.VaultAccessor at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(R
[JIRA] (JENKINS-59342) Ability to download Specific Objects bundles
Title: Message Title Allan BURDAJEWICZ updated JENKINS-59342 Jenkins / JENKINS-59342 Ability to download Specific Objects bundles Change By: Allan BURDAJEWICZ 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.201893.1568352322000.10103.1571379900487%40Atlassian.JIRA.
[JIRA] (JENKINS-59651) PIPELINE_VERSION can not export to shell environment.
Title: Message Title Alex Lei updated an issue Jenkins / JENKINS-59651 PIPELINE_VERSION can not export to shell environment. Change By: Alex Lei Then plugin works file when I use old jenkins release.When I upgrade jenkins to latest version. I found shell env missing PIPELINE_VERSION variable. Also test on delivery-pipeline-plugin 1.4.0 1.3.2 clone git commit 04d7810b96af1ad893d761edf1e0e6faa79f72c9change 2.187run mvn testThere are test failures. 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.202341.1570157505000.10101.1571377680182%40Atlassian.JIRA.
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Aleksi Simell commented on JENKINS-59724 Re: no known implementation of class java.lang.String is named Target Denis Bel The plugin uses only InfluxDbGlobalConfig as of version 2.0. Deleting the other file should be safe, but it shouldn't matter if it is there. If you delete it, you cannot rollback to an older version of the plugin. I would suggest taking a copy of that in case you want to delete it. If I understood correctly, you're not getting the error anymore and the issue is 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.202441.1570700819000.10099.1571375760177%40Atlassian.JIRA.
[JIRA] (JENKINS-59651) PIPELINE_VERSION can not export to shell environment.
Title: Message Title Alex Lei updated an issue Jenkins / JENKINS-59651 PIPELINE_VERSION can not export to shell environment. Change By: Alex Lei Environment: jenkins-2.187.war osx jdk8 delivery-pipeline-plugin 1.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.202341.1570157505000.10095.1571370180188%40Atlassian.JIRA.
[JIRA] (JENKINS-42759) XML report file generated by CloverPHP plugin is not fully compatible with Clover format
Title: Message Title Upkar Rai commented on JENKINS-42759 Re: XML report file generated by CloverPHP plugin is not fully compatible with Clover format Is there a workaround ? 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.179751.1489505843000.10088.1571367420251%40Atlassian.JIRA.
[JIRA] (JENKINS-59835) Agent fails to connect from Mac OS Catalina
Title: Message Title dip kasyap created an issue Jenkins / JENKINS-59835 Agent fails to connect from Mac OS Catalina Issue Type: Bug Assignee: Unassigned Components: jenkinswalldisplay Created: 2019-10-18 02:50 Priority: Major Reporter: dip kasyap java.nio.file.FileSystemException: /Jenkins: Read-only file systemjava.nio.file.FileSystemException: /Jenkins: Read-only file system at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) at java.nio.file.Files.createDirectory(Files.java:674) at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) at java.nio.file.Files.createDirectories(Files.java:767) at org.jenkinsci.remoting.engine.WorkDirManager.initializeWorkDir(WorkDirManager.java:212) at hudson.remoting.Engine.startEngine(Engine.java:251) at hudson.remoting.Engine.startEngine(Engine.java:227) at hudson.remoting.jnlp.Main.main(Main.java:228) at hudson.remoting.jnlp.Main._main(Main.java:223) at hudson.remoting.jnlp.Main.main(Main.java:189) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.javaws.Launcher.executeApplication(Unknown Source) at com.sun.javaws.Launcher.executeMainClass(Unknown Source) at com.sun.javaws.Launcher.doLaunchApp(Unknown Source) at com.sun.javaws.Launcher.run(Unknown Source) at java.lang.Thread.run(Thread.java:745)
[JIRA] (JENKINS-59824) Ignore timeout while provisioning
Title: Message Title Jie Shen commented on JENKINS-59824 Re: Ignore timeout while provisioning According to discussion at https://github.com/Azure/azure-sdk-for-node/issues/1491, it seems to be a service side issue. I also have not figured out how to change it in the java sdk. So it is possible to improve the image itself or try to deploy to different locations? 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.202559.1571318032000.10085.1571363580206%40Atlassian.JIRA.
[JIRA] (JENKINS-59824) Ignore timeout while provisioning
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-59824 Ignore timeout while provisioning Change By: Jie Shen Assignee: Azure DevOps Jie Shen 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.202559.1571318032000.10083.1571363460600%40Atlassian.JIRA.
[JIRA] (JENKINS-59834) Retry Mechanism for collate and analyze when it fails
Title: Message Title Sandeep Moras created an issue Jenkins / JENKINS-59834 Retry Mechanism for collate and analyze when it fails Issue Type: Bug Assignee: Maria Narcisa Galan Components: hp-application-automation-tools-plugin Created: 2019-10-18 01:09 Priority: Minor Reporter: Sandeep Moras Hi, We are having a problem with PC 12.62 version where it intermittently fails during collate or analyze. After failure we are able to manually complete collate and analyze. Can we have a option to retry collate and/analyze? This failure makes our jenkins job/pipeline unreliable. We suspect that the issue might be with time taken for data to be properly synchronized in the servers/repos before it can be collated / analyzed. Below are the logs. Thanks for your support. Sandeep Test ID: 639 Test Instance ID: 296 Timeslot Duration: 1:30(h:mm) Post Run Action: Collate and Analyze Use VUDS: false Mon 2019 Aug 19 at 23:54:40.915 PM GMT - Run started (TestID: 639, RunID: 2490, TimeslotID: 59551) Mon 2019 Aug 19 at 23:54:44.091 PM GMT - test name is PI7_Price_Baselining_Testing_Spike Mon 2019 Aug 19 at 23:54:44.092 PM GMT - Set Environment Variable: PC_RUN_ID = 2490 Mon 2019 Aug 19 at 23:54:44.176 PM GMT - RunID: 2490 - State = Initializing Mon 2019 Aug 19 at 23:55:45.286 PM GMT - RunID: 2490 - State = Running Mon 2019 Aug 19 at 23:57:27.120 PM GMT - RunID: 2490 - State = Collating Results Mon 2019 Aug 19 at 23:57:37.323 PM GMT - RunID: 2490 - State = Before Creating Analysis Data Mon 2019 Aug 19 at 23:57:38.459 PM GMT - RunID: 2490 - State = Creating Analysis Data Tue 2019 Aug 20 at 00:00:57.584 AM GMT - RunID: 2490 - State = Failed Creating Analysis Data Tue 2019 Aug 20 at 00:01:02.689 AM GMT - Failure: FAILED_CREATING_ANALYSIS_DATA. Event Log: ID | TYPE | TIME | DESCRIPTION 5814608 | Error | 2019-08-20 00:00:57 | Failed executing operation 'Analyzing', internal error: 'Process HP.PC.AnalysisWrapper abnormally terminated' 5814603 | Info | 2019-08-20 00:00:55
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title
John Rocha commented on JENKINS-54472
Re: Pin build at Perforce Label does not support variable expansion
Hello Karl Wirth, I was able to get this to work with plugin 1.10.5 (I haven't tried for awhile, so it may work with earlier versions too). What I did was as follows:
Define a choice parameter: P4_LABEL, with string trimming enabled.
Set the Perforce field "Pin build at Perforce Label" to ${P4_LABEL}
With this I successfully synced to change set 34307 by entering a value of @34307. Moreover, if I enter nothing, using the default where P4_LABEL is now set to nothing, it correctly pulls latest as expected. I think this case can be closed. I don't know if there was a fix that went in from when I first reported or if it was a miss-configuration on my part... but it works now when I do as explained above.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195237.154144342.10076.1571356740150%40Atlassian.JIRA.
[JIRA] (JENKINS-59831) update JsonPath from 0.5.5 to 2.4.0
Title: Message Title Kemal Soysal commented on JENKINS-59831 Re: update JsonPath from 0.5.5 to 2.4.0 Pullrequest https://github.com/jenkinsci/urltrigger-plugin/pull/25 is implementing the desired behavior. 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.202566.1571343899000.10071.1571353440628%40Atlassian.JIRA.
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title suryatej yaramada commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) Here is latest Polling change that we seeing rebuilds for every 10 min Git Polling Log Started on Oct 17, 2019 9:22:07 PM Using strategy: Default [poll] Last Built Revision: Revision 9af93c1a4cf6e2e8a625ee7898dcfdb2339acbc6 (origin/master) No credentials specified > git --version # timeout=10 > git ls-remote -h g...@bitbucket.org:abc/testapp # timeout=10 Found 3 remote heads on g...@bitbucket.org:abc/testapp [poll] Latest remote head revision on refs/heads/master is: 9af93c1a4cf6e2e8a625ee7898dcfdb2339acbc6 - already built by 161 Using strategy: Specific revision [poll] Last Built Revision: Revision a7cf4fd0c7484765c4a5166a36613c387aee8501 (master) No credentials specified > git --version # timeout=10 > git ls-remote -h g...@bitbucket.org:abc/shared # timeout=10 Found 3 remote heads on g...@bitbucket.org:abc/shared [poll] Latest remote head revision on refs/heads/master is: 019f70307c622c80ac33b168e7c5dc134aa5d02a Using strategy: Default [poll] Last Built Revision: Revision 9af93c1a4cf6e2e8a625ee7898dcfdb2339acbc6 (origin/master) using credential 6e83116e-4fb6-491a-a2c9-9ac9d51d4765 > git --version # timeout=10 using GIT_SSH to set credentials > git ls-remote -h g...@bitbucket.org:abc/testapp # timeout=10 Found 3 remote heads on g...@bitbucket.org:abc/testapp [poll] Latest remote head revision on refs/heads/master is: 9af93c1a4cf6e2e8a625ee7898dcfdb2339acbc6 - already built by 161 Done. Took 3.1 sec Changes found we didn't have any commits to shared library just we had few open branches Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-57428) Duplicate warnings when using error-prone and java scan
Title: Message Title Ulli Hafner updated JENKINS-57428 Jenkins / JENKINS-57428 Duplicate warnings when using error-prone and java scan Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199240.1557749846000.10056.1571346600289%40Atlassian.JIRA.
[JIRA] (JENKINS-59831) update JsonPath from 0.5.5 to 2.4.0
Title: Message Title Kemal Soysal updated an issue Jenkins / JENKINS-59831 update JsonPath from 0.5.5 to 2.4.0 Change By: Kemal Soysal I have a git repository where I would want to see changes on branches by certain criteria on their names.The JsonPath 0.5.5 does not work with regular expressions well.The JsonPath 2.4.0 does offer richer regular _expression_ syntax allowing me to discover changes on revisions for multiple branches of interest. For the test file oldJsonContent.json you can check on [https://jsonpath.herokuapp.com|https://jsonpath.herokuapp.com/] $..[?(@.category =~ /refer.+/)].titleshould deliver["Title A"]and the test file newJsonContent.json["Sayings of the Century"] 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 discus
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Upkar Rai created an issue Jenkins / JENKINS-59833 Stash Pull Request Builder Multiple PR in single build Issue Type: Bug Assignee: Jakub Bochenski Components: stash-pullrequest-builder-plugin Created: 2019-10-17 21:03 Priority: Major Reporter: Upkar Rai Ref : https://github.com/HB-2012 comments on https://gitter.im/jenkinsci/stash-pullrequest-builder-plugin Hi there. In my organization I have a PR pipeline set up using the experimental support for pipelines. I keep noticing that our job keeps building a bunch of PRs in a single build, which is undesirable since the Stash Notifier plugin doesn't understand this and only reports a successful build for a single PR, even tho apparently the PR builder plugin recognizes it has started builds for multiple PRs. We're dealing with a huge amount of PRs here (about 20-30 developers and therefor we can have 40 PRs open at any given time). Git settings are configured as per the manual and we've set the following configuration for the Git PR builder plugin Is this standard behavior for the Stash PR builder or am I missing something? Add Comment
[JIRA] (JENKINS-59832) Multiple inheritFrom templates ignored in declarative pipeline
Title: Message Title
Andrey Cherkashin created an issue
Jenkins / JENKINS-59832
Multiple inheritFrom templates ignored in declarative pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
kubernetes-plugin
Created:
2019-10-17 20:41
Environment:
Jenkins ver. 2.197 Plugin version: 1.20.0
Priority:
Minor
Reporter:
Andrey Cherkashin
This was working with 1.16.1 version of a plugin. Possible regression? Here is agent configuration that used to work:
agent {
kubernetes {
label "${pipelineParams.argoApplicationPrefix}-preflight"
defaultContainer 'jnlp'
idleMinutes 1
inheritFrom "maven mysql-57 kaniko"
}
After upgrading to to 1.20.0 resulting pod template only what was in last entry in that list. Documentation is lacking on how one can change `yamlMergeStrategy` in declarative pipeline, but I tried creating the same pod temple in Global Configuration with `merge` as strategy - no luck.
[JIRA] (JENKINS-59831) update JsonPath from 0.5.5 to 2.4.0
Title: Message Title Kemal Soysal created an issue Jenkins / JENKINS-59831 update JsonPath from 0.5.5 to 2.4.0 Issue Type: Improvement Assignee: Gregory Boissinot Components: urltrigger-plugin Created: 2019-10-17 20:24 Priority: Major Reporter: Kemal Soysal I have a git repository where I would want to see changes on branches by certain criteria on their names. The JsonPath 0.5.5 does not work with regular expressions well. The JsonPath 2.4.0 does offer richer regular _expression_ syntax allowing me to discover changes on revisions for multiple branches of interest. Add Comment
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck updated an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Change By: Jonathan Buck Labels: UI freestyle gui ssh-agent ui user-experience 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.202538.1571249068000.10044.1571343480075%40Atlassian.JIRA.
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck updated an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Change By: Jonathan Buck When using the "SSH Agent" setting in the "Build Environment" section, credentials are not showing up when creating/modifying a freestyle project. This is the case with both credentials created from the credential page or from the "Credentials" option under the "SSH Agent" option. I've tried multiple types of credentials to see what would populate the list, although my understanding is that this should work with credentials stored as "SSH Username with private key". I also use the Ansible plugin and all available credentials are showing up within that credentials drop-down menu within the same project configuration page. My assumption is that this has something to do with the "SSH Agent" plugin interacting with the "Credentials" or "SSH Credentials" plugin. There's no option do downgrade the plugin, so that was not attempted. I have no problem getting the SSH-Agent plugin working within a pipeline job. !image-2019-10-17-14-42-56-399.png!!Jenkins_Credentials.PNG! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59830) Support google cloud source repos with git client plugin
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59830
Support google cloud source repos with git client plugin
Change By:
Mark Waite
Google cloud source repositories can host Git repositories (optionally copied from Bitbucket or GitHub) on Google cloud infrastructure.When I configured a Google cloud source repository with my Google account, it offered an SSH url format that is not supported by the Jenkins git client plugin. The URL format is:{noformat}ssh://mark.earl.wa...@gmail.com@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin{noformat}Note that there is an extra '@' character embedded in the username portion of that ssh URL. I've never seen the '@' character as an allowed part of the username or password in a URL, but I assume it must be allowed.When the git client plugin checks the remote server for branches, it detects the branches correctly using the {{git ls-remote}} command. However, when it attempts to clone the repository, the message is:{noformat}Fetching upstream changes from ssh://mark.earl.waite%40gmail@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin > git fetch --tags --force --progress --prune -- ssh://mark.earl.waite%40gmail@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin +refs/heads/*:refs/remotes/google-cloud/* # timeout=10ERROR: Error fetching remote repo 'google-cloud'hudson.plugins.git.GitException: Failed to fetch from ssh://mark.earl.waite%40gmail@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:897) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1112) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1143) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress --prune -- ssh://mark.earl.waite%40gmail@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin +refs/heads/*:refs/remotes/google-cloud/*" returned status code 128:stdout: stderr: Host key verification failed.fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2372) at org.jenkinsci.plugins.gitclient.CliGitAPIIm
[JIRA] (JENKINS-59830) Support google cloud source repos with git client plugin
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59830
Support google cloud source repos with git client plugin
Change By:
Mark Waite
Google cloud source repositories can host Git repositories (optionally copied from Bitbucket or GitHub) on Google cloud infrastructure.When I configured a Google cloud source repository with my Google account, it offered an SSH url format that is not supported by the Jenkins git client plugin. The URL format is:{noformat}ssh://mark.earl.wa...@gmail.com@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin{noformat} Note that there is an extra '@' character embedded in the username portion of that ssh URL. I've never seen the '@' character as an allowed part of the username or password in a URL, but I assume it must be allowed.When the git client plugin checks the remote server for branches, it detects the branches correctly using the {{git ls-remote}} command. However, when it attempts to clone the repository, the message is:{noformat}Fetching upstream changes from ssh://mark.earl.waite%40gmail@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin > git fetch --tags --force --progress --prune -- ssh://mark.earl.waite%40gmail@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin +refs/heads/*:refs/remotes/google-cloud/* # timeout=10ERROR: Error fetching remote repo 'google-cloud'hudson.plugins.git.GitException: Failed to fetch from ssh://mark.earl.waite%40gmail@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:897) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1112) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1143) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress --prune -- ssh://mark.earl.waite%40gmail@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin +refs/heads/*:refs/remotes/google-cloud/*" returned status code 128:stdout: stderr: Host key verification failed.fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2372) at org.jenkinsci.plugins.gitclient.CliGitAPII
[JIRA] (JENKINS-59830) Support google cloud source repos with git client plugin
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-59830 Support google cloud source repos with git client plugin Issue Type: Improvement Assignee: Mark Waite Components: git-client-plugin Created: 2019-10-17 19:39 Environment: Jenkins 2.190.1 Git client plugin 3.0.0-beta11 Priority: Major Reporter: Mark Waite Google cloud source repositories can host Git repositories (optionally copied from Bitbucket or GitHub) on Google cloud infrastructure. When I configured a Google cloud source repository with my Google account, it offered an SSH url format that is not supported by the Jenkins git client plugin. The URL format is: ssh://mark.earl.wa...@gmail.com@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin
[JIRA] (JENKINS-59830) Support google cloud source repos with git client plugin
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59830 Support google cloud source repos with git client plugin Change By: Mark Waite Assignee: Mark Waite 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.202565.157134115.10040.1571341200189%40Atlassian.JIRA.
[JIRA] (JENKINS-59756) NameEncoder.decode can introduce duplicate characters per build to name-utf8.txt
Title: Message Title Karl Shultz started work on JENKINS-59756 Change By: Karl Shultz 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.202479.1570827139000.10038.1571340300110%40Atlassian.JIRA.
[JIRA] (JENKINS-59829) GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository
Title: Message Title Kyle Jackson commented on JENKINS-59829 Re: GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository Thanks Mark! 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.202564.1571336378000.10037.1571339820198%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Florian Schmaus assigned an issue to Florian Schmaus Jenkins / JENKINS-36826 Support Jenkins Pipeline for Jabber notifications Change By: Florian Schmaus Assignee: Jim Klimov Florian Schmaus 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.172870.1469028488000.10004.1571339524832%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Florian Schmaus updated JENKINS-36826 Jenkins / JENKINS-36826 Support Jenkins Pipeline for Jabber notifications Change By: Florian Schmaus 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.172870.1469028488000.9970.1571339524145%40Atlassian.JIRA.
[JIRA] (JENKINS-59829) GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository
Title: Message Title Mark Waite commented on JENKINS-59829 Re: GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository Since there was no change in git plugin between the working and the non-working case, I assume you'll need to work with Google Cloud support to identify and resolve the issue. My experiments with Google Cloud to host a git repository seem to indicate that the Jenkins git plugin will need some additional work to better support Google Cloud Source Repositories. There seem to be several surprises in the initial tests that I've performed. 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.202564.1571336378000.9967.1571339340126%40Atlassian.JIRA.
[JIRA] (JENKINS-59829) GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository
Title: Message Title Kyle Jackson commented on JENKINS-59829 Re: GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository Hey Mark, I had this working with git@3.9.3 and it broke. I upgraded to 3.12.1 with the same issue. flow.xml I believe this issue is using a service account to access the GSR. Using a personal account is not the issue though it would be good to validate that as well. For the "pipeline script from scm", how would you use a private json key with the method you describe? 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.202564.1571336378000.9965.1571338740147%40Atlassian.JIRA.
[JIRA] (JENKINS-59829) GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository
Title: Message Title Kyle Jackson updated an issue Jenkins / JENKINS-59829 GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository Change By: Kyle Jackson Attachment: flow.xml 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.202564.1571336378000.9963.1571338620164%40Atlassian.JIRA.
[JIRA] (JENKINS-59829) GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository
Title: Message Title
Mark Waite edited a comment on JENKINS-59829
Re: GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository
Did you recently update your Jenkins git plugin version?I just created a google cloud repository using my Google account and connected it to the GitHub repository of the Jenkins git client plugin. I can list the remote branches in the repository but when I try to clone the repository, it complains and fails to clone because my Google ID in the repository URL is 'mark.earl.wa...@gmail.com' and the Jenkins git client plugin seems to incorrectly URL escape the '@' sign in the URL.Google cloud shows that the clone command I should use is:{{git clone ssh://mark.earl.wa...@gmail.com@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin}}Notice how there are two embedded '@' characters in the clone command. One is from my e-mail address, while the other is used to separate the username from the hostname in the ssh URL.
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.202564.1571336378000.9959.1571338320113%40Atlassian.JIRA.
[JIRA] (JENKINS-59829) GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository
Title: Message Title Mark Waite commented on JENKINS-59829 Re: GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository Did you recently update your Jenkins git plugin version? I just created a google cloud repository using my Google account and connected it to the GitHub repository of the Jenkins git client plugin. I can list the remote branches in the repository but when I try to clone the repository, it complains fails to clone because my Google ID in the repository URL is 'mark.earl.wa...@gmail.com' and the Jenkins git client plugin seems to incorrectly URL escape the '@' sign in the URL. Google cloud shows that the clone command I should use is: git clone ssh://mark.earl.wa...@gmail.com@source.developers.google.com:2022/p/jenkins-plugins-markewaite/r/github_markewaite_git-client-plugin Notice how there are two embedded '@' characters in the clone command. One is from my e-mail address, while the other is used to separate the username from the hostname in the ssh URL. 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.202564.1571336378000.9957.1571338260249%40Atlassian.JIRA.
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck updated an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Change By: Jonathan Buck Labels: ssh-agent 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.202538.1571249068000.9955.1571338260129%40Atlassian.JIRA.
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck updated an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Change By: Jonathan Buck When using the "SSH Agent" setting in the "Build Environment" section, credentials are not showing up when creating/modifying a freestyle project. This is the case with both credentials created from the credential page or from the "Credentials" option under the "SSH Agent" option. I've tried multiple types of credentials to see what would populate the list, although my understanding is that this should work with credentials stored as "SSH Username with private key". I also use the Ansible plugin and all available credentials are showing up within that credentials drop-down menu within the same project configuration page. My assumption is that this has something to do with the "SSH Agent" plugin interacting with the "Credentials" or "SSH Credentials" plugin. There's no option do downgrade the plugin, so that was not attempted.!image-2019-10-17-14-42-56-399.png! !Jenkins_Credentials.PNG! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck updated an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Change By: Jonathan Buck Attachment: Jenkins_Credentials.PNG Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202538.1571249068000.9954.1571338080158%40Atlassian.JIRA.
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck updated an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Change By: Jonathan Buck When using the "SSH Agent" setting in the "Build Environment" section, credentials are not showing up when creating/modifying a freestyle project. This is the case with both credentials created from the credential page or from the "Credentials" option under the "SSH Agent" option. I've tried multiple types of credentials to see what would populate the list, although my understanding is that this should work with credentials stored as "SSH Username with private key". I also use the Ansible plugin and all available credentials are showing up within that credentials drop-down menu within the same project configuration page. My assumption is that this has something to do with the "SSH Agent" plugin interacting with the "Credentials" or "SSH Credentials" plugin. There's no option do downgrade the plugin, so that was not attempted.!image-2019-10-17-14-42-56-399.png! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck updated an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Change By: Jonathan Buck Attachment: Jenkins_Credentials.PNG Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202538.1571249068000.9950.1571338020169%40Atlassian.JIRA.
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck updated an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Change By: Jonathan Buck Attachment: Jenkins_Credentials.PNG Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202538.1571249068000.9951.1571338020340%40Atlassian.JIRA.
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck updated an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Change By: Jonathan Buck When using the "SSH Agent" setting in the "Build Environment" section, credentials are not showing up when creating/modifying a freestyle project. This is the case with both credentials created from the credential page or from the "Credentials" option under the "SSH Agent" option. I've tried multiple types of credentials to see what would populate the list, although my understanding is that this should work with credentials stored as "SSH Username with private key". I also use the Ansible plugin and all available credentials are showing up within that credentials drop-down menu within the same project configuration page. My assumption is that this has something to do with the "SSH Agent" plugin interacting with the "Credentials" or "SSH Credentials" plugin. There's no option do downgrade the plugin, so that was not attempted. !image-2019-10-17-14-42-56-399.png! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck updated an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Change By: Jonathan Buck Attachment: image-2019-10-17-14-42-56-399.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202538.1571249068000.9948.1571337780069%40Atlassian.JIRA.
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck updated an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Change By: Jonathan Buck I'm attempting to use When using the "SSH Agent" setting in the "Build Environment" section . My issue is , credentials are not showing up when creating/modifying a freestyle project. This is the case with both credentials created from the credential page or from the "Credentials" option under the "SSH Agent" option. I've tried multiple types of credentials to see what would populate the list, although my understanding is that this should work with credentials stored as "SSH Username with private key". I also use the Ansible plugin and all available credentials are showing up within that credentials drop-down menu within the same project configuration page. My assumption is that this has something to do with the "SSH Agent" plugin interacting with the "Credentials" or "SSH Credentials" plugin. There's no option do downgrade the plugin, so that was not attempted. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59829) GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository
Title: Message Title Kyle Jackson created an issue Jenkins / JENKINS-59829 GitSCM Unable to Pull Pipeline script from SCM from Google Cloud Source Repository Issue Type: Bug Assignee: Mark Waite Attachments: Screen Shot 2019-10-17 at 2.03.44 PM.png Components: git-plugin Created: 2019-10-17 18:19 Priority: Blocker Reporter: Kyle Jackson Ever since Monday night 10/14/19 i have not been able to successfully pull "Pipeline script from SCM" from Google's Cloud Source Repository. I am able to pull it down with a normal clone (just not the pipeline script) I have been debugging this for 4 days and finally arrived at this solution. If i change the repo to a public GitHub repo it works. Im wondering if this helps me or not.. i also opened up a case with google. Add Comment
[JIRA] (JENKINS-59825) Can't update git client plugin
Title: Message Title Robert Hill updated an issue Jenkins / JENKINS-59825 Can't update git client plugin Change By: Robert Hill I'm new to Jenkins. I installed the various git plugins and had it working for a pipeline project. Recently, Jenkins notified me of a security vulnerability for the git client. I choose to downgrade from 3.0 to the previous version. After doing that, my pipeline lost it's reference to the git login. Any new pipelines doesn't list git as a choice. When I go into the manage plugins, it doesn't list the git-client with an available update. How do I get it back to using the 3.x 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-issu
[JIRA] (JENKINS-59828) Support the creation of GitSCMFileSystem for tags
Title: Message Title Steven Terrana created an issue Jenkins / JENKINS-59828 Support the creation of GitSCMFileSystem for tags Issue Type: Task Assignee: Mark Waite Components: git-plugin Created: 2019-10-17 17:33 Environment: git plugin 3.12.1 jenkins 2.190.1 Priority: Minor Reporter: Steven Terrana Currently the git-plugin only supports the SCM API for creating GitSCMFileSystem's if the ref specified is a branch and begins with ref/heads. It would be beneficial if tags could also be supported. I am opening a PR that addresses this and look forward to the discussion! Add Comment
[JIRA] (JENKINS-46988) String.eachLine only reads first line
Title: Message Title Jo Rhett edited a comment on JENKINS-46988 Re: String.eachLine only reads first line I don't feel that this issue is Minor, nor do I feel that the workaround is an acceptable solution. This basically means that every Jenkins user worldwide will burn some hours diagnosing this problem only to end up here. That this bug is more than 2 years old speaks to a significant lack of care. 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.185366.1505906799000.9909.1571332140516%40Atlassian.JIRA.
[JIRA] (JENKINS-59704) NoSuchMethodError occurs when promoting a build using parametrized trigger
Title: Message Title Filipe Roque commented on JENKINS-59704 Re: NoSuchMethodError occurs when promoting a build using parametrized trigger and a PR for parameterized-trigger-plugin: https://github.com/jenkinsci/parameterized-trigger-plugin/pull/130 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.202405.157054141.9895.1571331901520%40Atlassian.JIRA.
[JIRA] (JENKINS-46988) String.eachLine only reads first line
Title: Message Title Jo Rhett edited a comment on JENKINS-46988 Re: String.eachLine only reads first line I don'tfeel that this issue is Minor, nor do I feel that the workaround is an acceptable solution. This basically means that every Jenkins user worldwide will burn some hours diagnosing this problem only to end up here. 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.185366.1505906799000.9892.1571331901488%40Atlassian.JIRA.
[JIRA] (JENKINS-58643) CPS Mismatches on cpsScript.InvokeMethod
Title: Message Title Ward Hopeman commented on JENKINS-58643 Re: CPS Mismatches on cpsScript.InvokeMethod We are also seeing this on Jenkins v2.190.1; Artifactory plugin v3.40; Groovy plugin v2.2 artifactoryUploadexpected to call org.jfrog.hudson.pipeline.common.types.ArtifactoryServer.upload but wound up catching artifactoryUpload; see: 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.200910.1563983113000.9877.1571331901142%40Atlassian.JIRA.
[JIRA] (JENKINS-46988) String.eachLine only reads first line
Title: Message Title Jo Rhett commented on JENKINS-46988 Re: String.eachLine only reads first line I don't 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.185366.1505906799000.9849.1571331120466%40Atlassian.JIRA.
[JIRA] (JENKINS-59818) Mangement of "Disable Auth Request Signature" flag is inverted
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-59818 Change By: Ivan Fernandez Calvo 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.202550.1571302616000.9847.1571329681311%40Atlassian.JIRA.
[JIRA] (JENKINS-54346) tee keeps file open
Title: Message Title
Alexander Ukhanov commented on JENKINS-54346
Re: tee keeps file open
In our installation(2.176.4) tee on windows nodes works good with workflow-job plugin <=2.25. After upgrade workflow-job plugin to 2.26+ version job with
node('windows')
{
tee {bat ... }
cleanWs()
}
drops with ERROR: Cannot delete workspace: Unable to delete '...'. Tried 3 times...
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.195001.1540906753000.9829.1571329140678%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Mathieu Delrocq edited a comment on JENKINS-59790 Re: Container cannot connect to node because it doesn't exist I close this issue related wih to [jenkinsci/docker-plugin#757|https://github.com/jenkinsci/docker-plugin/issues/757] 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.202520.1571136505000.9823.1571326860326%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Mathieu Delrocq closed an issue as Won't Fix Jenkins / JENKINS-59790 Container cannot connect to node because it doesn't exist Change By: Mathieu Delrocq Status: Open Closed Resolution: Won't Fix 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.202520.1571136505000.9817.1571326800544%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Mathieu Delrocq edited a comment on JENKINS-59790 Re: Container cannot connect to node because it doesn't exist I close this issue related wih [ github jenkinsci/docker-plugin#757|https://github.com/jenkinsci/docker-plugin/issues/757] 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.202520.1571136505000.9813.1571326740194%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Mathieu Delrocq commented on JENKINS-59790 Re: Container cannot connect to node because it doesn't exist I close this issue related wih github jenkinsci/docker-plugin#757 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.202520.1571136505000.9809.1571326680131%40Atlassian.JIRA.
[JIRA] (JENKINS-59827) Wrong commit link to GitLab
Title: Message Title Eugene Seliverstov created an issue Jenkins / JENKINS-59827 Wrong commit link to GitLab Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-10-17 15:18 Environment: Jenkins LTS 2.190.1 (self-hosted), git plugin 3.12.1, GitLab 12 Priority: Minor Reporter: Eugene Seliverstov Let we have a job that points to GitLab repository. Any Jenkins changes view with a list of commits provides a wrong link to GitLab commit (changeset). Example page: https://JENKINS_URL/job/JOB_NAME/job/master/1/changes Expected link: https://gitlab.com/OWNER/REPO/commit/HASH Actual link: https://gitlab.com/commit/HASH I suppose the `GitLab::getChangeSetLink` is broken since maybe gitlab 7. It should include repository information in the URL. Add Comment
[JIRA] (JENKINS-59826) Error launching agent into second cloud
Title: Message Title
Andrew Cameron-Douglas created an issue
Jenkins / JENKINS-59826
Error launching agent into second cloud
Issue Type:
Bug
Assignee:
Unassigned
Components:
kubernetes-plugin
Created:
2019-10-17 15:11
Priority:
Minor
Reporter:
Andrew Cameron-Douglas
I am having trouble launching a second k8s based agent into a new cluster. My use case is that I have a "shared" cluster (where Jenkins lives) where agents usually run and I have additional clusters for dev/tst/etc. Agents in shared (using the Kubernetes plugin) cluster run CI and then deploy built app containers to the dev cluster (for example) using kubectl. Once an app container is running I want to be able to launch a new agent into the [dev] cluster using the plugin to run some tests. It looks like I should just be able to set up the second cloud in Jenkins (we use config code) and the reference it in the top of the pod definition in the pipeline when I want to launch the new agent. However, when I do the agent tries to launch in the existing cluster ("shared" in this example) rather than the cloud I prescribe. In the logs I see: ``` Oct 17, 2019 10:27:21 AM INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision Template for label jknode-devops-repotemplate-dotnetcore-test-15: Kubernetes Pod Template Oct 17, 2019 10:27:21 AM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud Building connection to Kubernetes primary-aks-eurw-dev URL https://primary-aks-eurw-dev-wr-aasda324.hcp.westeurope.azmk8s.io:443/ namespace null Oct 17, 2019 10:27:21 AM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud Connected to Kubernetes primary-aks-eurw-dev URL https://primary-aks-eurw-shared-wr-dasdad242.hcp.westeurope.azmk8s.io:443/ ``` At a glance in the source code, it looks like the plugin is pulling the incorrect client out of the cache. As you can see from the logs it looks like it starts to build the connection to the dev cluster and then retrieves the client for the shared cluster
[JIRA] (JENKINS-51191) hudson.remoting.Channel$CallSiteStackTrace: Remote call to
Title: Message Title Jeff Thompson commented on JENKINS-51191 Re: hudson.remoting.Channel$CallSiteStackTrace: Remote call to Interesting. I don't know what would have caused that change. I just scanned the Java changelog and didn't see any obvious causes. Thanks for sharing the info here! 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.190504.1525766236000.9708.1571323891074%40Atlassian.JIRA.
[JIRA] (JENKINS-59825) Can't update git client plugin
Title: Message Title Robert Hill created an issue Jenkins / JENKINS-59825 Can't update git client plugin Issue Type: Bug Assignee: Unassigned Components: git-client-plugin Created: 2019-10-17 14:34 Environment: Ubuntu Priority: Major Reporter: Robert Hill I'm new to Jenkins. I installed the various git plugins and had it working for a pipeline project. Recently, Jenkins notified me of a security vulnerability for the git client. I choose to downgrade from 3.0 to the previous version. After doing that, my pipeline lost it's reference to the git login. When I go into the manage plugins, it doesn't list the git-client with an available update. How do I get it back to using the 3.x version? Add Comment
[JIRA] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title suryatej yaramada commented on JENKINS-52816 Re: scm poll triggers even there is no change in repository(bitbucket) Mark Waite updated description with the steps to reproduce , please let me know if need 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.192737.1533040103000.9680.1571322780294%40Atlassian.JIRA.
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title Jesse Glick commented on JENKINS-59777 Re: nested docker.withRegistry() does not work I have no idea if it will be accepted; I do not maintain this plugin. Just noting the general workaround for any issues with this class of 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.202501.1571053962000.9678.1571321580253%40Atlassian.JIRA.
[JIRA] (JENKINS-47717) Allow different "Discard Old Build" options per branch on multibranch pipelines
Title: Message Title Kalle Niemitalo commented on JENKINS-47717 Re: Allow different "Discard Old Build" options per branch on multibranch pipelines roe_p pinhas, AFAIK, it works OK in a Multibranch Pipeline, where each branch becomes a nested project that discards its builds independently from the other branches. 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.186203.1509215223000.9665.1571321400473%40Atlassian.JIRA.
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title Art V commented on JENKINS-59777 Re: nested docker.withRegistry() does not work I'm hoping to get to one-shot agents (pushing for JenkinsX when it supports GitLab/Artifactory appropriately) but due to various teams/groups and the current state of our CI I am unable to do this at the moment. We also have a tendency to never want to update Jenkins and the installed plugins due to no one wanted to manage this. So I've been trying to keep Jenkins and the plugins up to date, but I keep having to hold off on updating the docker-workflow plugin due to this change in behavior. So I decided to look into it and provide a fix/PR for this scenario. And to implement your last suggestion; I would need to update our 100+ workflows and that would take time that gives very little end benefit when the long term goal is to move towards JenkinsX. So if this proposed change will not be accepted then okay; then I will stay on an older version of the plugin until I've switched to JenkinsX. 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.202501.1571053962000.9662.1571321100118%40Atlassian.JIRA.
[JIRA] (JENKINS-47717) Allow different "Discard Old Build" options per branch on multibranch pipelines
Title: Message Title roe_p pinhas commented on JENKINS-47717 Re: Allow different "Discard Old Build" options per branch on multibranch pipelines This solution/workaround doesn't seems to work. Let's say I have configured the pipeline to use: buildDiscarder(logRotator(numToKeepStr: env.BRANCH_NAME == 'master' ? '5' : '1')) This will be as an example build (branch) history: #1 master #2 master #3 master #4 master #5 master #6 master #7 feature #8 feature In this case according to the explanation of the policy when I build the master branch 5 times it will save them and will drop build#1 when I start the 6 build. If I build #7 as non master branch it will keep all the builds (#2-6) and on #8 it will remove #7 only. However this is not the case, what really happens is that on build #7 it's evaluating the condition and now the value of the buildDiscarder is 1 so its removing all the builds and keeping #7 only regardless of the branch name (it doesn't evaluate each build with the corresponding branch name) 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.186203.1509215223000.9650.1571320980412%40Atlassian.JIRA.
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title Jesse Glick commented on JENKINS-59777 Re: nested docker.withRegistry() does not work this would affect other pipelines running on the same node with different access rights Well, you can set an environment variable for the config location, but of course in this setup you have no real security anyway (including when using withRegistry)—you should use one-shot agents if at all possible. 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.202501.1571053962000.9639.1571320260586%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Soeren Uttrup commented on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. Hi Tomas Westling Not able to upgrade to 1.23.1 only 1.23.0 available 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.202251.1569939008000.9629.1571319240539%40Atlassian.JIRA.
[JIRA] (JENKINS-59611) Symlink target update fails when "noclobber" set
Title: Message Title Charusheela Bopardikar commented on JENKINS-59611 Re: Symlink target update fails when "noclobber" set P4JAVA issue. Fixed Need to test in P4Jenkins. 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.202252.1569940696000.9612.1571319000174%40Atlassian.JIRA.
[JIRA] (JENKINS-59611) Symlink target update fails when "noclobber" set
Title: Message Title Charusheela Bopardikar edited a comment on JENKINS-59611 Re: Symlink target update fails when "noclobber" set P4JAVA issue. Fixed . Need to test in P4Jenkins. 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.202252.1569940696000.9614.1571319000216%40Atlassian.JIRA.
[JIRA] (JENKINS-50573) Wrong username used for git clone with OpenSSH 7.7
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-50573 Wrong username used for git clone with OpenSSH 7.7 Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189647.1522857709000.9601.1571318760905%40Atlassian.JIRA.
[JIRA] (JENKINS-59824) Ignore timeout while provisioning
Title: Message Title Mike K updated an issue Jenkins / JENKINS-59824 Ignore timeout while provisioning Change By: Mike K Issue Type: Improvement 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.202559.1571318032000.9598.1571318100274%40Atlassian.JIRA.
[JIRA] (JENKINS-59824) Ignore timeout while provisioning
Title: Message Title
Mike K created an issue
Jenkins / JENKINS-59824
Ignore timeout while provisioning
Issue Type:
Improvement
Assignee:
Azure DevOps
Components:
azure-vm-agents-plugin
Created:
2019-10-17 13:13
Priority:
Major
Reporter:
Mike K
We've set up a new custom image which takes a lot of time provisioning (40+ minutes). I've set the deployment timeout to 5000 seconds but after around 40 minutes the VM will get deleted cause of this exception:
AzureVMCloud: createProvisionedAgent: Deployment win10pp16-1017121639027 not yet finished (Running): Microsoft.Compute/virtualMachines:win10pp-725b70 - waited 2,310 seconds
Oct 17, 2019 12:56:06 PM SEVERE com.microsoft.azure.vmagent.AzureVMCloud$2 callFailure creating provisioned agent 'win10pp-725b70'
com.microsoft.azure.vmagent.exceptions.AzureCloudException: AzureVMCloud: createProvisionedAgent: Deployment Failed: Microsoft.Compute/virtualMachines:win10pp-725b70 - Conflict - {status=Failed, error={code=ResourceDeploymentFailure, message=The resource operation completed with terminal provisioning state 'Failed'., details=[{code=OSProvisioningTimedOut, message=OS Provisioning for VM 'win10pp-725b70' did not finish in the allotted time. The VM may still finish provisioning successfully. Please check provisioning state later. Also, make sure the image has been properly prepared (generalized).
* Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/
* Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/ }]}}
at com.microsoft.azure.vmagent.exceptions.AzureCloudException.create(AzureCloudException.java:37)
at com.microsoft.azure.vmagent.AzureVMCloud.createProvisionedAgent(AzureVMCloud.java:584)
at com.microsoft.azure.vma
[JIRA] (JENKINS-47591) Allow each Kubernetes slave pod to use unique Persistent Volume / Storage
Title: Message Title Torsten Reinhard commented on JENKINS-47591 Re: Allow each Kubernetes slave pod to use unique Persistent Volume / Storage Carlos Sanchez Can this dynamic PVC cause issues, like described at https://groups.google.com/forum/#!topic/jenkinsci-users/W83Ew2Og5Zo ? How to avoid those issues ? 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.186064.1508775809000.9567.1571317320517%40Atlassian.JIRA.
[JIRA] (JENKINS-44849) Changeset for first run of generated job is empty
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-44849 Changeset for first run of generated job is empty Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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.182912.1497360024000.9518.1571316182303%40Atlassian.JIRA.
[JIRA] (JENKINS-33274) "Base build" link for first build of branch project
Title: Message Title Jesse Glick updated JENKINS-33274 Jenkins / JENKINS-33274 "Base build" link for first build of branch project Change By: Jesse Glick Status: Reopened Open 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.168665.145693029.9512.1571316066095%40Atlassian.JIRA.
[JIRA] (JENKINS-58601) Allow deletion of one or more entries from job's config history
Title: Message Title Hank Zill commented on JENKINS-58601 Re: Allow deletion of one or more entries from job's config history I just wanted to chime in and say that allowing people with build job privileges to delete change entries makes this plugin much less useful from an auditing and compliance perspective. 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.200761.1563800501000.9495.1571315700500%40Atlassian.JIRA.
[JIRA] (JENKINS-59638) Notify Testers
Title: Message Title Paul O'Brien commented on JENKINS-59638 Re: Notify Testers Thanks so much Mez Pahlan! Enjoy the holiday! 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.202320.1570088671000.9492.1571315520160%40Atlassian.JIRA.
[JIRA] (JENKINS-59823) Extend cps interface so plugins can que additional Steps.
Title: Message Title Leon Moll created an issue Jenkins / JENKINS-59823 Extend cps interface so plugins can que additional Steps. Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-plugin Created: 2019-10-17 12:27 Priority: Minor Reporter: Leon Moll I'm building a Plugin in Jenkins that provides an API for scripts that are started from a pipeline-script to independently communicate with jenkins. For example a shell-script can then tell jenkins to start a new stage from the running script. After getting the communication between the plugin and the script working with Unix Domain Sockets, I wanted to start a stage from an exported callback proxy. Here is where I've hit a brick wall. I was unable to hook into life cycle and inject a new StageStep in any way I could think of. This SO issue demonstrates my stuggles: https://stackoverflow.com/q/58409878/3968618 So finally I've got it to work with reflection (see the answer), but as you can tell, it's hacky as hell. This issue is a request to provide an interface to safely inject a new step by name. Basically a way to simply call DSL.invokeStep(sd, args) from inside a step/callback. I understand this is not the intentional usage, and you might feel the request is hacky in and of itself. But I have been thinking about building a way for scripts to asynchronously communicate with jenkins for some time now, and feel it would be a very good way to make calling things like shell scripts from a pipeline much more powerful, useful and extendable. If my company will allows this, I am planning to make the plugin publicly available for anyone to use.
[JIRA] (JENKINS-58607) Problem configuring BitBucket Push and Pull Request Plugin
Title: Message Title Christian Del Monte started work on JENKINS-58607 Change By: Christian Del Monte 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.200768.1563829779000.9488.1571313960912%40Atlassian.JIRA.
[JIRA] (JENKINS-58607) Problem configuring BitBucket Push and Pull Request Plugin
Title: Message Title Christian Del Monte commented on JENKINS-58607 Re: Problem configuring BitBucket Push and Pull Request Plugin Hi Renat Kabirov please create an issue on the github repository of the plugin: https://github.com/jenkinsci/bitbucket-push-and-pull-request-plugin Thanks Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200768.1563829779000.9486.1571313960709%40Atlassian.JIRA.
[JIRA] (JENKINS-59822) When users are running build with parameters are not printed on console or in build home page unlike builds triggered by timers display these values in console output and in bui
Title: Message Title Chandra Babu created an issue Jenkins / JENKINS-59822 When users are running build with parameters are not printed on console or in build home page unlike builds triggered by timers display these values in console output and in build home page Issue Type: Improvement Assignee: Unassigned Attachments: image-2019-10-17-16-01-00-655.png, image-2019-10-17-16-01-34-455.png Components: parameterized-trigger-plugin Created: 2019-10-17 12:03 Priority: Minor Reporter: Chandra Babu When users are running build with parameters are not printed on console or in build home page unlike builds triggered by timers display these values in console output and in build home page This is confusing in below scenario - If parameterized build is triggered by a timer and the same build if user triggers, it still shows the parameters used by the timer in console output and in build home page, than showing new parameters used by the user while rebuilding.. See screenshot It would be good if started by user also shows parameters since user has selected different set of parameters when rebuilt
[JIRA] (JENKINS-59808) Jenkins PR(pull request) build fails for 1st time
Title: Message Title Christian Del Monte commented on JENKINS-59808 Re: Jenkins PR(pull request) build fails for 1st time Hi tanzeel rehman please assign the issue to the mantainer of the Bitbucket Branch Source plugin. I can help you only in case you are using exclusively the Bitbucket Push And Pull Request Plugin Thanks Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202539.1571256507000.9483.1571313780379%40Atlassian.JIRA.
[JIRA] (JENKINS-59820) Getting 403 error when builds are triggering.
<<< text/html; charset="UTF-8": Unrecognized >>>
[JIRA] (JENKINS-59821) Support AWS SSM Session Manager SSH Connection
Title: Message Title Ebrahim Moshaya created an issue Jenkins / JENKINS-59821 Support AWS SSM Session Manager SSH Connection Issue Type: New Feature Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-10-17 10:47 Environment: Jenkins ver. 2.199 Priority: Minor Reporter: Ebrahim Moshaya AWS Have release an update to https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-getting-started-enable-ssh-connections.html Only change on the client side is to add the following to ~/.ssh/config # SSH over Session Manager host i-* mi-* ProxyCommand sh -c "aws ssm start-session --target %h --document-name AWS-StartSSHSession --parameters 'portNumber=%p'" The ec2 plugin needs updating to allow instance id be an option in the Connection Strategy dropdown.
[JIRA] (JENKINS-59820) Getting 403 error when builds are triggering.
Title: Message Title bjm 78973 updated an issue Jenkins / JENKINS-59820 Getting 403 error when builds are triggering. Change By: bjm 78973 Attachment: InkedCapture (002)_LI.jpg 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.202554.1571306766000.9473.1571308080106%40Atlassian.JIRA.
[JIRA] (JENKINS-59820) Getting 403 error when builds are triggering.
Title: Message Title bjm 78973 updated an issue Jenkins / JENKINS-59820 Getting 403 error when builds are triggering. Change By: bjm 78973 Attachment: Capture.JPG 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.202554.1571306766000.9472.1571307840072%40Atlassian.JIRA.
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title Art V edited a comment on JENKINS-59777 Re: nested docker.withRegistry() does not work I cannot use the cli `docker login` approach as this would affect other pipelines running on the same node with different access rights.In my use case we use Artifactory where we have a virtual repo for reading and a dev repo for publishing our docker images. For example our dockerfile uses the virtual read repo for the `FROM` clause of the image.Artifactory uses it's own permissions to limit the access to different internal repos of the virtual repo access and using the cli `docker login` approach will overwrite the credentials allowing other pipelines to access things not allowed.So with the example above, this works in 1.15 of docker-workflow plugin, but any newer versions of the plugin only the last `docker.withRegistry()` works. So updating the logic of docker-commons, this above example will continue to work when using newer versions of docker-workflow 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.202501.1571053962000.9471.1571307720129%40Atlassian.JIRA.
[JIRA] (JENKINS-59777) nested docker.withRegistry() does not work
Title: Message Title Art V assigned an issue to Jesse Glick Jenkins / JENKINS-59777 nested docker.withRegistry() does not work Change By: Art V Assignee: Art V Jesse Glick 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.202501.1571053962000.9469.1571307660237%40Atlassian.JIRA.
[JIRA] (JENKINS-59694) When build step fails or get aborted upload is still tried
Title: Message Title Mez Pahlan commented on JENKINS-59694 Re: When build step fails or get aborted upload is still tried Hi, sorry I haven't had time to look at this just yet. I'm on holiday at the moment but might get some time on the weekend. 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.202393.1570520886000.9467.1571307180138%40Atlassian.JIRA.
[JIRA] (JENKINS-59638) Notify Testers
Title: Message Title Mez Pahlan commented on JENKINS-59638 Re: Notify Testers I'm on holiday at the moment but should get some time this weekend to release this. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202320.1570088671000.9464.1571307121109%40Atlassian.JIRA.
[JIRA] (JENKINS-59820) Getting 403 error when builds are triggering.
Title: Message Title bjm 78973 created an issue Jenkins / JENKINS-59820 Getting 403 error when builds are triggering. Issue Type: Bug Assignee: Unassigned Attachments: Capture.JPG Components: jenkins-cloudformation Created: 2019-10-17 10:06 Labels: jenkins Bitbucket atlassian Priority: Critical Reporter: bjm 78973 After upgrading jenkins to 2.190.1 pull request builds are not triggering from the bitbucket. When we trigger a jeninks build getting 403 error. Add Comment
[JIRA] (JENKINS-59638) Notify Testers
Title: Message Title Paul O'Brien commented on JENKINS-59638 Re: Notify Testers Hi Mez Pahlan Niall Kelly, thanks for raising and fixing this issue. Do you know when this will intended to be released? Cheers, Paul 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.202320.1570088671000.9461.1571305320307%40Atlassian.JIRA.
[JIRA] (JENKINS-59819) Inheritance Plugin causes 'Rebuild' button to disappear from Pipeline jobs
Title: Message Title Artalus S. created an issue Jenkins / JENKINS-59819 Inheritance Plugin causes 'Rebuild' button to disappear from Pipeline jobs Issue Type: Bug Assignee: Unassigned Components: project-inheritance-plugin Created: 2019-10-17 09:24 Environment: Jenkins ver. 2.184 inheritance-plugin Version 19.08.02 Priority: Major Reporter: Artalus S. With Inheritance Plugin installed, every new Pipeline job run lacks the `Rebuild` button. "New" in terms that if I check some old build `#90` from a week or so ago, the button is present and working; but if I press it, or start a build in any other way, in build `#91` the button is gone. If I manually change URL in browser from `pipeline/91` to `pipeline/91/rebuild`, I get the following stacktrace: java.lang.AbstractMethodError: you must override the new overload of isApplicable in hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor at com.sonyericsson.rebuild.RebuildValidator.isApplicable(RebuildValidator.java:50) at com.sonyericsson.rebuild.RebuildActionFactory.createFor(RebuildActionFactory.java:61) at hudson.model.Run.getTransientActions(Run.java:386) at hudson.model.Run.getDynamic(Run.java:2566) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:454) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:7
[JIRA] (JENKINS-45181) Description does not display line breaks
Title: Message Title Alexey Marchenko commented on JENKINS-45181 Re: Description does not display line breaks I think it will be OK not to change design — just do like Git — display only first line of multiline description on page with builds list and full description on build page 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.183302.1498661029000.9450.1571303100186%40Atlassian.JIRA.
[JIRA] (JENKINS-59818) Mangement of "Disable Auth Request Signature" flag is inverted
Title: Message Title Ben Wolf updated an issue Jenkins / JENKINS-59818 Mangement of "Disable Auth Request Signature" flag is inverted Change By: Ben Wolf Environment: Plugin name: SAML PluginPlugin version: 1.1.3 In this version, there is an inverted management of the checkbox "Disable Auth Request Signature".When it is not checked, the "securityRealm/metadata" route does not expose anymore the certificated.When it is checked it expose the certificate.That should be the opposite. 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.202550.1571302616000.9448.1571302920603%40Atlassian.JIRA.
