[JIRA] (JENKINS-35524) new ec2 slave is terminated or terminating during launch
Title: Message Title Neil Rhine commented on JENKINS-35524 Re: new ec2 slave is terminated or terminating during launch For us, this ended up being on the AWS side, we were hitting a limit on EBS drives. I can imagine it could also be from instance type, number of instances, etc. I have also seen something similar when the AMI has an encrypted drives and the access/secret don't have permissions to access it. I think this bug should really be about making the error more verbose. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35524) new ec2 slave is terminated or terminating during launch
Title: Message Title Neil Rhine commented on JENKINS-35524 Re: new ec2 slave is terminated or terminating during launch Any word on this? It hit us super hard today. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Neil Rhine commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit Any ideas here? Even with separate accounts for each repository our organization hits the api limit constantly due to a large number of branches/PRs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38937) GitHub API cache is not working
Title: Message Title
Neil Rhine edited a comment on JENKINS-38937
Re: GitHub API cache is not working
The cache is being written to after all, just in a very minor capacity, before it is 's cleared it is 's only at 16kb and since the rate limit is being hit , I expected to see more usage. I think it is more related to JENKINS-36121 and less this bug after all, but this is my list of plugins:{code}Pipeline: API (workflow-api): 2.4Gradle Plugin (gradle): 1.25Job Configuration History Plugin (jobConfigHistory): 2.15Git client plugin (git-client): 2.1.0_javascript_ GUI Lib: ACE Editor bundle plugin (ace-editor): 1.1Jackson 2 API Plugin (jackson2-api): 2.7.3LDAP Plugin (ldap): 1.12Branch API Plugin (branch-api): 1.11.1Pipeline: SCM Step (workflow-scm-step): 2.2OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.5MapDB API Plugin (mapdb-api): 1.0.9.0GitHub Pull Request Builder (ghprb): 1.33.1Structs Plugin (structs): 1.5Node and Label parameter plugin (nodelabelparameter): 1.7.2Checkstyle Plug-in (checkstyle): 3.46Ant Plugin (ant): 1.4Icon Shim Plugin (icon-shim): 2.0.3Xvnc plugin (xvnc): 1.24Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.4Job DSL (job-dsl): 1.50Git plugin (git): 3.0.0Groovy Postbuild (groovy-postbuild): 2.3.1Throttle Concurrent Builds Plug-in (throttle-concurrents): 1.9.0Credentials Binding Plugin (credentials-binding): 1.9Audit Trail (audit-trail): 2.2xUnit plugin (xunit): 1.102Pipeline: Step API (workflow-step-api): 2.4GitHub Organization Folder Plugin (github-organization-folder): 1.5_javascript_ GUI Lib: Handlebars bundle plugin (handlebars): 1.1.1Post-Build Script Plug-in (postbuildscript): 0.17Email Extension Plugin (email-ext): 2.47Display URL API (display-url-api): 0.5Jira Issue Updater (jenkins-jira-issue-updater): 1.18CloudBees Amazon Web Services Credentials Plugin (aws-credentials): 1.16Pipeline: Basic Steps (workflow-basic-steps): 2.1build timeout plugin (build-timeout): 1.17.1TAP Plugin (tap): 2.0.1Pipeline: Supporting APIs (workflow-support): 2.8GitHub plugin (github): 1.22.4ShiningPanda Plugin (shiningpanda): 0.23JIRA plugin (jira): 2.2.1Xvfb plugin (xvfb): 1.1.3Pipeline: Build Step (pipeline-build-step): 2.2Artifactory Plugin (artifactory): 2.6.0Email Extension Template Plugin (emailext-template): 1.0Pipeline: Stage Step (pipeline-stage-step): 2.2GIT server Plugin (git-server): 1.7Environment Injector Plugin (envinject): 1.92.1OWASP Dependency-Check Plugin (dependency-check-jenkins-plugin): 1.4.2Pipeline: Job (workflow-job): 2.6Token Macro Plugin (token-macro): 1.12.1Matrix Authorization Strategy Plugin (matrix-auth): 1.4Pipeline Graph Analysis Plugin (pipeline-graph-analysis): 1.1Amazon Web Services SDK (aws-java-sdk): 1.11.37GitHub Integration Plugin (github-pullrequest): 0.1.0-rc12_javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin (jquery-detached): 1.2.1Timestamper (timestamper): 1.8.5Folders Plugin (cloudbees-folder): 5.12Dashboard View (dashboard-view): 2.9.10External Monitor Job Type Plugin (external-monitor-job): 1.6EZ Templates (ez-templates): 1.2.1SSH Slaves plugin (ssh-slaves): 1.11Copy Artifact Plugin (copyartifact): 1.38.1Pipeline (workflow-aggregator): 2.3JiraTestResultReporter plugin (JiraTestResultReporter): 2.0.3HTML Publisher plugin (htmlpublisher): 1.11Pipeline: Multibranch (workflow-multibranch): 2.9Port Allocator Plug-in (port-allocator): 1.9-SNAPSHOT (private-61b7bdb7-neil.rhine)Script Security Plugin (script-security): 1.23PMD Plug-in (pmd): 3.45JUnit Plugin (junit): 1.18Pipeline: REST API Plugin (pipeline-rest-api): 2.0SSH Credentials Plugin (ssh-credentials): 1.12Javadoc Plugin (javadoc): 1.4Workspace Cleanup Plugin
[JIRA] (JENKINS-38937) GitHub API cache is not working
Title: Message Title Neil Rhine commented on JENKINS-38937 Re: GitHub API cache is not working The cache is being written to after all, just in a very minor capacity, before it is cleared it is only at 16kb and since the rate limit is being hit, I expected to see more usage. I think it is more related to JENKINS-36121 and less this bug after all, but this is my list of plugins: Pipeline: API (workflow-api): 2.4 Gradle Plugin (gradle): 1.25 Job Configuration History Plugin (jobConfigHistory): 2.15 Git client plugin (git-client): 2.1.0 _javascript_ GUI Lib: ACE Editor bundle plugin (ace-editor): 1.1 Jackson 2 API Plugin (jackson2-api): 2.7.3 LDAP Plugin (ldap): 1.12 Branch API Plugin (branch-api): 1.11.1 Pipeline: SCM Step (workflow-scm-step): 2.2 OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.5 MapDB API Plugin (mapdb-api): 1.0.9.0 GitHub Pull Request Builder (ghprb): 1.33.1 Structs Plugin (structs): 1.5 Node and Label parameter plugin (nodelabelparameter): 1.7.2 Checkstyle Plug-in (checkstyle): 3.46 Ant Plugin (ant): 1.4 Icon Shim Plugin (icon-shim): 2.0.3 Xvnc plugin (xvnc): 1.24 Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.4 Job DSL (job-dsl): 1.50 Git plugin (git): 3.0.0 Groovy Postbuild (groovy-postbuild): 2.3.1 Throttle Concurrent Builds Plug-in (throttle-concurrents): 1.9.0 Credentials Binding Plugin (credentials-binding): 1.9 Audit Trail (audit-trail): 2.2 xUnit plugin (xunit): 1.102 Pipeline: Step API (workflow-step-api): 2.4 GitHub Organization Folder Plugin (github-organization-folder): 1.5 _javascript_ GUI Lib: Handlebars bundle plugin (handlebars): 1.1.1 Post-Build Script Plug-in (postbuildscript): 0.17 Email Extension Plugin (email-ext): 2.47 Display URL API (display-url-api): 0.5 Jira Issue Updater (jenkins-jira-issue-updater): 1.18 CloudBees Amazon Web Services Credentials Plugin (aws-credentials): 1.16 Pipeline: Basic Steps (workflow-basic-steps): 2.1 build timeout plugin (build-timeout): 1.17.1 TAP Plugin (tap): 2.0.1 Pipeline: Supporting APIs (workflow-support): 2.8 GitHub plugin (github): 1.22.4 ShiningPanda Plugin (shiningpanda): 0.23 JIRA plugin (jira): 2.2.1 Xvfb plugin (xvfb): 1.1.3 Pipeline: Build Step (pipeline-build-step): 2.2 Artifactory Plugin (artifactory): 2.6.0 Email Extension Template Plugin (emailext-template): 1.0 Pipeline: Stage Step (pipeline-stage-step): 2.2 GIT server Plugin (git-server): 1.7 Environment Injector Plugin (envinject): 1.92.1 OWASP Dependency-Check Plugin (dependency-check-jenkins-plugin): 1.4.2 Pipeline: Job (workflow-job): 2.6 Token Macro Plugin (token-macro): 1.12.1 Matrix Authorization Strategy Plugin (matrix-auth): 1.4 Pipeline Graph Analysis Plugin (pipeline-graph-analysis): 1.1 Amazon Web Services SDK (aws-java-sdk): 1.11.37 GitHub Integration Plugin (github-pullrequest): 0.1.0-rc12 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin (jquery-detached): 1.2.1 Timestamper (timestamper): 1.8.5 Folders Plugin (cloudbees-folder): 5.12 Dashboard View (dashboard-view): 2.9.10 External Monitor Job Type Plugin (external-monitor-job): 1.6 EZ Templates (ez-templates): 1.2.1 SSH Slaves plugin (ssh-slaves): 1.11 Copy Artifact Plugin (copyartifact): 1.38.1 Pipeline (workflow-aggregator): 2.3 JiraTestResultReporter plugin (JiraTestResultReporter): 2.0.3 HTML Publisher plugin (htmlpublisher): 1.11 Pipeline: Multibranch (workflow-multibranch): 2.9 Port Allocator Plug-in (port-allocator): 1.9-SNAPSHOT (private-61b7bdb7-neil.rhine) Script Security Plugin
[JIRA] (JENKINS-38937) GitHub API cache is not working
Title: Message Title Neil Rhine commented on JENKINS-38937 Re: GitHub API cache is not working Any updates here or suggestions to mitigate? Our organization is also constantly hitting the API limit on all of the indexing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin
Title: Message Title Neil Rhine commented on JENKINS-29652 Re: Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin I added another patch to the ticket that retries on more cases. This one will allow for both the eventual joined build to run on both failure and success until all upstream jobs succeed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin
Title: Message Title Neil Rhine updated an issue Jenkins / JENKINS-29652 Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin Change By: Neil Rhine Attachment: 002-Join-plugin-fix-to-allow-retry-on-failure.patch Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
