2 ways integration with Jenkins

[Dominik Ruf]

Long Vu <long.vu at intelerad.com> schrieb am Mi., 4. Okt. 2017 um 17:19 Uhr:

> On Tue, Oct 3, 2017 at 8:42 PM, Mads Kiilerich <mads at kiilerich.com> wrote:
> > On 10/03/2017 05:35 PM, Long Vu wrote:
> >>
> >> Hi,
> >>
> >> I think I've seen on this list a hook in Kallithea that can trigger a
> >> Jenkins build on push.
> >>
> >> That hook can also automatically create a brand new job if a new
> >> branch was detected.  Please correct me if I was dreaming.
> >>
> >> That's one way for me.
> >>
> >> The other way is for Jenkins to report the pass/fail status back to
> >> Kallithea to be displayed when someone is browsing the PR or the
> >> commits.
> >>
> >> Is this reverse way possible?
> >
> >
> >
> > I did this for Mercurial repos by having a cron job polling the "CI"
> system
> > and creating "$BUILDNUMBER-pass" / "...-fail" local tags for revisions.
> Not
> > a perfect solution, but shows that it is "possible".
>
> Interesting work-around.  I assume the localtag file will grow
> indefinitely with this solution.
>
> >
> > Another way could be to have a special user account that approve/reject
> > tested revisions - perhaps by polling, perhaps by having the CI system
> > connect through the API.
> >
>
> Kallithea already has an API for CI system to push extra data to each
> revision/PR ?
>
> You already can add a comment via the API.
In fact my jenkins plugin
https://kallithea.dominikruf.com/kallithea/kallithea-jenkins-plugin (that I
mentioned before on this list and for which I really should publish a
release version soon) does this.

>
> --
> Long Vu | Build Controller | Intelerad | +1-514-931-6222 ext. 7743
> <+1%20514-931-6222>
>
> --
>
> This email or any attachments may contain confidential or legally
> privileged information intended for the sole use of the addressees. Any
> use, redistribution, disclosure, or reproduction of this information,
> except as intended, is prohibited. If you received this email in error,
> please notify the sender and remove all copies of the message, including
> any attachments.
>
> _______________________________________________
> kallithea-general mailing list
> kallithea-general at sfconservancy.org
> https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sfconservancy.org/pipermail/kallithea-general/attachments/20171005/01a86455/attachment.html>