[JIRA] (JENKINS-60347) Unable to run a query in jenkins through azure cli plugin
Title: Message Title ram kumar Bodanki created an issue Jenkins / JENKINS-60347 Unable to run a query in jenkins through azure cli plugin Issue Type: Bug Assignee: Tomer Rosenthal Components: azure-cli-plugin Created: 2019-12-03 08:13 Priority: Major Reporter: ram kumar Bodanki I need to run a query in jenkins through azure cli plugin where i need to get the list of device id in iot hub. When i ran in azure vm , it ran well, but when im trying to run in jenkins , it is running long without failing or getting succeeded. az iot hub query -g resourcegroup --subscription id -n IOTHUBNAME -q "select deviceid from devices" *Added azure service principal to jenkins credentials. Add Comment
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Idan Adar commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Got hit with this limitation as well. Nuts. What is the workaround here? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.10840.1575360842854%40Atlassian.JIRA.
[JIRA] (JENKINS-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title Joerg Schwaerzler commented on JENKINS-53162 Re: Blueocean support for visualizing stages in parallel block in scripted pipeline Great to see this is finally available Olivier Lamy: Can you already tell when there will be a release containing this 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.193173.1534855202000.10844.1575361381681%40Atlassian.JIRA.
[JIRA] (JENKINS-55811) Jenkins pipeline idle lightweight executor list is growing
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-55811 Jenkins pipeline idle lightweight executor list is growing Change By: Ramon Leon Labels: lts-candidate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197205.1548669487000.10917.1575361500537%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Ramon Leon assigned an issue to Ramon Leon Jenkins / JENKINS-57304 Multiple "idle" entries on Build Executor Status for non-existant executors Change By: Ramon Leon Assignee: Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.10933.1575361566361%40Atlassian.JIRA.
[JIRA] (JENKINS-55811) Jenkins pipeline idle lightweight executor list is growing
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-55811 Jenkins pipeline idle lightweight executor list is growing Change By: Ramon Leon Labels: lts-candidate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197205.1548669487000.10919.1575361562932%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-57304 Multiple "idle" entries on Build Executor Status for non-existant executors Change By: Ramon Leon Labels: lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.10931.1575361565979%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Ramon Leon commented on JENKINS-57304 Re: Multiple "idle" entries on Build Executor Status for non-existant executors Assigned to me to keep track of it and added the lts-candidate as the PR seems to fix a bunch of tickets. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.10955.1575361622594%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Ramon Leon started work on JENKINS-57304 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.10967.1575361622949%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Ramon Leon updated JENKINS-57304 Jenkins / JENKINS-57304 Multiple "idle" entries on Build Executor Status for non-existant executors Change By: Ramon Leon Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.10969.1575361622974%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Konstantin Grammatikati updated an issue Jenkins / JENKINS-55220 Multibranch Pipeline jobs get randomly lost Change By: Konstantin Grammatikati Attachment: Jenkins_remove_branches_1.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.196298.154504211.10981.1575362041582%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Konstantin Grammatikati commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Dave Nichols We are having random branches disappearance in our Jenkins too (Jenkins ver. 2.190.3 standalone on CentOS machine). This is screenshot from Scan GitLab Project Log: But we have master branch and Jenkinsfile there. I don't know why Jenkins counting this branch as orphaned and don't see anything in logs and in Multibranch pipeline events section. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196298.154504211.11000.1575362220774%40Atlassian.JIRA.
[JIRA] (JENKINS-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title
Thomas M commented on JENKINS-55139
Re: ansicolor 0.6.0 shows terminal escape sequences in console log
I can confirm this bug and also that downgrading to 0.5.3 (from http://updates.jenkins-ci.org/download/plugins/ansicolor/) helps. My sh commands use double quotes (but only single-line, as in sh "bash path/to/script ${arg1} ${arg2}") already so I cannot confirm Dennis Hoer workaround. With the 0.6.2 I get output similar to Marc Benstein comment.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196206.1544605559000.11017.1575362882892%40Atlassian.JIRA.
[JIRA] (JENKINS-58742) IOException: Unexpected Fingerprint type
Title: Message Title Barnabas Bodnar commented on JENKINS-58742 Re: IOException: Unexpected Fingerprint type Occurred on my Jenkins v2.191.1 too, causing a build-error although the Maven-build itself was successful. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201044.1564597106000.11062.1575365460149%40Atlassian.JIRA.
[JIRA] (JENKINS-58742) IOException: Unexpected Fingerprint type
Title: Message Title Barnabas Bodnar edited a comment on JENKINS-58742 Re: IOException: Unexpected Fingerprint type Occurred on my Jenkins v2.191.1 too, causing after a build-error although the succesful Maven-build itself was successful . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201044.1564597106000.11065.1575365640146%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-57304 Multiple "idle" entries on Build Executor Status for non-existant executors Change By: Baptiste Mathus Priority: Trivial Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.11069.157535541%40Atlassian.JIRA.
[JIRA] (JENKINS-60348) Followup - Investigate root cause of idle executors
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-60348 Followup - Investigate root cause of idle executors Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-12-03 09:54 Priority: Minor Reporter: Ramon Leon There are some issues talking about idle executors populating Jenkins: https://issues.jenkins-ci.org/browse/JENKINS-57304 https://issues.jenkins-ci.org/browse/JENKINS-55811 https://issues.jenkins-ci.org/browse/JENKINS-55484 There is already a fix to manually tested that seems to avoid that, at least, the steps to reproduce the problem confirm it works: https://github.com/jenkinsci/jenkins/pull/4329 In the comments of the PR Jesse Glick expressed some concerns about the fix, maybe it's solving the symptoms but not the root cause. As the fix is valuable by itself, avoiding instances to show hung executors, we have gone forward with it and we have filed this ticket to analyze whether any other improvement could be done to solve the issue. Look into: https://github.com/jenkinsci/jenkins/pull/4329#pullrequestreview-316248853 https://github.com/jenkinsci/jenkins/pull/4329#issuecomment-555025416 https://github.com/jenkinsci/jenkins/pull/4329#issuecomment-555049195 to know where he is pointing out to. The way to work on it, I guess, should be, revert the fix on the [PR|https://github.com/jenkinsci/jenkins/pull/4329] and look where/when the final
[JIRA] (JENKINS-60045) JCasC export doesn't work with Custom Tools installed and configured
Title: Message Title Kalle Niemitalo commented on JENKINS-60045 Re: JCasC export doesn't work with Custom Tools installed and configured The exception was thrown during the newInstance call at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe(DataBoundConfigurator.java:299): T ref = (T) constructor.newInstance(args); The type being constructed should be CustomTool, and I think it is. If the type had been CustomTool[] or ToolInstallation[] or ToolInstallation, then DataBoundConfigurator.getDataBoundConstructor would have returned null, and DefaultConfiguratorRegistry.internalLookup would not have created an instance of DataBoundConfigurator. So, it seems to be a matter of incorrect arguments being generated for the CustomTool constructor. Perhaps the error is triggered by the @CheckForNull LabelSpecifics[] labelSpecifics parameter of that constructor. If CustomTool.getLabelSpecifics returns an empty array, then the type of this array does not implement java.util.Collection, so DataBoundConfiguration.describe assigns args[i] = Collections.singletonList(converted), which is not acceptable to the constructor. If this theory is correct, then the error could be fixed either by changing CustomTool to use a collection type instead of the array type, or by changing DataBoundConfiguration to check for array types as well. I cannot currently test these changes myself. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60045) JCasC export doesn't work with Custom Tools installed and configured
Title: Message Title
Kalle Niemitalo edited a comment on JENKINS-60045
Re: JCasC export doesn't work with Custom Tools installed and configured
The exception was thrown during the {{newInstance}} call at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe([DataBoundConfigurator.java:299|https://github.com/jenkinsci/configuration-as-code-plugin/blob/c0528a7b412fd83908f2ef2ce5c32d2bb499823d/plugin/src/main/java/io/jenkins/plugins/casc/impl/configurators/DataBoundConfigurator.java#L299]):{code:java}T ref = (T) constructor.newInstance(args);{code}The type being constructed should be {{CustomTool}}, and I think it is. If the type had been {{CustomTool[]}} or {{ToolInstallation[]}} or {{ToolInstallation}}, then {{DataBoundConfigurator.getDataBoundConstructor}} would have returned null, and {{DefaultConfiguratorRegistry.internalLookup}} would not have created an instance of {{DataBoundConfigurator}}.So, it seems to be a matter of incorrect arguments being generated for the [{{CustomTool}} constructor|https://github.com/jenkinsci/custom-tools-plugin/blob/28152af024c2e5a3e46b02a3b185869488d3a6e4/src/main/java/com/cloudbees/jenkins/plugins/customtools/CustomTool.java#L94-L104].Perhaps the error is triggered by the {{@CheckForNull LabelSpecifics[] labelSpecifics}} parameter of that constructor. If [{{CustomTool.getLabelSpecifics}}|https://github.com/jenkinsci/custom-tools-plugin/blob/28152af024c2e5a3e46b02a3b185869488d3a6e4/src/main/java/com/cloudbees/jenkins/plugins/customtools/CustomTool.java#L132-L134] returns an empty array, then the type of this array does not implement {{java.util.Collection}}, so {{DataBoundConfiguration.describe}} assigns {{args[i] = Collections.singletonList(converted)}}, which is not acceptable to the constructor.If this theory is correct, then the error could be fixed either by changing {{CustomTool}} to use a collection type instead of the array type, or by changing {{DataBoundConfiguration}} to check for array types as well. I cannot currently test these changes myself.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60349) User credentials not usable by Git plugin
Title: Message Title Robert Schulze created an issue Jenkins / JENKINS-60349 User credentials not usable by Git plugin Issue Type: Bug Assignee: Mark Waite Components: credentials-plugin, git-client-plugin Created: 2019-12-03 10:52 Environment: org.jenkins-ci.main:jenkins-war:2.190.3 org.jenkins-ci.plugins:git:4.0.0 org.jenkins-ci.plugins:git-client:3.0.0 org.jenkins-ci.plugins:credentials:2.3.0 Labels: git jenkins plugin Priority: Major Reporter: Robert Schulze While I can select user-level credentials in a job (configured to run as the specified user), I obtain an error "Warning: CredentialId "xyz" could not be found." when trying to run the job. Can you tell me which additional information you need? Add Comment
[JIRA] (JENKINS-60349) User credentials not usable by Git plugin
Title: Message Title Robert Schulze updated an issue Jenkins / JENKINS-60349 User credentials not usable by Git plugin Change By: Robert Schulze While I can select user-level credentials in a job (configured to run as the specified user), I obtain an error "Warning: CredentialId "xyz" could not be found." when trying to run the job.Can you tell me which additional information you need? I believe the problem should be with com.cloudbees.plugins.credentials.CredentialsMatchers as used in hudson.plugins.git.gitSCM. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203366.1575370328000.11094.1575370440334%40Atlassian.JIRA.
[JIRA] (JENKINS-59651) PIPELINE_VERSION can not export to shell environment.
Title: Message Title Adi C commented on JENKINS-59651 Re: PIPELINE_VERSION can not export to shell environment. In my mind this is critical as this is breaking CI/CD process as the versioning is not set and developers cannot promote to higher environments. Is there a fix for this in the upcoming horizon? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202341.1570157505000.11097.1575370500310%40Atlassian.JIRA.
[JIRA] (JENKINS-58727) Misleading log message when no e-mail is sent
Title: Message Title Nikita Jethani commented on JENKINS-58727 Re: Misleading log message when no e-mail is sent I am facing same issue Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201021.1564483585000.11101.1575370860479%40Atlassian.JIRA.
[JIRA] (JENKINS-60045) JCasC export doesn't work with Custom Tools installed and configured
Title: Message Title
Kalle Niemitalo edited a comment on JENKINS-60045
Re: JCasC export doesn't work with Custom Tools installed and configured
The exception was thrown during the {{newInstance}} call at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe([DataBoundConfigurator.java:299|https://github.com/jenkinsci/configuration-as-code-plugin/blob/c0528a7b412fd83908f2ef2ce5c32d2bb499823d/plugin/src/main/java/io/jenkins/plugins/casc/impl/configurators/DataBoundConfigurator.java#L299]):{code:java}T ref = (T) constructor.newInstance(args);{code}The type being constructed should be {{CustomTool}}, and I think it is. If the type had been {{CustomTool[]}} or {{ToolInstallation[]}} or {{ToolInstallation}}, then {{DataBoundConfigurator.getDataBoundConstructor}} would have returned null, and {{DefaultConfiguratorRegistry.internalLookup}} would not have created an instance of {{DataBoundConfigurator}}.So, it seems to be a matter of incorrect arguments being generated for the [{{CustomTool}} constructor|https://github.com/jenkinsci/custom-tools-plugin/blob/28152af024c2e5a3e46b02a3b185869488d3a6e4/src/main/java/com/cloudbees/jenkins/plugins/customtools/CustomTool.java#L94-L104].Perhaps the error is triggered by the {{@CheckForNull LabelSpecifics[] labelSpecifics}} parameter of that constructor. If [{{CustomTool.getLabelSpecifics}}|https://github.com/jenkinsci/custom-tools-plugin/blob/28152af024c2e5a3e46b02a3b185869488d3a6e4/src/main/java/com/cloudbees/jenkins/plugins/customtools/CustomTool.java#L132-L134] returns an array, then the type of this array does not implement {{java.util.Collection}}, so {{DataBoundConfiguration.describe}} assigns {{args[i] = Collections.singletonList(converted)}}, which is not acceptable to the constructor.If this theory is correct, then the error could be fixed either by changing {{CustomTool}} to use a collection type instead of the array type, or by changing {{ DataBoundConfiguration DataBoundConfigurator }} to check for array types as well. I cannot currently test these changes myself.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60350) Recover Deleted Dashboard view in jenkins main page
Title: Message Title Senthilkumar Palanisamy created an issue Jenkins / JENKINS-60350 Recover Deleted Dashboard view in jenkins main page Issue Type: Story Assignee: Tobias Gruetzmacher Components: dashboard-view-plugin Created: 2019-12-03 11:24 Priority: Minor Reporter: Senthilkumar Palanisamy Team, Please can you help me here: We have removed Dashboard view on our Jenkins Main page. Is it possible to recover accidentally removed views in Jenkins Our Jenkins Version 2.190.2 Add Comment This me
[JIRA] (JENKINS-60350) Recover Deleted Dashboard view in jenkins main page
Title: Message Title Senthilkumar Palanisamy updated an issue Jenkins / JENKINS-60350 Recover Deleted Dashboard view in jenkins main page Change By: Senthilkumar Palanisamy Team,Please can you help me here:We have removed Dashboard view on our Jenkins Main page. Is it possible to recover accidentally removed views in JenkinsOur Jenkins Version 2.190.2 ThanksSenthil Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203367.1575372289000.7.1575372362197%40Atlassian.JIRA.
[JIRA] (JENKINS-59704) NoSuchMethodError occurs when promoting a build using parametrized trigger
Title: Message Title Oleg Nenashev resolved as Fixed It should be fixed in 3.5: https://github.com/jenkinsci/promoted-builds-plugin/releases/tag/promoted-builds-3.5 . I tested it manually and it looks to work fine, but more feedback would be appreciated Jenkins / JENKINS-59704 NoSuchMethodError occurs when promoting a build using parametrized trigger Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Released As: Promoted Builds 3.5 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59953) Job's Promotion Status generating invalid links
Title: Message Title Oleg Nenashev commented on JENKINS-59953 Re: Job's Promotion Status generating invalid links Please try 3.5. https://github.com/jenkinsci/promoted-builds-plugin/releases/tag/promoted-builds-3.5 . It should have fixed the behavior on all Jenkins versions, but I am not 100% sure Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202757.1572189054000.11149.1575375240166%40Atlassian.JIRA.
[JIRA] (JENKINS-54285) Changeset not reflective of Pull Request
Title: Message Title
Anna Tikhonova commented on JENKINS-54285
Re: Changeset not reflective of Pull Request
I wanted to use 'when { changeset ... }' to test changes in my monorepo as well (I'm using Bitbucket branch source, Bitbucket Server) and then came to find this... Why don't we have pull request changes? Webhook payload has the destination branch, so why not have the behaviour the author suggested in the description?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194931.1540594429000.11154.1575380460597%40Atlassian.JIRA.
[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49514 No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax Change By: Karl Wirth Summary: No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188416.1518459572000.11159.1575380940261%40Atlassian.JIRA.
[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49514 No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188416.1518459572000.11161.1575380940297%40Atlassian.JIRA.
[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49514 No builds triggered using p4 plugin polling with view filters - Use Perforce Syntax Change By: Karl Wirth Labels: P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188416.1518459572000.11163.1575381001059%40Atlassian.JIRA.
[JIRA] (JENKINS-45856) support view Mask filters with wildcards
Title: Message Title Karl Wirth commented on JENKINS-45856 Re: support view Mask filters with wildcards ++Usage case - Need to exclude changes that include *.inf files. For example not trigger the build if it matches: //depot/MyProject/inf Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184068.150126216.11167.1575381420909%40Atlassian.JIRA.
[JIRA] (JENKINS-45856) support view Mask filters with wildcards
Title: Message Title
Karl Wirth edited a comment on JENKINS-45856
Re: support view Mask filters with wildcards
++Usage case - Need to exclude changes that include *.inf files. For example not trigger the build if it matches:{code:java}//depot/MyProject/inf{code} *NOTE FOR DEVELOPERS: Is this now possible with the new map code in P4JAVA?*
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184068.150126216.11174.1575381900299%40Atlassian.JIRA.
[JIRA] (JENKINS-45856) support view Mask filters with wildcards
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-45856 support view Mask filters with wildcards Change By: Karl Wirth Labels: P4_A P4_BACKLOG Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184068.150126216.11181.1575381960373%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh updated an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Change By: Daljit singh Attachment: 1.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.203136.157375217.11188.1575382263110%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh updated an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Change By: Daljit singh Attachment: 3.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.203136.157375217.11192.1575382320329%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh updated an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Change By: Daljit singh Attachment: 2.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.203136.157375217.11190.1575382320287%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh updated an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Change By: Daljit singh Attachment: image-2019-12-03-19-42-54-249.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.203136.157375217.11196.1575382380497%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh updated an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Change By: Daljit singh Attachment: image-2019-12-03-19-42-11-938.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.203136.157375217.11194.1575382380468%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh updated an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Change By: Daljit singh Attachment: image-2019-12-03-19-43-17-429.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.203136.157375217.11198.1575382440139%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh updated an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Change By: Daljit singh Attachment: image-2019-12-03-19-44-08-344.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.203136.157375217.11200.1575382500574%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh updated an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Change By: Daljit singh Attachment: image-2019-12-03-19-44-59-440.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.203136.157375217.11202.1575382560179%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh updated an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Change By: Daljit singh Attachment: image-2019-12-03-19-46-03-659.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.203136.157375217.11204.1575382620237%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh updated an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Change By: Daljit singh Attachment: image-2019-12-03-19-46-41-526.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.203136.157375217.11206.1575382620263%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh updated an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Change By: Daljit singh Attachment: OKTA_1.jpg Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203136.157375217.11208.1575382680410%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh commented on JENKINS-60176 Re: Groups are not working | SAML | Authorization Matrix I have tried all the ways as per my documentations Jenkins: SAML Settings ++ SettingsRole based Created a Global Role Now Assigned Global role to an OKTA Group the same name group exist in OKTA Okta setting as per Okta portal: Test User who can access OKTA application Group settings in Okta But after doing this all the groups are not resolving by Jenkins as the issue remains on the Jenkins Input based Job but If I write the Email address in Jenkins file it works perfectly fine as authentication with OKTA is happening perfectly fine but the Group based strategy is not working as the SAML inspect response in Browser is not showing the group payload is not coming as well. followed later this document : https://dev.to/setevoy/jenkins-saml-authentication-via-okta-and-users-groups-2koh and in last slide it's not showing the icon in front of DevOps Group name. Not Sure. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203136.157375217.11210.1575382980344%40Atlassian.JIRA.
[JIRA] (JENKINS-60351) can not disable the retries of Util.delete
Title: Message Title James Nord created an issue Jenkins / JENKINS-60351 can not disable the retries of Util.delete Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-12-03 14:23 Priority: Minor Reporter: James Nord https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/hudson/Util.java#L1581-L1596 is confused. The properties is for "retries" which you should be able to disable with a count of zero. but you can not. but the comment implies it is just for the number of tries (not retries). However the code calls PathRemover.newFilteredRobustRemover(pathChecker, DELETION_MAX - 1, GC_AFTER_FAILED_DELETE, WAIT_BETWEEN_DELETION_RETRIES); which ends up in https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/jenkins/util/io/PathRemover.java#L63-L65 which is using a max retries. However if you run a test with the system property set to one. then you do get one retry not one try. -DargLine=-Dhudson.Util.maxFileDeletionRetries=1 Unable to delete 'C:\Users\IEUser\Desktop\oc-server\target\tmp\j h6725733765603761727'. Tried 2 time (of a maximum of 2) waiting 0.1 sec between attempts. so the property does seem to be acting as a retry despite the code comment but you can not set it to zero one because... static int DELETION_MAX = Math.max(1, SystemProperties.getInteger(Util.class.getName() + ".maxFileDeletionRetries", 3));
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Baptiste Mathus updated JENKINS-57304 Jenkins / JENKINS-57304 Multiple "idle" entries on Build Executor Status for non-existant executors Change By: Baptiste Mathus Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.11214.1575383101518%40Atlassian.JIRA.
[JIRA] (JENKINS-60351) can not disable the retries of Util.delete
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-60351
can not disable the retries of Util.delete
Change By:
James Nord
[https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/hudson/Util.java#L1581-L1596] is confused. The properties is for "retries" which you should be able to disable with a count of zero. but you can not. but the comment implies it is just for the number of tries (not retries).However the code calls [{{PathRemover.newFilteredRobustRemover(pathChecker, DELETION_MAX - 1, GC_AFTER_FAILED_DELETE, WAIT_BETWEEN_DELETION_RETRIES);}}| [https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/hudson/Util.java #L1635]]which ends up in [https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/jenkins/util/io/PathRemover.java#L63-L65] which is using a max retries. However if you run a test with the system property set to one. then you do get one retry not one try. -DargLine=-Dhudson.Util.maxFileDeletionRetries=1 {noformat} Unable to delete 'C:\Users\IEUser\Desktop\oc-server\target\tmp\j h6725733765603761727'. Tried 2 time (of a maximum of 2) waiting 0.1 sec between attempts. {noformat} so the property does seem to be acting as a retry despite the code comment but you can not set it to zero one because... {noformat}static int DELETION_MAX = Math.max(1, SystemProperties.getInteger(Util.class.getName() + ".maxFileDeletionRetries", 3)); {noformat} and the [PathRemover|[https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/jenkins/util/io/PathRemover.java#L64]]..{noformat}return new PathRemover(new PausingGCRetryStrategy(Math.max(maxRetries, 1), gcAfterFailedRemove, waitBetweenRetries), pathChecker);{noformat}
Add Comment
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Ihor Tymoshenko commented on JENKINS-59503 Re: Plugin does not save settings It is still producing for the `Notify Build Start` option. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202124.1569316263000.11235.1575383288155%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-57304 Multiple "idle" entries on Build Executor Status for non-existant executors Change By: Baptiste Mathus Released As: (towards) 2.208 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.11238.1575383288962%40Atlassian.JIRA.
[JIRA] (JENKINS-60351) can not disable the retries of Util.delete
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-60351
can not disable the retries of Util.delete
Change By:
James Nord
[https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/hudson/Util.java#L1581-L1596] is confused. The properties is for "retries" which you should be able to disable with a count of zero. but you can not. but the comment implies it is just for the number of tries (not retries).However the code calls [{{PathRemover.newFilteredRobustRemover(pathChecker, DELETION_MAX - 1, GC_AFTER_FAILED_DELETE, WAIT_BETWEEN_DELETION_RETRIES);}}|#L1635]] which ends up in [https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/jenkins/util/io/PathRemover.java#L63-L65] which is using a max retries.However if you run a test with the system property set to one. then you do get one retry not one try.-DargLine=-Dhudson.Util.maxFileDeletionRetries=1 {noformat} Unable to delete 'C:\Users\IEUser\Desktop\oc-server\target\tmp\j h6725733765603761727'. Tried 2 time (of a maximum of 2) waiting 0.1 sec between attempts. {noformat}so the property does seem to be acting as a retry despite the code comment but you can not set it to zero one because...{noformat}static int DELETION_MAX = Math.max(1, SystemProperties.getInteger(Util.class.getName() + ".maxFileDeletionRetries", 3)); {noformat} and the [PathRemover| [https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/java/jenkins/util/io/PathRemover.java #L64]].. {noformat}return new PathRemover(new PausingGCRetryStrategy(Math.max(maxRetries, 1), gcAfterFailedRemove, waitBetweenRetries), pathChecker);{noformat} which means it will always retry once, which is a PITA when trying to some timing bugs.
Add Comment
[JIRA] (JENKINS-60351) can not disable the retries of Util.delete
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-60351 can not disable the retries of Util.delete Change By: James Nord Assignee: James Nord Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203368.1575383029000.11253.1575384060208%40Atlassian.JIRA.
[JIRA] (JENKINS-60351) can not disable the retries of Util.delete
Title: Message Title James Nord started work on JENKINS-60351 Change By: James Nord 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.203368.1575383029000.11254.1575384060310%40Atlassian.JIRA.
[JIRA] (JENKINS-60352) Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Viv Cheolu created an issue Jenkins / JENKINS-60352 Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1 Issue Type: Bug Assignee: John Westcott Components: ansible-tower-plugin Created: 2019-12-03 14:50 Environment: CloudBees Jenkins : 1.11.22 Managed Master Version: 2.176.4 Priority: Critical Reporter: Viv Cheolu Jenkins job is not passing credentials to job template in Tower for Ansible tower version 3.6.1. This used to work with Tower version 2.9 Add Comment
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-60176 Re: Groups are not working | SAML | Authorization Matrix This Jira is not a support site if you have questions please use the google groups, see https://wiki.jenkins.io/display/JENKINS/How+to+report+an+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.203136.157375217.11258.1575385320117%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Alessio Moscatello commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Liam Newman your comment you are saing to set a JVM argument. I've added it to my Jenkins instance, and from the Jenkins script console I see that JAVA_OPTS variable is being populated like this: JAVA_OPTS=-Dorg.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true This is sufficient to verify that the script splitting is enabled? Because I haven't seen any differences (my declarative pipeline is still failing). Another question you are talking about version 1.4 of which plugin? BR, Alessio Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.11260.1575385863755%40Atlassian.JIRA.
[JIRA] (JENKINS-60353) Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404
Title: Message Title Vladimir Kuklin created an issue Jenkins / JENKINS-60353 Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404 Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-12-03 15:25 Priority: Minor Reporter: Vladimir Kuklin How to reproduce: Use multibranch-pipeline workflow Create a branch, develop it and make it nonmergable into the target branch Push the branch and open the Pull Request in GH Find out that the branch is not-mergeable Fix the code, push the newer revision # Add Comment
[JIRA] (JENKINS-60353) Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404
Title: Message Title Vladimir Kuklin updated an issue Jenkins / JENKINS-60353 Non-mergable Pull-request Contents Get into GH Cache with False-Positive 404 Change By: Vladimir Kuklin How to reproduce:Use multibranch-pipeline workflow with merge PR strategy # Create a branch, develop it and make it nonmergable into the target branch # Push the branch and open the Pull Request in GH # Find out that the branch is not-mergeable # Fix the code, push the newer revision Expected Result:The pipeline is triggered.Actual Result: # On step #2 Jenkins gets the 404 in the request to ...refs/pull//merge/contents # The 404 is cached # On the step 4 it does not query GH but rather returns a cryptic error of 'Jenkins File not found' although it does not check for it at allProposed solution: do not check for the contents of the "refs.//merge" URL if the PR is not mergable.Versions:Jenkins 2.190.1GitHub Branch Source Plugin 2.5.8+ (some irrelevant local patches) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Brian J Murrell commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Can we please have this re-opened. I can confirm it's still happening here on 1.19.0 also. This together with stage-view being pretty crippled means finding logs of currently-running pipelines (i.e. in Pipeline Steps) is pretty cumbersome even for a Jenkins pro. Pretty much unusable for casual users with it's lack of collapsibility, etc. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.11336.1575387421086%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title Raphael Pionke commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching i submitted a pull request, which fixes the problem: https://github.com/jenkinsci/ec2-plugin/pull/418 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.11366.1575389520295%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title tapvir virk commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching Raphael Pionke - Can you give me the hpi file to test on my jenkins instance? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.11373.1575390180717%40Atlassian.JIRA.
[JIRA] (JENKINS-60334) The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing
Title: Message Title Ted commented on JENKINS-60334 Re: The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:3.6 is missing If you are not a developer and you just want to try it out, please use the update center to download https://jenkins.io/doc/book/managing/plugins/ The simplest and most common way of installing plugins is through the Manage Jenkins > Manage Plugins view, available to administrators of a Jenkins environment. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203346.1575115143000.11375.1575390420238%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title Raphael Pionke started work on JENKINS-59633 Change By: Raphael Pionke 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.202315.157004916.11383.1575390721255%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title Raphael Pionke commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching tapvir virk you can find the hpi file here: https://ci.jenkins.io/job/Plugins/job/ec2-plugin/job/PR-418/1/artifact/org/jenkins-ci/plugins/ec2/1.47-rc1073.62885629c57c/ec2-1.47-rc1073.62885629c57c.hpi Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.11378.1575390720967%40Atlassian.JIRA.
[JIRA] (JENKINS-60311) contentReplace does not appear in the Snippet Generator
Title: Message Title Florian Patzl commented on JENKINS-60311 Re: contentReplace does not appear in the Snippet Generator I experienced the same issues today and had to downgrade to 1.0.10. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203307.1574923665000.11399.1575390901005%40Atlassian.JIRA.
[JIRA] (JENKINS-60199) jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login
Title: Message Title Pierre-Yves Bigourdan commented on JENKINS-60199 Re: jenkins 2.205 behind reverse proxy redirects to 127.0.0.1 after login Adding ProxyPreserveHost On to our httpd configuration did solve the problem for us as well. Thanks for the tip! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203169.1574080196000.11396.1575390900845%40Atlassian.JIRA.
[JIRA] (JENKINS-39287) Ability to select from existing credentials list at runtime
Title: Message Title Drew Waranis commented on JENKINS-39287 Re: Ability to select from existing credentials list at runtime Unfortunately, therein lies the rub: We already have the Jenkins Perforce Credentials created and can pick between them at DSL job generation time, but now we have a set of jobs that can use either of two Jenkins P4 Credentials at job runtime based on the location of the build node running them. So we need either: The likely simpler way is to have an option for the P4 Plugin use the P4PORT, P4SERVER, and P4TRUST variables set in the job runner's Jenkins Node Properties. Or, a more complicated option is the ability to map Jenkins Node Labels to Jenkins P4 Credentials and then be able to pass that mapping to the P4 Plugin instead of a Jenkins P4 Credential. Thank you! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175718.1477521864000.11428.1575390968439%40Atlassian.JIRA.
[JIRA] (JENKINS-38316) Entering, then cancelling, quiet mode causes builds to hang
Title: Message Title Jesse Glick reopened an issue (incorrect resolution) Jenkins / JENKINS-38316 Entering, then cancelling, quiet mode causes builds to hang Change By: Jesse Glick 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/
[JIRA] (JENKINS-38316) Entering, then cancelling, quiet mode causes builds to hang
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-38316 Entering, then cancelling, quiet mode causes builds to hang Change By: Jesse Glick Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174488.147422949.11456.1575390969080%40Atlassian.JIRA.
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title tapvir virk commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching Raphael Pionke Fix is working for me. 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.202315.157004916.11458.1575391800185%40Atlassian.JIRA.
[JIRA] (JENKINS-60354) Updated pipeline build step does not work with retry
Title: Message Title
Jonathan B created an issue
Jenkins / JENKINS-60354
Updated pipeline build step does not work with retry
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline-build-step-plugin, workflow-basic-steps-plugin
Created:
2019-12-03 16:54
Priority:
Minor
Reporter:
Jonathan B
We just upgraded pipeline-build-step from 2.9 to 2.10. The following no longer retries:
pipeline {
agent any
stages {
stage('bug') {
steps {
retry(3) {
echo 'in the retry loop'
//throw new Exception('failing in retry loop') // This runs (when uncommented) several times before the pipeline exits with failure.
build(job: 'some/job/that/fails', propagate: true) // This only runs once before the pipeline exits with failure.
}
}
}
}
}
When the sub-build fails, the retry loop exits immediately and does not retry. This didn't used to happen. When raising an error in another way (e.g. the `throw new Exception`, commented out, in the code above), `retry` works as expected.
[JIRA] (JENKINS-60355) Updating openshift-synch-configuration from jenkins-cli does not result in watching newly assigned namespaces
Title: Message Title Daniel Horn created an issue Jenkins / JENKINS-60355 Updating openshift-synch-configuration from jenkins-cli does not result in watching newly assigned namespaces Issue Type: Improvement Assignee: Gabe Montero Attachments: image-2019-12-03-17-30-29-372.png, image-2019-12-03-17-36-07-360.png Components: cli, openshift-sync-plugin Created: 2019-12-03 16:58 Priority: Minor Reporter: Daniel Horn Hi Support Team, we are currently trying to set up a containerized Jenkins-Soulution in our company based n OpenShift. For this, we want to onboard new OpenShuft-Projects via self-service and needed a solution to update the monitored namespaces without human intervention. On our research we found, that it is possible to update the OpenShift-Synch values by jenkins-cli and developed a solution. The update does result in the values being visible by the Configuration-Screen, but created BuildConfigurations do not appear in the Project-Dashboard. Configuration on a freshly deployed Jenkins in namespace dhorn-jenkins-test Content of newConfig.yaml - after reading the whole configuration, we have seen, that the menitored namespaces are listed under unclassified -> globalPluginConfiguration -> namespace --- unclassified: globalPluginConfiguration: namespace: dhorn-jenkins-test dhorn-automated
[JIRA] (JENKINS-60355) Updating openshift-sync-configuration from jenkins-cli does not result in watching newly assigned namespaces
Title: Message Title Daniel Horn updated an issue Jenkins / JENKINS-60355 Updating openshift-sync-configuration from jenkins-cli does not result in watching newly assigned namespaces Change By: Daniel Horn Summary: Updating openshift- synch sync -configuration from jenkins-cli does not result in watching newly assigned namespaces Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203372.1575392303000.11466.1575392340355%40Atlassian.JIRA.
[JIRA] (JENKINS-60354) Updated pipeline build step does not work with retry
Title: Message Title
Jonathan B updated an issue
Jenkins / JENKINS-60354
Updated pipeline build step does not work with retry
Change By:
Jonathan B
We just upgraded pipeline-build-step from 2.9 to 2.10. The following no longer retries:{code}pipeline {agent anystages {stage('bug') {steps {retry(3) {echo 'in the retry loop'//throw new Exception('failing in retry loop') // This runs (when uncommented) several times before the pipeline exits with failure.build(job: 'some/job/that/fails', propagate: true) // This only runs once before the pipeline exits with failure.}}}}}{code}When the sub-build fails, the retry loop exits immediately and does not retry. This didn't used to happen. When raising an error in another way (e.g. the `throw new Exception`, commented out, in the code above), `retry` works as expected. A workaround is to try/catch the `build()` call and, in catch, `throw new Exception(...)`. If the caught exception is directly re-thrown, we see the same behavior where `retry` does not loop.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60213 P4 environment variables non-reentrant Change By: Karl Wirth Labels: P4_A P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.11469.1575392820137%40Atlassian.JIRA.
[JIRA] (JENKINS-60213) P4 environment variables non-reentrant
Title: Message Title
Karl Wirth commented on JENKINS-60213
Re: P4 environment variables non-reentrant
Verified still sporadically broken in 1.10.7. P4_CLIENT is wrong. The full expansion for me is correct and matches the rest of the job:
P4: saving built changes.
Found last change 2240 on syncID jenkins-NODE_NAME-JENKINS-60213-ConcurrentVariables-EXECUTOR_NUMBER
... p4 login -s
... p4 client -o jenkins-master-JENKINS-60213-ConcurrentVariables-3
... p4 info
... p4 info
... p4 client -o jenkins-master-JENKINS-60213-ConcurrentVariables-3
... p4 login -s
... p4 client -o jenkins-master-JENKINS-60213-ConcurrentVariables-3
... p4 info
... p4 info
... p4 client -o jenkins-master-JENKINS-60213-ConcurrentVariables-3
... done
[JENKINS-60213-ConcurrentVariables@2] $ /bin/bash /tmp/jenkins6561639748343680378.sh
==
WORKSPACE:/var/lib/jenkins/workspace/JENKINS-60213-ConcurrentVariables@2
P4_CLIENT:jenkins-master-JENKINS-60213-ConcurrentVariables-4
EXECUTOR NUMBER: 3
CLIENT_FROM_VARS: jenkins-master-JENKINS-60213-ConcurrentVariables-3
==
Finished: SUCCESS
Note for dev: In the above ${P4_CLIENT} is wrong but expansion is correct.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this m
[JIRA] (JENKINS-60213) P4CLIENT environment variable non-reentrant
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60213 P4CLIENT environment variable non-reentrant Change By: Karl Wirth Summary: P4 P4CLIENT environment variables variable non-reentrant Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203186.1574180065000.11473.1575393540572%40Atlassian.JIRA.
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Karl Wirth commented on JENKINS-60142 Re: ConnectionHelper.java constructors call connectionRetry() Confirmed. One invocation of the above script against a freestyle job that had 8 successful executions caused 24 P4 commands to be run: 2019/12/03 17:32:31 pid 1868 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1869 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1870 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1871 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1872 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1873 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1874 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1875 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1876 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1877 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1878 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1879 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1880 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1881 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1882 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1883 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1884 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1885 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1886 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1887 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1888 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1889 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1890 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1891 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' $ grep user- tmpa.txt | wc -l 24 For a job with 4 successful runs I saw 11 commands kicked off: 2019/12/03 17:40:17 pid 2509 super@__
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Karl Wirth commented on JENKINS-60142 Re: ConnectionHelper.java constructors call connectionRetry() Confirmed. One invocation of the above script against a freestyle job that had 8 successful executions caused 24 P4 commands to be run: 2019/12/03 17:32:31 pid 1868 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1869 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1870 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1871 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1872 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1873 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1874 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1875 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1876 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1877 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1878 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1879 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1880 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1881 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1882 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1883 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1884 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1885 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1886 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1887 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1888 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1889 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1890 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1891 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' $ grep user- tmpa.txt | wc -l 24 For a job with 4 successful runs I saw 11 commands kicked off: 2019/12/03 17:40:17 pid 2509 super@__
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title
Karl Wirth edited a comment on JENKINS-60142
Re: ConnectionHelper.java constructors call connectionRetry()
Confirmed. One invocation of the above script against a freestyle job that had 8 successful executions caused 24 P4 commands to be run:{code:java} 2019/12/03 17:32:31 pid 1868 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1869 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1870 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1871 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1872 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1873 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1874 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1875 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1876 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1877 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1878 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1879 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1880 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1881 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1882 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1883 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1884 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1885 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1886 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1887 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1888 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1889 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1890 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1891 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s'$ grep user- tmpa.txt | wc -l24{code}For a job with 4 successful runs I saw 11 commands kicked off:{code:java} 2019/12/03 17:40:17 pid 2509 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:40:17 pid 2510 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:40:48 pid 2512 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:40:48 pid 2513 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:40:48 pid 2514 super@_CLIENT_UNSET
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title
Karl Wirth updated an issue
Jenkins / JENKINS-60142
ConnectionHelper.java constructors call connectionRetry()
Change By:
Karl Wirth
Comment:
Confirmed. One invocation of the above script against a freestyle job that had 8 successful executions caused 24 P4 commands to be run:{code:java} 2019/12/03 17:32:31 pid 1868 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1869 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1870 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1871 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1872 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1873 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1874 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1875 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1876 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1877 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1878 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1879 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1880 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1881 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1882 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1883 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:31 pid 1884 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:31 pid 1885 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1886 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1887 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1888 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1889 nouser@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-info' 2019/12/03 17:32:32 pid 1890 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s' 2019/12/03 17:32:32 pid 1891 super@_CLIENT_UNSET_ 127.0.0.1 [jenkins.p4-plugin/1.10.7/Linux] 'user-login -s'$ grep user- tmpa.txt | wc -l24{code}For a job with 4 successful runs I saw 11 commands kicked off:{code:java} 2019/12/03 17:40:17 pid 2509 super@_CLIENT_UNSET_ 127.0.0.1 [je
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-60142 ConnectionHelper.java constructors call connectionRetry() Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203003.1573562093000.11491.1575395460398%40Atlassian.JIRA.
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60142 ConnectionHelper.java constructors call connectionRetry() Change By: Karl Wirth Labels: P4_SUPPORT P4_A Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203003.1573562093000.11488.1575395460355%40Atlassian.JIRA.
[JIRA] (JENKINS-60142) ConnectionHelper.java constructors call connectionRetry()
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60142 ConnectionHelper.java constructors call connectionRetry() Change By: Karl Wirth Labels: P4_A P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203003.1573562093000.11493.1575395460464%40Atlassian.JIRA.
[JIRA] (JENKINS-60356) Provide a link to the jacoco XML report
Title: Message Title Glauco Aquino created an issue Jenkins / JENKINS-60356 Provide a link to the jacoco XML report Issue Type: Improvement Assignee: Glauco Aquino Attachments: jacoco-xml-link.png Components: jacoco-plugin Created: 2019-12-03 17:55 Priority: Major Reporter: Glauco Aquino Portfolio metrics and other project quality-related automated tools could consume JaCoCo results directly from CI to collect coverage data even if they don't have access to the codebase or build environment. The JaCoCo XML report is the most suitable representation of the coverage data to be processed by an automated tool. Currently, jacoco-plugin provides a link for the aggregated jacoco.exec file, however, it cannot be processed without having a working local build. The goal here is to provide an additional link in the coverage results page to download the aggregated jacoco.xml file. Add Comment
[JIRA] (JENKINS-60356) Provide a link to the jacoco XML report
Title: Message Title Glauco Aquino started work on JENKINS-60356 Change By: Glauco Aquino 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.203373.1575395724000.11496.1575395820230%40Atlassian.JIRA.
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title
Karl Wirth edited a comment on JENKINS-60144
Re: Cant delete Jenkins job if the perforce template client has been deleted
Confirmed. The job is disabled but not deleted. An alternative workaround is to change the source control in the job to 'None' if this is a Freestyle job. Error seen when using *Above Reproduction Steps*:{code:java}A problem occurred while processing the request.Please check our bug tracker to see if a similar problem has already been reported.If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem.If you think this is a new issue, please file a new issue.When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins.The users list might be also useful in understanding what has happened.Stack traceAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to KarlsDesktop at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at org.jenkinsci.plugins.p4.PerforceScm.processWorkspaceBeforeDeletion(PerforceScm.java:830) at hudson.scm.SCM.processWorkspaceBeforeDeletion(SCM.java:245) at hudson.model.AbstractProject.performDelete(AbstractProject.java:358) at hudson.model.AbstractItem.delete(AbstractItem.java:775) at hudson.model.Job.delete(Job.java:675) at hudson.model.AbstractItem.doDoDelete(AbstractItem.java:645) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.ja
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title Karl Wirth commented on JENKINS-60144 Re: Cant delete Jenkins job if the perforce template client has been deleted Confirmed. The job is disabled but not deleted. An alternative workaround is to change the source control in the job to 'None' if this is a Freestyle job. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203005.1573570536000.11499.1575396060435%40Atlassian.JIRA.
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60144 Cant delete Jenkins job if the perforce template client has been deleted Change By: Karl Wirth Labels: P4_SUPPORT P4_A P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203005.1573570536000.11507.1575396120474%40Atlassian.JIRA.
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title
Karl Wirth edited a comment on JENKINS-60144
Re: Cant delete Jenkins job if the perforce template client has been deleted
Confirmed. The job is disabled but not deleted. An alternative workaround is to change the source control in the job to 'None' if this is a Freestyle job.Passing to developers. Error seen when using *Above Reproduction Steps*:{code:java}A problem occurred while processing the request.Please check our bug tracker to see if a similar problem has already been reported.If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem.If you think this is a new issue, please file a new issue.When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins.The users list might be also useful in understanding what has happened.Stack traceAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to KarlsDesktop at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at org.jenkinsci.plugins.p4.PerforceScm.processWorkspaceBeforeDeletion(PerforceScm.java:830) at hudson.scm.SCM.processWorkspaceBeforeDeletion(SCM.java:245) at hudson.model.AbstractProject.performDelete(AbstractProject.java:358) at hudson.model.AbstractItem.delete(AbstractItem.java:775) at hudson.model.Job.delete(Job.java:675) at hudson.model.AbstractItem.doDoDelete(AbstractItem.java:645) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFi
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-60144 Cant delete Jenkins job if the perforce template client has been deleted Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203005.1573570536000.11510.1575396180177%40Atlassian.JIRA.
[JIRA] (JENKINS-60356) Provide a link to the jacoco XML report
Title: Message Title Glauco Aquino updated JENKINS-60356 Jenkins / JENKINS-60356 Provide a link to the jacoco XML report Change By: Glauco Aquino 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.203373.1575395724000.11512.1575397920169%40Atlassian.JIRA.
[JIRA] (JENKINS-60356) Provide a link to the jacoco XML report
Title: Message Title
Glauco Aquino updated an issue
Jenkins / JENKINS-60356
Provide a link to the jacoco XML report
Change By:
Glauco Aquino
Portfolio metrics and other project quality-related automated tools could should consume JaCoCo results directly from CI to collect coverage data even if they don't have access to the codebase or build environment.The JaCoCo XML report is the most suitable representation of the coverage data to be processed by an automated tool.Currently, jacoco-plugin provides a link for to the aggregated {{jacoco.exec}} file, however, it cannot be processed without having a working local build.The goal here is to provide an additional link in the coverage results page to download the aggregated {{jacoco.xml}} file.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkin
[JIRA] (JENKINS-60350) Recover Deleted Dashboard view in jenkins main page
Title: Message Title Tobias Gruetzmacher commented on JENKINS-60350 Re: Recover Deleted Dashboard view in jenkins main page No, there is not. There are ways if you are prepared: You could use the https://plugins.jenkins.io/jobConfigHistory plugin You could restore from backup (You do have backups, right?) You could power off your system and try disaster recovery from the file system Anyways, since is not problem with the plugin itself, I'll close this issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203367.1575372289000.11515.1575398040671%40Atlassian.JIRA.
[JIRA] (JENKINS-60350) Recover Deleted Dashboard view in jenkins main page
Title: Message Title Tobias Gruetzmacher closed an issue as Not A Defect Jenkins / JENKINS-60350 Recover Deleted Dashboard view in jenkins main page Change By: Tobias Gruetzmacher 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.203367.1575372289000.11517.1575398040724%40Atlassian.JIRA.
[JIRA] (JENKINS-60357) Test may fail due to a different order of items in XML
Title: Message Title Context Shuffling created an issue Jenkins / JENKINS-60357 Test may fail due to a different order of items in XML Issue Type: Bug Assignee: Oliver Gondža Components: jenkins-test-harness Created: 2019-12-03 18:37 Priority: Minor Reporter: Context Shuffling Test in CopyOnWriteListTest depends on XStream to serialize and deserilize XML. The test assertions use hard-coded strings. However, the test may fail due to a different order of serialization results. Add Comment This
[JIRA] (JENKINS-60357) Test may fail due to a different order of items in XML
Title: Message Title Context Shuffling updated an issue Jenkins / JENKINS-60357 Test may fail due to a different order of items in XML Change By: Context Shuffling Test in [CopyOnWriteListTest | https://github.com/jenkinsci/jenkins/blob/ead55ac41d7a06cca09fcc59cbbf1bfc8c0f81f7/core/src/test/java/hudson/util/CopyOnWriteListTest.java] depends on XStream to serialize and deserilize XML. The test assertions use hard-coded strings. However, the test may fail due to a different order of serialization results. So tests may fail or pass without any modifications to source code. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203374.1575398244000.11521.15753983
[JIRA] (JENKINS-48828) Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2
Title: Message Title Timothy Tabing commented on JENKINS-48828 Re: Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2 Same issue here. Any update? I am running Jenkins: 2.181 Bitbucket Branch Source: 2.4.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187612.1515180451000.11523.1575402600660%40Atlassian.JIRA.
