@slide https://github.com/jenkinsci/docker-agent#configurations still references
jenkins4eval as a Windows image source. Should I change it to jenkins/agent` and call them official in this release?
1 reply
@slide Trusted CI runs for Windows images fail due to the lack of agents
[Pipeline] }
21:09:48 Still waiting to schedule task
21:09:48 All nodes of label ‘windock’ are offline
22:09:33 Cancelling nested steps due to timeout
[Pipeline] // nodeDid we mess it up while migrating agents from Azdue to AWS? CC @olblak
Same for ci.jenkins.io, https://ci.jenkins.io/job/Packaging/job/docker-agent/job/master/2/console . Looking for logs there
com.microsoft.azure.vmagent.exceptions.AzureCloudException: AzureVMCloud: createProvisionedAgent: Deployment Failed: Microsoft.Compute/virtualMachines:win2019-982351 - Conflict - {status=Failed, error={code=ResourceDeploymentFailure, message=The resource operation completed with terminal provisioning state 'Failed'., details=[{code=OSProvisioningClientError, message=OS Provisioning for VM 'win2019-982351' did not finish in the allotted time. However, the VM guest agent was detected running. This suggests the guest OS has not been properly prepared to be used as a VM image (with CreateOption=FromImage). To resolve this issue, either use the VHD as is with CreateOption=Attach or prepare it properly for use as an image:
* Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/
* Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/ }]}}
at com.microsoft.azure.vmagent.exceptions.AzureCloudException.create(AzureCloudException.java:37)
at com.microsoft.azure.vmagent.AzureVMCloud.createProvisionedAgent(AzureVMCloud.java:586)
at com.microsoft.azure.vmagent.AzureVMCloud$2.call(AzureVMCloud.java:831)
at com.microsoft.azure.vmagent.AzureVMCloud$2.call(AzureVMCloud.java:809)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
@slide @timja Hi. I have hit an issue with undocumented
latest agent image tag for Windows. I suggest to disable itwhile we figure out better naming: jenkinsci/docker-agent#126
which image are you trying to publish?
oh, duh, agent
Which build is it on trusted?
@oleg-nenashev it looks like the Jenkinsfile doesn't have the tag publishing code
Let me PR it
Yes, the ssh-agent and inbound-agent have the tag stuff already
So... 4.3-4 then? :)
You want me to merge that PR?
Once the release is done you may need to manually launch the repo scan and then to trigger the tag build for Windows @slide
Shouldn't release drafter pick up my changes automatically and create notes in the unreleased version?
@slide while we are here, what do we do with the SSH images?
jenkins/ssh-agent or jenkins/ssh-build-agent?
If we take the first name, I will need to drop Windows builds as well there
... tags
@slide I will proceed with ssh-agent. I have the IDE open, so I will do it quickly