On Fri, Feb 8, 2019 at 8:11 PM R. Tyler Croy <[email protected]> wrote: > If core alone is causing a denial of service on ci.jenkins.io (it's not)
But it is. I have personally had my work obstructed on multiple occasions by core PR builds (though `git-plugin` has been a lesser contributor). > one easy solution is to add a specific label for core only Though this would make for poor resource utilitization. Baptiste already suggested using a Jenkins plugin to prioritize plugin builds over core builds, which would be better than nothing, though it would not address the wasted cost issue. James Nord wrote: > Jenkins-x addresses the issue… Yes, Tide’s behavior is already mentioned in INFRA-1633. This is certainly one option, though it would involve nontrivial new feature development as well as a workflow change. -- 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/CANfRfr1q31HSHxdAKZxP7wSTwYHHXkRys8DzpN%2BEq14Y62cbMg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
