On Tue, May 1, 2018 at 10:42 AM, nicolas de loof <[email protected]> wrote: >> There is a gigantic long tail of Jenkins features (mostly plugins) >> which would not work in a Build Publisher-like environment > > Not sure what you have in mind (if you have a concrete sample this could > help).
The first thing that pops into my head is Throttle Concurrent Builds, but I think if you start going through randomly selected plugins you will find dozens if not hundreds of examples. > what I'd like to achieve is to fully remove Jenkins Web UI and only > rely on Github commit status > for user interaction […]. So plugins > would only make sense > during the build, and any UI contributing plugin would just be excluded. OK, this is definitely an interesting project, but I would consider it a novel CI system with a modest degree of Jenkins compatibility. > echo "entering stage foo" > /var/run/jenkins.sock Or I was just thinking some kind of magic string to stdout/stderr. I have seen some scripts using ANSI control characters, or the (freestyle-compatible) plugin I mentioned before lets you configure any regexp. -- 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/CANfRfr1d1SSTBOT7WUT9gTKupB8avAAxE%3Ddzxkz2NffoYT%3DZMw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
