[JIRA] (TEST-176) Crear Secuencia Ahorros Savings fidelity
Title: Message Title R. Tyler Croy deleted an issue test / TEST-176 Crear Secuencia Ahorros Savings fidelity This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202108.156926916.337.1581804420167%40Atlassian.JIRA.
[JIRA] (JENKINS-59632) Plugin does not respect the jenkinsUrl configuration from configuration-as-code
Title: Message Title
R. Tyler Croy commented on JENKINS-59632
Re: Plugin does not respect the jenkinsUrl configuration from configuration-as-code
I have a workaround which I am using for now, which relies on the init.groovy.d/ support in Jenkins:
/*
* This script helps work around an issue with the Jenkins Kubernetes plugin
* which doesn't properly receive the configured `jenkinsUrl` on restart.
*
* The script is making an assumption that we can wait for a few seconds on
* bootstrap before overwriting the URL on the object directly
*
* See: //issues.jenkins-ci.org/browse/JENKINS-59632>
*/
import jenkins.model.*
import org.csanchez.jenkins.plugins.kubernetes.*
/*
* Spinning off a separate thread to do this work so this doesn't block the
* bootstrap of the Jenkins master
*/
Thread.start {
sleep 5000
/*
* On the off chance we have more clouds, this is looking for the
* Kubernetes one only, and then setting the URL to what we have in our
* environment defined as an override.
*/
for (cloud in Jenkins.instance.clouds) {
if (cloud.class == KubernetesCloud) {
if (System.env.KUBERNETES_JENKINS_URL) {
println "Overwriting the Kubernetes Jenkisn URL to: ${System.env.KUBERNETES_JENKINS_URL}"
cloud.setJenkinsUrl(System.env.KUBERNETES_JENKINS_URL);
Jenkins.instance.save();
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59632) Plugin does not respect the jenkinsUrl configuration from configuration-as-code
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-59632 Plugin does not respect the jenkinsUrl configuration from configuration-as-code Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-10-02 20:02 Environment: Jenkins 2.176.3, plugin version 1.19.1 Priority: Major Reporter: R. Tyler Croy It appears the the "Jenkins URL" configuration in the main configuration is not properly over-writable from the configuration as code plugin. The configuration snippet below is always overwritten at runtime, it seems, with whatever the Kubernetes master Service IP turns out to be. In the case of my local testing of our Jenkins master image, which is not running in Kubernetes, after booting with the configuration below the "Jenkins URL" setting is `http://:` --- jenkins: clouds: - kubernetes: connectTimeout: 5 jenkinsUrl: "https://some-external-dns-entry/"
[JIRA] (JENKINS-58961) Cannot provision vm because of 'specify OS disk size' issue
Title: Message Title R. Tyler Croy commented on JENKINS-58961 Re: Cannot provision vm because of 'specify OS disk size' issue Just to make sure this detail isn't lost. We did not see any issues here until we tried the "Pool" retention strategy (in effect, 0 size disk, with pool retention). We have reverted our configuration to a Idle retention strategy with the default "0" size disk. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201308.1565947259000.5457.1566227820222%40Atlassian.JIRA.
[JIRA] (JENKINS-58997) Agents not cleaned up in the interface after being used
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-58997 Agents not cleaned up in the interface after being used Issue Type: Bug Assignee: Azure DevOps Attachments: aca.png Components: azure-container-agents-plugin Created: 2019-08-19 14:42 Environment: Azure Container Agents 1.1.0 Priority: Minor Reporter: R. Tyler Croy It's not clear to me what is causing this, but it just seems to naturally happen over time. Agents seem to be left in offline states but are not deleted at the end of their workload. We periodically run doDoDelete() through the Script Console to delete these :-/ Add Comment
[JIRA] (JENKINS-58893) ci.jenkins.io returns 404 when accessing BO for the very first time
Title: Message Title R. Tyler Croy commented on JENKINS-58893 Re: ci.jenkins.io returns 404 when accessing BO for the very first time This is a really annoying Blue Ocean bug which I don't think is with the infrastructure, since i've seen it on private Jenkins instances as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201189.1565304999000.1212.1565621100864%40Atlassian.JIRA.
[JIRA] (JENKINS-58861) Plugin believes the quota has been reached when no nodes are present.
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-58861 Plugin believes the quota has been reached when no nodes are present. Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2019-08-08 15:01 Environment: Jenkins LTS 2.176.22 Azure VM agents plugin 1.1.1 Priority: Major Reporter: R. Tyler Croy We noticed this behavior on ci.jenkins.io where a number of agents failed to provision due to timeout errors in the Azure API. The resource group was filled with VMs but there were not corresponding agents listed in Jenkins. Looking at the logs I noticed that the instance was complaining that it could not provision more machines due to the quota, despite very few agents actually being listed under /computer. After deleting the resource group in question, Jenkins started provisioning new agents while still complaining about the quota in the logs. I have no idea what happened here, but it seemed like the Azure timeout exceptions accumulated and caused some error condition with managing the quota.
[JIRA] (JENKINS-57207) Azure VM agents still provision when Jenkins is "preparing for shutdown"
Title: Message Title R. Tyler Croy commented on JENKINS-57207 Re: Azure VM agents still provision when Jenkins is "preparing for shutdown" I'm not entirely sure what good reproduction case would be, since I encountered this issue when: An Azure server side error (maximum deployments for quota) caused provisioning of agents to fail. I put Jenkins in "Prepare for Shutdown" mode I deleted deployments in Azure, allowing new deployments to be created. It might be reproducible if you disconnected a master from the network, so that it couldn't reach an Azure API. Then triggered a pipeline which would cause a VM to provision. Then once the plugin starts to try to provision, put the master in shutdown mode, and reconnect the network. Just a thought, but definitely a tricky failure to reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-57207) Azure VM agents still provision when Jenkins is "preparing for shutdown"
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-57207 Azure VM agents still provision when Jenkins is "preparing for shutdown" Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2019-04-27 15:52 Priority: Minor Reporter: R. Tyler Croy With the latest version of Jenkins and the plugin on ci.jenkins.io, I noticed today that even when the master is "preparing to shutdown" (i.e. the queue is in read-only mode, etc), the Azure VM Agents plugin continues to provision Azure agents. I would expect that "preparing for shutdown" would cause the agents not to provision Add Comment
[JIRA] (JENKINS-57204) Provision failures does not clean up deployments
Title: Message Title
R. Tyler Croy created an issue
Jenkins / JENKINS-57204
Provision failures does not clean up deployments
Issue Type:
Bug
Assignee:
Azure DevOps
Components:
azure-container-agents-plugin
Created:
2019-04-27 15:26
Priority:
Critical
Reporter:
R. Tyler Croy
We're seeing a number of failures on ci.jenkins.io which stem from Azure Container Agents failing to provision. It looks like failed ACI deployments don't get cleaned up automatically by the plugin. ACI is returning the following failure:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n \"error\": {\r\n \"code\": \"ServiceUnavailable\",\r\n \"message\": \"The requested resource is not available in the location 'eastus2' at this moment. Please retry with a different resource request or in another location. Resource requested: '2' CPU '4' GB memory 'Linux' OS\"\r\n }\r\n}"}]}
Which is annoying, but whatever. The bug here is that the plugin does not clean up this failed deployment, so we have exceeded our quota of Deployments of 800, all failures like this one! I recall this exact same issue in the Azure VM Agents plugin at one point as well.
[JIRA] (JENKINS-56869) Conditionals allOf anyOf and not behaving backwards
Title: Message Title R. Tyler Croy assigned an issue to Andrew Bayer These types of tickets are best suited for the JENKINS project in Jira. INFRA is for project infrastructure only, I've moved this over and re-assigned it Jenkins / JENKINS-56869 Conditionals allOf anyOf and not behaving backwards Change By: R. Tyler Croy Assignee: R. Tyler Croy Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56869) Conditionals allOf anyOf and not behaving backwards
Title: Message Title R. Tyler Croy moved an issue Jenkins / JENKINS-56869 Conditionals allOf anyOf and not behaving backwards Change By: R. Tyler Croy Project: Infrastructure Jenkins Key: INFRA JENKINS - 2067 56869 Workflow: classic default workflow JNJira + In-Review Component/s: pipeline Component/s: pipeline-library Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56824) VMs not cleaned up per retention policy when they are in a failed provisioning state.
Title: Message Title R. Tyler Croy commented on JENKINS-56824 Re: VMs not cleaned up per retention policy when they are in a failed provisioning state. Unfortunately I don't have a strong reproduction case, just behavior observed in production Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56824) VMs not cleaned up per retention policy when they are in a failed provisioning state.
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-56824 VMs not cleaned up per retention policy when they are in a failed provisioning state. Issue Type: Bug Assignee: Azure DevOps Attachments: windows-failed-azure.png, windows.failed.png Components: azure-vm-agents-plugin Created: 2019-03-31 19:21 Environment: Azure VM Agents 0.9.0, Jenkins 2.164.1 Priority: Minor Reporter: R. Tyler Croy This has happened a couple of times on ci.j.io. For whatever reason, we're not entirely sure, the init script for our Windows VMs sometimes fails. As a result, the agents are provisioned in Azure, but Jenkins fails to launch the JNLP agent on the machines. Unfortunately, Jenkins doesn't clean up these resources properly using our 20 minute idle retention policy. I discovered this morning that we had 50 VMs online for quite a few days, which never executed a single workload because their init script failed to run, and they were not cleaned up properly by the plugin.
[JIRA] (JENKINS-54119) ESlint rules are not applied on the client
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy Jenkins / JENKINS-54119 ESlint rules are not applied on the client Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54119) ESlint rules are not applied on the client
Title: Message Title R. Tyler Croy started work on JENKINS-54119 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-51451) BugBash session for Evergreen client/server setup
Title: Message Title R. Tyler Croy closed an issue as Won't Do Jenkins / JENKINS-51451 BugBash session for Evergreen client/server setup Change By: R. Tyler Croy Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-51449) Testing of P1 cases for evergreen client/server setup
Title: Message Title R. Tyler Croy closed an issue as Won't Do Jenkins / JENKINS-51449 Testing of P1 cases for evergreen client/server setup Change By: R. Tyler Croy Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-50534) git-plugin quality audit for Evergreen
Title: Message Title R. Tyler Croy closed an issue as Won't Do Jenkins / JENKINS-50534 git-plugin quality audit for Evergreen Change By: R. Tyler Croy Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-51425) Define quality bar for client/server setup
Title: Message Title R. Tyler Croy closed an issue as Won't Do Jenkins / JENKINS-51425 Define quality bar for client/server setup Change By: R. Tyler Croy Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.
