You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@impala.apache.org by Todd Lipcon <to...@apache.org> on 2018/06/01 18:35:06 UTC
jenkins.impala.io account
Hey folks,
Would someone mind generating an account for me on the Impala jenkins
server so I can run gerrit verify jobs?
Though I'm officially a committer (due to participation as a mentor during
incubation) I'm not yet an experienced patch contributor, so I'll be
prudent with my review/commit privileges.
Thanks
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
Re: jenkins.impala.io account
Posted by Philip Zeyliger <ph...@cloudera.com>.
Thanks!
On Tue, Jun 5, 2018 at 9:13 AM, Michael Brown <mi...@cloudera.com> wrote:
> gerrit-verify-dryrun-external and gerrit-verify-dryrun with
> DRY_RUN=true will now post
> 1. When a build is starting
> 2. The build's final status
> But will not attempt to Submit.
>
> Let me know if you run into any trouble.
>
>
> On Mon, Jun 4, 2018 at 9:24 AM, Michael Brown <mi...@cloudera.com> wrote:
> >> I guess we could change the "dry run" part only to be about doing the
> commit portion and still always mark whether verified.
> >
> > The change looks straightforward. I'm testing that it works in a private
> job.
>
Re: jenkins.impala.io account
Posted by Michael Brown <mi...@cloudera.com>.
gerrit-verify-dryrun-external and gerrit-verify-dryrun with
DRY_RUN=true will now post
1. When a build is starting
2. The build's final status
But will not attempt to Submit.
Let me know if you run into any trouble.
On Mon, Jun 4, 2018 at 9:24 AM, Michael Brown <mi...@cloudera.com> wrote:
>> I guess we could change the "dry run" part only to be about doing the commit portion and still always mark whether verified.
>
> The change looks straightforward. I'm testing that it works in a private job.
Re: jenkins.impala.io account
Posted by Michael Brown <mi...@cloudera.com>.
> I guess we could change the "dry run" part only to be about doing the commit portion and still always mark whether verified.
The change looks straightforward. I'm testing that it works in a private job.
Re: jenkins.impala.io account
Posted by Michael Brown <mi...@cloudera.com>.
Ahh no, it doesn't do that. Currently you have to go back and check the job
status yourself.
I guess we could change the "dry run" part only to be about doing the
commit portion and still always mark whether verified.
On Fri, Jun 1, 2018 at 11:43 AM, Todd Lipcon <to...@cloudera.com> wrote:
> On Fri, Jun 1, 2018 at 11:37 AM, Michael Brown <mi...@cloudera.com> wrote:
>
> > Thanks for taking an interest!
> >
> > Is https://jenkins.impala.io/job/gerrit-verify-dryrun-external/ suitable
> > for you? It's open to all contributors. It's just a wrapper around
> > gerrit-verify-dryrun, sans commit-after-passing-build bit.
> >
>
> Will this give the proper "+1 verified" mark on a gerrit such that it can
> be committed?
>
> -Todd
>
>
> > On Fri, Jun 1, 2018 at 11:35 AM, Todd Lipcon <to...@apache.org> wrote:
> >
> > > Hey folks,
> > >
> > > Would someone mind generating an account for me on the Impala jenkins
> > > server so I can run gerrit verify jobs?
> > >
> > > Though I'm officially a committer (due to participation as a mentor
> > during
> > > incubation) I'm not yet an experienced patch contributor, so I'll be
> > > prudent with my review/commit privileges.
> > >
> > > Thanks
> > > -Todd
> > > --
> > > Todd Lipcon
> > > Software Engineer, Cloudera
> > >
> >
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera
>
Re: jenkins.impala.io account
Posted by Todd Lipcon <to...@cloudera.com>.
On Fri, Jun 1, 2018 at 11:37 AM, Michael Brown <mi...@cloudera.com> wrote:
> Thanks for taking an interest!
>
> Is https://jenkins.impala.io/job/gerrit-verify-dryrun-external/ suitable
> for you? It's open to all contributors. It's just a wrapper around
> gerrit-verify-dryrun, sans commit-after-passing-build bit.
>
Will this give the proper "+1 verified" mark on a gerrit such that it can
be committed?
-Todd
> On Fri, Jun 1, 2018 at 11:35 AM, Todd Lipcon <to...@apache.org> wrote:
>
> > Hey folks,
> >
> > Would someone mind generating an account for me on the Impala jenkins
> > server so I can run gerrit verify jobs?
> >
> > Though I'm officially a committer (due to participation as a mentor
> during
> > incubation) I'm not yet an experienced patch contributor, so I'll be
> > prudent with my review/commit privileges.
> >
> > Thanks
> > -Todd
> > --
> > Todd Lipcon
> > Software Engineer, Cloudera
> >
>
--
Todd Lipcon
Software Engineer, Cloudera
Re: jenkins.impala.io account
Posted by Michael Brown <mi...@cloudera.com>.
Thanks for taking an interest!
Is https://jenkins.impala.io/job/gerrit-verify-dryrun-external/ suitable
for you? It's open to all contributors. It's just a wrapper around
gerrit-verify-dryrun, sans commit-after-passing-build bit.
On Fri, Jun 1, 2018 at 11:35 AM, Todd Lipcon <to...@apache.org> wrote:
> Hey folks,
>
> Would someone mind generating an account for me on the Impala jenkins
> server so I can run gerrit verify jobs?
>
> Though I'm officially a committer (due to participation as a mentor during
> incubation) I'm not yet an experienced patch contributor, so I'll be
> prudent with my review/commit privileges.
>
> Thanks
> -Todd
> --
> Todd Lipcon
> Software Engineer, Cloudera
>