Konstantin Veretennicov <[email protected]> schrieb am Sa., 29. Apr. 2017 um 21:05 Uhr:
> On Tue, Mar 14, 2017 at 10:58 PM, Dominik Ruf <[email protected]> > wrote: > > Hi, > > > > I just wanted to let you know, that I have a first prototype of a jenkins > > SCMSource plugin, similar to > > > https://wiki.jenkins-ci.org/display/JENKINS/Bitbucket+Branch+Source+Plugin > . > > You can see it in action here > > https://jenkins.dominikruf.com/view/All/job/kallithea-mb-pipeline/ . > > Sounds nice! > > > What it does is, it creates a project for every branch and every pull > > request that contains a Jenkins file. > > We use Pipeline, but not Jenkinsfiles. Any chance to have PR builds > without Jenkinsfile? > I have another plugin with a "pull request trigger". Eventually I'll merge the two. > > > > > So, not only does it run all the tests (incl. coverage) and pylint when > new > > changesets are pushed, it also runs all the tests etc. when there is a > new > > pull request. So before you even look at the new pull request you can > see if > > the pull request broke some tests. > > > > My plugin is still in a very early stage. There are a quite a few things > I > > need to clean up and kallithea also needs a view API improvements to > make it > > work. But I think you can see the genral idea. > > > > Let me know what you think and if you have some more ideas about a > jenkins > > plugin. > > Does it comment back to the PR about the state of the build, the way > https://github.com/graydon/bors does with GitHub? That would have been > nice. > Yes. > > -- > Konstantin >
_______________________________________________ kallithea-general mailing list [email protected] https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
