Jenkins CI granting excessive +1s

[dcaro]

I just rolled out the CI flag to all the projects this morning, restricting
jenkins to set only that flag, did that happen again after it?

On 06/17, Dan Kenigsberg wrote:
> On Tue, Jun 16, 2015 at 08:48:17PM +0200, dcaro wrote:
> > On 06/16, Eyal Edri wrote:
> > > Sounds like a bug.
> > > Jenkins should only use the CI flag and not change CR and V flags.
> > > 
> > > Might have been a misunderstanding.
> > > David, can you fix it so Jenkins will only update CI flag?
> > 
> > Can someone pass me an example of the patch that had the reviews? It's possible
> > that previously the jobs were manually modified to only set the ci flag and we
> > updated them on yaml and the manual changes got reverted. Having a sample patch
> > would allow me to trim down the list of possible jobs that give that review.
> > 
> > 
> > That can be prevented globally easily, but until all projects have the ci flag
> > we can't enforce it globally.
> 
> See for example https://gerrit.ovirt.org/#/c/42362/
> 
> Patch Set 5: Code-Review+1 Continuous-Integration+1 Verified+1
> 
> in a later run seems to have fixed this
> 
> Patch Set 6: Continuous-Integration+1

-- 
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Tel.: +420 532 294 605
Email: dcaro at redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20150617/daf3d526/attachment.sig>