On Fri, Mar 16, 2018 at 9:11 PM, martinda <[email protected]> wrote: > I have the impression that you are saying that this > GSoC project idea is a bit too shallow on the quantity of code for GSoC.
Perhaps. Depends on what approach you want the feature to take—adding a convenience veneer atop the existing Jenkins features, or writing something with a very different design from scratch. > do you have recommendations to make it more substantial? Not offhand. There are hundreds of issues I follow in the general area of multibranch, but I have no idea which you would consider important in this context. > some automatic detection of reports like JUnit XML reports, HTML reports, > summary display reports, etc. FYI the `pipeline-maven` plugin does some things like this—for Maven builds only, of course. > a default merge before build Already a standard part of Jenkins branch sources. > a default of having PR builds triggered by the user (rather > than automatic) There are some RFEs in this area. -- 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/CANfRfr1HF9ObXHq1PRhtsUJee5ZA7oeGdwQ7xXLbhbyDfnYapA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
