[JIRA] (JENKINS-22400) Git timeout on other actions than fetch/clone
Title: Message Title
Marat Radchenko edited a comment on JENKINS-22400
Re: Git timeout on other actions than fetch/clone
bq. I'm impressed that you've found a case where it requires more than 10 minutes to complete.Large repo + interrupted checkout during previous build == almost all I/O happens during {{git reset --hard}}. If you add LFS to the mix, that I/O also involves transferring files over network.Simpler way to reproduce: just remove everything from working copy, but keep {{.git}} it in. Voila, you've got a massive {{git reset --hard}} for next build in the same working copy .
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154201.139599399.4109.1582271640557%40Atlassian.JIRA.
[JIRA] (JENKINS-22400) Git timeout on other actions than fetch/clone
Title: Message Title
Marat Radchenko edited a comment on JENKINS-22400
Re: Git timeout on other actions than fetch/clone
bq. I'm impressed that you've found a case where it requires more than 10 minutes to complete.Large repo + interrupted checkout during previous build == almost all I/O happens during {{git reset --hard}}. If you add LFS to the mix, that I/O also involves transferring files over network.Simpler way to reproduce: just remove everything from working copy, but keep {{.git}} it in. Voila, you've got a massive {{git reset --hard}} for next 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.154201.139599399.4107.1582271640515%40Atlassian.JIRA.
[JIRA] (JENKINS-22400) Git timeout on other actions than fetch/clone
Title: Message Title Marat Radchenko commented on JENKINS-22400 Re: Git timeout on other actions than fetch/clone I'm impressed that you've found a case where it requires more than 10 minutes to complete. Large repo + interrupted checkout during previous build == almost all I/O happens during git reset --hard. If you add LFS to the mix, that I/O also involves transferring files over network. Simpler way to reproduce: just remove everything from working copy, but keep .git it in. Voila, you've got a massive git reset --hard. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154201.139599399.4093.1582271580249%40Atlassian.JIRA.
[JIRA] (JENKINS-61174) BoostTest-1.x in xUnit plugin fails to parse a test log containing skipped tests
Title: Message Title Hisayori Noda created an issue Jenkins / JENKINS-61174 BoostTest-1.x in xUnit plugin fails to parse a test log containing skipped tests Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2020-02-21 07:21 Environment: Windows 10 Pro 1909 Japanese Oracle JDK 11.0.6 64-bit Jenkins ver. 2.204.2 xUnit plugin 2.3.8 Running Jenkins directly on a PC. (Not on a container.) Jenkins is accessed directly. (Not through a reverse proxy.) Jenkins is installed with a Windows installer. Firefox 73.0.1 (64 bits) Priority: Minor Reporter: Hisayori Noda I tried to parse the log of a unit test with BoostTest-1.x in xUnit plugin. Unfortunately it failed with the following error message. ユーザーHisayori Nodaが実行 Running as SYSTEM ビルドします。 ワークスペース: D:\data\Jenkins\workspace\xunit_plugin.experimental INFO: Starting to record. INFO: Processing BoostTest-1.x (default) INFO: [BoostTest-1.x (default)] - 1 test report file(s) were found with the pattern '*.xml' relative to 'D:\data\Jenkins\workspace\xunit_plugin.experimental' for the testing framework 'BoostTest-1.x (default)'. WARNING: The file 'D:\data\Jenkins\workspace\xunit_plugin.experimental\log.xml' is an invalid file. WARNING: At line 1 of file:/D:/data/Jenkins/workspace/xunit_plugin.experimental/log.xml:cvc-complex-type.3.2.2: 要素'TestCase'に属性'skipped'を含めることはできません。 WARNING: At line 1 of file:/D:/data/Jenkins/workspace/xunit_plugin.experimental/log.xml:cvc-complex-type.3.2.2: 要素'TestCase'に属性'reason'を含めることはできません。 WARNING: At line 1 of file:/D:/data/Jenkins/workspace/xunit_plugin.experimental/log.xml:cvc-complex
[JIRA] (JENKINS-60111) Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60111 Re: Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline I wonder, could the impersonation at https://github.com/jenkinsci/jenkins/blob/jenkins-2.204.2/core/src/main/java/hudson/model/User.java#L388 leverage the https://github.com/jenkinsci/jenkins/blob/jenkins-2.204.2/core/src/main/java/jenkins/security/UserDetailsCache.java ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202957.1573231443000.4085.1582266240229%40Atlassian.JIRA.
[JIRA] (JENKINS-61173) Audit trail plugin stop working unexpectedly
Title: Message Title An Nguyen created an issue Jenkins / JENKINS-61173 Audit trail plugin stop working unexpectedly Issue Type: Bug Assignee: Pierre Beitz Components: audit-trail-plugin Created: 2020-02-21 04:34 Priority: Major Reporter: An Nguyen I found below stacktrace when I realized audit log is not produced anymore. Audit trail plugin: 3.2 Jenkins: 2.220 ``` Feb 21, 2020 11:06:35 AM hudson.ExpressionFactory2$JexlExpression evaluateFeb 21, 2020 11:06:35 AM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /job/APP1/job/MODULE-1/configure. Reason: java.lang.NullPointerException: Descriptor list is null for context 'class com.cloudbees.hudson.plugins.folder.Folder' in thread 'Handling GET /job/APP1/job/MODULE-1/configure from 10.213.209.217 : Jetty (winstone)-622816 AbstractFolder/configure.jelly FolderLibraries/DescriptorImpl/config.jelly LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly MultiSCM/DescriptorImpl/config.jelly'java.lang.NullPointerException: Descriptor list is null for context 'class com.cloudbees.hudson.plugins.folder.Folder' in thread 'Handling GET /job/APP1/job/MODULE-1/configure from 10.213.209.217 : Jetty (winstone)-622816 AbstractFolder/configure.jelly FolderLibraries/DescriptorImpl/config.jelly LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly MultiSCM/DescriptorImpl/config.jelly' at hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:73) at hudson.Functions.filterDescriptors(Functions.java:1938) at jdk.internal.reflect.GeneratedMethodAccessor2034.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execut
[JIRA] (JENKINS-60917) Jenkins Pipeline requires at least one successfull build for the trigger to work
Title: Message Title Aidin F edited a comment on JENKINS-60917 Re: Jenkins Pipeline requires at least one successfull build for the trigger to work I see the same behavior. Exactly as if "Bitbucket Server trigger build after push" is not checked. This does not happen with freestyle projects, only with pipelines. I see the webhooks coming in, but nothing triggered --- Payload: com.atlassian.bitbucket.jenkins.internal.trigger.RefsChangedWebhookEvent@117c02dFeb 20, 2020 6:15:25 PM FINE com.atlassian.bitbucket.jenkins.internal.trigger.BitbucketWebhookConsumerReceived refs changed event from repo: HAL/dobbyFeb 20, 2020 6:15:25 PM FINE com.atlassian.bitbucket.jenkins.internal.trigger.BitbucketWebhookConsumer Also, [~sbv] I'm assuming you saw the rest of the conversation in case of Kevin Reynolds. In his case, the "Bitbucket Server trigger build after push" option was not selected, and instead a similar sounding checkbox related to a different Bitbucket plugin (Bitbucket branch plugin? ) was selected. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204311.1580371734000.4074.1582252440212%40Atlassian.JIRA.
[JIRA] (JENKINS-60917) Jenkins Pipeline requires at least one successfull build for the trigger to work
Title: Message Title Aidin F commented on JENKINS-60917 Re: Jenkins Pipeline requires at least one successfull build for the trigger to work I see the same behavior. Exactly as if "Bitbucket Server trigger build after push" is not checked. This does not happen with freestyle projects, only with pipelines. I see the webhooks coming in, but nothing triggered Payload: com.atlassian.bitbucket.jenkins.internal.trigger.RefsChangedWebhookEvent@117c02d Feb 20, 2020 6:15:25 PM FINE com.atlassian.bitbucket.jenkins.internal.trigger.BitbucketWebhookConsumer Received refs changed event from repo: HAL/dobby Feb 20, 2020 6:15:25 PM FINE com.atlassian.bitbucket.jenkins.internal.trigger.BitbucketWebhookConsumer Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204311.1580371734000.4068.1582252260242%40Atlassian.JIRA.
[JIRA] (JENKINS-60492) Connection with Bitbucket server over SSH
Title: Message Title Martin Henschke started work on JENKINS-60492 Change By: Martin Henschke 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.203581.1576452688000.4062.1582251420635%40Atlassian.JIRA.
[JIRA] (JENKINS-60492) Connection with Bitbucket server over SSH
Title: Message Title Martin Henschke assigned an issue to Martin Henschke Jenkins / JENKINS-60492 Connection with Bitbucket server over SSH Change By: Martin Henschke Assignee: Martin Henschke Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203581.1576452688000.4060.1582251420607%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-61167
Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Hi [~andrewsumner], * My Current Jenkins Version - [Jenkins ver. 2.220|https://jenkins.io/] * Jenkins ProGet Plugin Version - 1.3 * ProGet application - Version 5.2.24 (Build 6)I don't think file size will be a problem here because my package file (JenkinsPackage.upack) size is just 58 mb.also is there any issue with the way I'm getting the $FINANCIALVERSION number here? Because I'm using a customize version number instead of using ${BUILD_NUMBER} as version . .
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.4055.1582248540122%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-61167
Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Hi [~andrewsumner], * My Current Jenkins Version - [Jenkins ver. 2.220|https://jenkins.io/] * Jenkins ProGet Plugin Version - [ 1.3 * |https://ci.dev.townsuite.com/pluginManager/plugin/inedo-proget/thirdPartyLicenses] * ProGet application - Version 5.2.24 (Build 6)I don't think file size will be a problem here because my package file (JenkinsPackage.upack) size is just 58 mb.also is there any issue with the way I'm getting the $FINANCIALVERSION number here? Because I'm using a customize version number instead of ${BUILD_NUMBER}.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.4053.1582248480110%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title
Amila Gunathilake edited a comment on JENKINS-61167
Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Hi [~andrewsumner],* My Current Jenkins Version - [Jenkins ver. 2.220|https://jenkins.io/]* Jenkins ProGet Plugin Version - [1.3* |https://ci.dev.townsuite.com/pluginManager/plugin/inedo-proget/thirdPartyLicenses]ProGet application - Version 5.2.24 (Build 6)I don't think file size will be a problem here because my package file (JenkinsPackage.upack) size is just 58 mb.also is there any issue with the way I'm getting the $FINANCIALVERSION number here? Because I'm using a customize version number instead of ${BUILD_NUMBER}.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.4051.1582248360141%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title
Amila Gunathilake commented on JENKINS-61167
Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Hi Andrew Sumner,
My Current Jenkins Version - Jenkins ver. 2.220 * Jenkins ProGet Plugin Version - [1.3 * |https://ci.dev.townsuite.com/pluginManager/plugin/inedo-proget/thirdPartyLicenses]ProGet application - Version 5.2.24 (Build 6)
I don't think file size will be a problem here because my package file (JenkinsPackage.upack) size is just 58 mb. also is there any issue with the way I'm getting the $FINANCIALVERSION number here? Because I'm using a customize version number instead of ${BUILD_NUMBER}.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.4049.1582248300141%40Atlassian.JIRA.
[JIRA] (JENKINS-11111) Add SVN author and commit message env vars
Title: Message Title Alex H edited a comment on JENKINS-1 Re: Add SVN author and commit message env vars Still waiting for this to be implemented. I'm calling Ansible from Jenkins and Ansible needs the user ID of the person who checked in the build. Short of getting this patch included (which I'm not holding my breath for since it it has been in the works for coming on 9 years) what are my other options? I use a nant plugin to run a powershell script. I could collect the name in my script, but how can I pass this back to Jenkins as an evironment environment variable? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.141330.131696196.4039.1582242660879%40Atlassian.JIRA.
[JIRA] (JENKINS-11111) Add SVN author and commit message env vars
Title: Message Title Alex H commented on JENKINS-1 Re: Add SVN author and commit message env vars Still waiting for this to be implemented. I'm calling Ansible from Jenkins and Ansible needs the user ID of the person who checked in the build. Short of getting this patch included (which I'm not holding my breath for since it it has been in the works for coming on 9 years) what are my other options? I use a nant plugin to run a powershell script. I could collect the name in my script, but how can I pass this back to Jenkins as an evironment variable? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.141330.131696196.4037.1582242660803%40Atlassian.JIRA.
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-60133
Re: Default HOME folder in containers does not exist
[~pgomez] Setting the system property {{-Dorg.csanchez.jenkins.plugins.kubernetes.PodTemplateBuilder .defaultHome =/home/jenkins/agent}} should workaround that problem and mock the behavior that was there before JENKINS-58705.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.4027.1582241400184%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Andrew Sumner edited a comment on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error I will have a look at this over the weekend and get back to you as soon as I can. Could you let me know the version of both the jenkins proget plugin and proget application that versions you are using ? for the following: * Jenkins * Jenkins ProGet Plugin * ProGet application I know there is an issue with large files (over 200MB) that I'm hoping to look into soon, however I don't think this would explain your 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.204701.1582203816000.4024.1582241220129%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Andrew Sumner commented on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error I will have a look at this over the weekend and get back to you as soon as I can. Could you let me know the version of both the jenkins proget plugin and proget application that you are using? I know there is an issue with large files (over 200MB) that I'm hoping to look into soon, however I don't think this would explain your 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.204701.1582203816000.4022.1582241040207%40Atlassian.JIRA.
[JIRA] (JENKINS-60007) Timestamper scripting API doesn't work for Pipeline jobs since version 1.9
Title: Message Title Daniel Kirkdorffer commented on JENKINS-60007 Re: Timestamper scripting API doesn't work for Pipeline jobs since version 1.9 Basil Crow I don't have a ready setup to test it against. Apologies. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202824.1572556491000.4019.1582240140241%40Atlassian.JIRA.
[JIRA] (JENKINS-56468) githubPRComment throws NPE
Title: Message Title Scott Hubbard commented on JENKINS-56468 Re: githubPRComment throws NPE Any update on this? It still happens on plugin version 2.6.0. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198067.1551981547000.4015.1582240020152%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Mark Waite commented on JENKINS-57205 Re: Null pointer exception in JGit pre-build merge Thanks for doing that. Your experience matches mine when exploring a bug. By the time I've duplicated the bug in a unit test, I've understood it well enough that the bug fix is simple compared to all the learning that preceded it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198962.1556378819000.4009.1582239480188%40Atlassian.JIRA.
[JIRA] (JENKINS-60007) Timestamper scripting API doesn't work for Pipeline jobs since version 1.9
Title: Message Title Basil Crow commented on JENKINS-60007 Re: Timestamper scripting API doesn't work for Pipeline jobs since version 1.9 I have not yet released this fix, but an incremental build is available with the above changes which I believe should resolve this bug. Daniel Kirkdorffer, Rickard Dybeck, and T. Houdayer, are any of you interested in testing the incremental build before I release it? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202824.1572556491000.4007.1582239060240%40Atlassian.JIRA.
[JIRA] (JENKINS-23977) Promoted-builds does not allow build secrets
Title: Message Title
Andy Shinn commented on JENKINS-23977
Re: Promoted-builds does not allow build secrets
I can't seem to get this working (or maybe am not understanding it correctly). I have a promotion which sets a predefined parameter of credentialssh=analytics-jenkins-deployer-staging. In my triggered downstream job I have a credential parameter named credentialssh. When the downstream job is triggered by the promotion I get a failure with error:
ERROR: Could not find credentials entry with ID '${credentialssh}'
But when I run it manually it works fine. 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.156447.1406232862000.4002.1582238400240%40Atlassian.JIRA.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title
Brian Ray commented on JENKINS-57205
Re: Null pointer exception in JGit pre-build merge
Yep. Finally have a test that replicates the scenario available for a sneak peak here in my fork.
[ERROR] Failures:
[ERROR] JGitClientTest.testGetTags_packedRefs:143
Expected: a collection containing (hasProperty("name", "lightweight_tag") and hasProperty("SHA1", ))
but: mismatches were: [hasProperty("name", "lightweight_tag") property 'name' was "annotated_tag", hasProperty("SHA1", ) property 'SHA1' was null]
[INFO]
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
That was almost as tricky to write as the NPE was to track down. (I wish the tests were Spock specs. ) Fixing the bug might be the easiest part! Time to rebase, then the actual patch, then the PR ... maybe by the end of the week.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198962.1556378819000.3996.1582237080283%40Atlassian.JIRA.
[JIRA] (JENKINS-61170) Document the basic setup of the Kubernetes Jenkins plugin
Title: Message Title Marky Jackson commented on JENKINS-61170 Re: Document the basic setup of the Kubernetes Jenkins plugin PR: https://github.com/jenkinsci/kubernetes-plugin/pull/716 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204710.158222872.3993.1582237020120%40Atlassian.JIRA.
[JIRA] (JENKINS-60007) Timestamper scripting API doesn't work for Pipeline jobs since version 1.9
Title: Message Title Basil Crow updated JENKINS-60007 Fixed in jenkinsci/timestamper-plugin#47. Jenkins / JENKINS-60007 Timestamper scripting API doesn't work for Pipeline jobs since version 1.9 Change By: Basil Crow 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
[JIRA] (JENKINS-59603) Create unit test for MatrixBridge
Title: Message Title Dennis Campagna assigned an issue to Dennis Campagna Jenkins / JENKINS-59603 Create unit test for MatrixBridge Change By: Dennis Campagna Assignee: Dennis Campagna Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202244.1569923168000.3988.1582236360138%40Atlassian.JIRA.
[JIRA] (JENKINS-59591) Issue column tooltip always shows totals
Title: Message Title Dennis Campagna commented on JENKINS-59591 Re: Issue column tooltip always shows totals I'm starting to 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.202232.1569875889000.3986.1582236120136%40Atlassian.JIRA.
[JIRA] (JENKINS-59591) Issue column tooltip always shows totals
Title: Message Title Dennis Campagna assigned an issue to Dennis Campagna Jenkins / JENKINS-59591 Issue column tooltip always shows totals Change By: Dennis Campagna Assignee: Dennis Campagna Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202232.1569875889000.3984.1582236060296%40Atlassian.JIRA.
[JIRA] (JENKINS-60007) Timestamper scripting API doesn't work for Pipeline jobs since version 1.9
Title: Message Title Basil Crow updated JENKINS-60007 Jenkins / JENKINS-60007 Timestamper scripting API doesn't work for Pipeline jobs since version 1.9 Change By: Basil Crow 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.202824.1572556491000.3967.1582233600465%40Atlassian.JIRA.
[JIRA] (JENKINS-60007) Timestamper scripting API doesn't work for Pipeline jobs since version 1.9
Title: Message Title Basil Crow started work on JENKINS-60007 Change By: Basil Crow 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.202824.1572556491000.3965.1582233600436%40Atlassian.JIRA.
[JIRA] (JENKINS-61172) ALM Plug in not working while running from Linux
Title: Message Title Mark Waite moved an issue Jenkins / JENKINS-61172 ALM Plug in not working while running from Linux Change By: Mark Waite Project: Infrastructure Jenkins Key: INFRA JENKINS - 2475 61172 Workflow: classic default workflow JNJira + In-Review Component/s: hp-application-automation-tools-plugin Component/s: ci.jenkins.io Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) --
[JIRA] (JENKINS-56594) Warnings trend graph has no y-axis legend
Title: Message Title
Ulli Hafner edited a comment on JENKINS-56594
Re: Warnings trend graph has no y-axis legend
I think it would make sense to move the decision of what to show one layer up and not in the chart code. So the UI should simply have an {{if-else}}. This could be done similar to the other UI view: [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/resources/io/jenkins/plugins/analysis/core/model/IssuesDetail/index.jelly#L23 . ]The code for the trend is located in [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/resources/io/jenkins/plugins/analysis/core/model/JobAction/floatingBox.jelly.] So you need to have the {{if-else}} here and show the trend or something else. The {{if}} needs to test an boolean property of {{$\{from}}} which is the instance of the [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/core/model/JobAction.java] Here we should have a method in the style of [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/core/model/JobAction.java#L201] that iterates over all the results and checks if the number of warnings = 0.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198216.1552902109000.3948.1582232280528%40Atlassian.JIR
[JIRA] (JENKINS-56594) Warnings trend graph has no y-axis legend
Title: Message Title
Ulli Hafner edited a comment on JENKINS-56594
Re: Warnings trend graph has no y-axis legend
I think it would make sense to move the decision of what to show one layer up and not in the chart code. So the UI should simply have an {{if-else}}. This could be done similar to the other UI view: [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/resources/io/jenkins/plugins/analysis/core/model/IssuesDetail/index.jelly#L23] . The code for the trend is located in [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/resources/io/jenkins/plugins/analysis/core/model/JobAction/floatingBox.jelly . ] . So you need to have the {{if-else}} here and show the trend or something else. The {{if}} needs to test an boolean property of {{$\{from}}} which is the instance of the [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/core/model/JobAction.java] Here we should have a method in the style of [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/core/model/JobAction.java#L201] that iterates over all the results and checks if the number of warnings = 0.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198216.1552902109000.3954.1582232280653%40Atlassia
[JIRA] (JENKINS-56594) Warnings trend graph has no y-axis legend
Title: Message Title
Ulli Hafner edited a comment on JENKINS-56594
Re: Warnings trend graph has no y-axis legend
I think it would make sense to move the decision of what to show a different screen should be one layer up and not in the chart code. So the UI should simply have an {{if-else}}. This could be done similar to the other UI view: [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/resources/io/jenkins/plugins/analysis/core/model/IssuesDetail/index.jelly#L23.]The code for the trend is located in [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/resources/io/jenkins/plugins/analysis/core/model/JobAction/floatingBox.jelly.] So you need to have the {{if-else}} here and show the trend or something else. The {{if}} needs to test an boolean property of {{$\{from}}} which is the instance of the [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/core/model/JobAction.java] Here we should have a method in the style of [https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/core/model/JobAction.java#L201] that iterates over all the results and checks if the number of warnings = 0.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198216.1552902109000.393
[JIRA] (JENKINS-60007) Timestamper scripting API doesn't work for Pipeline jobs since version 1.9
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-60007 Timestamper scripting API doesn't work for Pipeline jobs since version 1.9 Change By: Basil Crow Summary: Timestamper scripting API doesn't work for Pipeline jobs since version 1.9 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202824.1572556491000.3942.1582232221334%40Atlassian.JIRA.
[JIRA] (JENKINS-60007) Timestamper scripting API doesn't work for Pipeline jobs since version 1.9
Title: Message Title Basil Crow assigned an issue to Basil Crow Jenkins / JENKINS-60007 Timestamper scripting API doesn't work for Pipeline jobs since version 1.9 Change By: Basil Crow Assignee: Steven G Brown Basil Crow Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202824.1572556491000.3945.1582232221371%40Atlassian.JIRA.
[JIRA] (JENKINS-60007) Timestamper API doesn't work for Pipeline jobs since version 1.9
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-60007 Timestamper API doesn't work for Pipeline jobs since version 1.9 Change By: Basil Crow Summary: Timestamper REST API doesn't work for Pipeline jobs since version 1.9 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202824.1572556491000.3939.1582232221299%40Atlassian.JIRA.
[JIRA] (JENKINS-60007) Timestamper REST API doesn't work for Pipeline jobs since version 1.9
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-60007 Timestamper REST API doesn't work for Pipeline jobs since version 1.9 Change By: Basil Crow Summary: Timestamper REST API doesn't work for Pipeline jobs since version 1.9 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202824.1572556491000.3936.1582232221261%40Atlassian.JIRA.
[JIRA] (JENKINS-55167) PCT crashes on Java 11 due to unsafe usage in nl.jqno.equalsverifier
Title: Message Title Basil Crow updated JENKINS-55167 Fixed in jenkinsci/timestamper-plugin#42. Jenkins / JENKINS-55167 PCT crashes on Java 11 due to unsafe usage in nl.jqno.equalsverifier Change By: Basil Crow 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 th
[JIRA] (JENKINS-56594) Warnings trend graph has no y-axis legend
Title: Message Title
Ulli Hafner commented on JENKINS-56594
Re: Warnings trend graph has no y-axis legend
I think it would make sense to show a different screen should be one layer up and not in the chart code. So the UI should simply have an if-else. This could be done similar to the other UI view: https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/resources/io/jenkins/plugins/analysis/core/model/IssuesDetail/index.jelly#L23. The code for the trend is located in https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/resources/io/jenkins/plugins/analysis/core/model/JobAction/floatingBox.jelly. So you need to have the if-else here and show the trend or something else. The if needs to test an boolean property of ${from} which is the instance of the https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/core/model/JobAction.java Here we should have a method in the style of https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/core/model/JobAction.java#L201 that iterates over all the results and checks if the number of warnings = 0.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198216.1552902109000.3921.1582232100206%40Atlassian.JIRA.
[JIRA] (JENKINS-41336) Cron based jobs are triggered at random times and also at the time Stash is unavailable
Title: Message Title Luis Ehlen reopened an issue Jenkins / JENKINS-41336 Cron based jobs are triggered at random times and also at the time Stash is unavailable Change By: Luis Ehlen Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178115.1485195646000.3907.1582231140516%40Atlassian.JIRA.
[JIRA] (JENKINS-41336) Cron based jobs are triggered at random times and also at the time Stash is unavailable
Title: Message Title Luis Ehlen commented on JENKINS-41336 Re: Cron based jobs are triggered at random times and also at the time Stash is unavailable I just updated to the latest Jenkins LTS 2.204.2 and the latest version of the stash pull request builder plugin 1,17 (from 1.8) and the mentioned behavior with the cron based jobs appeared. I can see this on my logs: Feb 19, 2020 12:25:29 PM WARNING hudson.triggers.Trigger checkTriggersTrigger stashpullrequestbuilder.stashpullrequestbuilder.StashBuildTrigger.run() triggered by hudson.maven.MavenModuleSet@45177041[JOB_NAME] spent too much time (54 sec) in its execution, other timers can be affected Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178115.1485195646000.3899.1582231080232%40Atlassian.JIRA.
[JIRA] (JENKINS-61170) Document the basic setup of the Kubernetes Jenkins plugin
Title: Message Title Marky Jackson commented on JENKINS-61170 Re: Document the basic setup of the Kubernetes Jenkins plugin A member of the community is concerned that the README.md does not detail the basic setup of this plugin. I am taking the initiative to document a straight forward configuration and will work with this community member to ensure they deem it acceptable. I will PR it once I am completed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204710.158222872.3884.1582228920198%40Atlassian.JIRA.
[JIRA] (JENKINS-61171) JiraTestReporterPlugin no longer works
Title: Message Title Dave Bourdon created an issue Jenkins / JENKINS-61171 JiraTestReporterPlugin no longer works Issue Type: Bug Assignee: Catalin Luta Components: jiratestresultreporter-plugin Created: 2020-02-20 19:59 Environment: Jenkins ver. 2.204.1 JiraTestResultReporter plugin 2.0.7 Priority: Blocker Reporter: Dave Bourdon The plugin stopped working in jobs over the weekend and will no longer validate the Jira Project Key and allow further config and use. This is most likely caused by Jira Cloud deprecations for GDPR - issue was seen starting this week - https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944#M408883 logs show: Feb 20, 2020 2:55:36 PM SEVERE org.jenkinsci.plugins.JiraTestResultReporter.JiraUtils logError The issue might be deleted, or there is no internet connection, etc. org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487) at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) at com.atlassian.jira.rest.client.internal.json.CommentJsonParser.parse(CommentJsonParser.java:37) at com.atlassian.jira.rest.client.internal.json.CommentJsonParser.parse(CommentJsonParser.java:27) at com.atlassian.jira.rest.client.internal.json.JsonWeakParserForJsonObject.parse(JsonWeakParserForJsonObject.java:39) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parseArray(IssueJsonParser.java:146) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:216) at com.atlassian.jira.rest.client.internal.json.IssueJsonParser.parse(IssueJsonParser.java:88) at com.atlassian.jira.rest
[JIRA] (JENKINS-61170) Document the basic setup of the Kubernetes Jenkins plugin
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-61170 Document the basic setup of the Kubernetes Jenkins plugin Issue Type: Task Assignee: Marky Jackson Components: kubernetes-plugin Created: 2020-02-20 19:58 Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Googl
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Ian Katz commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR This is JIRA Cloud, https://mydomain.atlassian.net/ All I noticed at the moment is that now it says "Success" instead of "Failed to login to JIRA" when I validate the settings in Jenkins. I haven't looked deeper than that. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198679.155502593.3866.1582227720251%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Ian Katzare you using the jira-plugin against JIRA Cloud, or your own private JIRA Server? The GDPR change has been deployed to JIRA Cloud which has broken this plugin when you actually to create a JIRA ticket. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198679.155502593.3857.1582227420224%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Philip Aston commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Thanks for investigating Karl. Yes, that configuration corresponds to mine. I guess the one difference might be that my jobs run on nodes on different machines, with different workspaces. Also, the later commit will trigger another run of the upstream job (on a different machine). Its not recurred since I've downgraded, so I'm going to run with this for 1.9.6 for next week, then I'll try upgrading again. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.3849.1582227300270%40Atlassian.JIRA.
[JIRA] (JENKINS-38276) Increase size of text area for pipeline script code
Title: Message Title Jesse Glick commented on JENKINS-38276 Re: Increase size of text area for pipeline script code Tested pull requests would be very welcome! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174439.1474032648000.3814.1582226940651%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Ian Katz commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR I'm using the latest version of the plugin as specified here and it seems to validate properly https://issues.jenkins-ci.org/browse/JENKINS-60305 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198679.155502593.3802.1582226100239%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Jesper Matthiesen Unfortunately the version of jira-rest-java-client that is used in the Jenkins jira-plugin is a few years old, and the patch is to the latest version. I'm not familiar enough with the jira-plugin code to move this forward, but I'm trying since I heavily depend on this plugin working with JIRA Cloud. See this thread: https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944#U1304511 to see the discussion with Atlassian. There are a lot of people that have been affected by this API change in JIRA cloud. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198679.155502593.3793.1582225920273%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-56987 Atlassian Jira API Changes for GDPR Change By: Craig Rodrigues see changes [https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement/] See also this thread on the Atlassian forums: https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944#U1304511 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198679.155502593.3789.1582225800580%40Atlassian.JIRA.
[JIRA] (JENKINS-60797) remote-file-plugin: enable selecting a fallback branch
Title: Message Title Tiran Meltser commented on JENKINS-60797 Re: remote-file-plugin: enable selecting a fallback branch Hi, Our lab was finally fixed this week and I was able to test this addition - seems to be working fine! Great work! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204125.1579192122000.3778.1582225620140%40Atlassian.JIRA.
[JIRA] (JENKINS-56594) Warnings trend graph has no y-axis legend
Title: Message Title Colin Wlodkowski commented on JENKINS-56594 Re: Warnings trend graph has no y-axis legend I recently reached out to the EChart mailing list to see if it is possible to provide an integer based axis, however, have yet to receive a response. In the meantime, does anyone have any documentation on how the EChart JS lib is being used to display graphs within the plugin or where in the source code the graph is being displayed to the UI? Im rather new and would like to try and create a POC for hiding the chart and showing the no issues screen when there are no warnings so I'll take any help I can get, 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.198216.1552902109000.3772.1582225020579%40Atlassian.JIRA.
[JIRA] (JENKINS-60940) Convert git client plugin tests from JUnit 3 to JUnit 4
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60940 Convert git client plugin tests from JUnit 3 to JUnit 4 Change By: Mark Waite The git client plugin tests have started their transition process to retire the JUnit 3 based GitAPITestCase, CliGitAPIImplTest, and JGitAPIImplTest. They should be replaced by the parameterized GitClientTest.For each test in GitAPITestCase, CliGitAPIImplTest, and JGitAPIImplTest:* If it is already tested in GitClientTest, delete the test from the JUnit 3 based tests* If it is not already tested in GitClientTest, write a test in GitClientTest or in a new test class and delete the test from the JUnit 3 based testsThis issue could be worked by multiple people concurrently, so long as they coordinate with one another on the specific tests they are converting. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Hi Philip Aston - I just tried the following test with 1.10.10 and it seemed to work: (1) Add CL 123 to downstream job directory. (2) Add CL 124 to upstream job directory. (3) Trigger upstream job that has a 20 second sleep as a build step. (4) Add 2 more CLs to each directory. (5) Downstream job is triggered with CL124 as the paramater and jobs is pinned to that CL. P4-Plugin looks for most recent CL in downstream depot path and syncs CL 123. My setup is - Upstream job... Downstream job... and: Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.3755.1582221240263%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-33163 Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Change By: Karl Wirth Attachment: image-2020-02-20-17-50-12-201.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.3739.1582221060594%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-33163 Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Change By: Karl Wirth Attachment: image-2020-02-20-17-50-50-682.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.3747.1582221060738%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-33163 Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Change By: Karl Wirth Attachment: image-2020-02-20-17-49-11-213.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.3731.1582221000361%40Atlassian.JIRA.
[JIRA] (JENKINS-61169) Non-Serializable exception thrown on wrong object
Title: Message Title
Matthew Eggers updated an issue
Jenkins / JENKINS-61169
Non-Serializable exception thrown on wrong object
Change By:
Matthew Eggers
I am getting an exception when attempting to serialize a groovy Map that I've generated:{code:java}an exception which occurred: in field groovy.lang.Closure.delegate in object Script1$_run_closure1@30d6aac5 in field com.nike.acid.pipeline.configuration.adaptors.AdvancedClientAdaptor.clientConverter in object com.nike.acid.pipeline.configuration.adaptors.AdvancedClientAdaptor@629f71ba in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@2c17fa09 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@1635b321 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@146f27c2 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@19d1436 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@1d8bbdc9 in field com.cloudbees.groovy.cps.Continuable.e in object org.jenkinsci.plugins.workflow.cps.SandboxContinuable@39c61bdb in field org.jenkinsci.plugins.workflow.cps.CpsThread.program in object org.jenkinsci.plugins.workflow.cps.CpsThread@7ebbe670 in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@3b2aa9f8 in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@3b2aa9f8Caused: java.io.NotSerializableException: Script1 {code}The problem here is, I'm not asking {{AdvancedClientAdaptor}} to persist the {{clientConverter}} field (It has Closures in it). I'm asking it to persist a JsonStringified groovy map. The issue appears to be in the {{AdvanceClientAdaptor}} class I've written. It accepts groovy map that it performs transformations on. Here is a trivial example: {code:java}def Map = [ targetConfig: [ foo: "bar" ], clientConverter: [ foo: { targetConfig, value -> targetConfig['foo'] = value }]] {code} The {{AdvancedClientConverter}} class basically accepts this Map as an input, assigns 2 member property variables to _each_ of the 2 map fields above:{code:java}class AdvancedClientConverter implements Serializable { Map targetConfig Map clientConverter def steps //running groovy instance AdvancedClientConverter(Map converterMap, def steps) { this.clientConverter = converterMap.clientConverter this.targetConfig = converterMap.targetConfig this.steps = steps } def converterOperation() { this.targetConfig.foo = this.clientConverter.foo(this.targetConfig, "baz"); String fileString = JsonOutput.prettyPrint(JsonOutput.toJson(targetConfig))} steps.echo ("final config: ${fileString}") steps.writeFile file: "FinalConfig.text", text: fileString return target }} {code}The above is all invoked in a running Jenkins Pipeline:{code}#!groovy@Library
[JIRA] (JENKINS-61169) Non-Serializable exception thrown on wrong object
Title: Message Title
Matthew Eggers updated an issue
Jenkins / JENKINS-61169
Non-Serializable exception thrown on wrong object
Change By:
Matthew Eggers
I am getting an exception when attempting to serialize a groovy Map that I've generated:{code:java}an exception which occurred: in field groovy.lang.Closure.delegate in object Script1$_run_closure1@30d6aac5 in field com.nike.acid.pipeline.configuration.adaptors.AdvancedClientAdaptor.clientConverter in object com.nike.acid.pipeline.configuration.adaptors.AdvancedClientAdaptor@629f71ba in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@2c17fa09 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@1635b321 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@146f27c2 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@19d1436 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@1d8bbdc9 in field com.cloudbees.groovy.cps.Continuable.e in object org.jenkinsci.plugins.workflow.cps.SandboxContinuable@39c61bdb in field org.jenkinsci.plugins.workflow.cps.CpsThread.program in object org.jenkinsci.plugins.workflow.cps.CpsThread@7ebbe670 in field org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.threads in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@3b2aa9f8 in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@3b2aa9f8Caused: java.io.NotSerializableException: Script1 {code}The problem here is, I'm not asking {{AdvancedClientAdaptor}} to persist the {{clientConverter}} field (It has Closures in it). I'm asking it to persist a JsonStringified groovy map. The issue appears to be in the {{AdvanceClientAdaptor}} class I've written. It accepts groovy map that it performs transformations on. Here is a trivial example: {code:java}def Map = [ targetConfig: [ foo: "bar" ], clientConverter: [ foo: { targetConfig, value -> targetConfig['foo'] = value }]] {code} The {{AdvancedClientConverter}} class basically accepts this Map as an input, assigns 2 member property variables to _each_ of the 2 map fields above:{code:java}class AdvancedClientConverter implements Serializable { Map targetConfig Map clientConverter def steps //running groovy instance AdvancedClientConverter(Map converterMap, def steps) { this.clientConverter = converterMap.clientConverter this.targetConfig = converterMap.targetConfig this.steps = steps } def converterOperation() { this.targetConfig.foo = this.clientConverter.foo(this.targetConfig, "baz"); String fileString = JsonOutput.prettyPrint(JsonOutput.toJson(targetConfig))} steps.echo ("final config: ${fileString}") steps.writeFile file: "FinalConfig.text", text: fileString return target }} {code}The above is all invoked in a running Jenkins Pipeline:{code}#!groovy@Libra
[JIRA] (JENKINS-61169) Non-Serializable exception thrown on wrong object
Title: Message Title Matthew Eggers created an issue Jenkins / JENKINS-61169 Non-Serializable exception thrown on wrong object Issue Type: Bug Assignee: Suresh Kumar Components: core, file-operations-plugin, pipeline-utility-steps-plugin Created: 2020-02-20 17:42 Environment: Jenkins 2.164.1 pipelines-groovy plugin Priority: Major Reporter: Matthew Eggers I am getting an exception when attempting to serialize a groovy Map that I've generated: an exception which occurred: in field groovy.lang.Closure.delegate in object Script1$_run_closure1@30d6aac5 in field com.nike.acid.pipeline.configuration.adaptors.AdvancedClientAdaptor.clientConverter in object com.nike.acid.pipeline.configuration.adaptors.AdvancedClientAdaptor@629f71ba in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@2c17fa09 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@1635b321 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@146f27c2 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@19d1436 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@1d8bbdc9 in field com.cloudbees.groovy.cps.Continuable.e in object org.jenkinsci.plugins.workflow.cps.SandboxContinuable@39c61bdb in field org.jenkinsci.plugins.workflow.cps.CpsThread.program in object org.jenkinsci.plugins.workflow.cps.CpsThread@7ebbe670 in field org.j
[JIRA] (JENKINS-61156) Regression: P4 Plugin 1.10.10 trigger doesn't run jobs
Title: Message Title Karl Wirth commented on JENKINS-61156 Re: Regression: P4 Plugin 1.10.10 trigger doesn't run jobs Hi Tom Cramer - Quick update. I just upgraded my test instance to 1.10.10 and for me the trigger is still working so it's possible this is to do with the paths involved or could be Jenkins version related also. If you can get me the data mentioned above and the paths involved that would be great (for example is it a stream, are there spaces, numbers or non ASCII characters). If you'd feel more comfortable in sending the data to me directly please send it to supp...@perforce.com for my attention. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204686.158215634.3720.1582219200191%40Atlassian.JIRA.
[JIRA] (JENKINS-55167) PCT crashes on Java 11 due to unsafe usage in nl.jqno.equalsverifier
Title: Message Title Jesse Glick started work on JENKINS-55167 Change By: Jesse Glick 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.196234.1544690574000.3664.1582215660491%40Atlassian.JIRA.
[JIRA] (JENKINS-55167) PCT crashes on Java 11 due to unsafe usage in nl.jqno.equalsverifier
Title: Message Title Jesse Glick updated JENKINS-55167 Jenkins / JENKINS-55167 PCT crashes on Java 11 due to unsafe usage in nl.jqno.equalsverifier Change By: Jesse Glick 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.196234.1544690574000.3667.1582215660543%40Atlassian.JIRA.
[JIRA] (JENKINS-58425) withMaven prints debug log and pollutes
Title: Message Title Garr commented on JENKINS-58425 Re: withMaven prints debug log and pollutes +1 for adding " | tail -1" to mvn help:evaluate. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200552.1562762817000.3635.1582212900370%40Atlassian.JIRA.
[JIRA] (JENKINS-58425) withMaven prints debug log and pollutes
Title: Message Title Garrett Smith updated an issue Jenkins / JENKINS-58425 withMaven prints debug log and pollutes Change By: Garrett Smith Comment: Is there a way around this? I'm even trying to log to a temporary file and I'm still seeing the stdout info. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200552.1562762817000.3621.1582212240315%40Atlassian.JIRA.
[JIRA] (JENKINS-58425) withMaven prints debug log and pollutes
Title: Message Title Garrett Smith commented on JENKINS-58425 Re: withMaven prints debug log and pollutes Is there a way around this? I'm even trying to log to a temporary file and I'm still seeing the stdout info. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200552.1562762817000.3614.1582212120399%40Atlassian.JIRA.
[JIRA] (JENKINS-61168) testing purpose
Title: Message Title Dinesh Kumar created an issue Jenkins / JENKINS-61168 testing purpose Issue Type: Bug Assignee: Unassigned Components: adaptive-disconnector-plugin Created: 2020-02-20 15:01 Priority: Minor Reporter: Dinesh Kumar Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To u
[JIRA] (JENKINS-61157) Jenkins automatically set entityId as https://jenkins.company.com/securityRealm/finishLogin
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61157 Re: Jenkins automatically set entityId as https://jenkins.company.com/securityRealm/finishLogin https://github.com/jenkinsci/saml-plugin/blob/master/doc/TROUBLESHOOTING.md#no-valid-subject-assertion-found-in-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.204687.1582176654000.3608.1582209960360%40Atlassian.JIRA.
[JIRA] (JENKINS-61157) Jenkins automatically set entityId as https://jenkins.company.com/securityRealm/finishLogin
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect Jenkins / JENKINS-61157 Jenkins automatically set entityId as https://jenkins.company.com/securityRealm/finishLogin Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: 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.204687.1582176654000.3610.1582209960394%40Atlassian.JIRA.
[JIRA] (JENKINS-61106) Load runner scenario file is getting deleted once i start executing the JOB and also Job is failing.
Title: Message Title Rolando-Mihai Vlad edited a comment on JENKINS-61106 Re: Load runner scenario file is getting deleted once i start executing the JOB and also Job is failing. Are you running the job on the jenkins server or on a slave machine?The path which the plugin wants to delete is the jenkins workspace and your scenario (.lrs file) should not be on that path. We can also schedule a webex tommorow starting from 10am GMT+2. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204618.1581918604000.3606.1582208700127%40Atlassian.JIRA.
[JIRA] (JENKINS-61106) Load runner scenario file is getting deleted once i start executing the JOB and also Job is failing.
Title: Message Title Rolando-Mihai Vlad commented on JENKINS-61106 Re: Load runner scenario file is getting deleted once i start executing the JOB and also Job is failing. Are you running the job on the jenkins server or on a slave machine? The path which the plugin wants to delete is the jenkins workspace and your scenario (.lrs file) should not be on that path. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204618.1581918604000.3604.1582208340161%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Jesper Matthiesen commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Craig Rodrigues did you succeed in incorporating the patch? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198679.155502593.3587.1582206540292%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title
Amila Gunathilake updated an issue
Jenkins / JENKINS-61167
Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Change By:
Amila Gunathilake
Hi all,I'm having declarative pipeline in my Jenkinsfile code. I changed my Jenkinsfile code as below, because I wanted to archive my artifact file by using Inedo ProGet plugin into my Proget site. I already configured Proget in Jenkins with API key and installed the plugin. I have added the ProGet API Key settings into the Jenkins' system config settings and it's testing the connection successfully. !image-2020-02-20-08- 10 24 - 02 40 - 266 897 .png! *{color:#0747a6}Below is the code change I added in my Jenkinsfile.{color}* !image-2020-02-20-08-02-45-754.png!So as above script underline shows the way I'm getting my build artifact's Version Number. Also below is the new *{color:#0747a6} .upack {color}* Package file I'm creating with the PackageName " {color:#0747a6} JenkinsPackage.upack {color} " for the purpose of upload to the Proget site. !image-2020-02-20-08-19-00-759.png!But here the issue I'm facing is when I'm running my build job and it's not success and failing the Proget Upload command with below error log message from Console-Output. !image-2020-02-20-08-21-46-822.png! {color:#d24939} Please anyone assist me on this ? What's the issue I'm having here, what blocking me to uploading my package file into Proget site ?{color}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sh
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Amila Gunathilake updated an issue Jenkins / JENKINS-61167 Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error Change By: Amila Gunathilake Attachment: image-2020-02-20-08-24-40-897.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.3582.1582205100193%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title
Amila Gunathilake updated an issue
Jenkins / JENKINS-61167
Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Change By:
Amila Gunathilake
Hi all,I'm having declarative pipeline in my Jenkinsfile code. I changed my Jenkinsfile code as below, because I wanted to archive my artifact file by using Inedo ProGet plugin into my Proget site. I already configured Proget in Jenkins with API key and installed the plugin. I have added the ProGet API Key settings into the Jenkins' system config settings and it's testing the connection successfully. !image-2020-02-20-08-10-02-266.png! *{color:#0747a6} Below is the code change I added in my Jenkinsfile. {color}* !image-2020-02-20-08-02-45-754.png! h1 So as above script underline shows the way I'm getting my build artifact's Version Number . Also below is the new .upack Package file I'm creating with the PackageName "JenkinsPackage.upack" for the purpose of upload to the Proget site. !image-2020-02-20-08-19-00-759.png!But here the issue I'm facing is when I'm running my build job and it's not success and failing the Proget Upload command with below error log message from Console-Output. !image-2020-02-20-08-21-46-822.png! {color:#d24939} Please anyone assist me on this ? What's the issue I'm having here, what blocking me to uploading my package file into Proget site ?{color}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Amila Gunathilake updated an issue Jenkins / JENKINS-61167 Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error Change By: Amila Gunathilake Attachment: image-2020-02-20-08-21-46-822.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.3578.1582204920154%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Amila Gunathilake updated an issue Jenkins / JENKINS-61167 Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error Change By: Amila Gunathilake Attachment: image-2020-02-20-08-19-00-759.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.3576.1582204800126%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Amila Gunathilake updated an issue Jenkins / JENKINS-61167 Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error Change By: Amila Gunathilake Attachment: image-2020-02-20-08-10-02-266.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.3574.1582204260158%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Amila Gunathilake created an issue Jenkins / JENKINS-61167 Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error Issue Type: Bug Assignee: Andrew Sumner Attachments: image-2020-02-20-08-02-45-754.png Components: inedo-proget-plugin, nuget-plugin Created: 2020-02-20 13:03 Priority: Major Reporter: Amila Gunathilake Hi all, I'm having declarative pipeline in my Jenkinsfile code. I changed my Jenkinsfile code as below, because I wanted to archive my artifact file by using Inedo ProGet plugin into my Proget site. Below is the code change I added in my Jenkinsfile. Add Comment
[JIRA] (JENKINS-60359) Use standard breadcrumbs
Title: Message Title Lu Liu resolved as Fixed Jenkins / JENKINS-60359 Use standard breadcrumbs Change By: Lu Liu Status: Open Resolved 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.203380.1575442072000.3570.1582203840557%40Atlassian.JIRA.
[JIRA] (JENKINS-60359) Use standard breadcrumbs
Title: Message Title Lu Liu assigned an issue to Lu Liu Jenkins / JENKINS-60359 Use standard breadcrumbs Change By: Lu Liu Assignee: Shenyu Zheng Lu Liu Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203380.1575442072000.3564.1582203720321%40Atlassian.JIRA.
[JIRA] (JENKINS-61166) Improve how security warnings are shown
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-61166 Improve how security warnings are shown Issue Type: Improvement Assignee: Daniel Beck Components: core Created: 2020-02-20 12:58 Labels: security Priority: Minor Reporter: Daniel Beck Currently, the "Updates" tab of the plugin manager does not have any indication like "Installing this update will address a currently active security warning". It's really annoying to see the warning, go to the plugin manager, and be presented with 30 updates, when all you want to do is apply security updates. Need to switch back and forth between looking at the list of updates, and the security warning popup, to figure out what needs updating. Add Comment
[JIRA] (JENKINS-60359) Use standard breadcrumbs
Title: Message Title Ulli Hafner commented on JENKINS-60359 Re: Use standard breadcrumbs Yippie!! And so easy to fix... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203380.1575442072000.3556.1582203480236%40Atlassian.JIRA.
[JIRA] (JENKINS-61151) Adding "alpha" keyword to version number
Title: Message Title Dennis Gu updated JENKINS-61151 Jenkins / JENKINS-61151 Adding "alpha" keyword to version number Change By: Dennis Gu Status: In Review Resolved 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.204681.1582128515000.3554.1582203360118%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Matej Dro commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error This PR has not been merged since September. I don't think waiting for them to finally merge is a good solution. Would forking rest java client be a good idea? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194307.1537972591000.3542.1582202400345%40Atlassian.JIRA.
[JIRA] (JENKINS-61159) HTTP DELETE requests can be crafted to delete jobs
Title: Message Title Phu Mai updated an issue Jenkins / JENKINS-61159 HTTP DELETE requests can be crafted to delete jobs Change By: Phu Mai Attachment: Step6c.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204693.1582193154000.3537.1582202220174%40Atlassian.JIRA.
[JIRA] (JENKINS-61111) Soft-deleted AWS Secrets Manager secrets still appear in Jenkins
Title: Message Title Chris Kilding updated JENKINS-6 In the absence of further information I'll have to assume that Ethan soft-deleted a secret and loaded the Jenkins credentials page within the 5-minute cache window. As mentioned, this is not something that can be fixed as long as we have to poll Secrets Manager for data. If, in the future, AWS allows Secrets Manager API clients to subscribe for updates on a push basis, then we could revisit this. Jenkins / JENKINS-6 Soft-deleted AWS Secrets Manager secrets still appear in Jenkins Change By: Chris Kilding Status: In Review Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61159) HTTP DELETE requests can be crafted to delete jobs
Title: Message Title Phu Mai updated an issue Jenkins / JENKINS-61159 HTTP DELETE requests can be crafted to delete jobs Change By: Phu Mai Attachment: Step6c.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204693.1582193154000.3539.1582202220234%40Atlassian.JIRA.
[JIRA] (JENKINS-61111) Soft-deleted AWS Secrets Manager secrets still appear in Jenkins
Title: Message Title Chris Kilding edited a comment on JENKINS-6 Re: Soft-deleted AWS Secrets Manager secrets still appear in Jenkins The bit I missed was that the bug description does not say whether the deletion was recent i.e. within the 5 minute cache window.It is expected behaviour (indeed it is a tautology) that if a secret is deleted within the cache window, its entry will continue to be shown (though it will not be functional). It is indeed an idiosyncrasy in the user experience that we would rather not have, but it is unavoidable given the current polling strategy of integrating with Secrets Manager: there is no way for Jenkins to know that the secret is (soft-)deleted until it refreshes the cache and calls Secrets Manager again.When the time comes to refresh the cache, the ListSecretsOperation dutifully filters out soft-deleted secrets. This has been tested and is known to work. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204624.1581937282000.3534.1582202100177%40Atlassian.JIRA.
[JIRA] (JENKINS-61111) Soft-deleted AWS Secrets Manager secrets still appear in Jenkins
Title: Message Title Chris Kilding updated JENKINS-6 Jenkins / JENKINS-6 Soft-deleted AWS Secrets Manager secrets still appear in Jenkins Change By: Chris Kilding 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.204624.1581937282000.3536.1582202100257%40Atlassian.JIRA.
[JIRA] (JENKINS-61111) Soft-deleted AWS Secrets Manager secrets still appear in Jenkins
Title: Message Title Chris Kilding started work on JENKINS-6 Change By: Chris Kilding 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.204624.1581937282000.3535.1582202100234%40Atlassian.JIRA.
[JIRA] (JENKINS-61111) Soft-deleted AWS Secrets Manager secrets still appear in Jenkins
Title: Message Title Chris Kilding commented on JENKINS-6 Re: Soft-deleted AWS Secrets Manager secrets still appear in Jenkins The bit I missed was that the bug description does not say whether the deletion was recent i.e. within the 5 minute cache window. It is expected behaviour (indeed it is a tautology) that if a secret is deleted within the cache window, its entry will continue to be shown (though it will not be functional). It is indeed an idiosyncrasy in the user experience that we would rather not have, but it is unavoidable given the current polling strategy of integrating with Secrets Manager: there is no way for Jenkins to know that the secret is (soft-)deleted until it refreshes the cache and calls Secrets Manager again. When the time comes to refresh the cache, the ListSecretsOperation dutifully filters out soft-deleted secrets. This has been tested and is known to work. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204624.1581937282000.3533.1582201740045%40Atlassian.JIRA.
[JIRA] (JENKINS-61111) Soft-deleted AWS Secrets Manager secrets still appear in Jenkins
Title: Message Title Chris Kilding edited a comment on JENKINS-6 Re: Soft-deleted AWS Secrets Manager secrets still appear in Jenkins This is interesting because in theory we already have an integration test tests for this very scenario, which passes pass , demonstrating that it works - :* CredentialsProviderIT#shouldTolerateDeletedCredentials . * CredentialsProviderIT#shouldTolerateRecentlyDeletedCredentials If that’s correct then what Ethan saw was probably a one-off event. If not, something may be wrong in this test’s soft deletion logic. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204624.1581937282000.3529.1582200900054%40Atlassian.JIRA.
[JIRA] (JENKINS-61148) Improve error handling if 'Space not found'
Title: Message Title Roland Mueller commented on JENKINS-61148 Re: Improve error handling if 'Space not found' We also have this NPE with 2.0.5 when the job is running, although the space does exist. After a rollback to 2.0.3 it works again. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204678.1582120375000.3528.1582199880152%40Atlassian.JIRA.
[JIRA] (JENKINS-60359) Use standard breadcrumbs
Title: Message Title Lu Liu commented on JENKINS-60359 Re: Use standard breadcrumbs I've managed to fixed this issue with PR 141(https://github.com/jenkinsci/code-coverage-api-plugin/pull/141) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203380.1575442072000.3523.1582199520376%40Atlassian.JIRA.
[JIRA] (JENKINS-61164) Configure Clouds - no credentials visible for vSphere Cloud
Title: Message Title Daniel Hoerner updated an issue Jenkins / JENKINS-61164 Configure Clouds - no credentials visible for vSphere Cloud Change By: Daniel Hoerner After updating to new jenkins version, the clouds configuration page has moved.When accessing the new config page, the "Credentials" dropddown for my existing vSphere Cloud is " - none - ". Before the update, I had configured credentails for that cloud. Also if I open the drop-down, the list only contains "-none". Also if I click "Add" and add new Global credentials, the DropDown keeps empty. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204698.1582196162000.3520.1582196820059%40Atlassian.JIRA.
