Most welcome! So I usually just write a script that run this and then uses the built in email notification from a Jenkins job. Maybe not the most glorious way but it solves the immediate need. Have a good rest of the week 🙂
> On Jun 4, 2020, at 1:15 AM, Ewelina Wilkosz <[email protected]> wrote: > >  > wow, thanks a lot!! > >> On Thursday, June 4, 2020 at 10:08:12 AM UTC+2, Marky Jackson wrote: >> I have always had super good luck writing a go script job and incorporating >> https://github.com/crazy-max/diun >> >> >> >>>> On Jun 4, 2020, at 1:04 AM, Ewelina Wilkosz <[email protected]> wrote: >>>> >>>  >>> well it wouldn't automatically, blindly try to apply it on production :) >>> >>> the process I have in mind is: >>> 1. new lts pushed to docker hub >>> 2. I get notified/I monitor and discover it happened >>> 3. I discover what is the actual version number for lts >>> 4. I update my Dockerfile and build new docker image >>> >>> I know I can pull the image and check the version e.g. with inspect, but I >>> was wondering if it is possible to get the information without pulling, and >>> if there is some notification mechanism in place >>> >>>> On Thursday, June 4, 2020 at 9:59:08 AM UTC+2, Marky Jackson wrote: >>>> Would this be for a production type instances of Jenkins or a personal >>>> instance? >>>> >>>> >>>>>> On Jun 4, 2020, at 12:55 AM, Ewelina Wilkosz <[email protected]> wrote: >>>>>> >>>>>  >>>>> Hi! >>>>> >>>>> I am trying to automate updating jenkins when new lts image is released >>>>> do you know: >>>>> 1. if there is some notification mechanism in place? something I can >>>>> "watch" and learn that new version is out? >>>>> 2. I do not want to really go for "jenkins/jenkins:lts", I want to match >>>>> lts to specific version. Anyone has an elegant way of getting, e.g. from >>>>> docker hub, the information which other tags are applied to "lts" image? >>>>> >>>>> not sure if docker hub or e.g. github is the right place to look for >>>>> those information/event >>>>> >>>>> it's a very general idea for now :) no specific technical solutions in >>>>> place, checking what's available >>>>> -- >>>>> You received this message because you are subscribed to the Google Groups >>>>> "Jenkins Developers" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send an >>>>> email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/fe0bffc9-e2cc-4680-96ad-658f1835c718%40googlegroups.com. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/b18d49b6-a411-4d5e-bdc3-ceb6da1979eb%40googlegroups.com. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/67357173-17f0-4ba1-ac67-bf6f85dd490a%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/472BADAD-A023-4C10-A533-26B1DFE02A84%40gmail.com.
