by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Oleg Nenashev
    @oleg-nenashev
    Tag build: /job/Containers/job/Windows/job/docker/job/docker-inbound-agent/view/tags/job/4.3-2/
    Alex Earl
    @slide
    can we clean up the branches after all the tags are successfully pushed? :)
    Oleg Nenashev
    @oleg-nenashev
    Done, you should not need to wait for builds
    I am keeping jdk11 and alpine branches for historical reasons (before DockerHub added support of custom Dockerfile names), but the rest is cleaned
    Alex Earl
    @slide
    thanks :)
    Oleg Nenashev
    @oleg-nenashev
    @slide Looks like ssh-agent doest not publish releases for Windows after all
    Alex Earl
    @slide
    let me look
    Oleg Nenashev
    @oleg-nenashev
    For this image we use another format, and hence the block is just skipped
    Alex Earl
    @slide
    ok, I can fix that up
    I should have thought of that...
    Oleg Nenashev
    @oleg-nenashev
    nws
    Also, I made a mistake in https://hub.docker.com/r/jenkins/inbound-agent DockerHub configuration. We might need a 4.3-3 tag to retrigger publishing
    Better to verify /job/Containers/job/Windows/job/docker/job/docker-inbound-agent/view/tags/job/4.3-2/1/console first, of course
    Alex Earl
    @slide
    it's at the testing stage right now
    Oleg Nenashev
    @oleg-nenashev
    Failed, looks like wrong version parameter is used:
    00:43:28  Step 1/8 : ARG VERSION=4.3-4
    00:43:28  Step 2/8 : FROM jenkins/agent:${VERSION}-nanoserver-1809
    00:43:28  docker : manifest for jenkins/agent:4.3-2-nanoserver-1809 not found: manifest unknown: manifest unknown
    00:43:28  
    00:43:28  At line:1 char:1
    00:43:28  
    00:43:28  + docker build --build-arg VERSION='4.3-2' -t jenkins/inbound-agent:nan ...
    00:43:28  
    00:43:28  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    00:43:28  
    00:43:28      + CategoryInfo          : NotSpecified: (manifest for je...anifest unknown:String) [], RemoteException
    00:43:28  
    00:43:28      + FullyQualifiedErrorId : NativeCommandError
    00:43:28  
    00:43:28   
    00:43:28  
    00:43:28  Building  => tag=4.3-2-nanoserver-1809-jdk8
    00:43:28  Sending build context to Docker daemon  10.75kB
    00:43:28  
    00:43:28  Step 1/8 : ARG VERSION=4.3-4
    00:43:28  Step 2/8 : FROM jenkins/agent:${VERSION}-nanoserver-1809
    00:43:28  docker : manifest for jenkins/agent:4.3-2-nanoserver-1809 not found: manifest unknown: manifest unknown
    00:43:28  
    00:43:28  At line:1 char:1
    00:43:28  
    00:43:28  + docker build --build-arg VERSION='4.3-2' -t jenkins/inbound-agent:4.3 ...
    00:43:28  
    00:43:28  + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    00:43:28  
    00:43:28      + CategoryInfo          : NotSpecified: (manifest for je...anifest unknown:String) [], RemoteException
    00:43:28  
    00:43:28      + FullyQualifiedErrorId : NativeCommandError
    00:43:28
    @slide It is quite late in my timezone. Would you be fine if I leave it as is? You can release inbound-agent and ssh-agent with fixes if you want to do it and have time. If not, I will just get it over the line tomorrow
    Alex Earl
    @slide
    ok, will look at them
    Oleg Nenashev
    @oleg-nenashev
    ty
    For inbound-agent there is definitely a mix of jenkins-agent and jenkins-inbound-agent versions for tag builds. Not sure what is the easiest fix, maybe not overriding vestion from make.ps at all
    Alex Earl
    @slide
    Thanks you!
    Oleg Nenashev
    @oleg-nenashev
    Or having a second paremeter...
    Oleg Nenashev
    @oleg-nenashev
    @slide Looks like Windows agents are not being published anyway in new releases
    Alex Earl
    @slide
    Yeah, I worked on it and then had a giant headache
    Oleg Nenashev
    @oleg-nenashev
    Same for me :( Anyway, no hurry. It's done when it's done
    I suggest we do a more formal announcement for official Windows images availability next week
    Alex Earl
    @slide
    Sounds good
    Tom Mortimer-Jones
    @morty
    The ssh-slave docker image is based on openjdk:8-jdk. This upstream image seems to have changed from Debian Stretch to Buster recently. This has broken my build and probably has for other people too. Obviously I can fork your github repo, change the Dockerfile to use openjdk:8-jdk-stretch and push an image to my dockerhub account. But this isn't ideal.
    29 replies
    Graeme Wilson
    @techlunacy
    hi would this be a reasonable place to ask a question about the jenkins helm chart? or if not a recommendation for where would be?
    Tim Jacomb
    @timja

    jenkinsci on kubernetes slack

    jenkins-ci
    Graeme Wilson
    @techlunacy
    thanks, that of course is blocked on this network
    i will find a way
    Tim Jacomb
    @timja
    phone? :D
    Graeme Wilson
    @techlunacy
    :D
    Alex Earl
    @slide
    @oleg-nenashev would you be ok with giving me access to dockerhub for the jenkins repo so I can help?
    2 replies
    Oleg Nenashev
    @oleg-nenashev
    @slide sure, will do it on the morning
    Alex Earl
    @slide
    Thanks
    Oleg Nenashev
    @oleg-nenashev
    Docker agent images renaming is announced: https://twitter.com/jenkinsci/status/1258351572377051138
    Scott Shipp
    @ScottAShipp_twitter
    Hi does anyone know if there's a way to install and use Maven using a Dockerfile? Is it just a matter of setting MAVEN_HOME
    Alex Earl
    @slide
    @ScottAShipp_twitter There are docker images for Maven that you can use as a base for your image
    Scott Shipp
    @ScottAShipp_twitter
    Right now I have jenkins/jenkins:jdk11 should I be using something else
    Alex Earl
    @slide
    Oh, you are trying to do a master?
    Scott Shipp
    @ScottAShipp_twitter
    Yeah
    Alex Earl
    @slide
    Why do you want maven on the master? normally you would spin up other docker containers as agents to do the actual builds
    Scott Shipp
    @ScottAShipp_twitter
    Probably because I don't know what I don't know ;) One thing that I have to work on is we have an internal Nexus repository, and I need to provide a settings.xml for Maven that has the correct repository configuration and credentials
    Alex Earl
    @slide
    You can do that via docker and mounting a volume
    Scott Shipp
    @ScottAShipp_twitter
    Does anyone know if there's a way with the jenkins/jenkins Docker image to preconfigure Jenkins in an automated way? Or do most people manually set it up and persist the volume
    Alex Earl
    @slide
    @ScottAShipp_twitter you can use the install-plugins.sh to have plugins installed, and provide reference files for various things (init groovy scripts, etc)