On Tue, 2017-10-17 at 13:15 +0200, Konrad Windszus wrote: > Great, thanks for that. Is it possible to directly expose the last > build result in the Github PR though? I guess the according Jenkins > Plugin should support that Ootb.
The result is exposed, but for merged pull requests it's a bit hidden. In https://github.com/apache/sling-site/pull/3 click the 'View details' button to expose the checks, including the Jenkins one. In https://github.com/apache/sling-site/pull/2, which is not merged yet, you will see a 'Checks' container at the bottom, including one which says 'All checks have passed'. Click on 'Show all checks' to see the Jenkins status. Thanks, Robert > > Konrad > > > Am 17.10.2017 um 13:00 schrieb Robert Munteanu <romb...@apache.org> > > : > > > > Hi, > > > > In order to validate that we are able to validate pull requests > > without > > nagging infra I added experimental pull request validation to the > > sling > > site repo. > > > > The results are visible in the jenkins job [1] and in an example > > pull > > request [2]. > > > > The Jenkins job is multi-branch pipeline and it's using a personal > > access token under my account to communicate with Github. That's > > why my > > face is next to the check, but once we are migrated we can request > > a > > technical user from infra for this. > > > > Robert > > > > [1]: https://builds.apache.org/view/S-Z/view/Sling/job/sling-site/ > > [2]: https://github.com/apache/sling-site/pull/3 > >
