Thanks all, I have enabled it in the org. Feel free to add it to your repositories which have images. First pull request: https://github.com/jenkinsci/role-strategy-plugin/pull/108
On Tuesday, October 8, 2019 at 12:45:52 AM UTC+2, Oleg Nenashev wrote: > > Yes, it is only about the served/packaged size. There is no practical way > to change the repo size, and optimizing images will actually increase that > slightly. > But it is important to have content size optimized to improve loading > times over network and to reduce package sizes > > P.S: Don't forget to test it on the Chuck Norris plugin! > > On Monday, October 7, 2019 at 5:37:12 PM UTC+2, Liam Newman wrote: >> >> It's not about size in the repo but size being served. +1. >> >> On Mon, Oct 7, 2019 at 8:25 AM Baptiste Mathus <[email protected]> >> wrote: >> >>> I'm a bit unconvinced this really changes the situation given things are >>> still versioned and kept in the repo history, but still +1 why not! :) >>> >>> Le lun. 7 oct. 2019 à 10:09, Oleg Nenashev <[email protected]> a >>> écrit : >>> >>>> Hi all, >>>> >>>> I would like to enable ImgBot <https://github.com/marketplace/imgbot>in >>>> some of my plugins in order to optimize image sizes. ImgBot is a bot which >>>> creates pull requests with image optimizations, e.g. here is a sample pull >>>> requests for the Jenkins Core: >>>> https://github.com/oleg-nenashev/jenkins/pull/38. There are a lot of >>>> historical images in Jenkins, and it could be a good opportunity to >>>> optimize them. >>>> >>>> There is a free open-source plan for ImgBot, so I think enabling the >>>> bot should not be a problem. As for other bots, I suggest we enable it in >>>> the org but do not enable it widely by default. Each plugin maintainer >>>> will >>>> be able to enable it on his/her own. >>>> >>>> What do you think? >>>> >>>> Thanks in advance, >>>> Oleg >>>> >>>> -- >>>> 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/CAPfivLDM57J9zbP-MKrvQ64R%3Dm5xKLu%2BY235WM41NUYkr6EEQw%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDM57J9zbP-MKrvQ64R%3Dm5xKLu%2BY235WM41NUYkr6EEQw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >>> 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/CAPyTVp3wet6VecECQqZDLAiTOHERfuPXsZ%2BhpNDLefDxS8tr6w%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPyTVp3wet6VecECQqZDLAiTOHERfuPXsZ%2BhpNDLefDxS8tr6w%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- 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/c3b28a11-7c25-4e90-a71e-2ed0c80388eb%40googlegroups.com.
