Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Saveliy Yusufov
    @smu160
    I have a basic working Jenkinsfile, and I'd like to actually add in my building and testing into it. I have:
    pipeline {
        agent {
            label 'cuda'
        }
        stages {
            stage('testing 123') {
                steps {
                    sh 'nvidia-smi'
                }
            }
        }
    }
    Where would I put the docker-workflow (https://docs.cloudbees.com/docs/admin-resources/latest/plugins/docker-workflow) style build steps in my Jenkinsfile?
    Oleg Nenashev
    @oleg-nenashev
    Would appreciate feedback w.r.t Docker agent image naming in https://groups.google.com/forum/#!topic/jenkinsci-dev/oxD-Hd_7l9k
    @/all Just a heads-up, we are renaming agent images today and tomorrow. There should be no disruptions for common Jenkins users. https://groups.google.com/forum/#!topic/jenkinsci-dev/oxD-Hd_7l9k
    Oleg Nenashev
    @oleg-nenashev
    @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
    Alex Earl
    @slide
    @oleg-nenashev yes, that would be great
    Oleg Nenashev
    @oleg-nenashev

    @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] // node

    Did 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)
    Alex Earl
    @slide
    It should be fixed on ci.j.io
    Alex Earl
    @slide
    trusted.ci is good now too
    Oleg Nenashev
    @oleg-nenashev
    Confirmed
    Oleg Nenashev
    @oleg-nenashev
    @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
    Tim Jacomb
    @timja
    :thumbsup:
    Oleg Nenashev
    @oleg-nenashev
    @slide Hi. How do you actually deliver Windows agent releases at the moment? /job/Containers/job/Windows/job/docker/job/docker-agent/view/tags/ on trusted CI does not show any build history for tags, but I see they were deployed by jenkinsinfraadmin
    Oleg Nenashev
    @oleg-nenashev
    So my proposal is to... Do a 4.3-2 release an official release for the renaming. After that we do 4.3-3 where we make Windows agents fully official and ship them from the same DockerHub repo
    Oleg Nenashev
    @oleg-nenashev
    I am shipping 4.3-3 for docker-agent to ensure there is no collisions for tagged releases. I cannot just spin Windows images release without burning a version, because it picks up Jenkinsfile from a tag
    Oleg Nenashev
    @oleg-nenashev
    @slide I tried the Pipeline again, and looks like it just does not publish versions to jenkins/agent DockerHub. Maybe I am missing something
    Alex Earl
    @slide
    on trusted?
    which image are you trying to publish?
    oh, duh, agent
    Oleg Nenashev
    @oleg-nenashev
    Yes. The build passed, but publishing steps do not get invoked for a tag build. Did not dive further, got interrupted
    Alex Earl
    @slide
    ah, I haven't had a way to test that, so I may need to fix something. Is this on trusted that you are looking?
    Which build is it on trusted?
    @oleg-nenashev it looks like the Jenkinsfile doesn't have the tag publishing code
    Let me PR it
    Alex Earl
    @slide
    Oleg Nenashev
    @oleg-nenashev
    :+1: will we need to patch all other images?
    Alex Earl
    @slide
    No, I think I had added that to my PR's for Windows changes already, but let me check
    Yes, the ssh-agent and inbound-agent have the tag stuff already
    Oleg Nenashev
    @oleg-nenashev
    Nice, thanks!
    So... 4.3-4 then? :)
    Alex Earl
    @slide
    Sure :)
    You want me to merge that PR?
    Oleg Nenashev
    @oleg-nenashev
    @slide go for it, I will get to the laptop only in 2 hours or so. If you do the release for jenkins/agent, I will try to do the remaining work for downstream images afterwards
    Alex Earl
    @slide
    Ok, I'll try and follow the youtube video :)
    Oleg Nenashev
    @oleg-nenashev
    There is a lot of blah-blah-blah there. Just cut a release from GitHub, and let robots do the rest :)
    Once the release is done you may need to manually launch the repo scan and then to trigger the tag build for Windows @slide
    Alex Earl
    @slide
    oh, that's a bummer, can't we have that done automatically?
    Shouldn't release drafter pick up my changes automatically and create notes in the unreleased version?
    Tim Jacomb
    @timja
    i assume trusted isn't reachable from the internet
    Alex Earl
    @slide
    not directly, no
    Alex Earl
    @slide
    ok, we'll see if I got the release right...
    Oleg Nenashev
    @oleg-nenashev
    Edited the changelog a bit, but should be fine overall
    @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
    Alex Earl
    @slide
    I'm fine either way, I can make the Windows changes if needed
    Tim Jacomb
    @timja
    RE: release drafter, it will but the SaaS app is slow sometimes, github action ones are instant though
    Alex Earl
    @slide
    ah