Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Alex Earl
    @slide
    Great meeting! I like the new meeting time, thanks @MarkEWaite for being so flexible
    Mark Waite
    @MarkEWaite
    Thanks @slide!
    Jim Crowley
    @james-crowley
    @MarkEWaite Sorry about missing the meeting today. Had it on my work calendar but not personal calendar. I'll watch the video and catch up with you!
    Mark Waite
    @MarkEWaite
    Thanks @james-crowley
    Jim Crowley
    @james-crowley
    @MarkEWaite I assume since your away from home the videos will be uploaded later? Was just looking for them on the youtube play list
    Mark Waite
    @MarkEWaite
    Oops, forgot to upload them. No excuse for that, just forgot.
    Jim Crowley
    @james-crowley
    All good take your time!
    Alex Earl
    @slide
    @james-crowley The publish experimental is currently failing, see https://ci.jenkins.io/blue/organizations/jenkins/Packaging%2Fdocker/detail/master/5293/pipeline/158, I am wondering if I am missing something in how it should be done. The Jenkinsfile is doing this:
     sh 'make publish-tags'
     sh 'make publish-manifests'
    errors
    no such manifest: docker.io/jenkins4eval/jenkins:2.270-debian-arm64
    
    [2020-12-08T18:13:33.438Z] Pulling 2.270-debian-arm64
    
    [2020-12-08T18:13:33.697Z] Error response from daemon: manifest for jenkins4eval/jenkins:2.270-debian-arm64 not found: manifest unknown: manifest unknown
    
    [2020-12-08T18:13:33.697Z] Makefile:131: recipe for target 'publish-tags-latest' failed
    Tim Jacomb
    @timja
    Ha, got my m1 mac and Jenkins isnt running too well on it :(, going to have a bit more of a dig but at least 1 issue is with jna port not finished yet, jenkins test rule completely bombs out too :(
    Gavin Mogan
    @halkeye
    Tim Jacomb
    @timja
    hmm test rule might have actually just been that plugin
    most of the errors I see are related
    to ProcessTree
    java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native
        at hudson.util.ProcessTree$Darwin.<clinit>(ProcessTree.java:1828)
        at hudson.util.ProcessTree.get(ProcessTree.java:457)
        at hudson.Launcher$LocalLauncher.kill(Launcher.java:1015)
        at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:525)
        at hudson.model.Run.execute(Run.java:1907)
        at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
        at hudson.model.ResourceController.execute(ResourceController.java:97)
        at hudson.model.Executor.run(Executor.java:429)
    this test fails: processProperlyKilledUnix in jenkins core
    also got this once:
    2020-12-09 07:41:57.091+0000 [id=18]    WARNING    h.i.i.InstallUncaughtExceptionHandler#handleException: Caught unhandled exception with ID b412cb0f-a54a-4335-ba7a-887f7dbddb8d
    java.lang.IllegalStateException: Illegal Result type: null
        at com.cloudbees.workflow.rest.external.StatusExt.valueOf(StatusExt.java:74)
        at com.cloudbees.workflow.rest.external.RunExt.initStatus(RunExt.java:391)
        at com.cloudbees.workflow.rest.external.RunExt.createMinimal(RunExt.java:239)
        at com.cloudbees.workflow.rest.external.RunExt.createNew(RunExt.java:315)
        at com.cloudbees.workflow.rest.external.RunExt.create(RunExt.java:307)
        at com.cloudbees.workflow.rest.external.JobExt.create(JobExt.java:143)
        at com.cloudbees.workflow.rest.endpoints.JobAPI.doRuns(JobAPI.java:69)
        at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710)
        at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
    Caused: java.lang.reflect.InvocationTargetException
        at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400)
        at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)
        at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:30)
    Caused: java.lang.RuntimeException: Unexpected exception while serving JSON
        at com.cloudbees.workflow.util.ServeJson$Processor.invoke(ServeJson.java:34)
        at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26)
        at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)
        at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)
        at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:536)
        at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
        at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:766)
        at org.kohsuke.stapler.Stapler.invoke(Stapler.java:898)
        at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:457)
        at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:766)
        at org.kohsuke.stapler.Stapler.invoke(Stapler.java:898)
        at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:281)
        at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
        at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:766)
        at org.kohsuke.stapler.Stapler.invoke(Stapler.java:898)
        at org.kohsuke.stapler.Stapler.invoke(Stapler.java:694)
        at org.kohsuke.stapler.Stapler.service(Stapler.java:240)
    2020-12-09 07:41:39.832+0000 [id=262]    WARNING    hudson.util.ProcessTree#get: Failed to load winp. Reverting to the default
    java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native
        at hudson.util.ProcessTree$Darwin.<clinit>(ProcessTree.java:1828)
        at hudson.util.ProcessTree.get(ProcessTree.java:457)
        at hudson.Launcher$LocalLauncher.kill(Launcher.java:1015)
        at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.lambda$finish$1(ExecutorStepExecution.java:737)
        at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        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)
    Jim Crowley
    @james-crowley
    @slide From looking at the logs it seems some of the tags are not pushed up to the docker repository. Also from looking around, did you by chance ever call publish-images?
    Also just an FYI I got pulled in on a project that will run until the second week of January. So it might take me a little to fix up the PR
    Alex Earl
    @slide
    I'll try adding publish-images
    slide-o-mix
    @slide-o-mix:matrix.org
    [m]
    FYI, here is the PR that removed the "official" Jenkins from the docker-library repo: docker-library/official-images@d62d6d5
    slide-o-mix
    @slide-o-mix:matrix.org
    [m]
    fyi, I submitted this issue to the docker-library/docks repo for tracking changes to the deprecation notice and such on dockerhub for the old jenkins images: docker-library/docs#1851
    Tim Jacomb
    @timja
    o hi matrix slide
    slide-o-mix
    @slide-o-mix:matrix.org
    [m]
    heh
    Tim Jacomb
    @timja
    why is setting up a multi arch build so hard :(
    for docker
    core-pr-tester now works for me on arm :p
    Tim Jacomb
    @timja
    and it should get updated every week now
    Oleg Nenashev
    @oleg-nenashev
    :+1: Should I still disable Docker autobuilds?
    Tim Jacomb
    @timja
    @oleg-nenashev yes please
    Alex Earl
    @slide
    @timja multiarch on docker is painful
    Tim Jacomb
    @timja
    yup -.-
    the automatic building seems to be working fine :) should change it off my api token at some point :p
    Mark Waite
    @MarkEWaite
    Tim Jacomb
    @timja
    Where do you want issues raised for https://github.com/jenkinsci/jnlp-agents ?
    issues are disabled, can't see a matching jira component and no info in the repo
    the docker repo says 'Please note that only issues related to this Docker image will be addressed here.'
    (specific issue is related to many agents running as root by default, which is the reason for the jenkins core tests failing after the security fix last week)
    Oleg Nenashev
    @oleg-nenashev
    @timja I enabled GitHub Issues in this repo. There was no other location AFAICT
    Tim Jacomb
    @timja
    thanks
    Kara submitted a PR anyway so will skip the issue :p
    Oleg Nenashev
    @oleg-nenashev
    I would like to grant @Marcck write access in https://github.com/jenkinsci/jnlp-agents/ so that the pull requests could be tested. Any concerns?
    Tim Jacomb
    @timja
    go for it
    Mark Waite
    @MarkEWaite
    +1 from me