[JIRA] (JENKINS-53208) Split main configuration page, takes too long to load
Title: Message Title Dirk Heinrichs commented on JENKINS-53208 Re: Split main configuration page, takes too long to load More than a year has passed now and loading that page takes longer and longer while Docker templates are added. 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.193234.1535030695000.4977.1576051320174%40Atlassian.JIRA.
[JIRA] (JENKINS-60435) shell scripts file permission set the default value to 0600
Title: Message Title Minghui Ma created an issue Jenkins / JENKINS-60435 shell scripts file permission set the default value to 0600 Issue Type: New Feature Assignee: Unassigned Components: core Created: 2019-12-11 08:21 Environment: Jenkins ver. 2.176.1 master is ubuntu 16.04. all slaves is ubuntu 14.04. Priority: Minor Reporter: Minghui Ma rw-rw-r- 1 buildfarm buildfarm 71 Dec 11 15:33 /tmp/jenkins2989735420931240305.sh rw-rw-r- 1 buildfarm buildfarm 71 Dec 11 15:32 /tmp/jenkins4366322686308396837.sh rw-rw-r- 1 buildfarm buildfarm 563 Dec 11 15:32 /tmp/jenkins6911470318430213229.sh I found the jenkins save the shell script in the /tmp path on ubuntu linux, and the file permission is 644. there are security risks. on the same server other linux account can access these shell script files, maybe he/she will get password from these files (if i save the password into these hell script files). so I suggest that set these scripts file permission to 0600. like ssh-slaves-plugin set the remote working directory permission to 0700.
[JIRA] (JENKINS-60435) shell scripts file permission set the default value to 0600
Title: Message Title Minghui Ma updated an issue Jenkins / JENKINS-60435 shell scripts file permission set the default value to 0600 Change By: Minghui Ma -rw-rw-r-- 1 buildfarm buildfarm 71 Dec 11 15:33 /tmp/jenkins2989735420931240305.sh-rw-rw-r-- 1 buildfarm buildfarm 71 Dec 11 15:32 /tmp/jenkins4366322686308396837.sh-rw-rw-r-- 1 buildfarm buildfarm 563 Dec 11 15:32 /tmp/jenkins6911470318430213229.shI found the jenkins save the shell script in the /tmp path on ubuntu linux, and the file permission is 644.there are security risks.on the same server other linux account can access these shell script files, maybe he/she will get password from these files (if i save the password into these hell shell script files).so I suggest that set these scripts file permission to 0600. (or give a way to set permission for these script ) like ssh-slaves-plugin set the remote working directory permission to 0700. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this me
[JIRA] (JENKINS-32349) Entering a newline in a Label description makes "slave" matrix axis unavailable
Title: Message Title Benedikt Brückmann commented on JENKINS-32349 Re: Entering a newline in a Label description makes "slave" matrix axis unavailable We just ran across this issue. Reproduced: german Umlauts like ü are not a problem Reproduced: new lines are the problem Futhermore a "corrupted" label destroys the configuration of a job if one saves the job (without any change by the user). Steps 2 repeat for this: Having a working matrix job create label with newline Opening Job Config Hit save (no manual changes) => Job is no longer working, as the setting of labels/slaves was deleted from the underlying 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.167458.1452195489000.4982.1576052880378%40Atlassian.JIRA.
[JIRA] (JENKINS-51849) Plugins install fails due to java.net.SocketTimeoutException: Read timed out error
Title: Message Title Simon Tunnat commented on JENKINS-51849 Re: Plugins install fails due to java.net.SocketTimeoutException: Read timed out error I'm currently having the same issue: Starting the installation of chucknorris on behalf of anonymous Dec 11, 2019 9:29:22 AM INFO hudson.model.UpdateCenter$UpdateCenterConfiguration downloadDownloading chucknorris Dec 11, 2019 9:29:22 AM SEVERE hudson.model.UpdateCenter$DownloadJob runFailed to install chucknorris java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:607) at sun.net.NetworkClient.doConnect(NetworkClient.java:175) at sun.net.www.http.HttpClient.openServer(HttpClient.java:463) at sun.net.www.http.HttpClient.openServer(HttpClient.java:558) at sun.net.www.http.HttpClient.(HttpClient.java:242) at sun.net.www.http.HttpClient.New(HttpClient.java:339) at sun.net.www.http.HttpClient.New(HttpClient.java:357) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1226) at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:990) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498) at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:3061) at java.net.URLConnection.getHeaderFieldLong(URLConnection.java:629) at java.net.URLConnection.getContentLengthLong(URLConnection.java:501) at java.net.URLConnection.getContentLength(URLConnection.java:485) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1161) Caused: java.net.SocketTimeoutException: connect timed out at sun.reflect.GeneratedConstructorAccessor60.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1950) at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1945) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1944) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1514) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1177) Caused: java.io.IOException: Failed to load http://updates.jenkins-ci.org/download/plugins/chucknorris/1.2/chucknorris.hpi to /opt/jenkins/plugins/chucknorris.jpi.tmp at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1184) Caused: java.io.IOException: Failed to download from http://updates.jenkins-ci.org/download/plugins/chucknorris/1.2/chuck
[JIRA] (JENKINS-51849) Plugins install fails due to java.net.SocketTimeoutException: Read timed out error
Title: Message Title Simon Tunnat commented on JENKINS-51849 Re: Plugins install fails due to java.net.SocketTimeoutException: Read timed out error Even curl fails: $ curl -i --verbose http://updates.jenkins-ci.org * About to connect() to updates.jenkins-ci.org port 80 (#0) * Trying 52.202.51.185... * Connection refused * Failed connect to updates.jenkins-ci.org:80; Connection refused * Closing connection 0 curl: (7) Failed connect to updates.jenkins-ci.org:80; Connection refused 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.191325.1528691966000.5002.1576053186653%40Atlassian.JIRA.
[JIRA] (JENKINS-60398) Maven Artifact ChoiceListProvider (Nexus) sorting issue
Title: Message Title shyam varghese commented on JENKINS-60398 Re: Maven Artifact ChoiceListProvider (Nexus) sorting issue thanks Stephan Watermeyer, Any plans to have this 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.203453.157587112.5004.1576054380562%40Atlassian.JIRA.
[JIRA] (JENKINS-60239) Aborted catchError sets build result to ABORTED if fail fast is true
Title: Message Title Daniel Puiu assigned an issue to Andrew Bayer Jenkins / JENKINS-60239 Aborted catchError sets build result to ABORTED if fail fast is true Change By: Daniel Puiu Assignee: Andrew Bayer 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.203219.1574333797000.5011.1576054680309%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title Pedro Cuello Orozco commented on JENKINS-60409 Re: Cloud Configuration Length Cap Hi guys, I am facing the same issue when I try to give access to a new user into my permission matrix Role. I guess it happens in cloud version, but I am facing it in the not cloud version 2.207. I am forced to get back to my previous version 2.196 Regards, 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.203466.1575915955000.5018.1576055761013%40Atlassian.JIRA.
[JIRA] (JENKINS-60430) stopping a job while in reconcile will not stop the reconcile (the job itself will however stop)
Title: Message Title Karl Wirth commented on JENKINS-60430 Re: stopping a job while in reconcile will not stop the reconcile (the job itself will however stop) Hi Eric Daigneault - Thanks for letting us know about this. Please let me know which version of the plugin you are using and which version of P4D it is connected to. 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.203502.1576019104000.5023.1576056060336%40Atlassian.JIRA.
[JIRA] (JENKINS-60436) Password verification failed
Title: Message Title Anamika Gupta created an issue Jenkins / JENKINS-60436 Password verification failed Issue Type: Bug Assignee: Azure DevOps Components: azure-app-service-plugin Created: 2019-12-11 09:57 Priority: Major Reporter: Anamika Gupta java.security.UnrecoverableKeyException: Password verification failed at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:783) Caused: java.io.IOException: Keystore was tampered with, or password was incorrect at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:785) at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:56) at sun.security.provider.KeyStoreDelegator.engineLoad(KeyStoreDelegator.java:224) at sun.security.provider.JavaKeyStore$DualFormatJKS.engineLoad(JavaKeyStore.java:70) at java.security.KeyStore.load(KeyStore.java:1445) at sun.security.ssl.TrustStoreManager$TrustAnchorManager.loadKeyStore(TrustStoreManager.java:367) at sun.security.ssl.TrustStoreManager$TrustAnchorManager.getTrustedCerts(TrustStoreManager.java:315) at sun.security.ssl.TrustStoreManager.getTrustedCerts(TrustStoreManager.java:59) at sun.security.ssl.TrustManagerFactoryImpl.engineInit(TrustManagerFactoryImpl.java:51) Caused: java.security.KeyStoreException: problem accessing trust store at sun.security.ssl.TrustManagerFactoryImpl.engineInit(TrustManagerFactoryImpl.java:75) at javax.net.ssl.TrustManagerFactory.init(TrustManagerFactory.java:250) at okhttp3.internal.Util.platformTrustManager(Util.java:664) Caused: java.lang.AssertionError: No System TLS at okhttp3.internal.Util.assertionError(Util.java:502) at okhttp3.internal.Util.platformTrustManager(Util.java:672) at okhttp3.OkHttpClient.(OkHttpClient.java:248)
[JIRA] (JENKINS-60434) "Prepare for shutdown" should continue executing already running pipelines to completion
Title: Message Title Ulrich Köhler commented on JENKINS-60434 Re: "Prepare for shutdown" should continue executing already running pipelines to completion Another use case: The ThinBackup plugin sets Jenkins to shutdown and waits for all jobs to finish. But Pipeline Jobs never finishes: dead lock. 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.203506.1576045591000.5040.1576058402783%40Atlassian.JIRA.
[JIRA] (JENKINS-60436) Password verification failed while integrating Azure App Service deployment
Title: Message Title Anamika Gupta updated an issue Jenkins / JENKINS-60436 Password verification failed while integrating Azure App Service deployment Change By: Anamika Gupta Summary: Password verification failed while integrating Azure App Service deployment 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.203508.157605826.5057.1576058460768%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 Sai Kiran, I need more context. If oyu open a issue on the github repo of the plugin, it would go definitely faster would be easier for me to help you. Thanks. https://github.com/jenkinsci/bitbucket-push-and-pull-request-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.200768.1563829779000.5074.1576058820762%40Atlassian.JIRA.
[JIRA] (JENKINS-58607) Problem configuring BitBucket Push and Pull Request Plugin
Title: Message Title Sai Kiran commented on JENKINS-58607 Re: Problem configuring BitBucket Push and Pull Request Plugin Can you Please Check your e-mail, I have shared all the details over there...If still you need any reference, I will create a issue on your github page. Waiting for your kind response. 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.5078.1576059060318%40Atlassian.JIRA.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Matthieu R. commented on JENKINS-58061 Re: Can't configure SonarQube User Token (text field replaced with credentials drop-down). Hello, Is this issue will be resolved ? Or a workaround will be explained ? I can't configure Sonar Scanner without downgrade plugins versions. 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.200082.1560824562000.5080.1576059060374%40Atlassian.JIRA.
[JIRA] (JENKINS-60437) Manually setting git commit status sets it for two contexts
Title: Message Title
Cyprien Quilici created an issue
Jenkins / JENKINS-60437
Manually setting git commit status sets it for two contexts
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-12-11 10:14
Environment:
Jenkins: 2.190.1 Git plugin: 4.0.0
Priority:
Minor
Reporter:
Cyprien Quilici
I'm trying to create two different jobs, the build job and E2E tests job. I'd like the two jobs to annotate the git commit with their results and the results not to get mixed up. On the build job, I didn't change any configuration and the git plugin does its magic in the background as expected. In my E2E Jenkinsfile, I'm setting the git commit status manually as lots of guys on the internet suggest, with a method: void setBuildStatus (String message, JobResult jobResult, def repoName) { step([ $class : "GitHubCommitStatusSetter", reposSource : [$class: "ManuallyEnteredRepositorySource", url: "https://github.com/Talend/$repoName"], contextSource : [$class: "ManuallyEnteredCommitContextSource", context: "E2E tests"], errorHandlers : [[$class: "ChangingBuildStatusErrorHandler", result: JobResult.UNSTABLE.name()]], statusResultSource: [$class: "ConditionalStatusResultSource", results: [[$class: "AnyBuildResult", message: message, state: jobResult.name()]] ] ]) } Which is used at startup, in post > success and post > failure. When only the build job runs, the git commit is marked with continuous-integration/jenkins/branch, the details link points to my build job, this is as intended. When the E2E tests run though, the commit gets marked with E2E tests (good) but the continuous-integration/jenkins/branch ** gets overwritten by the result of the E2E tests job and that's not intended. Both details link now p
[JIRA] (JENKINS-60398) Maven Artifact ChoiceListProvider (Nexus) sorting issue
Title: Message Title Stephan Watermeyer commented on JENKINS-60398 Re: Maven Artifact ChoiceListProvider (Nexus) sorting issue There is no ETA. Feel free to raise a PR and then i can merge it to get a new release build. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203453.157587112.5092.1576059480123%40Atlassian.JIRA.
[JIRA] (JENKINS-60418) issue of Integration webhook with bitbucket when using bitbucket pull and push plugin
Title: Message Title Christian Del Monte commented on JENKINS-60418 Re: issue of Integration webhook with bitbucket when using bitbucket pull and push plugin Hi vikas goyal may you deinstall both plugins and after that reinstall only the 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.203480.1575978042000.5094.1576059600376%40Atlassian.JIRA.
[JIRA] (JENKINS-58607) Problem configuring BitBucket Push and Pull Request Plugin
Title: Message Title Sai Kiran edited a comment on JENKINS-58607 Re: Problem configuring BitBucket Push and Pull Request Plugin Can you Please Check your e-mail, I have shared all the details over there...If still you need any reference, I will create a issue on your github page.Waiting for your kind response. 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.5105.1576059780712%40Atlassian.JIRA.
[JIRA] (JENKINS-60418) issue of Integration webhook with bitbucket when using bitbucket pull and push plugin
Title: Message Title vikas goyal edited a comment on JENKINS-60418 Re: issue of Integration webhook with bitbucket when using bitbucket pull and push plugin Hi Christian, Thanks for the reply. ( Appreciated ) What do you mean by deinstall? Are you talking about uninstall? I have tried this. but still no luck. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203480.1575978042000.5107.1576059781002%40Atlassian.JIRA.
[JIRA] (JENKINS-60418) issue of Integration webhook with bitbucket when using bitbucket pull and push plugin
Title: Message Title vikas goyal commented on JENKINS-60418 Re: issue of Integration webhook with bitbucket when using bitbucket pull and push plugin Hi Christian, What do you mean by deinstall? Are you talking about uninstall? I have tried this. but still no luck. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203480.1575978042000.5102.1576059780510%40Atlassian.JIRA.
[JIRA] (JENKINS-60418) issue of Integration webhook with bitbucket when using bitbucket pull and push plugin
Title: Message Title vikas goyal commented on JENKINS-60418 Re: issue of Integration webhook with bitbucket when using bitbucket pull and push plugin One more question is this plugin works if Bitbucket pull request plugin is installed on Jenkins. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203480.1575978042000.5109.1576059900209%40Atlassian.JIRA.
[JIRA] (JENKINS-60438) updates.jenkins.io down/offline - SPOF - no documentation
Title: Message Title Gunter Grodotzki created an issue Jenkins / JENKINS-60438 updates.jenkins.io down/offline - SPOF - no documentation Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-12-11 10:25 Priority: Blocker Reporter: Gunter Grodotzki updates.jenkins.io is down/offline (intermittent). It is a single-point-of-failure which is currently blocking jenkins installations. There is no easy way to mirror. Rsync offers files, but it can not be used as direct replacement as updaters rely on /download/ which is not part of the sync. Add Comment
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Ian Williams commented on JENKINS-58061 Re: Can't configure SonarQube User Token (text field replaced with credentials drop-down). Jeff VIncent, wondering why this is not flagged as Component "sonar" as well? That might get the attention of the SonarQube team. 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.200082.1560824562000.5118.1576060560351%40Atlassian.JIRA.
[JIRA] (JENKINS-53208) Split main configuration page, takes too long to load
Title: Message Title pjdarton commented on JENKINS-53208 Re: Split main configuration page, takes too long to load FYI most of the folks currently writing/maintaining Jenkins & its plugins ended up in that position simply because, at some point in the past, they wanted a change that nobody else wanted as much as they did. The great strength of FOSS like Jenkins is that, unlike privately owned software, you always have the option to join in. 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.193234.1535030695000.5116.1576060560325%40Atlassian.JIRA.
[JIRA] (JENKINS-60216) Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible
Title: Message Title Max Matissek commented on JENKINS-60216 Re: Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible I want to Start a Jenkins-Job from a Pipeline with a "Extensible Choice Parameter" (SELECTEDVERSION). Pipeline-Command: build job: 'testjob', parameters: [string(name: 'SELECTEDVERSION', value: artifactUrl)] After the update of the "Pipeline: Build Step" Plugin to Verison 2.10 I get the Message "The parameter 'SELECTEDVERSION' did not have the type expected by testjob. Converting to Extensible Choice". What should I use instead of "string"? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203189.1574194043000.5125.1576060860149%40Atlassian.JIRA.
[JIRA] (JENKINS-59671) Support storing multiple Jenkins credentials in a single Secrets Manager secret
Title: Message Title Chris Kilding commented on JENKINS-59671 Re: Support storing multiple Jenkins credentials in a single Secrets Manager secret After further consideration, there are significant problems with storing multiple credentials in 1 AWS secret: An AWS binary secret cannot hold multiple PKCS#12 certificate credentials, (a) because a single certificate cred is close to the secret size limits already (b) because there would be no indicator of where one certificate ended and the next began, without inventing a custom binary schema and adding extra parsing code. Credentials tracking & Cloudwatch logs. The 1:1 model makes this easy: accessing 1 credential creates 1 entry in Cloudwatch. If there are multiple credentials in a secret, we cannot know from Cloudwatch which one was actually used. Permissions. The 1:1 model makes permissions easy: if you granted access to a secret in IAM, Jenkins can access that secret. If we have multiple creds per secret we cannot limit access to individual creds with IAM. 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 v
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title Charusheela Bopardikar started work on JENKINS-60144 Change By: Charusheela Bopardikar 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.203005.1573570536000.5144.1576062840652%40Atlassian.JIRA.
[JIRA] (JENKINS-60439) Unable to specify ExecuteDslScripts.additionalParameters from Groovy
Title: Message Title
Carsten Pfeiffer created an issue
Jenkins / JENKINS-60439
Unable to specify ExecuteDslScripts.additionalParameters from Groovy
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2019-12-11 11:21
Priority:
Minor
Reporter:
Carsten Pfeiffer
I'm trying to set additionalParameters from Groovy code, similar to JENKINS-44128.
steps {
jobDsl {
additionalClasspath(somePath)
removedJobAction('DELETE')
removedViewAction('DELETE')
targets(someTargets)
additionalParameters([arg1: 'test', arg2: 'test2'])
}
}
Whatever I do, I cannot specify the map of additionalParameters. I always get:
ERROR: (unknown source) No signature of method: javaposse.jobdsl.plugin.structs.DescribableContext.additionalParameters() is applicable for argument types: (java.util.LinkedHashMap) values: ...
Could it be that maps cannot be passed at all, atm, maybe because they are not handled in https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/structs/DescribableContext.groovy#L72 ?
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Matthew Smeeth closed an issue as Won't Fix Not fixing due to being able to prevent login -s being called by enabling the "hide tickets" option. Jenkins / JENKINS-60142 ConnectionHelper.java constructors call connectionRetry() Change By: Matthew Smeeth 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...@
[JIRA] (JENKINS-60434) "Prepare for shutdown" should continue executing already running pipelines to completion
Title: Message Title
Thomas de Grenier de Latour commented on JENKINS-60434
Re: "Prepare for shutdown" should continue executing already running pipelines to completion
In case it can be useful to anyone, here is the "planned upgrade" process we have for Jenkins in my company. It relies on a custom quiet-mode implementation we've implemented in an internal plugin, which basically allows already running builds to terminate (including Pipelines), but forbids starting execution of new builds (expect if they are necessary for termination of the already running builds). The overall process is automated (we have many Jenkins instances), and it goes like this:
activate the custom quiet-down mode (forbid starting new builds)
poll Jenkins until it's idle, for up to X minutes, and then do the upgrade (including an actual restart)
on time-out of this polling, cancel the planned upgrade (cancel the custom quiet-mode), and retry it all later (sometimes we have to find arrangements with users, so that they don't launch their freaking 18 hours tests suite on the day we are planning to do an upgrade)
We don't have plans/time to publish and maintain this as a community plugin, but if someone wants to do something similar, I will dump the code below, feel free to reuse what you want. Note that we would probably never had written this code if we had not been bitten many times by JENKINS-34256. A few years ago, we were simply using the standard Jenkins quiet-mode, but then stuck Pipelines (when the upgrade was cancelled) really became an issue... Now that JENKINS-34256 is fixed, I don't know, we might consider going back to this standard solution. But I think our users prefer having their Pipelines finished before the upgrade, rather than paused/resumed (mainly because the "resume" part is not always smooth: some plugins upgrades might break compatibility of the serialized data, etc.). Anyway, this is the "interesting" part of the code, the QuietDownQueueTaskDispatcher, which filters which new Queue.Item can actually be started when in (custom) quiet-mode.
@Extension
public class QuietDownQueueTaskDispatcher extends QueueTaskDispatcher {
@Inject
QuietDownStateManager quietDownStateManager;
// key: upstreamProject+upstreamBuild from an UpstreamCause
// value: true if children builds should be allowed to run
private ConcurrentHashMap knownUpstreamCauses = new ConcurrentHashMap<>();
// used to decide when cache should be flushed
private AtomicLong quietDownTimestamp = new AtomicLong(0l);
@Override
public @CheckForNull CauseOfBlockage canRun(Queue.Item item) {
QuietDownState currentState = quietDownStateManager.getState();
if (!currentState.isDown()) {
return null;
}
// flush cache if quietDown state has changed
if (quietDownTimestamp.getAndSet(currentState.since()) != currentState.since()) {
knownUpstreamCauses.clear();
}
Queue.Task task = item.task;
// always allow some kind of tasks
if (task instanceof NonBlockingTask || task instanceof ContinuedTask) {
return null;
}
// allow build task because of its upstream cause
if (hasAllowingCause(item.getCauses())) {
return null;
}
// not allowed, let's expl
[JIRA] (JENKINS-59671) Support storing multiple Jenkins credentials in a single Secrets Manager secret
Title: Message Title Chris Kilding commented on JENKINS-59671 Re: Support storing multiple Jenkins credentials in a single Secrets Manager secret I don’t believe the above problems are solvable without significantly complicating the plugin, or adding the possibility of users misunderstanding the credential storage format in Secrets Manager. I’m therefore inclined to close this ticket as wontfix, unless anyone has other ideas. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202363.1570221511000.5185.1576064100066%40Atlassian.JIRA.
[JIRA] (JENKINS-60117) Rework sorting for the Enabled columns of Installed in Plugin Manager
Title: Message Title Kalana Wijethunga commented on JENKINS-60117 Re: Rework sorting for the Enabled columns of Installed in Plugin Manager Hi Oleg Nenashev, Shall I work on this? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202966.157338165.5190.1576064760431%40Atlassian.JIRA.
[JIRA] (JENKINS-60440) Invalid git username/password on Jenkins agent when using Vault Username-Password Credential
Title: Message Title Gordon Li created an issue Jenkins / JENKINS-60440 Invalid git username/password on Jenkins agent when using Vault Username-Password Credential Issue Type: Bug Assignee: Mark Waite Components: git-plugin, hashicorp-vault-plugin Created: 2019-12-11 11:45 Environment: VM host: Windows 10 1909 running Docker Desktop Community 19.03.5 Jenkins master: Docker image jenkins/jenkins:latest Jenkins agent: Docker image openjdk:8-stretch + Swarm-Client 3.17 plugin Hashicorp Vault: Docker image vault:latest Labels: vault credentials Priority: Major Reporter: Gordon Li My Jenkins master is running Debian 9 with Jenkins 2.208, Git-plugin 4.0.0 and Hashicorp-vault-plugin 3.0.0. My Jenkins agent is running Debian 9 with Swarm-client plugin 3.17. My master is set to 0 executors so that all jobs run on the agent. I have my Bitbucket credentials saved in Jenkins 3 times - "Username with password", "Vault Username-Password Credential" with K/V engine 1 and "Vault Username-Password Credential" with K/V engine 2. I have a test freestyle job that does nothing except fetch a Git repository from https://bitbucket.org/... If set the job's Git credentials to use the "Username with password" credentials then the agent successfully fetches the repository. If I use either of the "Vault Username-Password Credential" credentials then the agent fails on the command "git fetch --tags --progress ..." with "remote: Invalid username or password" In a pipeline job with script from SCM, the master is able to fetch the repository with all 3 credential types but the agent can onl
[JIRA] (JENKINS-60117) Rework sorting for the Enabled columns of Installed in Plugin Manager
Title: Message Title Oleg Nenashev commented on JENKINS-60117 Re: Rework sorting for the Enabled columns of Installed in Plugin Manager Feel free to do so 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.202966.157338165.5194.1576065300184%40Atlassian.JIRA.
[JIRA] (JENKINS-60441) Upgrade AWS SDK dependency in Cloudbees Core
Title: Message Title Chris Kilding created an issue Jenkins / JENKINS-60441 Upgrade AWS SDK dependency in Cloudbees Core Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-12-11 11:55 Priority: Minor Reporter: Chris Kilding Cloudbees Core 2.176.4.3 depends (somehow) on an outdated version of the AWS SDK, which pre-dates fine-grained IAM role support for EKS. This means that plugins which use the AWS SDK can either: Hold back their dependency to be compatible with Cloudbees Core - and break support for this EKS feature. Hold back their dependency and then ask regular Jenkins users to specifically upgrade their AWS SDK plugin version - with the complication that entails. Upgrade their dependency, and break compatibility with this Cloudbees Core version. None of these is ideal (in fact I’ve had a Jenkins-on-EKS user get in touch already about this problem). So Cloudbees Core needs to have its AWS SDK dependency updated to at least 1.11.623.
[JIRA] (JENKINS-52490) Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable
Title: Message Title J Knurek commented on JENKINS-52490 Re: Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable I've had a try at implemented what is needed for this feature. I actually haven't tested it, or added any unit tests, because I'm not even sure this is a valid approach. So I'd appreciate some feedback on the PR before continuing: https://github.com/jenkinsci/git-plugin/pull/796 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.192321.1531328379000.5198.1576065600197%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Francisco Fernández assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-60393 cloudbees-folder circular dependency Change By: Francisco Fernández Assignee: Allan BURDAJEWICZ 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.203447.1575664332000.5206.1576065780571%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Francisco Fernández commented on JENKINS-60393 Re: cloudbees-folder circular dependency Hi Allan BURDAJEWICZ, https://github.com/jenkinsci/cloudbees-folder-plugin/pull/129 is causing a regression. Could you please have a look at it? Thanks in advance! 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.203447.1575664332000.5209.1576065840262%40Atlassian.JIRA.
[JIRA] (JENKINS-60441) Upgrade AWS SDK dependency in Cloudbees Core
Title: Message Title Chris Kilding updated an issue Jenkins / JENKINS-60441 Upgrade AWS SDK dependency in Cloudbees Core Change By: Chris Kilding Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203516.1576065321000.5215.1576066260269%40Atlassian.JIRA.
[JIRA] (JENKINS-60420) Skip notifications plugin fails after 1.0.4 release
Title: Message Title Michel Zanini commented on JENKINS-60420 Re: Skip notifications plugin fails after 1.0.4 release Seems to work, I updated and the error is not showing up anymore. 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.203491.1575988624000.5227.1576067220758%40Atlassian.JIRA.
[JIRA] (JENKINS-51968) sshagent plugin broken on Windows 10 version 1803
Title: Message Title ethorsa commented on JENKINS-51968 Re: sshagent plugin broken on Windows 10 version 1803 Is there any workaround known? 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.191460.1529061233000.5229.1576067220850%40Atlassian.JIRA.
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title Michel Zanini commented on JENKINS-39682 Re: Generated Multibranch Pipeline Job does not index branches PR https://github.com/jenkinsci/branch-api-plugin/pull/158 was merged to fix this issue but has caused a worse issue in my opinion. My seed job runs every 4 hours, it scans repositories in Bitbucket and create and/or update hundreds of jobs as a result. After updating the Branch API plugin to 2.5.5 with this PR included, now every 4 hours, ALL my ~ 250 jobs are triggering a branch scanning at the same time after seed job completes. This causes several API calls to Bitbucket all at the same time and then they hang, as Bitbucket has a limit on number of API calls. That means I have to revert the plugin to 2.5.4 as its impossible to continue with this behaviour. I understand what you are trying to fix here - to run it initially when the job gets created for the first time. But it should not happen when the job gets updated. Also, using a scan trigger fixes your problem and it is recommend to use one anyway (as sometimes Webhooks will be missed). It has never being a problem for us. Anyway, I think this has made things worse at the point of being a blocker. 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.176259.1478899646000.5283.1576068189702%40Atlassi
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title Michel Zanini edited a comment on JENKINS-39682 Re: Generated Multibranch Pipeline Job does not index branches PR [https://github.com/jenkinsci/branch-api-plugin/pull/158] was merged to fix this issue but has caused a worse issue in my opinion.My seed job runs every 4 hours, it scans repositories in Bitbucket and create and/or update hundreds of jobs as a result.After updating the Branch API plugin to 2.5.5 with this PR included, now every 4 hours, ALL my ~ 250 jobs are triggering a branch scanning at the same time after seed job completes.This causes several API calls to Bitbucket all at the same time and then they hang, as Bitbucket has a limit on number of API calls.That means I have to revert the plugin to 2.5.4 as its impossible to continue with this behaviour. I understand what you are trying to fix here - to run it initially when the job gets created for the first time. But it should not happen when the job gets updated.Also, using a scan trigger fixes your the problem of initial branch scanning and it is recommend to use one anyway (as sometimes Webhooks will be missed). It has never being a problem for us. Anyway, I think this has made things worse at the point of being a blocker.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.176259.147889964
[JIRA] (JENKINS-60442) Logs lost for declarative parallel child job builds
Title: Message Title Samuel Durand updated an issue Jenkins / JENKINS-60442 Logs lost for declarative parallel child job builds Change By: Samuel Durand Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203517.1576068782000.5324.1576068840428%40Atlassian.JIRA.
[JIRA] (JENKINS-60442) Logs lost for declarative parallel child job builds
Title: Message Title
Samuel Durand created an issue
Jenkins / JENKINS-60442
Logs lost for declarative parallel child job builds
Issue Type:
Bug
Assignee:
Unassigned
Components:
jenkinsfile-runner
Created:
2019-12-11 12:53
Priority:
Minor
Reporter:
Samuel Durand
When using declarative pipelines in combination with parallel builds and sub job starting, the build logs are lost. Example:
stage('Check pipelines') {
parallel {
stage('Check Java pipeline') {
steps {
script {
build job:'../dcx-service-template/master',
parameters: [string(name: 'SHARED_PIPELINE_BRANCH', value: "${GIT_BRANCH}")]
}
}
}
stage('Check NodeJs pipeline') {
steps {
script {
build job:'../jenkins-pipeline-testing-nodejs/master',
parameters: [string(name: 'SHARED_PIPELINE_BRANCH', value: "${GIT_BRANCH}")]
}
}
}
}
}
}
This will work and execute properly, but the build logs will disappear after the firrst "build job", which will make it look like this :
[...]
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Check pipelines)
[Pipeline] parallel
[Pipeline] { (Branch: Check Java pipeline)
[Pipeline] { (Branch: Check NodeJs pipeline)
[Pipeline] script
[Pipeline] {
[Pipeline] script
[Pipeline] {
[Pipeline] build (Building S
[JIRA] (JENKINS-60434) "Prepare for shutdown" should continue executing already running pipelines to completion
Title: Message Title Reinhold Füreder commented on JENKINS-60434 Re: "Prepare for shutdown" should continue executing already running pipelines to completion Thomas de Grenier de Latour Thanks for the insight! And wow, that is impressive and I am not sure you got that right in the first attempt 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.203506.1576045591000.5331.1576068900522%40Atlassian.JIRA.
[JIRA] (JENKINS-55524) Triggers on wrong branch when pushing multiple merges
Title: Message Title ovi craciun commented on JENKINS-55524 Re: Triggers on wrong branch when pushing multiple merges we are seeing this behavior 1. we have a project with "Build when a change is pushed to BitBucket" checked and "Branch Specifier (blank for 'any') " as origin/development. This one works as expected. 2. we have a second project with "Build when a change is pushed to BitBucket" checked and "Branch Specifier (blank for 'any') " as origin/master. This project is triggered for any commit to any branch. the only difference between the two projects is the branch it is supposed to build. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196657.1547153222000.5333.1576068900552%40Atlassian.JIRA.
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title greg oire commented on JENKINS-39682 Re: Generated Multibranch Pipeline Job does not index branches Triggering scan is not always possible. For instance you speak about 250 repos let say around 15 branches per repos that will quickly kill your api quota. On large orgs, you do that exceptionally and more per repos than at full scale 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.176259.1478899646000.5354.1576071600850%40Atlassian.JIRA.
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title Michel Zanini commented on JENKINS-39682 Re: Generated Multibranch Pipeline Job does not index branches I am not sure I understood well what you mean greg oire. The issue here is that my seed job creates/updates many jobs every few hours. That was working ok before and now after this change it started re-scanning all of the jobs at once. Do you agree this is a problem or what are you suggesting? 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.176259.1478899646000.5375.1576071840802%40Atlassian.JIRA.
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title greg oire commented on JENKINS-39682 Re: Generated Multibranch Pipeline Job does not index branches You were suggesting to enable the index scan trigger to prevent the initial scan. I was just pointing out that it is not always possible as it would result jenkins to make a lot of api call from time to time, that would result in the exact same issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176259.1478899646000.5396.1576072322843%40Atlassian.JIRA.
[JIRA] (JENKINS-60433) Version 1.80.0 throws JEP-200 error
Title: Message Title evernat updated JENKINS-60433 Thanks for the issue. It's fixed by https://github.com/jenkinsci/monitoring-plugin/commit/2712582481807bce64a6137994f7c8f7c094080e and ready for the next release (1.81). Jenkins / JENKINS-60433 Version 1.80.0 throws JEP-200 error Change By: evernat 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 e
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title Michel Zanini commented on JENKINS-39682 Re: Generated Multibranch Pipeline Job does not index branches But you can configure the the trigger to be every day or every week etc. They go randomically and then the API calls are spread and don't cause 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.176259.1478899646000.5423.1576072620570%40Atlassian.JIRA.
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title Michel Zanini commented on JENKINS-39682 Re: Generated Multibranch Pipeline Job does not index branches Also, another suggestion is do what has being done here but only if the job has just being created for the first time, then you trigger the scan, but not on a job update. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176259.1478899646000.5444.1576072680600%40Atlassian.JIRA.
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title
Michel Zanini edited a comment on JENKINS-39682
Re: Generated Multibranch Pipeline Job does not index branches
But you can configure the the trigger to be every day or every week etc. They go randomically and then the API calls are spread and don't cause issues. This is what I am using now:```triggers { periodic(24 * 60)}```
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.176259.1478899646000.5465.1576072740553%40Atlassian.JIRA.
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title
Michel Zanini edited a comment on JENKINS-39682
Re: Generated Multibranch Pipeline Job does not index branches
But you can configure the the trigger to be every day or every week etc. They go randomically and then the API calls are spread and don't cause issues.This is what I am using now: {code:java} ``` triggers { periodic(24 * 60)} ``` {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176259.1478899646000.5486.1576072800943%40Atlassian.JIRA.
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title
Michel Zanini edited a comment on JENKINS-39682
Re: Generated Multibranch Pipeline Job does not index branches
But you can configure the the trigger to be every day or every week etc. They go randomically and then the API calls are spread and don't cause issues.This is what I am using now:{code:java}triggers { periodic(24 * 60)//every 24 hours }{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176259.1478899646000.5507.1576072801390%40Atlassian.JIRA.
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title
Michel Zanini edited a comment on JENKINS-39682
Re: Generated Multibranch Pipeline Job does not index branches
But you can configure the the trigger to be every day or every week etc. They go randomically and then the API calls are spread and don't cause issues.This is what I am using now:{code:java}triggers { periodic(24 * 60) //every 24 hours} {code} This does not mean that all jobs will trigger the scan every at the same time. Unless I am wrong they are spread randomically and happen separately.
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.176259.1478899646000.5528.1576072860918%40Atlassian.JIRA.
[JIRA] (JENKINS-39682) Generated Multibranch Pipeline Job does not index branches
Title: Message Title
Michel Zanini edited a comment on JENKINS-39682
Re: Generated Multibranch Pipeline Job does not index branches
But you can configure the the trigger to be every day or every week etc. They go randomically and then the API calls are spread and don't cause issues.This is what I am using now:{code:java}triggers { periodic(24 * 60) //every 24 hours}{code}This does not mean that all jobs will trigger the scan every day at the same time. Unless I am wrong they are spread randomically and happen separately.
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.176259.1478899646000.5549.1576072861375%40Atlassian.JIRA.
[JIRA] (JENKINS-60391) Sending mail issue with email-ext plugin
Title: Message Title Pierre Lemasson updated JENKINS-60391 Jenkins / JENKINS-60391 Sending mail issue with email-ext plugin Change By: Pierre Lemasson 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.203445.1575648436000.5575.1576073523432%40Atlassian.JIRA.
[JIRA] (JENKINS-60391) Sending mail issue with email-ext plugin
Title: Message Title Pierre Lemasson commented on JENKINS-60391 Re: Sending mail issue with email-ext plugin I have modified the value of the argument "-Dmail.smtp.auth" in the jenkins.xml, and it seems to work correctly now. Thank you for your answers 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.203445.1575648436000.5573.1576073522812%40Atlassian.JIRA.
[JIRA] (JENKINS-60443) LDAP Plugin Ignores Group Search Filter
Title: Message Title
Julian Wissmann created an issue
Jenkins / JENKINS-60443
LDAP Plugin Ignores Group Search Filter
Issue Type:
Bug
Assignee:
Unassigned
Components:
ldap-plugin
Created:
2019-12-11 14:36
Environment:
LDAP Plugin 1.20 and newer Role Based Authorization Strategy 2.13 and later Jenkins 2.60 and later
Labels:
plugin security configuration
Priority:
Major
Reporter:
Julian Wissmann
When configuring a Group Serch Filter in Jenkins it is not evaluated. Step-Debugging the Plugin reveals that the AuthoritiesPopulatorImpl holds the default value in groupSearchFilter. Setting a Group memberhsip filter causes the groupSearchFilter Field in AuthoritiesPopulatorImpl to hold the Group membership filter. Our Group configuration in LDAP is a tree following this schema: ou:Project ---> ou:Tool ---> cn: posixGroup We use Group Search Filters to match the correct ou to search Groups having the same Groupname may exist in other tool OUs. The filter used is (ou:dn:=ci) as the Tools ou we host our Jenkins groups in is called ci. Having a group admin in this ou and having a group admin in another ou causes that other Group to also be matched. My discovery is, that with a Group Search Filter set in the LDAP Configuration, the AuthoritiesPopulatorImpl holds the Filter "(| (member={0}) (uniqueMember={0}) (memberUid={1}))" in the groupSearchFilter field. As a fix I was able to set the Group membership filter to "(&(ou:dn:=ci)(memberUid={1}))". Possible fixes: Either drop the Group search filter field entirely as it seems disused or restore usage of this field
[JIRA] (JENKINS-59527) Trim white space from pipeline library name and version field
Title: Message Title Devin Nusbaum updated JENKINS-59527 Jenkins / JENKINS-59527 Trim white space from pipeline library name and version field Change By: Devin Nusbaum Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202156.1569432268000.5580.1576075440582%40Atlassian.JIRA.
[JIRA] (JENKINS-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title Bruno Meneguello commented on JENKINS-39952 Re: "Registry credentials" is not working with a private docker registry Nearly 2020 and still having this issue. I just succeeded by adding a shell step with docker login ... before the step 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.176574.1479864408000.5583.1576075560270%40Atlassian.JIRA.
[JIRA] (JENKINS-60321) Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams
Title: Message Title Matthew Smeeth assigned an issue to Matthew Smeeth Jenkins / JENKINS-60321 Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams Change By: Matthew Smeeth Assignee: Matthew Smeeth 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.203319.157495971.5603.1576076161971%40Atlassian.JIRA.
[JIRA] (JENKINS-60430) stopping a job while in reconcile will not stop the reconcile (the job itself will however stop)
Title: Message Title Eric Daigneault commented on JENKINS-60430 Re: stopping a job while in reconcile will not stop the reconcile (the job itself will however stop) of course : Jenkins 2.190.3 on Centos 7 with OpenJDK Runtime Environment, 1.8.0_232-b09 Agent on Windows 10 on openjdk-hotspot-win64-11.0.4-11 P4 plugin 1.10.7 p4d : Server date: 2019/12/11 09:50:08 -0500 EST Server uptime: 936:31:10 Server version: P4D/LINUX26X86_64/2019.1/1876401 (2019/10/30) 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.203502.1576019104000.5604.1576076162011%40Atlassian.JIRA.
[JIRA] (JENKINS-60321) Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams
Title: Message Title Matthew Smeeth started work on JENKINS-60321 Change By: Matthew Smeeth 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.203319.157495971.5614.1576076342022%40Atlassian.JIRA.
[JIRA] (JENKINS-60321) Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams
Title: Message Title Matthew Smeeth updated an issue Jenkins / JENKINS-60321 Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams Change By: Matthew Smeeth Labels: P4_A P4_VERIFY 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.203319.157495971.5612.1576076341601%40Atlassian.JIRA.
[JIRA] (JENKINS-60391) Sending mail issue with email-ext plugin
Title: Message Title Alex Earl updated JENKINS-60391 Jenkins / JENKINS-60391 Sending mail issue with email-ext plugin Change By: Alex Earl Status: Fixed but Unreleased Closed Resolution: Fixed Not A Defect 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.203445.1575648436000.5607.1576076220438%40Atlassian.JIRA.
[JIRA] (JENKINS-60444) PCT test failure in async-http-client-plugin AHCTest.acceptGoodCertificate
Title: Message Title Ramon Leon started work on JENKINS-60444 Change By: Ramon Leon 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.203520.1576078652000.5642.1576078680618%40Atlassian.JIRA.
[JIRA] (JENKINS-60444) PCT test failure in async-http-client-plugin AHCTest.acceptGoodCertificate
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-60444 PCT test failure in async-http-client-plugin AHCTest.acceptGoodCertificate Issue Type: Bug Assignee: Unassigned Components: async-http-client-plugin Created: 2019-12-11 15:37 Environment: 1.7.24.2 Priority: Minor Reporter: Ramon Leon PCT test failure in jenkins.plugins.asynchttpclient.AHCTest.acceptGoodCertificate with: Error Message java.util.concurrent.TimeoutException: No response received after 6 Stacktrace java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException: No response received after 6 at com.ning.http.client.providers.netty.NettyResponseFuture.get(NettyResponseFuture.java:263) at com.ning.http.client.providers.netty.NettyResponseFuture.get(NettyResponseFuture.java:220) at jenkins.plugins.asynchttpclient.AHCTest.acceptGoodCertificate(AHCTest.java:131) 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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.jvnet.hudson.test.JenkinsRule$2.evaluate(JenkinsRule.java:550) at org.junit.rules.R
[JIRA] (JENKINS-60444) PCT test failure in async-http-client-plugin AHCTest.acceptGoodCertificate
Title: Message Title Ramon Leon assigned an issue to Ramon Leon Jenkins / JENKINS-60444 PCT test failure in async-http-client-plugin AHCTest.acceptGoodCertificate Change By: Ramon Leon Assignee: Ramon Leon 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.203520.1576078652000.5641.1576078680608%40Atlassian.JIRA.
[JIRA] (JENKINS-60444) PCT test failure in async-http-client-plugin AHCTest.acceptGoodCertificate
Title: Message Title Ramon Leon commented on JENKINS-60444 Re: PCT test failure in async-http-client-plugin AHCTest.acceptGoodCertificate It is because letsencrypt now uses SNI, that means the same IP is serving several hostnames and the plugin gets the wrong certificate. echo | openssl s_client -showcerts -connect letsencrypt.org:443 2>/dev/null | openssl x509 -inform pem -noout -text Returns the right certificate, for letsencrypt.org echo | openssl s_client -showcerts -connect 167.99.129.42:443 2>/dev/null | openssl x509 -inform pem -noout -text Returns Netlify, Inc I will change the test to use a different host without this problem. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203520.1576078652000.5643.1576078860064%40Atlassian.JIRA.
[JIRA] (JENKINS-60445) Depend on the AWS Global Configuration plugin
Title: Message Title Chris Kilding created an issue Jenkins / JENKINS-60445 Depend on the AWS Global Configuration plugin Issue Type: Improvement Assignee: Chris Kilding Components: aws-secrets-manager-credentials-provider-plugin Created: 2019-12-11 15:57 Priority: Minor Reporter: Chris Kilding Add a dependency on the AWS Global Configuration plugin. Read relevant config values from it instead of asking them to duplicate their configuration. Use the transitive AWS SDK dependency from the Global Configuration plugin too. Add Comment
[JIRA] (JENKINS-60445) Depend on the AWS Global Configuration plugin
Title: Message Title Chris Kilding commented on JENKINS-60445 Re: Depend on the AWS Global Configuration plugin Questions: Does the Global Config plugin contain the kind of config values we want? In particular, Endpoint Configuration. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203521.1576079821000.5660.1576079940060%40Atlassian.JIRA.
[JIRA] (JENKINS-60446) Add option to pass custom paramters from multibranch to the trigger jobs
Title: Message Title Oleksii Baranov created an issue Jenkins / JENKINS-60446 Add option to pass custom paramters from multibranch to the trigger jobs Issue Type: New Feature Assignee: Aytunc BEKEN Components: multibranch-action-triggers-plugin Created: 2019-12-11 16:04 Environment: multibranch-action-triggers-plugin v1.5 Priority: Minor Reporter: Oleksii Baranov It would be nice to have additional option in the multichannel pipline configuration to specify custom parameters to pass to the tirgger job. The problem we are facing right now is next. We have a lot of multibranch projects for different apps: app1 master branch feature1 app2 master app3 But for most of those apps the OnDelete trigger job performs the same steps. The only difference is that we need to cleanup resources according to the app name. We want to have only one OnDelete job for all those multibranch projects but provide parameters together with SOURCE_PROJECT_NAME param to indicate for what app we've triggered job. Also it might be useful to pass other custom parameters from the upstream job.
[JIRA] (JENKINS-60444) PCT test failure in async-http-client-plugin AHCTest.acceptGoodCertificate
Title: Message Title Ramon Leon commented on JENKINS-60444 Re: PCT test failure in async-http-client-plugin AHCTest.acceptGoodCertificate PR: https://github.com/jenkinsci/async-http-client-plugin/pull/12 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.203520.1576078652000.5667.1576081560122%40Atlassian.JIRA.
[JIRA] (JENKINS-60444) PCT test failure in async-http-client-plugin AHCTest.acceptGoodCertificate
Title: Message Title Ramon Leon updated JENKINS-60444 Jenkins / JENKINS-60444 PCT test failure in async-http-client-plugin AHCTest.acceptGoodCertificate Change By: Ramon Leon 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.203520.1576078652000.5668.1576081620206%40Atlassian.JIRA.
[JIRA] (JENKINS-60446) Add option to pass custom paramters from multibranch to the trigger jobs
Title: Message Title Aytunc BEKEN commented on JENKINS-60446 Re: Add option to pass custom paramters from multibranch to the trigger jobs Hi, I understand the situation you are having. It make sense when you have lots of jobs/branches. For a quick solution I can add another parameter with the Full name of the branch job ( Ex: app1/master) which calls the onDelete Trigger Job. Is this okay ? For adding custom parameters from the upstream job, I need to understand requirements well, can you give more detailed example ? Thanks for the suggestions! 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.203523.157608026.5677.1576082280748%40Atlassian.JIRA.
[JIRA] (TEST-195) Run Btc test in jenkins
Title: Message Title Mindaugas Mikuckas created an issue test / TEST-195 Run Btc test in jenkins Issue Type: New Feature Assignee: Mindaugas Mikuckas Components: foo Created: 2019-12-11 16:37 Priority: Critical Reporter: Mindaugas Mikuckas 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" grou
[JIRA] (JENKINS-60447) Optionally ignore reconcile permissions errors
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-60447 Optionally ignore reconcile permissions errors Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-12-11 16:37 Environment: p4-plugin 1.10.7 Jenkins 2.176.1 Priority: Major Reporter: Karl Wirth If you are using Perforce server version 20141 or earlier P4jenkins uses a memory intensive version of 'p4 reconcile'. This older version skips permissions errors. For example: P4 Task: tidying workspace to match have list. ... p4 reconcile -n -a -e -d -l -f /var/lib/jenkins/workspace/AutoCleanAnd___ + Not able to delete: /var/lib/jenkins/workspace/AutoCleanAndSync/submit/cfg/prod_Release.cfg duration: (68ms) If you are using a later version of P4D a new streaming reconcile is used that is faster and uses less memory. In this implementation permissions errors fail the build. For example: P4 Task: cleaning workspace to match have list p4 reconcile -f -w /var/lib/jenkins/workspace/AutoCleanAndSync/ ... +P4 Task: attempt: 1 ERROR: P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s): operating system will not allow deletion of file /var/lib/jenkins/workspace/AutoCleanAndSync/submit/cfg/prod_R
[JIRA] (TEST-195) Run Btc test in jenkins
Title: Message Title Mindaugas Mikuckas started work on TEST-195 Change By: Mindaugas Mikuckas 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.203525.1576082232000.5678.1576082460114%40Atlassian.JIRA.
[JIRA] (JENKINS-60447) Optionally ignore reconcile permissions errors
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60447 Optionally ignore reconcile permissions errors Change By: Karl Wirth Labels: P4_A P4_VERIFY 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.203524.1576082224000.5679.1576082880093%40Atlassian.JIRA.
[JIRA] (JENKINS-33398) UNABLE TO SEE AVAILABLE PLUGINS IN MANAGE PLUGINS
Title: Message Title Kavya Marri commented on JENKINS-33398 Re: UNABLE TO SEE AVAILABLE PLUGINS IN MANAGE PLUGINS Hi Raghuveer, I got the same issue,can you please help me if you know the solution ? 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.168806.1457454045000.5681.1576083000932%40Atlassian.JIRA.
[JIRA] (JENKINS-60448) Allow specification of error when deptrack server can't be reached
Title: Message Title Richard Lee created an issue Jenkins / JENKINS-60448 Allow specification of error when deptrack server can't be reached Issue Type: New Feature Assignee: Steve Springett Components: dependency-track-plugin Created: 2019-12-11 17:27 Priority: Minor Reporter: Richard Lee It would be useful to be able to differentiate between a failure of the deptrack step to communicate with the deptrack server from a failure to meet thresholds. It appears from the code that there are comments that the error should be configurable. See https://github.com/jenkinsci/dependency-track-plugin/blob/master/src/main/java/org/jenkinsci/plugins/DependencyTrack/DependencyTrackPublisher.java#L200 However, I also find it a little odd that the step is directly setting the build result rather than throwing an exception of some sort. The build will merrily continue on its way with a failed rather than immediately stopping (unless the pipeline owner has decided to try/catch around the call). Most other step throw exceptions when they encounter errors so that the build stops executing. Add Comment
[JIRA] (JENKINS-52490) Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable
Title: Message Title Mark Waite commented on JENKINS-52490 Re: Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable I am piv vacation for the rest of this week. Other maintainers may be available, but I am not. I generally don't accept pull requests that lack tests. However, I'm willing to recite for direction before tests are written 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.192321.1531328379000.5693.1576085340300%40Atlassian.JIRA.
[JIRA] (JENKINS-39952) "Registry credentials" is not working with a private docker registry
Title: Message Title
Bruno Meneguello edited a comment on JENKINS-39952
Re: "Registry credentials" is not working with a private docker registry
Nearly 2020 and still having I'm using this issue with Kubernetes cloud and a docker-dind image .I just succeeded by adding a shell step with {{docker login ... before the step . }}
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.176574.1479864408000.5696.1576085820303%40Atlassian.JIRA.
[JIRA] (JENKINS-60437) Manually setting git commit status sets it for two contexts
Title: Message Title
Cyprien Quilici updated an issue
Jenkins / JENKINS-60437
Manually setting git commit status sets it for two contexts
Change By:
Cyprien Quilici
I'm trying to create two different jobs, the build job and E2E tests job. I'd like the two jobs to annotate the git commit with their results and the results not to get mixed up. On the build job, I didn't change any configuration and the git plugin does its magic in the background as expected. In my E2E Jenkinsfile, I'm setting the git commit status manually as lots of guys on the internet suggest, with a method: void setBuildStatus (String message, JobResult jobResult, def repoName) { step([ $class : "GitHubCommitStatusSetter", reposSource : [$class: "ManuallyEnteredRepositorySource", url: "https://github.com/Talend/$repoName"], contextSource : [$class: "ManuallyEnteredCommitContextSource", context: "E2E tests"], errorHandlers : [[$class: "ChangingBuildStatusErrorHandler", result: JobResult.UNSTABLE.name()]], statusResultSource: [$class: "ConditionalStatusResultSource", results: [[$class: "AnyBuildResult", message: message, state: jobResult.name()]] ] ])} Which is used at startup, in post > success and post > failure. When only the build job runs, the git commit is marked with *continuous-integration/jenkins/branch,* the _details_ link points to my build job, this is as intended. When the E2E tests run though, the commit gets marked with *E2E tests* (good) but the *continuous-integration/jenkins/branch* ** gets overwritten by the result of the E2E tests job and that's not intended. Both _details_ link now point to the E2E job.The details links both point to the E2E tests job which is unexpected. The logs from my E2E job: [Set GitHub commit status (universal)] FAILURE on repos [GHRepository@431ca6e9[description=XXX,homepage=,name=tat-client,fork=false,archived=false,size=47243,milestones={},language=Java,commits={},source=,parent=,responseHeaderFields= \ {null=[HTTP/1.1 200 OK], Access-Control-Allow-Origin=[*], Access-Control-Expose-Headers=[ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type], Cache-Control=[private, max-age=60, s-maxage=60], Content-Encoding=[gzip], Content-Security-Policy=[default-src 'none'], Content-Type=[application/json; charset=utf-8], Date=[Wed, 11 Dec 2019 09:35:58 GMT], ETag=[W/"fd8af705e8350025323a01b7c75547f8"], Last-Modified=[Fri, 06 Dec 2019 10:37:49 GMT], OkHttp-Received-Millis=[1576056958700], OkHttp-Response-Source=[CONDITIONAL_CACHE 200], OkHttp-Selected-Protocol=[http/1.1], OkHttp-Sent-Millis=[1576056958550], Referrer-Policy=[origin-when-cross-origin, strict-origin-when-cross-origin], Server=[GitHub.com], Status=[200 OK], Strict-Transport-Security=[max-age=31536000; includeSubdomains; preload], Transfer-Encoding=[chunked], Vary=[Accept, Authorization, Cookie, X-GitHub-OTP], X-Accept
[JIRA] (JENKINS-60437) Manually setting git commit status sets it for two contexts
Title: Message Title
Cyprien Quilici updated an issue
Jenkins / JENKINS-60437
Manually setting git commit status sets it for two contexts
Change By:
Cyprien Quilici
I'm trying to create two different jobs, the build job and E2E tests job. I'd like the two jobs to annotate the git commit with their results and the results not to get mixed up. On the build job, I didn't change any configuration and the git plugin does its magic in the background as expected. In my E2E Jenkinsfile, I'm setting the git commit status manually as lots of guys on the internet suggest, with a method: {code} void setBuildStatus (String message, JobResult jobResult, def repoName) { step([$class : "GitHubCommitStatusSetter", reposSource : [$class: "ManuallyEnteredRepositorySource", url: "https://github.com/Talend/$repoName"], contextSource : [$class: "ManuallyEnteredCommitContextSource", context: "E2E tests"], errorHandlers : [[$class: "ChangingBuildStatusErrorHandler", result: JobResult.UNSTABLE.name()]],statusResultSource: [$class: "ConditionalStatusResultSource", results: [[$class: "AnyBuildResult", message: message, state: jobResult.name()]]] ])} {code} Which is used at startup, in post > success and post > failure.When only the build job runs, the git commit is marked with *continuous-integration/jenkins/branch,* the _details_ link points to my build job, this is as intended.When the E2E tests run though, the commit gets marked with *E2E tests* (good) but the *continuous-integration/jenkins/branch* ** gets overwritten by the result of the E2E tests job and that's not intended. Both _details_ link now point to the E2E job.The details links both point to the E2E tests job which is unexpected.The logs from my E2E job: {code} [Set GitHub commit status (universal)] FAILURE on repos [GHRepository@431ca6e9[description=XXX,homepage=,name=tat-client,fork=false,archived=false,size=47243,milestones={},language=Java,commits={},source=,parent=,responseHeaderFields={null=[HTTP/1.1 200 OK], Access-Control-Allow-Origin=[*], Access-Control-Expose-Headers=[ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type], Cache-Control=[private, max-age=60, s-maxage=60], Content-Encoding=[gzip], Content-Security-Policy=[default-src 'none'], Content-Type=[application/json; charset=utf-8], Date=[Wed, 11 Dec 2019 09:35:58 GMT], ETag=[W/"fd8af705e8350025323a01b7c75547f8"], Last-Modified=[Fri, 06 Dec 2019 10:37:49 GMT], OkHttp-Received-Millis=[1576056958700], OkHttp-Response-Source=[CONDITIONAL_CACHE 200], OkHttp-Selected-Protocol=[http/1.1], OkHttp-Sent-Millis=[1576056958550], Referrer-Policy=[origin-when-cross-origin, strict-origin-when-cross-origin], Server=[GitHub.com], Status=[200 OK], Strict-Transport-Security=[max-age=31536000; includeSubdomains; preload], Transfer-Encoding=[chunked], Vary=[Accept, Authorization, Cookie, X-GitHub-OTP], X-Accepted-OAuth-Scopes
[JIRA] (JENKINS-60437) Manually setting git commit status sets it for two contexts
Title: Message Title
Cyprien Quilici updated an issue
Jenkins / JENKINS-60437
Manually setting git commit status sets it for two contexts
Change By:
Cyprien Quilici
I'm trying to create two different jobs, the build job and E2E tests job. I'd like the two jobs to annotate the git commit with their results and the results not to get mixed up. On the build job, I didn't change any configuration and the git plugin does its magic in the background as expected. In my E2E Jenkinsfile, I'm setting the git commit status manually as lots of guys on the internet suggest, with a method:{code:java}void setBuildStatus (String message, JobResult jobResult, def repoName) { step([$class : "GitHubCommitStatusSetter", reposSource : [$class: "ManuallyEnteredRepositorySource", url: "https://github.com/myOrg/myRepo"], contextSource : [$class: "ManuallyEnteredCommitContextSource", context: "E2E tests"], errorHandlers : [[$class: "ChangingBuildStatusErrorHandler", result: JobResult.UNSTABLE.name()]],statusResultSource: [$class: "ConditionalStatusResultSource", results: [[$class: "AnyBuildResult", message: message, state: jobResult.name()]]] ])}{code}Which is used at startup, in post > success and post > failure.When only the build job runs, the git commit is marked with *continuous-integration/jenkins/branch,* the _details_ link points to my build job, this is as intended.When the E2E tests run though, the commit gets marked with *E2E tests* (good) but the *continuous-integration/jenkins/branch* ** gets overwritten by the result of the E2E tests job and that's not intended. Both _details_ link now point to the E2E job.The details links both point to the E2E tests job which is unexpected.The logs from my E2E job: {code:java} [Set GitHub commit status (universal)] FAILURE on repos [GHRepository@431ca6e9[description=XXX,homepage=,name=tat-client,fork=false,archived=false,size=47243,milestones={},language=Java,commits={},source=,parent=,responseHeaderFields={null=[HTTP/1.1 200 OK], Access-Control-Allow-Origin=[*], Access-Control-Expose-Headers=[ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type], Cache-Control=[private, max-age=60, s-maxage=60], Content-Encoding=[gzip], Content-Security-Policy=[default-src 'none'], Content-Type=[application/json; charset=utf-8], Date=[Wed, 11 Dec 2019 09:35:58 GMT], ETag=[W/"fd8af705e8350025323a01b7c75547f8"], Last-Modified=[Fri, 06 Dec 2019 10:37:49 GMT], OkHttp-Received-Millis=[1576056958700], OkHttp-Response-Source=[CONDITIONAL_CACHE 200], OkHttp-Selected-Protocol=[http/1.1], OkHttp-Sent-Millis=[1576056958550], Referrer-Policy=[origin-when-cross-origin, strict-origin-when-cross-origin], Server=[GitHub.com], Status=[200 OK], Strict-Transport-Security=[max-age=31536000; includeSubdomains; preload], Transfer-Encoding=[chunked], Vary=[Accept, Authorization, Cookie, X-GitHub-OTP], X-Accepted-OAuth-Scopes=[
[JIRA] (JENKINS-60437) Manually setting git commit status sets it for two contexts
Title: Message Title
Cyprien Quilici updated an issue
Jenkins / JENKINS-60437
Manually setting git commit status sets it for two contexts
Change By:
Cyprien Quilici
I'm trying to create two different jobs, the build job and E2E tests job. I'd like the two jobs to annotate the git commit with their results and the results not to get mixed up. On the build job, I didn't change any configuration and the git plugin does its magic in the background as expected. In my E2E Jenkinsfile, I'm setting the git commit status manually as lots of guys on the internet suggest, with a method: {code :java }void setBuildStatus (String message, JobResult jobResult, def repoName) { step([$class : "GitHubCommitStatusSetter", reposSource : [$class: "ManuallyEnteredRepositorySource", url: "https://github.com/ Talend myOrg / $repoName myRepo "], contextSource : [$class: "ManuallyEnteredCommitContextSource", context: "E2E tests"], errorHandlers : [[$class: "ChangingBuildStatusErrorHandler", result: JobResult.UNSTABLE.name()]],statusResultSource: [$class: "ConditionalStatusResultSource", results: [[$class: "AnyBuildResult", message: message, state: jobResult.name()]]] ])}{code} Which is used at startup, in post > success and post > failure.When only the build job runs, the git commit is marked with *continuous-integration/jenkins/branch,* the _details_ link points to my build job, this is as intended.When the E2E tests run though, the commit gets marked with *E2E tests* (good) but the *continuous-integration/jenkins/branch* ** gets overwritten by the result of the E2E tests job and that's not intended. Both _details_ link now point to the E2E job.The details links both point to the E2E tests job which is unexpected.The logs from my E2E job: {code :java } [Set GitHub commit status (universal)] FAILURE on repos [GHRepository@431ca6e9[description=XXX,homepage=,name=tat-client,fork=false,archived=false,size=47243,milestones={},language=Java,commits={},source=,parent=,responseHeaderFields={null=[HTTP/1.1 200 OK], Access-Control-Allow-Origin=[*], Access-Control-Expose-Headers=[ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type], Cache-Control=[private, max-age=60, s-maxage=60], Content-Encoding=[gzip], Content-Security-Policy=[default-src 'none'], Content-Type=[application/json; charset=utf-8], Date=[Wed, 11 Dec 2019 09:35:58 GMT], ETag=[W/"fd8af705e8350025323a01b7c75547f8"], Last-Modified=[Fri, 06 Dec 2019 10:37:49 GMT], OkHttp-Received-Millis=[1576056958700], OkHttp-Response-Source=[CONDITIONAL_CACHE 200], OkHttp-Selected-Protocol=[http/1.1], OkHttp-Sent-Millis=[1576056958550], Referrer-Policy=[origin-when-cross-origin, strict-origin-when-cross-origin], Server=[GitHub.com], Status=[200 OK], Strict-Transport-Security=[max-age=31536000; includeSubdomains; preload], Transfer-Encoding=[chunked], Vary=[Accept, Authorization, Cookie, X-G
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Karl Wirth commented on JENKINS-51552 Re: Cannot replay pipelines - files are read-only Hi Erez Arbell, If you don't know the appropriate change you could use '@now' for the latest. Also please get me the full console log. You should have a 'p4 changes' for the library similar to: [Pipeline] library 17:36:23 Loading library @now 17:36:23 ... p4 changes -m1 //depot/lib_autoload/libs/.../...@now + This is what the library loader uses to set '@-1' to a valid value. 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.190940.1527360591000.5711.1576086000211%40Atlassian.JIRA.
[JIRA] (JENKINS-60395) ALM jenkins plugin: ALM results upload issue
Title: Message Title Paul Oberly updated an issue Jenkins / JENKINS-60395 ALM jenkins plugin: ALM results upload issue Change By: Paul Oberly Attachment: console-output-long-running-job-start-first.txt Attachment: console-output-short-running-job-start-second.txt 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.203449.1575673998000.5717.1576086420277%40Atlassian.JIRA.
[JIRA] (JENKINS-60449) Optional extensions can blow up Jenkins
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-60449 Optional extensions can blow up Jenkins Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-12-11 17:47 Priority: Minor Reporter: Vincent Latombe If you have an optional extension (using the variant plugin) that is defining a private static method which has in its signature a type from its optional dependency, then Guice will blow up when attempting to load it, causing every subsequent extensions to fail loading. Upon loading a new extension, the ExtensionFinder scans for potential classloading problems but doesn't catch all cases. Additionally, I have found that when you load a plugin dynamically, extensions are refreshed before classloader of existing plugins have been updated which lead to having Guice trying to load classes without having the right classloading. Add Comment
[JIRA] (JENKINS-60395) ALM jenkins plugin: ALM results upload issue
Title: Message Title Paul Oberly commented on JENKINS-60395 Re: ALM jenkins plugin: ALM results upload issue Files added (on my customer's behalf), thing to look for in the short run console is "Upload test result to ALM is waiting for a checkpoint on Test Automation � Test Automation - GUI #605: " #605 is the first long running job each job runs a different VM (UFTRT001 vs UFTRT002) 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.203449.1575673998000.5721.1576086480337%40Atlassian.JIRA.
[JIRA] (JENKINS-51968) sshagent plugin broken on Windows 10 version 1803
Title: Message Title Jesse Glick commented on JENKINS-51968 Re: sshagent plugin broken on Windows 10 version 1803 You can skip this plugin and just use the withCredentials step to bind an SSH private key to a local file, which can then be passed to various commands typically with a -i option. In a CI context I would not consider this any less secure than using ssh-agent, and it is certainly easier to troubleshoot. 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.191460.1529061233000.5731.1576087020390%40Atlassian.JIRA.
[JIRA] (JENKINS-53321) Test functioning across restarts
Title: Message Title Jesse Glick commented on JENKINS-53321 Re: Test functioning across restarts Yes that looks right. Assign to yourself and mark 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.193402.1535548072000.5733.1576087140173%40Atlassian.JIRA.
[JIRA] (JENKINS-60437) Manually setting git commit status sets it for two contexts
Title: Message Title Mark Waite commented on JENKINS-60437 Re: Manually setting git commit status sets it for two contexts This needs to be assigned to the plugin that provides the GitHub notifier. It is not the fit 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.203509.1576059252000.5737.1576087560309%40Atlassian.JIRA.
[JIRA] (JENKINS-53321) Test functioning across restarts
Title: Message Title Alex Earl started work on JENKINS-53321 Change By: Alex Earl 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.193402.1535548072000.5746.1576087680051%40Atlassian.JIRA.
