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
    @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)
    Mark Waite
    @MarkEWaite

    @ScottAShipp_twitter you can define Jenkins configuration with the Docker image in several different ways.

    For example, files in the ref directory of the image you define (based on the jenkins/jenkins) will be placed into the working Jenkins image. I used that technique to store job configuration XML files, credential files, and more. Works great. I install plugins that way using a git large file storage repository. Records the exact versions of plugins I'm using without requiring that I insert their version numbers into a configuration file.

    You can define the exact version of plugins you want and call the plugin install script as described at https://github.com/jenkinsci/docker/blob/master/README.md#preinstalling-plugins .

    If you'd like to see a sample, refer to https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins

    You can use the configuration as code plugin and define your Jenkins configuration with a YAMLfile in the Docker image

    Scott Shipp
    @ScottAShipp_twitter
    Thank you @MarkEWaite @slide
    Scott Shipp
    @ScottAShipp_twitter
    @MarkEWaite I have the plugins stuff already. The stuff I'm interested in is what you said about the ref directory. I need to add configuration, for example, for our internal LDAP, Nexus repository, Gitlab keys, and so forth.
    I will dig in to documentation on that ref feature
    Mark Waite
    @MarkEWaite
    @ScottAShipp_twitter the configuration for those items is most likely supported by the Configuration as Code plugin so that you can express the configuration in an easy to read YAML format rather than storing XML conifguration files. However, there are still some plugins that don't support configuration as code plugin. In those cases, storing the XML files in the ref directory works just fine.
    Scott Shipp
    @ScottAShipp_twitter
    Thanks @MarkEWaite
    New question for you all. Is it better to use jenkins/jenkins and install Blue Ocean plugins separately, or to use the jenkinsci/blueocean as a base
    Both seem to have documentation which says "this is the recommended Docker image to use for Jenkins"
    or similar
    Mark Waite
    @MarkEWaite
    The jenkinsci/blueocean image provides some specific features that are needed in the Jenkins tutorial environment (like Docker in Docker). As far as I can tell, most users prefer the image without those tutorial centered features. I use jenkins/jenkins
    Scott Shipp
    @ScottAShipp_twitter
    Good to know, thanks
    Mark Waite
    @MarkEWaite
    We hope to eventually rework the tutorials to not require Docker in Docker, but it is so convenient to run a Python docker image or a NodeJS Docker image from the tutorial environment. Production users don't usually need the same simplicity (single computer, low compute use, etc.) that a tutorial user needs
    Scott Shipp
    @ScottAShipp_twitter
    We started with jenkins/jenkins, but when reading https://www.jenkins.io/doc/book/installing/#downloading-and-running-jenkins-in-docker it very strongly and confidently suggests only using the jenkinsci/blueocean image. "There are several Docker images of Jenkins available. The recommended Docker image to use is the jenkinsci/blueocean image (from the Docker Hub repository)"
    I wonder if that should be updated. It doesn't mention tutorials
    Mark Waite
    @MarkEWaite
    Yes, sorry about that confusing and conflicting information. Could you use the "Report an issue" link at the bottom left of that page to report that inconsistency? We'll get it fixed
    That is a good one for next week's user experience Hackfest. Docs are part of the user experience...
    Scott Shipp
    @ScottAShipp_twitter
    Sure thing!
    Bartłomiej Zieliński
    @fasolens
    Hi, is it possible to run docker.image('maxys/docusaurus-pdf:latest').withRun ("from-build --no-sandbox -v /var/jenkins_home/workspace/docs:/workspace -o /workspace/build/internal.pdf /workspace/build docs/Docusaurus/DocusaurusGetStarted docs") in any way?
    The argument is without - or -- and when I do it the way above Jenkins try to pull 'customArgument' image.
    By default the image is put at the end of command during job run and looks like this:
    docker run -d from-build --no-sandbox -o build/img/internal.pdf build docs/Docusaurus/DocusaurusGetStarted docs maxys/docusaurus-pdf:latest Unable to find image 'from-build:latest' locally docker: Error response from daemon: pull access denied for from-build, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
    Alex Earl
    @slide
    Hi @fasolens, you probably want the normal https://gitter.im/jenkinsci/jenkins channel is more geared towards using the docker containers that Jenkins provides
    Bartłomiej Zieliński
    @fasolens
    Hi @slide , yeah, that is wrong channel. I have solved the problem. Thanks
    spaceygithub
    @spaceygithub
    Hello All, good afternoon to you. I'm looking for a little help to better understand the docker jenkins/inbound-agent image. I've lots of jobs that need tools installing on the inbound-agent. I'd like to check my understanding is correct and that if i wish to install build tools on to the agent I'll need to make my own docker file and then install via apt-get or yum. Sorry I'm not actually clear what o/s the agent is running.
    Second part of the question... If i try and start the jenkins/inbound-agent locally on my laptop, with a view to then login via docker exec interactive bash shell etc etc. I can't because the image won't actually start unless it can connect to a jenkins master. Is there any way around this to allow me to test my build tools?
    Alex Earl
    @slide
    Yes, you would want to use the inbound-agent in a FROM to install additional tools for your requirements. In terms on testing, you should be able to pass /bin/bash to docker run to start a shell instead of trying to use exec