zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Han <h...@apache.org>
Subject Re: About Jenkins pre-commit job
Date Fri, 21 Sep 2018 01:44:45 GMT
Thanks Enrico for volunteering, it'll be cool if we can fix this.

On Wed, Sep 19, 2018 at 10:42 PM, Enrico Olivelli <eolivelli@gmail.com>
wrote:

> Il gio 20 set 2018, 01:17 Michael Han <hanm@apache.org> ha scritto:
>
> > We've seen lots of confusions recently around Jenkins pre-commit check
> > status on github pull request as well as questions like how to trigger
> > Jenkins job to get a green build. I added a section "Jenkins Pre-commit
> > Check" to our wiki page about this matter:
> >
> > https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToContribute
> >
> > I suspect the permission issue is about the fact that apache zookeeper
> > github is read only for most of us including committers. Only asfbot has
> > write access. When a Jenkins job is triggered through "Rebuild" button
> the
> > credential it's using is not asfbot thus the final job result will fail
> to
> > write back to github. I don't know how to solve this, but hopefully we
> have
> > workarounds (which though require PR creator to be more diligent on
> > obtaining a green build).
> >
>
> In Bookkeeper we have enabled the magic 'retest this please' and it is very
> useful.
>
> I can take a look in order to back port to ZK, I have access to ASF Jenkins
> so I can check current configuration for ZK.
>
> In Bookkeeper we also have the configuration of Jenkins jobs on git, using
> Jenkins DSL language. I can also take a look and see how to port to ZK
>
>
>
> Enrico
>
>
> > Michael.
> >
> --
>
>
> -- Enrico Olivelli
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message