Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    halkeye
    @halkeye:g4v.dev
    [m]
    are you sure? cause its saying its not there, I would try running docker-compose run jenkins ls -l /var/jenkins/home to confirm. Also this channel is for creating the jenkins packaging, not for jenkins help, I would recommend going to jenkinsci/jenkins room
    Sam Martin
    @sammartin:matrix.org
    [m]
    ok thanks
    Carlos Carvalho
    @cccarv82
    i'm trying to run a pipeline using docker agent in a jenkins/jenkins:lts-jdk11 docker image but the pipeline fails to run.
    /var/jenkins_home/workspace/rf-web-poc@tmp/durable-2d5d64cb/script.sh: 1: docker: not found
    halkeye
    @halkeye:g4v.dev
    [m]
    @cccarv82: jenkins docker image doesn't have docker cli. You'll have to extend the image, or use an agent outside of your controller (recommended)
    mangitkaur
    @mangitkaur
    Hi Team , please help, I am unable to update my kubernetes cluster with latest plugins, even though I have copied over newer version plugins via plugin-manager cli tool
    I am trying to upgrade few plugins because their older versions are causing dependencies issue, however when add them using plugin manager jar, they dont get updated in Kubernetes container, however they are in my image
    João Gabriel Bortot Cadore
    @joaobortotcadore

    Hi team.. I'm working with a project that uses espressif and to build it on my machine with docker way I do the following:

    docker run --rm -v $PWD:/project -w /project espressif/idf:v4.2.2 idf.py build (note that, first of all I make a cd to the project directory and then the PWD environment variable passes the correct path for mounting the volume)

    I would like to elaborate a declarative pipeline, and I would like to execute the command equivalent to the one above. The way I implemented it based on other examples that worked, and the log result below.

    I don't understand why the way to pass these 'idf.py build' arguments in the 'steps' block is not working. Does anyone have any ideas?

    My pipeline:

    pipeline {
        agent any
    
        environment {
            PROJ_NAME = 'test'
        }
        stages {
            stage('Checkout') {
                steps {
                    git url: 'ssh://git@bitbucket.org/joaogbc/iot-project.git'
                }
            }
            stage('Build') {
                agent {
                    docker {
                        image 'espressif/idf:v4.2.2'
                        args '--rm -v $PWD:/project -w /project'
                        reuseNode true
                    }
                }
                steps{
                    sh 'idf.py build'
                }
            }
        }
    }

    Error snippet:

    [Pipeline] withDockerContainer
    Jenkins does not seem to be running inside a container
    $ docker run -t -d -u 1000:1000 --rm -v $PWD:/project -w /project -w /var/lib/jenkins/workspace/iot-project-TEST -v /var/lib/jenkins/workspace/iot-project-TEST:/var/lib/jenkins/workspace/iot-project-TEST:rw,z -v /var/lib/jenkins/workspace/iot-project-TEST@tmp:/var/lib/jenkins/workspace/iot-project-TEST@tmp:rw,z -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** espressif/idf:v4.2.2 cat
    $ docker top 81920a1146eabe9bf5c08339a682d81ac23777de0421895e1184d2a8ef27fc8c -eo pid,comm
    ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements).
    Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`.
    [Pipeline] {
    [Pipeline] sh
    + idf.py build
    /var/lib/jenkins/workspace/iot-project-TEST@tmp/durable-b8bf6ce0/script.sh: 1: /var/lib/jenkins/workspace/iot-project-TEST@tmp/durable-b8bf6ce0/script.sh: idf.py: not found
    [Pipeline] }
    $ docker stop --time=1 81920a1146eabe9bf5c08339a682d81ac23777de0421895e1184d2a8ef27fc8c
    $ docker rm -f 81920a1146eabe9bf5c08339a682d81ac23777de0421895e1184d2a8ef27fc8c
    [Pipeline] // withDockerContainer
    [Pipeline] }
    [Pipeline] // stage
    [Pipeline] }
    [Pipeline] // withEnv
    [Pipeline] }
    [Pipeline] // node
    [Pipeline] End of Pipeline
    ERROR: script returned exit code 127
    Finished: FAILURE
    I've already managed to successfully headless-build with the eclipse image as follows:
    stage('Build') {
        agent {
            docker {
                image 'tool/stm32-cubeide-image:1.0'
                reuseNode true
            }
        }
        steps {
            sh '/opt/stm32cubeide/headless-build.sh -importAll $WORKSPACE -data $WORKSPACE -cleanBuild  $DIR/$OPT_BUILD'
        }
    }
    dduportal
    @dduportal:matrix.org
    [m]
    @timja: I'm not sure to understand why is jenkinsci/docker#1456 a docker (image) issue? If I understand correctly, it's the jenkins-plugin-cli which fails the plugin installation?
    Tim Jacomb
    @timja
    no it's a bash function that does version comparison bundled in the image
    dduportal
    @dduportal:matrix.org
    [m]
    @timja: i thought we got rid of the shell script install-plugins.sh (which was using the versionLT() bash function as far as I remember) ?
    7 replies
    Tim Jacomb
    @timja
    yes but plugins aren't in the image outside of the volume and then there's a script here that copies them:
    https://github.com/jenkinsci/docker/blob/00d1edcbf6e0bd78ff5b359731310b91bdac9b07/jenkins-support#L42
    dduportal
    @dduportal:matrix.org
    [m]
    oh I see, it's the "copy plugins at startup" script. Thanks for the explanation!
    halkeye
    @halkeye:g4v.dev
    [m]
    its kinda a jenkins core + docker issue. install plugin ci puts it in jenkins ref, and jenkins core only copies ref if the file doesn't exist.
    oh my bad, not core, is purely docker?
    dduportal
    @dduportal:matrix.org
    [m]
    Pure docker (pure shell even!)
    Rein Petersen
    @ReinsBrain
    Hi all, ive made a docker-compose.yml and Dockerfile for jenkins with the hope that I'll be able to locally test jobs and have it all automated so i don't need the web UI ... not immediately apparent is the best way to go about automation of creating jobs. Ive been trying to use jenkins-cli and a little bit hung up on auth ... or should i just place files in the right places in jenkins_home? Any advice is greatly appreciated :)
    another thing i'd like to do is just pass the admin password as a build arg ( or better way? )
    hervelemeur
    @hervelemeur:matrix.org
    [m]
    Rein Petersen
    @ReinsBrain

    have it all automated

    Use https://www.jenkins.io/projects/jcasc/ with job-dsl-plugin: https://github.com/jenkinsci/job-dsl-plugin/blob/master/docs/JCasC.md :)

    Well... that's just super-interesting and super-helpful - thanks a whole bunch :)

    hervelemeur
    @hervelemeur:matrix.org
    [m]
    there is even a dedicated channel for it if you need additional help: https://matrix.to/#/#jenkinsci\_configuration-as-code-plugin:gitter.im
    Rein Petersen
    @ReinsBrain

    there is even a dedicated channel for it if you need additional help: https://matrix.to/#/#jenkinsci\_configuration-as-code-plugin:gitter.im

    Im having trouble with the link, says "does not exist"

    hervelemeur
    @hervelemeur:matrix.org
    [m]
    I think it depends what you're using to view irg/gitter channels (I'm using Element for example)
    Try searching it from whatever you're using
    Rein Petersen
    @ReinsBrain
    thanks i will try d/l Element client
    Rein Petersen
    @ReinsBrain
    image.png
    @hervelemeur:matrix.org i have the element client for windows but the link doesn't seem to work out still:
    hervelemeur
    @hervelemeur:matrix.org
    [m]
    🤷
    search it manually ;)
    hervelemeur
    @hervelemeur:matrix.org
    [m]
    :point_up: Edit: 🤷
    search "jenkinsci/configuration-as-code" manually ;)
    Rein Petersen
    @ReinsBrain

    :point_up: Edit: 🤷
    search "jenkinsci/configuration-as-code" manually ;)

    found it! thanks :)

    Mayhem Bill
    @MayhemBill
    okay, I'm not sure what I'm doing wrong, but I am running Jenkins in Docker, and I am trying to create an image from a dockerfile, but when I try to run the docker command in the container I get a permission denied, and anything I change in the Jenkins container just gets reset after a reboot
    dduportal
    @dduportal:matrix.org
    [m]

    Hello @timja @MarkEWaite I'm investigating jenkinsci/docker-inbound-agent#279 and I discovered that the build of the main branch does NOT use the "latest" released version:

    Should we slighlty change the release process for this (and jenkins/agent as well)?

    FWIW, I'm opening a PR to leverage the risk + bump the version
    Tim Jacomb
    @timja
    @dduportal:matrix.org not sure I understand the issue
    it would be easier if they were in the same repository
    dduportal
    @dduportal:matrix.org
    [m]
    @timja: what is the "usual" release process for the docker images of the jenkins agents? Is it the draft release being published? (I wonder given the new version scheme is used, if there is a CD process ?)

    it would be easier if they were in the same repository

    +100

    Tim Jacomb
    @timja
    it's not using a new version scheme
    it uses the remoting version
    and versions always match that
    dduportal
    @dduportal:matrix.org
    [m]
    I though that the suffix -X was specific to the images, doesn't it?
    Tim Jacomb
    @timja
    the release process is, release the docker-agent repo via github releases.
    trigger it on trusted.ci.
    once green release docker-inbound-agent via github releases
    trigger it on trusted.ci
    yes it is that is extracted from the tag
    dduportal
    @dduportal:matrix.org
    [m]
    Ok, so the release process looks flawed: I would expect the "remoting version" to be infered from the tag then, right ?
    Tim Jacomb
    @timja
    it is inferred
    dduportal
    @dduportal:matrix.org
    [m]
    Oh i see. Then we should NOT deploy images if the build is not triggered by a tag