On Thu, May 10, 2018 at 5:37 AM, Steven F <[email protected]> wrote: > The examples in the article show elements such as linting, > build, static analysis as separate and individually runnable things. In > Jenkins 2.x Pipeline it feels like bundling these things together is more > encouraged.
Well, it is generally more straightforward to have those things be run as part of a single Jenkins build, triggered by SCM changes. What is missing is an API which would allow Jenkins report plugins (`Publisher & SimpleBuildStep`, for example) to indicate to the system that there is some information to be displayed in an abstract “change request”, perhaps associated with source code lines, which would then be implemented by `github-branch-source` with the Checks API. [email protected] wrote: > just rerunning the job from github would save a step See JENKINS-45455 for rerunning generally; again we would need a new API to allow this is to be integrated with in-PR “chatops” triggers, so that `github-branch-source` could receive GH events and refire them as requests to rerun parts of a build, which `pipeline-model-definition` would then interpret as a Declarative build trigger. All this would allow you to do more from GitHub and less from Blue Ocean or the Jenkins “classic” UI. @abayer has done the most work in this area and should probably be commenting. -- 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/CANfRfr0MNg5_9DFrFKnp%3Darrn06rkZTP-DzW%2BuwcVamF-TRSFQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
