by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Guy Sheffer
    @guysoft
    @markyjackson-taulia Thanks!
    I see it needs one more reviewer.
    Marky Jackson
    @markyjackson-taulia
    Yup, working on that now
    Marky Jackson
    @markyjackson-taulia
    Done @guysoft
    Guy Sheffer
    @guysoft
    @markyjackson-taulia Still getting [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project configurationslicing: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:configurationslicing:hpi:1.50 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Transfer failed for https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/configurationslicing/1.50/configurationslicing-1.50.hpi 401 Unauthorized -> [Help 1] .
    @markyjackson-taulia Do I need to do something?
    Marky Jackson
    @markyjackson-taulia
    I am away from my computer but will look later tonight or tomorrow morning. Keeping the kids busy
    Guy Sheffer
    @guysoft
    Ok, thanks @markyjackson-taulia . Will wait till then
    Guy Sheffer
    @guysoft

    Hey, seems like I managed to add my plugin to Artifactory. But it does not appear in the Jenking plugin manager, or the plugin page:
    https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/plugins/configurationslicing/1.50

    How do I make the artefact also available for everyone to download?
    (cc @markyjackson-taulia

    Mark Waite
    @MarkEWaite
    @guysoft there is a delay between initial push to artifactory and visibility in Jenkins update center. In the past, that delay was up to 24 hours. I see configuration slicing plugin 1.50 on my Jenkins server . It downloaded successfully and will be enabled on my next Jenkins restart
    Guy Sheffer
    @guysoft
    @markyjackson-taulia ok, thanks!
    @MarkEWaite This also seems to be out of date: https://plugins.jenkins.io/configurationslicing/
    steven-terrana
    @steven-terrana

    @guysoft the plugin site also takes some time to index and show the latest version.

    i’m seeing 1.50 on the plugin site right now

    Gavin Mogan
    @halkeye
    There's a date at the bottom of the plugin site. Its when it ran last
    It has to be run after update center sees the plugin
    Marky Jackson
    @markyjackson-taulia
    I will be offline for the next few days for personal reasons but just wanted to drop a note
    Mark Waite
    @MarkEWaite
    @res0nance and I have been investigating an issue related to assigning scm.extensions to a Groovy variable in a scripted pipeline. It fails with a not serializable exception. When I look at the Git extensions, they are definitely not serializable. See https://gist.github.com/res0nance/43f10db313d0f7e5a2237c9e459b8298 for a nicely simplified example or https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-43931/Jenkinsfile for a complicated example
    1 reply
    steven-terrana
    @steven-terrana

    @MarkEWaite unfortunately i’ve experienced this issue in all of its varieties during my own plugin development.

    There are basically 4 options.

    option 1: ensure everything you’re going to assign to a variable during hte course of pipeline execution serializable. this sometimes isn’t feasible or is a huge level of effort

    which leads to option 2: simply don’t assign non-serializable objects to variables and always infer their value like youre doing with scm.extensions

    alternatively, Option 3, you try to do non-serializable things in methods annotated @NonCPS but you should not try to run pipeline code in non-cps transformed methods. it leads to strange behavior.

    and then finally, a hacky work around.. Option 4: set the pipeline’s durability to PERFORMANCE_OPTIMIZED. this isn’t a scalable solution though. basically - the exception is being thrown when groovy-cps tries to persist the pipeline’s state to disk. Setting the durability to PERFORMANCE_OPTIMIZED makes this happen significantly less frequently. therefore - the pipeline never attemps to serialize the non-serializable variable meaning the exception is not thrown.

    Mark Waite
    @MarkEWaite
    Thanks so much @steven-terrana ! That is a great response. I won't worry further that the git plugin has made some terrible mistake with regard to serializing extensions. Your explanation of PERFORMANCE_OPTIMIZED showing the problem less frequently is good to know, since the problem is real but hidden with that setting, waiting to reappear at semi-random times
    steven-terrana
    @steven-terrana
    haha very happy to help. i did not think my pain on this topic would ever have the opportunity to help someone!
    Mark Waite
    @MarkEWaite
    I wonder if there is a way to capture your experience and the experience of @res0nance in the Jenkins Pipeline docs. I believe we already have a section that talks about the compromises related to performance optimized and maximum durability
    Would this topic fit better in that location or is it something that should be mentioned in a location that talks about advanced scripting with the DSL?
    Raihaan Shouhell
    @res0nance
    The current docs talks about the main difference being clean vs dirty shutdowns but not about serialization issues. This might be more of a topic for advanced scripting
    steven-terrana
    @steven-terrana
    @MarkEWaite if there’s a place in the docs i should open a PR i’d be happy to write up what i mentioned above.
    Mark Waite
    @MarkEWaite
    @steven-terrana would it fit reasonably as a section immediately after the 'Using @NonCPS' section on the "Best Practices" page? https://www.jenkins.io/doc/book/pipeline/pipeline-best-practices/#using-noncps
    steven-terrana
    @steven-terrana

    I think i would rename that section “Avoiding NotSerializableExceptions”

    and then have an overview describing some context and then subheaders for the options i presented

    one of which is the existing NonCPS info already described
    Mark Waite
    @MarkEWaite
    That sounds really good to me. Good to retain using nonCPS heading at some level so that links to that specific location continue to resolve to that information
    steven-terrana
    @steven-terrana

    would you happen to know where to find the file in github so i can update?

    haven’t made a formal docs contribution before

    i’ll make that update and tag you (@markewaite) as a PR reviewer some time today when i find time in between meetings :)
    steven-terrana
    @steven-terrana
    Oleg Nenashev
    @oleg-nenashev
    @markyjackson-taulia @steven-terrana Hi. I messed up the Hackfest schedule a bit yesterday, and now the Hackfest demos session overlaps with the Pipeline Authoring SIG meeting. Sorry about that. How would you prefer to handle the Zoom meeting? Would it be fine if we use the Jenkins Account with Webinar support, and you use the older CDF Zoom account?
    Marky Jackson
    @markyjackson-taulia
    I may need to skip the meeting today for personal reasons
    steven-terrana
    @steven-terrana
    i’m feeling a little under the weather today and am taking the day off.
    Marky Jackson
    @markyjackson-taulia
    Let’s go ahead and cancel. I will send a email to the mailing list
    Marky Jackson
    @markyjackson-taulia
    Oleg Nenashev
    @oleg-nenashev
    OK, problem solved. But looking forward to see you all next week!
    Marky Jackson
    @markyjackson-taulia
    +1
    Jerry
    @solvingj
    When using pipeline build step, is it possible return information from the child job to the parent job at some milestone of the child job (prior to completion)?
    Is there any sort of callback mechanism or status or something...
    Jerry
    @solvingj
    thanks, i'm currently considering the webhook step plugin https://plugins.jenkins.io/webhook-step/
    but, that requires me to plumb something a bit ugly
    Marky Jackson
    @markyjackson-taulia
    Should we be having discussion of perhaps postponing meetings this week?
    It still feels very "business as usual" within the project ... but certainly not back "in the real world" ...
    Marky Jackson
    @markyjackson-taulia
    Cc @bitwiseman
    Marky Jackson
    @markyjackson-taulia
    @/all hey everyone, due to what's going in the US we're going to postpone the SIG weekly meeting for this week. Thanks for understanding.
    Marky Jackson
    @markyjackson-taulia
    Email to the mailing list about this weeks meeting being canceled https://groups.google.com/forum/m/#!msg/jenkins-pipeline-authoring-sig/5DEuDYpwYGM/ufse-YTuAQAJ
    steven-terrana
    @steven-terrana
    thank you @markyjackson-taulia
    Marky Jackson
    @markyjackson-taulia
    you’re welcome