Re: [openstack-dev] [packaging][rpm] 3rd-party gates promotion to voting gates

2016-09-29 Thread Dirk Müller
Hi,

>> Gates that do not leave verified +1 are called non-voting, so
>> logically gates that leaves verified +1 are called voting gates.
> +1

Eh, what I wanted to +1 was:

+1 to promote the check jobs on rpm-packaging from MOS and SUSE CI as
voting jobs.

Sorry for mixing up definitions and then even quoting the wrong thing ;-)


Thanks,
Dirk

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [packaging][rpm] 3rd-party gates promotion to voting gates

2016-09-29 Thread Dirk Müller
Hi,

2016-09-29 14:12 GMT+02:00 Haïkel :

> Gates that do not leave verified +1 are called non-voting, so
> logically gates that leaves verified +1 are called voting gates.

+1


Greetings,
Dirk

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [packaging][rpm] 3rd-party gates promotion to voting gates

2016-09-29 Thread Anita Kuno

On 16-09-29 08:12 AM, Haïkel wrote:

2016-09-26 16:05 GMT+02:00 Anita Kuno :

On 16-09-26 07:48 AM, Haïkel wrote:

Hi,

following our discussions about 3rd party gates in RPM packaging project,
I suggest that we vote in order to promote the following gates as voting:
- MOS CI
- SUSE CI

After promotion, all patchsets submitted will have to validate these gates
in order to get merged. And gates maintainers should ensure that the gates
are running properly.

Please vote before (and/or during) our thursday meeting.


+1 to promote both MOS and SUSE CI as voting gates.

Regards,
H.


I'm not sure what you mean by voting gates. Gates don't vote, an individual
job can leave a verified +1 in the check queue or/and a verified +2 in the
gate queue.

Third party CI systems do not vote verified +2 in gerrit. They may if the
project chooses vote verified +1 on a project.


Yeah, that was pretty much what was assumed.
Gates that do not leave verified +1 are called non-voting, so
logically gates that leaves verified +1 are called voting gates.


Gate is a pipeline. Jobs run in pipelines (check, gate, post) and leave 
success or failure as results.


There is no such thing as a voting gate. There is a thing called a 
voting job. I think you mean voting job.


Thanks,
Anita.




If you need clarification in what third party ci systems may do in gerrit,
you are welcome to reply to this email, join the #openstack-infra channel or
participate in a third party meeting:
http://eavesdrop.openstack.org/#Third_Party_Meeting

Thank you,
Anita.


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [packaging][rpm] 3rd-party gates promotion to voting gates

2016-09-29 Thread Haïkel
2016-09-26 16:05 GMT+02:00 Anita Kuno :
> On 16-09-26 07:48 AM, Haïkel wrote:
>>
>> Hi,
>>
>> following our discussions about 3rd party gates in RPM packaging project,
>> I suggest that we vote in order to promote the following gates as voting:
>> - MOS CI
>> - SUSE CI
>>
>> After promotion, all patchsets submitted will have to validate these gates
>> in order to get merged. And gates maintainers should ensure that the gates
>> are running properly.
>>
>> Please vote before (and/or during) our thursday meeting.
>>
>>
>> +1 to promote both MOS and SUSE CI as voting gates.
>>
>> Regards,
>> H.
>
>
> I'm not sure what you mean by voting gates. Gates don't vote, an individual
> job can leave a verified +1 in the check queue or/and a verified +2 in the
> gate queue.
>
> Third party CI systems do not vote verified +2 in gerrit. They may if the
> project chooses vote verified +1 on a project.
>

Yeah, that was pretty much what was assumed.
Gates that do not leave verified +1 are called non-voting, so
logically gates that leaves verified +1 are called voting gates.

> If you need clarification in what third party ci systems may do in gerrit,
> you are welcome to reply to this email, join the #openstack-infra channel or
> participate in a third party meeting:
> http://eavesdrop.openstack.org/#Third_Party_Meeting
>
> Thank you,
> Anita.
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [packaging][rpm] 3rd-party gates promotion to voting gates

2016-09-26 Thread Anita Kuno

On 16-09-26 07:48 AM, Haïkel wrote:

Hi,

following our discussions about 3rd party gates in RPM packaging project,
I suggest that we vote in order to promote the following gates as voting:
- MOS CI
- SUSE CI

After promotion, all patchsets submitted will have to validate these gates
in order to get merged. And gates maintainers should ensure that the gates
are running properly.

Please vote before (and/or during) our thursday meeting.


+1 to promote both MOS and SUSE CI as voting gates.

Regards,
H.


I'm not sure what you mean by voting gates. Gates don't vote, an 
individual job can leave a verified +1 in the check queue or/and a 
verified +2 in the gate queue.


Third party CI systems do not vote verified +2 in gerrit. They may if 
the project chooses vote verified +1 on a project.


If you need clarification in what third party ci systems may do in 
gerrit, you are welcome to reply to this email, join the 
#openstack-infra channel or participate in a third party meeting: 
http://eavesdrop.openstack.org/#Third_Party_Meeting


Thank you,
Anita.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [packaging][rpm] 3rd-party gates promotion to voting gates

2016-09-26 Thread Ivan Udovichenko
Hi,

Thank you for bringing this topic up!

+1 from me.

We will do our best to keep services up-and-running from MOS (Mirantis)
side.

On 09/26/2016 02:48 PM, Haïkel wrote:
> Hi,
> 
> following our discussions about 3rd party gates in RPM packaging project,
> I suggest that we vote in order to promote the following gates as voting:
> - MOS CI
> - SUSE CI
> 
> After promotion, all patchsets submitted will have to validate these gates
> in order to get merged. And gates maintainers should ensure that the gates
> are running properly.
> 
> Please vote before (and/or during) our thursday meeting.
> 
> 
> +1 to promote both MOS and SUSE CI as voting gates.
> 
> Regards,
> H.
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [packaging][rpm] 3rd-party gates promotion to voting gates

2016-09-26 Thread Haïkel
Hi,

following our discussions about 3rd party gates in RPM packaging project,
I suggest that we vote in order to promote the following gates as voting:
- MOS CI
- SUSE CI

After promotion, all patchsets submitted will have to validate these gates
in order to get merged. And gates maintainers should ensure that the gates
are running properly.

Please vote before (and/or during) our thursday meeting.


+1 to promote both MOS and SUSE CI as voting gates.

Regards,
H.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev