[JIRA] (JENKINS-62019) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-62019 Re: Parameter is not interpreted in GIT Plugin - Branch Specifier This happens because tags are now supported at https://github.com/jenkinsci/git-plugin/blob/git-4.2.1/src/main/java/jenkins/plugins/git/GitSCMFileSystem.java#L262-L264. But when the GitSCMFileSystem is used, the branch specified is not expanded. If you remove that support, it works again. We can see that all those duplicates are about refs/tags and not refs/heads and the *lightweight checkout* (i.e. GitSCMFileSystem). If you try a parameterized refs/heads/ like for example refs/heads/$BRANCH you will notice that it does not work with either version 4.1.1 or 4.2.2. People are impact because now lightweight checkout supports tags, lightweight checkout is enabled by default, but the current implementation of the lightweight checkout does not expand variables. The workaround is to disable lightweight checkout if you use refs/tags. The fix is to support variable expansion of the branch specifier in GitSCMFileSystem. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205247.1584621644000.23497.1588908300129%40Atlassian.JIRA.
[JIRA] (JENKINS-62116) Organization Scan recreates hooks for all repository
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-62116 Re: Organization Scan recreates hooks for all repository I can actually still see this when disabling the "Manage Webhooks" under Manage Jenkins > Configure System > GitHub. The creation / deletion of webhooks in that case is still triggered. But fails with credentials issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206027.158820875.19748.1588210080133%40Atlassian.JIRA.
[JIRA] (JENKINS-62116) Organization Scan recreates hooks for all repository
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-62116
Organization Scan recreates hooks for all repository
Change By:
Allan BURDAJEWICZ
The organization scan recreates a hook for all repositories for which there is an item. We can see that A the WebHook of each repository is created / updated with events "[PULL_REQUEST, PUSH]" and then the webhook is *replaced* with events "[PULL_REQUEST, PUSH, REPOSITORY]". recreated: {code}Apr 30, 2020 12:42:08 AM FINE com.cloudbees.jenkins.GitHubWebHook$1 applyCalling registerHooks() for dse-team-apac/aburdajewicz/testOrg/public-repoApr 30, 2020 12:42:08 AM INFO org.jenkinsci.plugins.github.webhook.WebhookManager$1 runGitHub webhooks activated for job dse-team-apac/aburdajewicz/testOrg/public-repo with [GitHubRepositoryName[host=github.example.com,username=test-org,repository=public-repo]] (events: [PULL_REQUEST, PUSH])Apr 30, 2020 12:42:09 AM FINE org.jenkinsci.plugins.github.webhook.WebhookManager$3 applyNullSafeReplaced hook https://github.example.com/api/v3/repos/test-org/public-repo/hooks/32392 (events: [PULL_REQUEST, PUSH, REPOSITORY])Apr 30, 2020 12:42:09 AM FINE org.jenkinsci.plugins.github.webhook.WebhookManager$3 applyNullSafeCreated hook https://github.example.com/api/v3/repos/test-org/public-repo/hooks/32394 (events: [PULL_REQUEST, PUSH, REPOSITORY])Apr 30, 2020 12:42:10 AM FINE com.cloudbees.jenkins.GitHubWebHook$1 applyCalling registerHooks() for dse-team-apac/aburdajewicz/testOrg/private-repoApr 30, 2020 12:42:10 AM INFO org.jenkinsci.plugins.github.webhook.WebhookManager$1 runGitHub webhooks activated for job dse-team-apac/aburdajewicz/testOrg/private-repo with [GitHubRepositoryName[host=github.example.com,username=test-org,repository=private-repo]] (events: [PULL_REQUEST, PUSH])Apr 30, 2020 12:42:10 AM FINE org.jenkinsci.plugins.github.webhook.WebhookManager$3 applyNullSafeReplaced hook https://github.example.com/api/v3/repos/test-org/private-repo/hooks/32393 (events: [PULL_REQUEST, PUSH, REPOSITORY])Apr 30, 2020 12:42:10 AM FINE org.jenkinsci.plugins.github.webhook.WebhookManager$3 applyNullSafeCreated hook https://github.example.com/api/v3/repos/test-org/private-repo/hooks/32395 (events: [PULL_REQUEST, PUSH, REPOSITORY]){code}The GitHub audit log is then showing a "hook.destroy" / "hook.create" for each repository. API rate seems to be wasted and those recreation seem unnecessary. The differenc eof difference of events is odd too: {{[PULL_REQUEST, PUSH]}} vs {{[PULL_REQUEST, PUSH, REPOSITORY]}}. It seems related to how GitHub Plugin and GitHub Branch Source work together. h3 How to Reproduce* Configure a GitHub Server under **Manage Jenkins > Configure System > GitHub** and enabled "Manage Hooks"* Create a log recorder in **Manage Jenkins > System Logs** for {{org.jenkinsci.plugins.github.webhook.WebhookManager}}, {{com.cloudbees.jenkins.GitHubWebHook}}* Create an GitHub Organization item that match at least one repo* Run the Organization Scan a few timesCheck the log recorder and also the Audit
[JIRA] (JENKINS-62116) Organization Scan recreates hooks for all repository
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-62116 Organization Scan recreates hooks for all repository Issue Type: Bug Assignee: Kirill Merkushev Components: github-branch-source-plugin, github-plugin Created: 2020-04-30 01:05 Environment: github-branch-source:2.6.0 core:2.222.2 Priority: Major Reporter: Allan BURDAJEWICZ The organization scan recreates a hook for all repositories for which there is an item. We can see that A WebHook is created / updated with events "[PULL_REQUEST, PUSH]" and then the webhook is replaced with events "[PULL_REQUEST, PUSH, REPOSITORY]". Apr 30, 2020 12:42:08 AM FINE com.cloudbees.jenkins.GitHubWebHook$1 apply Calling registerHooks() for dse-team-apac/aburdajewicz/testOrg/public-repo Apr 30, 2020 12:42:08 AM INFO org.jenkinsci.plugins.github.webhook.WebhookManager$1 run GitHub webhooks activated for job dse-team-apac/aburdajewicz/testOrg/public-repo with [GitHubRepositoryName[host=github.example.com,username=test-org,repository=public-repo]] (events: [PULL_REQUEST, PUSH]) Apr 30, 2020 12:42:09 AM FINE org.jenkinsci.plugins.github.webhook.WebhookManager$3 applyNullSafe Replaced hook https://github.example.com/api/v3/repos/test-org/public-repo/hooks/32392 (events: [PULL_REQUEST, PUSH, REPOSITORY]) Apr 30, 2020 12:42:09 AM FINE org.jenkinsci.plugins.github.webhook.WebhookManager$3 applyNullSafe Created hook https://github.example.com/api/v3/repos/test-org/public-repo/hooks/32394 (events: [PULL_REQUEST, PUSH, REPOSITORY]) Apr 30, 2020 12:42:10 AM FINE com.cloudbees.jenkins.GitHubWebHook$1 apply Calling registerHooks() for
[JIRA] (JENKINS-59340) Pipeline hangs when Agent pod is Terminated
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-59340 Re: Pipeline hangs when Agent pod is Terminated Another way to reproduce this issue is by using an activeDeadlineSeconds to kill the pod after some time. The pod would fail with DeadlineExceeded but will not be deleted. The pipeline will hang until a manual operation is taken. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201891.1568335765000.8532.1586402580216%40Atlassian.JIRA.
[JIRA] (JENKINS-61096) Blue Ocean UI never allows you to have more than about 10 tabs open at a time
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-61096 Re: Blue Ocean UI never allows you to have more than about 10 tabs open at a time Can’t reproduce this. Using Chrome on OSX. In what browser did you test Alex Taylor and with what versions of core and plugins ? BO depends on plugins such as the SSE Gateway / Pub Sub light plugin that had known memory leak issues that have been fixed recently: https://issues.jenkins-ci.org/browse/JENKINS-51057 https://issues.jenkins-ci.org/browse/JENKINS-58684 https://issues.jenkins-ci.org/browse/JENKINS-59291 So I would suggests to upgrade to the latest to see if that is still an issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204589.1581688838000.7329.1586237280230%40Atlassian.JIRA.
[JIRA] (JENKINS-61815) Display per-component size estimation
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-61815 Display per-component size estimation Change By: Allan BURDAJEWICZ Summary: Display Support Core per-component size estimation Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205664.1586150452000.6692.1586150520305%40Atlassian.JIRA.
[JIRA] (JENKINS-61815) Display Support Core per-component size estimation
Title: Message Title Allan BURDAJEWICZ assigned an issue to Unassigned Jenkins / JENKINS-61815 Display Support Core per-component size estimation Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205664.1586150452000.6691.1586150520292%40Atlassian.JIRA.
[JIRA] (JENKINS-61815) Display Support Core per-component size estimation
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-61815 Display Support Core per-component size estimation Change By: Allan BURDAJEWICZ Summary: Display Support Bundle Core per - component size estimation Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205664.1586150452000.6689.1586150520263%40Atlassian.JIRA.
[JIRA] (JENKINS-61815) Display Support Bundle per component size estimation
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-61815 Display Support Bundle per component size estimation Issue Type: New Feature Assignee: Emilio Escobar Components: support-core-plugin Created: 2020-04-06 05:20 Priority: Major Reporter: Allan BURDAJEWICZ The idea would be to display the estimated size per component as well as the total estimated size of a support bundle in the Support Action page. For example next to each component checkbox in the UI. Add Comment
[JIRA] (JENKINS-60010) GCLogs are collected twice
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60010 Re: GCLogs are collected twice We should probably prevent the Master Log Recorders to include GC Logs. The method used to retrieve the GC Logs files from the "Garbage Collection Logs" component could be made reusable, so that the "Master Log Recorders" component can find out if there are any. Also the "Master Log Recorders" has an higher ordinal and will happen first. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202827.1572567497000.12409.1585093260049%40Atlassian.JIRA.
[JIRA] (JENKINS-60009) GCLogs component should be made Java 11 compatible
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60009 Jenkins / JENKINS-60009 GCLogs component should be made Java 11 compatible Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202826.1572566602000.12407.1585092780180%40Atlassian.JIRA.
[JIRA] (JENKINS-60009) GCLogs component should be made Java 11 compatible
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60009 Jenkins / JENKINS-60009 GCLogs component should be made Java 11 compatible Change By: Allan BURDAJEWICZ Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202826.1572566602000.12408.1585092780290%40Atlassian.JIRA.
[JIRA] (JENKINS-61653) Cannot "Add" credentials when configuring some components at the global level
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-61653 Re: Cannot "Add" credentials when configuring some components at the global level I suppose that using repeatableHetero could be a workaround. But there is a bug here, in either core or credentials-plugin. Also I wonder if the issue https://issues.jenkins-ci.org/browse/JENKINS-39324 does capture the problem ? it does look really specific though. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205383.1585016714000.11606.1585016940042%40Atlassian.JIRA.
[JIRA] (JENKINS-61653) Cannot "Add" credentials when configuring some components at the global level
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-61653
Cannot "Add" credentials when configuring some components at the global level
Change By:
Allan BURDAJEWICZ
h3. IssueIt is not possible to add credentials when configuring for example a shared library from the global configuration {{Manage Jenkins > Configure System > Global Pipeline Libraries}} . This is not only impacting Pipeline Shared Library. Other plugins that accepts credentials in the Jenkins global configuration seem to be impacted too.h3. Analysis Digged Digging a bit into this and hopefully , I could narrow down the problem . This : the issue seems to happenswhen using happen when the component that hold the credentials dropdown is created from an {{f:repeatableProperty}} or {{f:repeatable}} to allow adding configuration . It only happens on newly added configuration in the UI: for example in the gloabl global config, you must first add a Shared Library and then the component Shared Library item that you added has a credentials dropdown. h3. Example of plugins affected:* [JIRA plugin|https://github.com/jenkinsci/jira-plugin/blob/jira-3.0.12/src/main/resources/hudson/plugins/jira/JiraGlobalConfiguration/config.jelly#L5]* [TFS Plugin|https://github.com/jenkinsci/tfs-plugin/blob/tfs-5.157.0/tfs/src/main/resources/hudson/plugins/tfs/TeamPluginGlobalConfig/config.groovy#L10]* [Pipeline Shared Library|https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/workflow-cps-global-lib-2.15/src/main/resources/org/jenkinsci/plugins/workflow/libs/GlobalLibraries/config.jelly#L34]* [GitLab plugin|https://github.com/jenkinsci/gitlab-plugin/blob/gitlab-plugin-1.5.17/src/main/resources/com/dabsquared/gitlabjenkins/connection/GitLabConnectionConfig/config.jelly]Apparently it does not affect plugins that use the {{repeatableHeteroProperty}}:* [Bitbucket Branch Source plugin|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/cloudbees-bitbucket-branch-source-2.7.0/src/main/resources/com/cloudbees/jenkins/plugins/bitbucket/endpoints/BitbucketEndpointConfiguration/config.jelly#L6-L12]* [GitLab Branch Source plugin|https://github.com/jenkinsci/gitlab-branch-source-plugin/blob/gitlab-branch-source-1.4.4/src/main/resources/io/jenkins/plugins/gitlabserverconfig/servers/GitLabServers/config.groovy#L10]* [GitHub plugin|https://github.com/jenkinsci/github-plugin/blob/v1.29.5/src/main/resources/org/jenkinsci/plugins/github/config/GitHubPluginConfig/config.groovy#L12]h3. How to reproduce* Start a new Jenkins instance with no global credentials.* Go to {{Manage Jenkins > Configure System > Global Pipeline Libraries}}* Add a library* Use a "Modern SCM" and either "Git" or "GitHub"* Try to add credentials clicking on Add, it does not work..h3. Workarounds1. Create credentials from {{Manage Jenkins > Manage Credentials}} and then the credentials will be selectable in the global configuration.2. Partially fill the information for the shared library (without the credentials), save the configuration,
[JIRA] (JENKINS-61653) Cannot "Add" credentials when configuring some components at the global level
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-61653
Cannot "Add" credentials when configuring some components at the global level
Change By:
Allan BURDAJEWICZ
h3. IssueIt is not possible to add credentials when configuring for example a shared library from the global configuration {{Manage Jenkins > Configure System > Global Pipeline Libraries}} This is not only impacting Pipeline Shared Library. Other plugins that accepts credentials in the Jenkins global configuration seem to be impacted too.h3. Environmentsh3. AnalysisDigged a bit into this and hopefully could narrow down the problem. This issue seems to happenswhen using {{f:repeatableProperty}} or {{f:repeatable}} to allow adding configuration. It only happens on newly added configuration in the UI: for example in the gloabl config, you must first add a Shared Library and the component you added has a credentials dropdown. h3. Example of plugins affected:* [JIRA plugin|https://github.com/jenkinsci/jira-plugin/blob/jira-3.0.12/src/main/resources/hudson/plugins/jira/JiraGlobalConfiguration/config.jelly#L5]* [TFS Plugin|https://github.com/jenkinsci/tfs-plugin/blob/tfs-5.157.0/tfs/src/main/resources/hudson/plugins/tfs/TeamPluginGlobalConfig/config.groovy#L10]* [Pipeline Shared Library|https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/workflow-cps-global-lib-2.15/src/main/resources/org/jenkinsci/plugins/workflow/libs/GlobalLibraries/config.jelly#L34]* [GitLab plugin|https://github.com/jenkinsci/gitlab-plugin/blob/gitlab-plugin-1.5.17/src/main/resources/com/dabsquared/gitlabjenkins/connection/GitLabConnectionConfig/config.jelly]Apparently it does not affect plugins that use the {{repeatableHeteroProperty}}:* [Bitbucket Branch Source plugin|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/cloudbees-bitbucket-branch-source-2.7.0/src/main/resources/com/cloudbees/jenkins/plugins/bitbucket/endpoints/BitbucketEndpointConfiguration/config.jelly#L6-L12]* [GitLab Branch Source plugin|https://github.com/jenkinsci/gitlab-branch-source-plugin/blob/gitlab-branch-source-1.4.4/src/main/resources/io/jenkins/plugins/gitlabserverconfig/servers/GitLabServers/config.groovy#L10]* [GitHub plugin|https://github.com/jenkinsci/github-plugin/blob/v1.29.5/src/main/resources/org/jenkinsci/plugins/github/config/GitHubPluginConfig/config.groovy#L12]h3. How to reproduce* Start a new Jenkins instance with no global credentials.* Go to {{Manage Jenkins > Configure System > Global Pipeline Libraries}}* Add a library* Use a "Modern SCM" and either "Git" or "GitHub"* Try to add credentials clicking on Add, it does not work..h3. Workarounds1. Create credentials from {{Manage Jenkins > Manage Credentials}} and then the credentials will be selectable in the global configuration.2. Partially fill the information for the shared library (without the credentials), save the configuration, go back to the configuration. It is now possible to "Add" credentials
[JIRA] (JENKINS-61653) Cannot "Add" credentials when configuring some components at the global level
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-61653 Cannot "Add" credentials when configuring some components at the global level Issue Type: Bug Assignee: Unassigned Components: core, credentials-plugin Created: 2020-03-24 02:25 Environment: Environment 1: * Pipeline: Shared Groovy Libraries 2.8 * core: 2.60.3 * credentials: 2.1.13 Environment 2: * Pipeline: Shared Groovy Libraries 2.16 * core: 2.227 * credentials: 2.3.5 Priority: Minor Reporter: Allan BURDAJEWICZ Issue It is not possible to add credentials when configuring a shared library from the global configuration Manage Jenkins > Configure System > Global Pipeline Libraries This is not only impacting Pipeline Shared Library. Other plugins that accepts credentials in the Jenkins global configuration seem to be impacted too. Environments Analysis Digged a bit into this and hopefully could narrow down the problem. This issue seems to happenswhen using f:repeatableProperty or f:repeatable to allow adding configuration. It only happens on newly added configuration in the UI: for example in the gloabl config, you must first add a Shared Library and the component you added has a credentials dropdown. Example of plugins affected: JIRA plugin TFS Plugin Pipeline Shared Library GitLab plugin Apparently it does not affect plugins that use the repeatableHeteroProperty:
[JIRA] (JENKINS-59966) Prometheus Plugin: Causes StackOverFlowerError
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-59966 Re: Prometheus Plugin: Causes StackOverFlowerError This is supposedly solved in version 2.0.7 of the plugin: https://github.com/jenkinsci/prometheus-plugin/pull/143 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202770.1572283306000.9308.1584600780254%40Atlassian.JIRA.
[JIRA] (JENKINS-58141) Jenkins Startup issues with jobConfigHistory
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-58141 Re: Jenkins Startup issues with jobConfigHistory Awesome thanks! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200186.156111651.7430.1584318300360%40Atlassian.JIRA.
[JIRA] (JENKINS-58141) Jenkins Startup issues with jobConfigHistory
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-58141 Re: Jenkins Startup issues with jobConfigHistory I believe that this is fixed by https://github.com/jenkinsci/jobConfigHistory-plugin/pull/112. But unreleased at the moment. Stefan Brausch Do you plan for a release any soon ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200186.156111651.6546.1584072840329%40Atlassian.JIRA.
[JIRA] (JENKINS-59959) The Concurrency Limit is not always respected.
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-59959 Re: The Concurrency Limit is not always respected. I have noticed that the limit are better respected when not using the NoDelayProvisioningStrategy (using the system property -Dio.jenkins.plugins.kubernetes.disableNoDelayProvisioning=true) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202763.1572257812000.2721.1583735040328%40Atlassian.JIRA.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-61211
QueueItemAuthenticator causes Build Queue contention
Change By:
Allan BURDAJEWICZ
When using the Authorize Project plugin to configure authorization for build execution, this has severe consequences on the overall performances of a Jenkins master because it request information repeatedly "trying to get user details for impersonation" from the Security Realm. This can happen during in a thread that hold the {{Queue.Lock}}An instance will periodically become unavailable or take a very long time in builds especially when the build queue becomes large or when a lot of builds are happening all at the same time. If start a fresh instance with 2 master executors, configure a "Project default Build Authorization" under *Manage Jenkins > configure Global Security*, then create a single pipeline and execute it, you will see through FINE logging of {{hudson.model.User}} that the {{User#getUserDetailsForImpersonation} is requested 8 times:{code}Feb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a success{code} ### h3. WorkaroundCaching can be configured at the Security Realm level depending on the solution (for example for LDAP / Active directory). ### h3. Improvement ProposalI do however think that something could be improved and that since impersonation is happening so frequently, maybe the [UserDetailsCache|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/security/UserDetailsCache.java] can be used to improve performance.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-61211
QueueItemAuthenticator causes Build Queue contention
Change By:
Allan BURDAJEWICZ
When using the Authorize Project plugin to configure authorization for build execution, this has severe consequences on the overall performances of a Jenkins master because it request information repeatedly "trying to get user details for impersonation" from the Security Realm. This can happen during in a thread that hold the {{Queue.Lock}}An instance will periodically become unavailable or take a very long time in builds especially when the build queue becomes large or when a lot of builds are happening all at the same time. If start a fresh instance with 2 master executors, configure a "Project default Build Authorization" under *Manage Jenkins > configure Global Security*, then create a single pipeline and execute it, you will see through FINE logging of {{hudson.model.User}} that the {{User#getUserDetailsForImpersonation} is requested 8 times:{code} eb Feb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a success{code}### WorkaroundCaching can be configured at the Security Realm level depending on the solution (for example for LDAP / Active directory). ### Improvement ProposalI do however think that something could be improved and that since impersonation is happening so frequently, maybe the [UserDetailsCache|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/security/UserDetailsCache.java] can be used to improve performance.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title Allan BURDAJEWICZ updated JENKINS-61211 Jenkins / JENKINS-61211 QueueItemAuthenticator causes Build Queue contention Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204764.158259701.5812.1582600020314%40Atlassian.JIRA.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-61211
QueueItemAuthenticator causes Build Queue contention
Change By:
Allan BURDAJEWICZ
When using the Authorize Project plugin to configure authorization for build execution, this has severe consequences on the overall performances of a Jenkins master because it request information repeatedly "trying to get user details for impersonation" from the Security Realm. This can happen during in a thread that hold the {{Queue.Lock}}An instance will periodically become unavailable or take a very long time in builds especially when the build queue becomes large or when a lot of builds are happening all at the same time. If start a fresh instance with 2 master executors, configure a "Project default Build Authorization" under * * Manage Jenkins > configure Global Security* * , then create a single pipeline and execute it, you will see through FINE logging of {{hudson.model.User}} that the {{User#getUserDetailsForImpersonation} is requested 8 times:{code}eb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a success{code}### WorkaroundCaching can be configured at the Security Realm level depending on the solution (for example for LDAP / Active directory). ### Improvement ProposalI do however think that something could be improved and that since impersonation is happening so frequently, maybe the [UserDetailsCache|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/security/UserDetailsCache.java] can be used to improve performance.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-61211 QueueItemAuthenticator causes Build Queue contention Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204764.158259701.5808.1582599960122%40Atlassian.JIRA.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-61211 Change By: Allan BURDAJEWICZ 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.204764.158259701.5809.1582599960252%40Atlassian.JIRA.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title
Allan BURDAJEWICZ created an issue
Jenkins / JENKINS-61211
QueueItemAuthenticator causes Build Queue contention
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2020-02-25 02:16
Environment:
core:2.222
Labels:
performance
Priority:
Major
Reporter:
Allan BURDAJEWICZ
When using the Authorize Project plugin to configure authorization for build execution, this has severe consequences on the overall performances of a Jenkins master because it request information repeatedly "trying to get user details for impersonation" from the Security Realm. This can happen during in a thread that hold the Queue.Lock An instance will periodically become unavailable or take a very long time in builds especially when the build queue becomes large or when a lot of builds are happening all at the same time. If start a fresh instance with 2 master executors, configure a "Project default Build Authorization" under *Manage Jenkins > configure Global Security*, then create a single pipeline and execute it, you will see through FINE logging of hudson.model.User that the {{User#getUserDetailsForImpersonation} is requested 8 times:
eb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonation
Impersonation of the user admin was a success
Feb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonation
Impersonation of the user admin was a
[JIRA] (JENKINS-60111) Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-60111 Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline Change By: Allan BURDAJEWICZ Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202957.1573231443000.5802.1582595760288%40Atlassian.JIRA.
[JIRA] (JENKINS-60111) Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60111 Re: Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline I wonder, could the impersonation at https://github.com/jenkinsci/jenkins/blob/jenkins-2.204.2/core/src/main/java/hudson/model/User.java#L388 leverage the https://github.com/jenkinsci/jenkins/blob/jenkins-2.204.2/core/src/main/java/jenkins/security/UserDetailsCache.java ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202957.1573231443000.4085.1582266240229%40Atlassian.JIRA.
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-60133
Re: Default HOME folder in containers does not exist
[~pgomez] Setting the system property {{-Dorg.csanchez.jenkins.plugins.kubernetes.PodTemplateBuilder .defaultHome =/home/jenkins/agent}} should workaround that problem and mock the behavior that was there before JENKINS-58705.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.4027.1582241400184%40Atlassian.JIRA.
[JIRA] (JENKINS-60966) Administrative monitors global configuration long and unordered
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60966 Jenkins / JENKINS-60966 Administrative monitors global configuration long and unordered Change By: Allan BURDAJEWICZ 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.204429.158088555.2658.1582153680273%40Atlassian.JIRA.
[JIRA] (JENKINS-36929) Add the version of protocols used by connectors
Title: Message Title Allan BURDAJEWICZ updated JENKINS-36929 Jenkins / JENKINS-36929 Add the version of protocols used by connectors Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172983.1469467906000.1339.1582002360306%40Atlassian.JIRA.
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen I have also proposed https://github.com/jenkinsci/tfs-plugin/pull/233 to deal with potentially unclosed connections. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189378.1521699501000.1288.1581994801819%40Atlassian.JIRA.
[JIRA] (JENKINS-36929) Add the version of protocols used by connectors
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-36929 Change By: Allan BURDAJEWICZ 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.172983.1469467906000.9277.1581668220283%40Atlassian.JIRA.
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Allan BURDAJEWICZ edited a comment on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen I also found http://blogs.pitx3.com/2016/01/24/mulesoft-microsoft-java-tfs-stackoverflowerror / . This user has reached out to Microsoft and while they did not confirm it was a bug they provided him with a workaround. It is mentioned in the release note that Stackoverlflow issue is solved in https://github.com/microsoft/team-explorer-everywhere/releases/tag/v14.0.3. If we have a look at [the source code of the SDK|https://github.com/microsoft/team-explorer-everywhere/blob/releases/14.0.3/source/com.microsoft.tfs.core/src/com/microsoft/tfs/core/TFSTeamProjectCollection.java#L261-L276]) however, the TFSConfigurationServer is closed after the TFSTeamProjectCollection and (while the workaround is to close it before).We can see that the TFS plugin [does already this in a way|https://github.com/jenkinsci/tfs-plugin/blob/tfs-5.157.0/tfs/src/main/java/hudson/plugins/tfs/model/Server.java#L274-L290]. But there is some legacy code using reflection that could be cleaned up. Proposed https://github.com/jenkinsci/tfs-plugin/pull/230 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60966) Administrative monitors global configuration long and unordered
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60966 Jenkins / JENKINS-60966 Administrative monitors global configuration long and unordered Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204429.158088555.5392.1581339840209%40Atlassian.JIRA.
[JIRA] (JENKINS-60966) Administrative monitors global configuration long and unordered
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-60966 Change By: Allan BURDAJEWICZ 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.204429.158088555.5389.1581339780752%40Atlassian.JIRA.
[JIRA] (JENKINS-60966) Administrative monitors global configuration long and unordered
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-60966 Administrative monitors global configuration long and unordered Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204429.158088555.5388.1581339780723%40Atlassian.JIRA.
[JIRA] (JENKINS-60977) Setting working directory to '/home/jenkins' does not persist
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60977 Re: Setting working directory to '/home/jenkins' does not persist We should at least warn users of such behavior. We may also add a way to control this (for example a system property that allow to disable the migration / enforcement at https://github.com/jenkinsci/kubernetes-plugin/blob/kubernetes-1.21.1/src/main/java/org/csanchez/jenkins/plugins/kubernetes/ContainerTemplate.java#L435-L441) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204445.1580902639000.1727.1580902800070%40Atlassian.JIRA.
[JIRA] (JENKINS-60977) Setting working directory to '/home/jenkins' does not persist
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-60977 Setting working directory to '/home/jenkins' does not persist Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2020-02-05 11:37 Environment: kubernetes:1.18.0 and later Priority: Minor Reporter: Allan BURDAJEWICZ Since the change of default working directory from /home/jenkins to home/jenkins/agent (see JENKINS-58705), it is possible to change the working directory back to /home/jenkins but this does not survive a restart. This behavior is quite confusing. Reproduce Create a pod template and set the working Directory to /home/jenkins Restart Jenkins Check the pod template configuration *Expected* The pod template configuration hasn't changed. The working directory is /home/jenkins *Actual* The pod template configuration has changed. The working directory is /home/jenkins/agent. Source The descriptor migrates the value: https://github.com/jenkinsci/kubernetes-plugin/blob/kubernetes-1.21.1/src/main/java/org/csanchez/jenkins/plugins/kubernetes/ContainerTemplate.java#L435-L441 Workaround A reliable way to use /home/jenkins
[JIRA] (JENKINS-60966) Administrative monitors global configuration long and unordered
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-60966 Administrative monitors global configuration long and unordered Issue Type: Improvement Assignee: Unassigned Attachments: admin-monitor-list.png Components: core Created: 2020-02-05 06:52 Environment: core:2.219 Priority: Minor Reporter: Allan BURDAJEWICZ The list of Administrative Monitors that are configurable globally is getting long and the components are not ordered by the displayed name (probably by the extension ordinal?) Add Comment
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Allan BURDAJEWICZ edited a comment on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen I also found http://blogs.pitx3.com/2016/01/24/mulesoft-microsoft-java-tfs-stackoverflowerror/. This user has reached out to Microsoft and while they did not confirm it was a bug they provided him with a workaround. It is mentioned in the release note that Stackoverlflow issue is solved in https://github.com/microsoft/team-explorer-everywhere/releases/tag/v14.0.3. If we have a look at [the source code of the SDK|https://github.com/microsoft/team-explorer-everywhere/blob/releases/14.0.3/source/com.microsoft.tfs.core/src/com/microsoft/tfs/core/TFSTeamProjectCollection.java#L261-L276]) however, the TFSConfigurationServer is closed after the TFSTeamProjectCollection and (while the workaround is to close it before).We can see that the TFS plugin [does already this in a way|https://github.com/jenkinsci/tfs-plugin/blob/tfs-5.157.0/tfs/src/main/java/hudson/plugins/tfs/model/Server.java#L274-L290]. But there is some legacy code using reflection that could be cleaned up. Proposed https://github.com/jenkinsci/tfs-plugin/pull/230 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Allan BURDAJEWICZ edited a comment on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen I also found http://blogs.pitx3.com/2016/01/24/mulesoft-microsoft-java-tfs-stackoverflowerror/. This user has reached out to Microsoft and while they did not confirm it was a bug they provided him with a workaround. I It is mentioned in the release note that Stackoverlflow issue is solved in https://github.com/microsoft/team-explorer-everywhere/releases/tag/v14.0.3. If we have a look at [the source code of the SDK|https://github.com/microsoft/team-explorer-everywhere/blob/releases/14.0.3/source/com.microsoft.tfs.core/src/com/microsoft/tfs/core/TFSTeamProjectCollection.java#L261-L276]) however, the TFSConfigurationServer is closed after the TFSTeamProjectCollection and (while the workaround is to close it before).We can see that the TFS plugin [does already this in a way|https://github.com/jenkinsci/tfs-plugin/blob/tfs-5.157.0/tfs/src/main/java/hudson/plugins/tfs/model/Server.java#L274-L290]. But there is some legacy code using reflection that could be cleaned up. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen I also found http://blogs.pitx3.com/2016/01/24/mulesoft-microsoft-java-tfs-stackoverflowerror/. This user has reached out to Microsoft and while they did not confirm it was a bug they provided him with a workaround. I can see that the TFS plugin does already this in a way. But there is some legacy code using reflection that could be cleaned up. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189378.1521699501000.662.1580784960422%40Atlassian.JIRA.
[JIRA] (JENKINS-60886) Kubernetes Declarative Agent should support podRetention attribute.
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60886 Jenkins / JENKINS-60886 Kubernetes Declarative Agent should support podRetention attribute. Change By: Allan BURDAJEWICZ 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.204274.1580200315000.9128.1580425620101%40Atlassian.JIRA.
[JIRA] (JENKINS-60886) Kubernetes Declarative Agent should support podRetention attribute.
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60886 Jenkins / JENKINS-60886 Kubernetes Declarative Agent should support podRetention attribute. Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204274.1580200315000.8080.1580300280108%40Atlassian.JIRA.
[JIRA] (JENKINS-60900) ComputedFolders do not show a Disable/Enable button
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60900 Re: ComputedFolders do not show a Disable/Enable button After further investigation, the problem is that the AbstractFolder#supportsMakeDisabled and ComputedFolder#supportsMakeDisabled are protected methods and in that case jelly just pass through . Could not find the documentation about method visibility requirements for jelly though. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204290.1580269906000.7940.1580277960138%40Atlassian.JIRA.
[JIRA] (JENKINS-60900) ComputedFolders do not show a Disable/Enable button
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60900 Jenkins / JENKINS-60900 ComputedFolders do not show a Disable/Enable button Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204290.1580269906000.7939.1580277900114%40Atlassian.JIRA.
[JIRA] (JENKINS-60900) ComputedFolders do not show a Disable/Enable button
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-60900 ComputedFolders do not show a Disable/Enable button Change By: Allan BURDAJEWICZ Assignee: Francisco Fernández Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204290.1580269906000.7901.1580274900382%40Atlassian.JIRA.
[JIRA] (JENKINS-60900) ComputedFolders do not show a Disable/Enable button
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-60900 Change By: Allan BURDAJEWICZ 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.204290.1580269906000.7902.1580274900395%40Atlassian.JIRA.
[JIRA] (JENKINS-60900) ComputedFolders do not show a Disable/Enable button
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-60900 ComputedFolders do not show a Disable/Enable button Issue Type: Bug Assignee: Francisco Fernández Components: branch-api-plugin, cloudbees-folder-plugin Created: 2020-01-29 03:51 Environment: folders:6.11.0 Priority: Minor Reporter: Allan BURDAJEWICZ Although a ComputedFolder supports the disable functionality and can be used by appending /disable to the folder URL, they do not show the Enable/Disable button in the UI. According to the code, I think it should work https://github.com/jenkinsci/cloudbees-folder-plugin/blob/cloudbees-folder-6.11/src/main/resources/com/cloudbees/hudson/plugins/folder/AbstractFolder/view-index-top.jelly#L45-L68 but Multibranch / Organization folder fo not show that button. The UI seeems to match that Jelly but never passes the condition !it.supportsMakeDisabled() Add Comment
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-60133
Re: Default HOME folder in containers does not exist
[~pgomez] Most if of images have a user defined and a {{HOME}} directory. As an example the maven image's HOME dir is set to [/root|https://github.com/carlossg/docker-maven/blob/master/jdk-8/Dockerfile#L4] and that i what is used when the kubernetes plugin spins up an agent with an additional maven container, like in the [example|https://github.com/jenkinsci/kubernetes-plugin/blob/master/examples/maven-yaml.groovy].The real challenge with Openshift is that the arbitraty uids are generated dynamically without a {{$HOME}} directory / variable. The "trick" that was in place with the kubernetes plugin was to set the HOME directory to a location that for sure exists and is owned by the running user {{/home/jenkins}}. Now this has changed and that trick has become a breaking change for that scenario with Openshift. I do agree that this is a bug.Not sure what is the best solution here. Change the DEFAULT_HOME to match again the working directory, use another directory (but not sure which one, {{/tmp/}} ?), use an additional {{emptyDir}} as {{HOME}} ?Maybe [~vlatombe] has some ideas ?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60133 Re: Default HOME folder in containers does not exist Pablo Gomez Most if images have a user defined and a HOME directory. As an example the maven image's HOME dir is set to /root and that i what is used when the kubernetes plugin spins up an agent with an additional maven container, like in the example. The real challenge with Openshift is that the arbitraty uids are generated dynamically without a $HOME directory / variable. The "trick" that was in place with the kubernetes plugin was to set the HOME directory to a location that for sure exists and is owned by the running user /home/jenkins. Now this has changed and that trick has become a breaking change for that scenario with Openshift. I do agree that this is a bug. Not sure what is the best solution here. Change the DEFAULT_HOME to match again the working directory, use another directory (but not sure which one, /tmp/ ?), use an additional emptyDir as HOME ? Maybe Vincent Latombe has some ideas ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.7275.1580210340150%40Atlassian.JIRA.
[JIRA] (JENKINS-60886) Kubernetes Declarative Agent should support podRetention attribute.
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-60886 Change By: Allan BURDAJEWICZ 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.204274.1580200315000.7271.1580209440196%40Atlassian.JIRA.
[JIRA] (JENKINS-60886) Kubernetes Declarative Agent should support podRetention attribute.
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-60886 Kubernetes Declarative Agent should support podRetention attribute. Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204274.1580200315000.7270.1580209440135%40Atlassian.JIRA.
[JIRA] (JENKINS-60886) Kubernetes Declarative Agent should support podRetention attribute.
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-60886 Kubernetes Declarative Agent should support podRetention attribute. Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2020-01-28 08:31 Environment: kubernetes:1.23.1 Priority: Major Reporter: Allan BURDAJEWICZ The kubernetes declarative agent directive does not support the podRetention attribute that can however be configured from Pod Template configuration or podTemplate step. It would be great if this attribute be configurable from a pipeline declarative agent directive. Add Comment
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-60133
Re: Default HOME folder in containers does not exist
This is probably a side effect of the change of working directory to {{/home/jenkins/agent}} (i.e. https://issues.jenkins-ci.org/browse/ JENKINS-58705). If the {{/home/jenkins}} does not exist in the image, it will be automatically added during the mounting of the workspace volume but will not be writable.The {{DEFAULT_HOME}} might need to be changed. Otherwise images need to be adapted for arbitrary users as documented in https://access.redhat.com/documentation/en-us/openshift_container_platform/3.11/html/creating_images/creating-images-guidelines.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.4118.1579760640234%40Atlassian.JIRA.
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60133 Re: Default HOME folder in containers does not exist Pablo Gomez Setting the system property -Dorg.csanchez.jenkins.plugins.kubernetes.PodTemplateBuilder=/home/jenkins/agent should workaround that problem and mock the behavior that was there before JENKINS-58705. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.4116.1579760640207%40Atlassian.JIRA.
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60133 Re: Default HOME folder in containers does not exist This is probably a side effect of the change of working directory to /home/jenkins/agent (i.e. https://issues.jenkins-ci.org/browse/JENKINS-58705). If the /home/jenkins does not exist in the image, it will be automatically added during the mounting of the workspace volume but will not be writable. The DEFAULT_HOME might need to be changed. Otherwise images need to be adapted for arbitrary users as documented in https://access.redhat.com/documentation/en-us/openshift_container_platform/3.11/html/creating_images/creating-images-guidelines. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.3745.1579695600150%40Atlassian.JIRA.
[JIRA] (JENKINS-60009) GCLogs component should be made Java 11 compatible
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60009 Re: GCLogs component should be made Java 11 compatible https://docs.oracle.com/javase/9/tools/java.htm#GUID-BE93ABDC-999C-4CB5-A88B-1994AAAC74D5__CONVERTGCLOGGINGFLAGSTOXLOG-A5046BD1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202826.1572566602000.902.1579248300052%40Atlassian.JIRA.
[JIRA] (JENKINS-60009) GCLogs component should be made Java 11 compatible
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-60009 Change By: Allan BURDAJEWICZ 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.202826.1572566602000.880.1579240800465%40Atlassian.JIRA.
[JIRA] (JENKINS-41591) The Rebuild Last shortcut is missing for Pipeline jobs
Title: Message Title Allan BURDAJEWICZ updated JENKINS-41591 Jenkins / JENKINS-41591 The Rebuild Last shortcut is missing for Pipeline jobs Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178408.1485858407000.822.1579227480854%40Atlassian.JIRA.
[JIRA] (JENKINS-33394) Generate support bundle before providing download
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-33394 Generate support bundle before providing download Change By: Allan BURDAJEWICZ Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168802.1457451818000.786.1579221540740%40Atlassian.JIRA.
[JIRA] (JENKINS-41591) The Rebuild Last shortcut is missing for Pipeline jobs
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-41591 Change By: Allan BURDAJEWICZ 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.178408.1485858407000.724.1579216741359%40Atlassian.JIRA.
[JIRA] (JENKINS-41591) The Rebuild Last shortcut is missing for Pipeline jobs
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-41591 The Rebuild Last shortcut is missing for Pipeline jobs Change By: Allan BURDAJEWICZ Assignee: ragesh_nair Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178408.1485858407000.710.1579216741160%40Atlassian.JIRA.
[JIRA] (JENKINS-60788) NullPointerException when hitting Check Now against a custom update center
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-60788 NullPointerException when hitting Check Now against a custom update center Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-01-16 08:20 Environment: 2.204.1 Priority: Minor Reporter: Allan BURDAJEWICZ When using a *custom update site* pointing to a specific implementation of an update center, hitting the "Check Now" button in the Plugin Manager under *Manage Jenkins > Manage Plugins* may cause a NullPointerException: 2020-01-15 12:47:41.347+ [id=12] INFO hudson.util.Retrier#start: The attempt #1 to do the action check updates server failed with an allowed exception: java.lang.NullPointerException at hudson.tools.DownloadFromUrlInstaller$DescriptorImpl.isDefaultSchema(DownloadFromUrlInstaller.java:160) at hudson.tools.DownloadFromUrlInstaller$DescriptorImpl.access$000(DownloadFromUrlInstaller.java:124) at hudson.tools.DownloadFromUrlInstaller$DescriptorImpl$1.reduce(DownloadFromUrlInstaller.java:139) at hudson.model.DownloadService$Downloadable.updateNow(DownloadService.java:358) at hudson.PluginManager.checkUpdatesServer(PluginManager.java:1772) at hudson.util.Retrier.start(Retrier.java:62) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1736) 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
[JIRA] (JENKINS-60670) StackOverflowError due to the HP ALM implementation of GraphListener
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-60670 StackOverflowError due to the HP ALM implementation of GraphListener Issue Type: Bug Assignee: Maria Narcisa Galan Components: hp-application-automation-tools-plugin Created: 2020-01-07 08:08 Environment: hp-application-automation-tools-plugin:5.6.2 Priority: Critical Reporter: Allan BURDAJEWICZ Recently discovered a StackOverflowError originating from the HP ALM plugin: 2019-12-30 02:31:50.046+ [id=42]WARNING o.j.p.w.cps.CpsFlowExecution#notifyListeners java.lang.StackOverflowError at java.io.UnixFileSystem.getBooleanAttributes0(Native Method) at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:242) at java.io.File.exists(File.java:819) [...] at com.microfocus.application.automation.tools.octane.events.WorkflowListenerOctaneImpl.onNewHead(WorkflowListenerOctaneImpl.java:79) [...] at hudson.model.Job.getEstimatedDurationCandidates(Job.java:1045) at hudson.model.Job.getEstimatedDuration(Job.java:1059) at hudson.model.Run.getEstimatedDuration(Run.java:2450) at com.microfocus.application.automation.tools.octane.events.WorkflowListenerOctaneImpl.sendPipelineStartedEvent(WorkflowListenerOctaneImpl.java:92) at com.microfocus.application.automation.tools.octane.events.WorkflowListenerOctaneImpl.onNewHead(WorkflowListenerOctaneImpl.java:70) [...] at com.microfocus.application.automation.tools.octane.events.WorkflowListenerOctaneImpl.sendPipelineStartedEvent(WorkflowListenerOctaneImpl.java:92) at
[JIRA] (JENKINS-59868) Add information about missing working directory to Polling logs
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-59868 Re: Add information about missing working directory to Polling logs Proposed https://github.com/jenkinsci/git-plugin/pull/810 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202608.157166054.1473.1577952360506%40Atlassian.JIRA.
[JIRA] (JENKINS-59868) Add information about missing working directory to Polling logs
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-59868 Change By: Allan BURDAJEWICZ 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.202608.157166054.1474.1577952360540%40Atlassian.JIRA.
[JIRA] (JENKINS-59868) Add information about missing working directory to Polling logs
Title: Message Title Allan BURDAJEWICZ updated JENKINS-59868 Jenkins / JENKINS-59868 Add information about missing working directory to Polling logs Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202608.157166054.1475.1577952360555%40Atlassian.JIRA.
[JIRA] (JENKINS-59956) Support Core should log memory stats regularly
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-59956 Support Core should log memory stats regularly Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202760.1572224231000.1357.1577938860503%40Atlassian.JIRA.
[JIRA] (JENKINS-59956) Support Core should log memory stats regularly
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-59956 Re: Support Core should log memory stats regularly We should be able to get a lot of info from the GarbageCollectorMXBean. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202760.1572224231000.1354.1577938860440%40Atlassian.JIRA.
[JIRA] (JENKINS-53532) Kubernetes java.net.SocketTimeoutException: timeout
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-53532 Re: Kubernetes java.net.SocketTimeoutException: timeout The original issue java.net.SocketTimeoutException: timeout is due to a Socket Read Timeout. The value can be changed in the kubernetes cloud configuration since version 1.14.9. Before this version, there was a persistent issue and the value was reset to 0 every time the configuration was saved from the UI. Note that until version 1.22.3 a value of 0 does not mean no timeout. If a value of 0 is provided, the fabric8 kubernetes client does not explicitly set a timeout. But the okhttp client defaults to 10s. *A value of 0 actually means 10s*. Since version 1.22.3 of the kubernetes plugin: the minimum value for Read Timeout is 15s the minimum value of the connection timeout is 5s. The SocketTimeoutException: sent ping but didn't receive pong within ms is related to the Socket Ping Timeout interval and should be fixed since version 1.19.3 of the kubernetes plugin: https://issues.jenkins-ci.org/browse/JENKINS-58301. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60517) Kubernetes plugin crashes with docker plugin .inside command
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-60517
Re: Kubernetes plugin crashes with docker plugin .inside command
I am curious, as a workaround does that make any difference if you explicitly set a {{workingDir: "/home/jenkins/agent"}} to you container templates ? I do think it would pass the first condition and not fail on the second one (NPE) but I might b wrong
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203614.1576615322000.13944.1576824960153%40Atlassian.JIRA.
[JIRA] (JENKINS-60517) Kubernetes plugin crashes with docker plugin .inside command
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-60517
Re: Kubernetes plugin crashes with docker plugin .inside command
I am curious, as a workaround does that make any difference if you explicitly set a {{workingDir: "/home/jenkins/agent"}} to you container templates ?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203614.1576615322000.13942.1576824900221%40Atlassian.JIRA.
[JIRA] (JENKINS-60517) Kubernetes plugin crashes with docker plugin .inside command
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60517 Re: Kubernetes plugin crashes with docker plugin .inside command I am curious, does that make any difference if you explicitly set a workingDir: "/home/jenkins/agent" to you container templates ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203614.1576615322000.13940.1576824900183%40Atlassian.JIRA.
[JIRA] (JENKINS-60517) Kubernetes plugin crashes with docker plugin .inside command
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60517 Re: Kubernetes plugin crashes with docker plugin .inside command > From diff of 2 generated manifests the largest difference is that when it breaks - EVERY container has `workingDir: /home/jenkins/agent` Were the workingDir different with 1.22.0 ? The fact that /home/jenkins/agent is the same across all containers is not a problem as far as I understand. But I think that you are right, this bug may be caused by JENKINS-58975. That containerWorkingDirFilePath (derived from starter.pwd()) may be null. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203614.1576615322000.13938.1576824780595%40Atlassian.JIRA.
[JIRA] (JENKINS-60551) KubernetesCloud copy constructor is not copying all field
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60551 Jenkins / JENKINS-60551 KubernetesCloud copy constructor is not copying all field Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203656.1576816184000.13932.1576822380129%40Atlassian.JIRA.
[JIRA] (JENKINS-60551) KubernetesCloud copy constructor is not copying all field
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-60551 KubernetesCloud copy constructor is not copying all field Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203656.1576816184000.13933.1576822380211%40Atlassian.JIRA.
[JIRA] (JENKINS-60551) KubernetesCloud copy constructor is not copying all field
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-60551 Change By: Allan BURDAJEWICZ 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.203656.1576816184000.13931.1576818120098%40Atlassian.JIRA.
[JIRA] (JENKINS-60551) KubernetesCloud copy constructor is not copying all field
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-60551
KubernetesCloud copy constructor is not copying all field
Change By:
Allan BURDAJEWICZ
The [Kubernetes Cloud copy constructor|https://github.com/jenkinsci/kubernetes-plugin/blob/kubernetes-1.22.2/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud.java#L142-L170] is not copying all fields (for example {{serverCertificate}}, {{ capOnlyOnAlivePods}}, {{ readTimeout}}). This can have undesirable effect when relying on this API (for example default value of the {{readTimeout}} is {{0}} and not the jelly default {{15}})
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-60551) KubernetesCloud copy constructor is not copying all field
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-60551 KubernetesCloud copy constructor is not copying all field Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-12-20 04:29 Environment: kubernetes:1.22.2 Priority: Major Reporter: Allan BURDAJEWICZ The Kubernetes Cloud copy constructor is not copying all fields (for example serverCertificate, capOnlyOnAlivePods, readTimeout). This can have undesirable effect when relying on this API (for example default value of the readTimeout is 0 and not the jelly default 15) Add Comment
[JIRA] (JENKINS-58975) Executing shell in a container with a custom workingDir times out
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-58975 Re: Executing shell in a container with a custom workingDir times out To make this work, you must change the working directory of all containers in the pod, including the jnlp container. I think that this JIRA is actually an improvement ? to make the container block aware of the container context (reflecting working dir and *workspace*) that allows to use different workingDir in the containers of kubernetes agent pods. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201324.1566067268000.13406.1576724820186%40Atlassian.JIRA.
[JIRA] (JENKINS-58301) Kubernetes Plugin Repeated Socket Ping Timeout Exceptions
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-58301 Re: Kubernetes Plugin Repeated Socket Ping Timeout Exceptions I believe that this issue is resolved since the release of version 1.19.3 that uses kubernetes-client 4.6.0 in which the default ping interval is 30 seconds: https://github.com/fabric8io/kubernetes-client/commit/2b1799497f46de81c841ea43808472d3239e7209#diff-7a4b549d7e10b88fbe20ebe680f6b25b https://github.com/jenkinsci/kubernetes-plugin/commit/464320a012fa0fd47b92f3af3d0403afd22c41a5#diff-600376dffeb79835ede4a0b285078036 https://github.com/jenkinsci/kubernetes-client-api-plugin/blob/kubernetes-client-api-4.6.0-1/pom.xml#L20 maybe Vincent Latombe can confirm ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200367.1562076713000.9428.1576547640367%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60393 Jenkins / JENKINS-60393 cloudbees-folder circular dependency Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203447.1575664332000.6050.1576122961040%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-60393
Re: cloudbees-folder circular dependency
I can reproduce the problem when plugins like {{xunit}} and {{code-coverage-api}} are installed. I think because they use some initializer that happen before the folder global configuration is loaded: * https://github.com/jenkinsci/xunit-plugin/blob/xunit-2.3.7/src/main/java/org/jenkinsci/plugins/xunit/AliasInitializer.java#L42* https://github.com/jenkinsci/code-coverage-api-plugin/blob/code-coverage-api-1.1.1/src/main/java/io/jenkins/plugins/coverage/CoverageElementInitializer.java#L12It does not prevent Jenkins to start in the scenario I tested and a way to workaround that problem if Jenkins starts is to go to * * Manage Jenkins > Configure System* * (check that there is a section named "Folder") and save. Otherwise, another workaround is to ensure that there is already a global configuration: add the file [^com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration.xml] to {{$JENKINS_HOME/}} and restart Jenkins.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203447.1575664332000.6048.1576122961012%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60393 Re: cloudbees-folder circular dependency I can reproduce the problem when plugins like xunit and code-coverage-api are installed. I think because they use some initializer that happen before the folder global configuration is loaded: https://github.com/jenkinsci/xunit-plugin/blob/xunit-2.3.7/src/main/java/org/jenkinsci/plugins/xunit/AliasInitializer.java#L42 https://github.com/jenkinsci/code-coverage-api-plugin/blob/code-coverage-api-1.1.1/src/main/java/io/jenkins/plugins/coverage/CoverageElementInitializer.java#L12 It does not prevent Jenkins to start in the scenario I tested and a way to workaround that problem if Jenkins starts is to go to *Manage Jenkins > Configure System* (check that there is a section named "Folder") and save. Otherwise, another workaround is to ensure that there is already a global configuration: add the file com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration.xml to $JENKINS_HOME/ and restart Jenkins. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-60393 cloudbees-folder circular dependency Change By: Allan BURDAJEWICZ Attachment: com.cloudbees.hudson.plugins.folder.config.AbstractFolderConfiguration.xml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203447.1575664332000.6023.1576122780505%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60393 Re: cloudbees-folder circular dependency Maybe we should move the "auto" configuration outside the constructor and do it after all extensions are loaded: https://github.com/jenkinsci/cloudbees-folder-plugin/blob/cloudbees-folder-6.10.0/src/main/java/com/cloudbees/hudson/plugins/folder/config/AbstractFolderConfiguration.java#L34-L43 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203447.1575664332000.5985.1576120020346%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-60393 Change By: Allan BURDAJEWICZ 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.203447.1575664332000.5936.1576110901133%40Atlassian.JIRA.
[JIRA] (JENKINS-60413) Regression: Branch scanning fails when PR refer to a deleted fork
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-60413 Regression: Branch scanning fails when PR refer to a deleted fork Change By: Allan BURDAJEWICZ Labels: 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.203470.157594813.3265.1575953220152%40Atlassian.JIRA.
[JIRA] (JENKINS-60413) Regression: Branch scanning fails when PR refer to a deleted fork
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-60413 Change By: Allan BURDAJEWICZ 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.203470.157594813.3262.1575952440280%40Atlassian.JIRA.
[JIRA] (JENKINS-60413) Regression: Branch scanning fails when PR refer to a deleted fork
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-60413 Regression: Branch scanning fails when PR refer to a deleted fork Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203470.157594813.3261.1575952440222%40Atlassian.JIRA.
[JIRA] (JENKINS-60413) Regression: Branch scanning fails when PR refer to a deleted fork
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60413 Jenkins / JENKINS-60413 Regression: Branch scanning fails when PR refer to a deleted fork Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203470.157594813.3263.1575952440310%40Atlassian.JIRA.
[JIRA] (JENKINS-60413) Regression: Branch scanning fails when PR refer to a deleted fork
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-60413 Regression: Branch scanning fails when PR refer to a deleted fork Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-12-10 03:22 Environment: github-branch-source:2.5.7 Priority: Major Reporter: Allan BURDAJEWICZ When scanning a repository, if the source fork of a pull request have been deleted the scan fails: ERROR: [Mon Dec 09 22:02:34 GMT 2019] Could not fetch branches from source 09803c5b-0046-46ea-8ed5-3f98d5cf31e7 java.lang.NullPointerException at org.jenkinsci.plugins.github_branch_source.PullRequestSCMHead.(PullRequestSCMHead.java:95) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrievePullRequest(GitHubSCMSource.java:1168) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1027) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:283) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:635) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:164) at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1026) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) [Mon Dec 09 22:02:34 GMT 2019] Finished branch indexing. Indexing took 7.4 sec
[JIRA] (JENKINS-60073) support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-60073 support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202908.1573032472000.2766.1575870240410%40Atlassian.JIRA.
[JIRA] (JENKINS-60073) support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission
Title: Message Title Allan BURDAJEWICZ closed an issue as Fixed Jenkins / JENKINS-60073 support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission Change By: Allan BURDAJEWICZ Status: Open Closed 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.202908.1573032472000.2764.1575870240336%40Atlassian.JIRA.
[JIRA] (JENKINS-60073) support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60073 Re: support-core dynamic loading error: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission Right this is a duplicate. Thanks Arnaud Héritier! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202908.1573032472000.2768.1575870240469%40Atlassian.JIRA.
[JIRA] (JENKINS-59498) ItemsContent should be optimized and selected by default
Title: Message Title Allan BURDAJEWICZ updated JENKINS-59498 Jenkins / JENKINS-59498 ItemsContent should be optimized and selected by default Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202117.1569295137000.2311.1574038860208%40Atlassian.JIRA.
