Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    hervelemeur
    @hervelemeur:matrix.org
    [m]
    I'll probably add this issue to my list
    learning go on updatecli ^^
    halkeye
    @halkeye:g4v.dev
    [m]
    i think its better to fix the plugin manager cli than to maintain a seperate tool, but its your time :)
    hervelemeur
    @hervelemeur:matrix.org
    [m]
    the thing is I'm not currently (re)learning java :P
    DoofusCanadensis
    @kenrachynski:matrix.org
    [m]
    heh
    Tim Jacomb
    @timja
    for people who can't use renovate there's always this: jenkins-infra/docker-jenkins-weekly#442
    DoofusCanadensis
    @kenrachynski:matrix.org
    [m]
    oh! renovate is Jenkins-specific... I thought it was just another generic GitHub tool
    halkeye
    @halkeye:g4v.dev
    [m]
    no, renovate is a generic tool - https://www.whitesourcesoftware.com/free-developer-tools/renovate/
    In my opinion, far surperior to dependabot that only handles a couple package managers.
    updatecli is the one jenkins-infra created
    DoofusCanadensis
    @kenrachynski:matrix.org
    [m]
    Oh the link I was reading was for the Jenkins module for renovate
    dduportal
    @dduportal:matrix.org
    [m]
    jenkinsci/docker#1326 => to fix the missing arm64 images
    I need maintainer review
    Mark Waite
    @MarkEWaite
    Reviewed and explored jenkinsci/docker#1326 from my Ubuntu 20.04 machine and found no issues. I think we should consider delaying the execution of that change until Monday morning so that we have more time to handle surprises if they happen
    kenrachynski
    @kenrachynski:matrix.org
    [m]
    well, I'll give Jenkins points for persistence. this one job has been waiting for a "dind" agent for 26 days
    DoofusCanadensis
    @kenrachynski:matrix.org
    [m]
    I'll probably have to rebuild this job to build using kaniko or img because all the docker in kubernetes articles I've seen so far assume that kubernetes is using docker as its container engine. I'm not
    or maybe podman/buildah
    halkeye
    @halkeye:g4v.dev
    [m]
    It probably shouldn't matter. If you expose the containerd socket you can still probably use docker.
    DoofusCanadensis
    @kenrachynski:matrix.org
    [m]
    yeah, I don't actually want to reduce my security thusly
    halkeye
    @halkeye:g4v.dev
    [m]
    true dind should also work, a privledged container running dockerd
    DoofusCanadensis
    @kenrachynski:matrix.org
    [m]
    despite the "don't use the controller image, use the master image". d00d, they're the same thing
    dduportal
    @dduportal:matrix.org
    [m]
    @timja: @MarkEWaite The build that are fixing the jenkinsci/docker images takes more than 1 hour to be executed, which hits the 1 hour hard timeout. I don't see the "faulty" manifest being updated (example: skopeo inspect --raw docker://docker.io/jenkins/jenkins:2.319.1-alpine ) in the DockerHub: I assume that manifest are only updated once buildx finished all its build.
    To fix that, I'll replay the principal build on trusted.ci, on the weekly 2.318 which is out of the publish scope (last weekly before the N-1 LTS - 2.319.1-) and i'll test that it behaves as expected.
    Once ok (e.g. once manifest fixed + publish script forced to this version to see it as "published"), then I'll replay version per version until all is fixed
    Tim Jacomb
    @timja
    thanks
    dduportal
    @dduportal:matrix.org
    [m]
    (sorry, tha might be messy, hence the step by step on older and almost never used versions)
    dduportal
    @dduportal:matrix.org
    [m]
    ok, so it is interesting. When doing a "docker buildx bake --push", the manifest is pushed as application/vnd.docker.distribution.manifest.v2+json if there is only 1 CPU arch. It only updates it when adding another CPU arch.
    It means that my update in the PR jenkinsci/docker#1326 is not enough, because it assumed implicitly that all manifest are application/vnd.docker.distribution.manifest.list.v2+json . I realize that now: I need to update the script.
    dduportal
    @dduportal:matrix.org
    [m]
    For information :)
    dduportal
    @dduportal:matrix.org
    [m]
    => what is new is that the jenkinsci DockerHub organisation is now badged (for DockerHub users) as "Open Source Program", e.g. clearly more trustable than dduportal for instance :p
    DoofusCanadensis
    @kenrachynski:matrix.org
    [m]
    well no, jenkinsci is listed as deprecated, please see jenkins
    1 reply
    jenkinsci updated the blueocean image 7 hours ago as well
    but still, nice work getting that badge!
    halkeye
    @halkeye:g4v.dev
    [m]
    Yea ci.blueocean.io still needs to be shutdown sometime
    halkeye
    @halkeye:g4v.dev
    [m]
    (which is where that image is generated, and has probalby not been updated jenkins wise since I was at CB)
    DoofusCanadensis
    @kenrachynski:matrix.org
    [m]
    eep
    dduportal
    @dduportal:matrix.org
    [m]
    https://twitter.com/_crev_/status/1524375218449485826?s=21&t=L0pO8WHkl4YuYiNFTRIz4g that could help a lot to help visualizing the jenkins/docker-*-agent links to each other’s \o/
    hervelemeur
    @hervelemeur:matrix.org
    [m]
    tested dockerfilegraph:
    hervelemeur
    @hervelemeur:matrix.org
    [m]
    Hello there, anyone know if it's possible to make this cst test "portable" so I can use it on Linux and on Windows?
    Tim Jacomb
    @timja
    no idea
    hervelemeur
    @hervelemeur:matrix.org
    [m]
    Looking around I don't think so :/
    As I intended to finally do, it seems they add a specific cst.yml for windows
    dduportal
    @dduportal:matrix.org
    [m]
    damn :'(
    hervelemeur
    @hervelemeur:matrix.org
    [m]
    jenkins-infra/helpdesk#2873, the gift that never ends :D
    dduportal
    @dduportal:matrix.org
    [m]
    -DskipTests=true 🧌
    hervelemeur
    @hervelemeur:matrix.org
    [m]
    I'm seriously thinking about it ^^
    currently setting up a "-windows" prefix for windows cst tests, with a fileExist test in the final script
    dduportal
    @dduportal:matrix.org
    [m]
    hervelemeur: this is definitively acceptable to skip the "test" steps for the windows container for this first step. The lint, build, deploy is already a strong first step