Personally, I always add the remote review url as described in [1], so I just have to 'git push review' my changes.
[1] https://wiki.eclipse.org/Gerrit#Adding_a_dedicated_remote On Tue, May 5, 2015 at 4:28 PM, Mickael Istria <mist...@redhat.com> wrote: > On 05/05/2015 10:26 PM, Konstantin Komissarchik wrote: > > So what should I have done if I wanted to exercise the new verifier > feature? > > > To create a Gerrit review instead of pushing directly, push to branch > "refs/for/master" instead of "master". This creates the review and the > validation job starts ASAP. > > https://wiki.eclipse.org/index.php?title=Simrel/Contributing_to_Simrel_Aggregation_Build#Contribute_via_a_Gerrit_review > > -- > Mickael Istria > Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> > My blog <http://mickaelistria.wordpress.com> - My Tweets > <http://twitter.com/mickaelistria> > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > -- "Have you tried turning it off and on again" - The IT Crowd And if that fails, then http://goo.gl/tnBgH5
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
