Re: [Gluster-infra] [Gluster-devel] Migration from gerrit bugzilla hook to a jenkins job

[Mohammed Rafi K C]

On 08/17/2017 05:07 PM, Nigel Babu wrote:
> This change is taking the first step towards implementing those ideas.
> One of the major blockers to implementing them was that it was
> difficult to grant easy access to change the hook. Granting production
> access to Gerrit is next to impossible unless you really know what
> you're doing.
>
> We'll not increase the scope *right now* to include automating the
> entire bug workflow.

Cool. If I understand correctly , once we have the jenkins job in place,
we can resume the work done by Manikandan . is that right ?


~Rafi KC


>
> On Thu, Aug 17, 2017 at 4:53 PM, Mohammed Rafi K C
> <rkavu...@redhat.com <mailto:rkavu...@redhat.com>> wrote:
>
> Some time back (2 yrs :) ) , we had discussion on automated bug
> work flow enhancement [1] . Nandaja and Manikandan were working on
> this. I'm not sure about the current status. If you have some time
> take a look at the proposals [2] and how we can proceed.
>
>
> [1] :
> http://lists.gluster.org/pipermail/gluster-devel/2015-July/046084.html
> <http://lists.gluster.org/pipermail/gluster-devel/2015-July/046084.html>
>
> [2] :
> http://lists.gluster.org/pipermail/gluster-devel/2015-May/045374.html
> <http://lists.gluster.org/pipermail/gluster-devel/2015-May/045374.html>
>
>
> Regards
>
> Rafi
>
>
> On 08/17/2017 10:07 AM, Deepshikha Khandelwal wrote:
>>
>> Hello everyone,
>>
>> We are planning to move from posting to bugzilla via a gerrit
>> hook to a jenkins job on build.gluster.org
>> <http://build.gluster.org> so that it can be edited easily and
>> the output is properly visible.
>>
>> This bugzilla-post[1] job will be triggered by gerrit events and
>> will update the status of the bug on bugzilla. This job is
>> currently running in dry run mode, so it will not actually post
>> anything to bugzilla. We will be verifying the job over the
>> course of the next few days. If you notice anything odd in what
>> it’s doing, please let us know.
>>
>> [1] https://build.gluster.org/job/bugzilla-post/
>>
>> Thanks & Regards,
>> Deepshikha Khandelwal
>>
>>
>>
>> ___
>> Gluster-devel mailing list
>> gluster-de...@gluster.org <mailto:gluster-de...@gluster.org>
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>> <http://lists.gluster.org/mailman/listinfo/gluster-devel>
> ___ Gluster-infra
> mailing list Gluster-infra@gluster.org
> <mailto:Gluster-infra@gluster.org>
> http://lists.gluster.org/mailman/listinfo/gluster-infra
> <http://lists.gluster.org/mailman/listinfo/gluster-infra> 
>
> -- 
> nigelb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Migration from gerrit bugzilla hook to a jenkins job

[Mohammed Rafi K C]

Thanks Manikandan for your quick update. As nigel pointed out in the
previous mail, we can resume the work once the ongoing task has
finished. So hopefully we can finish this time.


Regards

Rafi KC


On 08/17/2017 05:08 PM, Manikandan Selvaganesh wrote:
> Hi all,
>
> We did work on the same and here is the BZ[1]. We had sent an initial
> patch[2] 
> and we wanted access to jenkins jobs to test and continue further.
> Nigel said
> he will continue the work from there. May be he can update the thread now.
>
> Here is the link for the public pad[3]. Not sure if this is still
> accessible.
>
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1285179
>
> [2] https://review.gluster.org/#/c/12822/
>
> [3] https://public.pad.fsfe.org/p/gluster-automated-bug-workflow
>
> --
> Thanks & Regards,
> Manikandan Selvaganesan.
> (@Manikandan Selvaganesh on Web)
>
> On Thu, Aug 17, 2017 at 4:53 PM, Mohammed Rafi K C
> <rkavu...@redhat.com <mailto:rkavu...@redhat.com>> wrote:
>
> Some time back (2 yrs :) ) , we had discussion on automated bug
> work flow enhancement [1] . Nandaja and Manikandan were working on
> this. I'm not sure about the current status. If you have some time
> take a look at the proposals [2] and how we can proceed.
>
>
> [1] :
> http://lists.gluster.org/pipermail/gluster-devel/2015-July/046084.html
> <http://lists.gluster.org/pipermail/gluster-devel/2015-July/046084.html>
>
> [2] :
> http://lists.gluster.org/pipermail/gluster-devel/2015-May/045374.html
> <http://lists.gluster.org/pipermail/gluster-devel/2015-May/045374.html>
>
>
> Regards
>
> Rafi
>
>
> On 08/17/2017 10:07 AM, Deepshikha Khandelwal wrote:
>>
>> Hello everyone,
>>
>> We are planning to move from posting to bugzilla via a gerrit
>> hook to a jenkins job on build.gluster.org
>> <http://build.gluster.org> so that it can be edited easily and
>> the output is properly visible.
>>
>> This bugzilla-post[1] job will be triggered by gerrit events and
>> will update the status of the bug on bugzilla. This job is
>> currently running in dry run mode, so it will not actually post
>> anything to bugzilla. We will be verifying the job over the
>> course of the next few days. If you notice anything odd in what
>> it’s doing, please let us know.
>>
>> [1] https://build.gluster.org/job/bugzilla-post/
>>
>> Thanks & Regards,
>> Deepshikha Khandelwal
>>
>>
>>
>> ___
>> Gluster-devel mailing list
>> gluster-de...@gluster.org <mailto:gluster-de...@gluster.org>
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>> <http://lists.gluster.org/mailman/listinfo/gluster-devel>
> ___ Gluster-devel
> mailing list gluster-de...@gluster.org
> <mailto:gluster-de...@gluster.org>
> http://lists.gluster.org/mailman/listinfo/gluster-devel
> <http://lists.gluster.org/mailman/listinfo/gluster-devel> 
>
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Migration from gerrit bugzilla hook to a jenkins job

[Mohammed Rafi K C]

Some time back (2 yrs :) ) , we had discussion on automated bug work
flow enhancement [1] . Nandaja and Manikandan were working on this. I'm
not sure about the current status. If you have some time take a look at
the proposals [2] and how we can proceed.


[1] : http://lists.gluster.org/pipermail/gluster-devel/2015-July/046084.html

[2] : http://lists.gluster.org/pipermail/gluster-devel/2015-May/045374.html


Regards

Rafi


On 08/17/2017 10:07 AM, Deepshikha Khandelwal wrote:
>
> Hello everyone,
>
> We are planning to move from posting to bugzilla via a gerrit hook to
> a jenkins job on build.gluster.org  so that
> it can be edited easily and the output is properly visible.
>
> This bugzilla-post[1] job will be triggered by gerrit events and will
> update the status of the bug on bugzilla. This job is currently
> running in dry run mode, so it will not actually post anything to
> bugzilla. We will be verifying the job over the course of the next few
> days. If you notice anything odd in what it’s doing, please let us know.
>
> [1] https://build.gluster.org/job/bugzilla-post/
> 
>
> Thanks & Regards,
> Deepshikha Khandelwal
>
>
>
> ___
> Gluster-devel mailing list
> gluster-de...@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Jenkins accounts for all devs.

[Mohammed Rafi K C]

On 01/22/2016 11:31 AM, Ravishankar N wrote:
> On 01/14/2016 12:16 PM, Kaushal M wrote:
>> On Thu, Jan 14, 2016 at 10:33 AM, Raghavendra Talur
>>  wrote:
>>>
>>> On Thu, Jan 14, 2016 at 10:32 AM, Ravishankar N
>>> 
>>> wrote:
 On 01/08/2016 12:03 PM, Raghavendra Talur wrote:
> P.S: Stop using the "universal" jenkins account to trigger jenkins
> build
> if you are not a maintainer.
> If you are a maintainer and don't have your own jenkins account
> then get
> one soon!
>
 I would request for a jenkins account for non-maintainers too, at
 least
 for the devs who are actively contributing code (as opposed to random
 one-off commits from persons). That way, if the regression failure is
 *definitely* not in my patch (or) is a spurious failure (or) is
 something
 that I need to take a netbsd slave offline to debug etc.,  I don't
 have to
 be blocked on the Maintainer. Since the accounts are anyway tied to an
 individual, it should be easy to spot if someone habitually re-trigger
 regressions without any initial debugging.

>>> +1

+2 ;)

In the last couple of days, It has become painful procedure  to get one
patch merged upstream. Having an account for everyone will definitely
help here to some extend.

Regards
Rafi KC




>> We'd like to give everyone accounts. But the way we're providing
>> accounts now gives admin accounts to all. This is not very secure.
>>
>> This was one of the reasons misc setup freeipa.gluster.org, to provide
>> controlled accounts for all. But it hasn't been used yet. We would
>> need to integrate jenkins and the slaves with freeipa, which would
>> give everyone easy access.
>
> Hi Michael,
> Do you think it is possible to have this integration soon so that all
> contributors can re-trigger/initiate builds by themselves?
> Regards,
> Ravi
 -Ravi
>>>
>>>
>>> ___
>>> Gluster-devel mailing list
>>> gluster-de...@gluster.org
>>> http://www.gluster.org/mailman/listinfo/gluster-devel
>
>
> ___
> Gluster-devel mailing list
> gluster-de...@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra