We have similar setup like openstack gerrit, and recently we added a new
repo to our CI infra.
Observations were as follows.
1. Initially it looked like, this newly added repo wasn't pushing the
changes to upstream github repository (our gerrit is integrated with Github
as upstream).
2. The revie
list should be “
> {enqueue,promote,show}”
>
> Regards,
>
> Octavian.
>
> [1] https://github.com/openstack-infra/zuul
>
>
> On 9 Jun 2015, at 21:40, Vinay Mahuli wrote:
>
> So, I believe that we cannot prioritize a review in gerrit at the moment.
> Is my unde
enqueue enqueue a change
promote promote one or more changes
showvalid show subcommands
Regards,
Vinay
On Thu, Jun 11, 2015 at 1:34 AM, Jeremy Stanley wrote:
> On 2015-06-10 19:18:58 + (+), Octavian Ciuhandu wrote:
> > > On 9 Jun 2015,
So, I believe that we cannot prioritize a review in gerrit at the moment.
Is my understanding correct?
Regards,
Vinay
On Fri, Jun 5, 2015 at 12:01 AM, Vinay Mahuli wrote:
> Does any one know how to prioritize reviews in gerrit?
>
> Regards,
> Vinay
>
> On Wed, Jun 3, 2015
Does any one know how to prioritize reviews in gerrit?
Regards,
Vinay
On Wed, Jun 3, 2015 at 12:47 AM, Vinay Mahuli wrote:
> Hi,
>
> We have a similar gerrit, zuul and jenkins setup as review.openstack.org.
>
> At times, we would like to prioritize certain reviews which are cr
Hi,
We have a similar gerrit, zuul and jenkins setup as review.openstack.org.
At times, we would like to prioritize certain reviews which are critical
and of high importance due to release timelines.
I don't see an option to prioritize reviews in zuul.
All the reviews will be queued up in zu
I need info on where to make this change in a similar way how Change-Id is
checked/validated.
Regards,
Vinay
On Fri, Mar 20, 2015 at 8:51 AM, Robert Collins
wrote:
> On 19 March 2015 at 20:57, Vinay Mahuli wrote:
> > We wanted to do this only for release branches where we want t
:
> On 03/18/2015 12:08 PM, Vinay Mahuli wrote:
> > Hi,
> >
> > How to enforce users to put the "bug ids" in the review commits ?
> > A user shouldn't be able to raise a review request if the user hasn't
> > put the corresponding "bug id"
Hi,
How to enforce users to put the "bug ids" in the review commits ?
A user shouldn't be able to raise a review request if the user hasn't put
the corresponding "bug id" in the commit message.
--
Regards,
Vinay
___
OpenStack-Infra mailing list
OpenSta
Hi,
We generally create branches in gerrit using the web ui accessing admin ->
projects -> select project -> branches
Is it possible to do it using command line?
I need to automate creation of branch in gerrit with a script.
--
Regards,
Vinay
___
Open
Hi,
We have a similar continuous integration (CI) as in openstack
ci.openstack.org
In such a setup, I want to use update_bug.py which is present in below
location.
https://github.com/openstack-infra/jeepyb/blob/master/jeepyb/cmd/update_bug.py
Does anyone know how to configure this in gerrit?
Hi,
I want to know how to get git-ids associated for a particular review
request.
I am looking out for a command which takes input as review commit-id and
gives git-id as output.
Any info about this would be helpful.
--
Regards,
Vinay
___
OpenStack-In
[Resending again with subject]
Hi,
We have a similar continuous integration (CI) as in openstack
ci.openstack.org
In such a setup, we have different projects (repositories) against which
the developers commit the patches.
We get too many emails from Zuul (code Review) when
1. a new commit/
Hi,
We have a similar continuous integration (CI) as in openstack
ci.openstack.org
In such a setup, we have different projects (repositories) against which
the developers commit the patches.
We get too many emails from Zuul (code Review) when
1. a new commit/patch is submitted in gerrit/revi
Hi,
I had the a project contrail-controller earlier which was accidentally
deleted.
After that, I tried running "manage-projects -dv" which is giving below
error while adding back the deleted project.
Now, I don't have anything in /home/gerrit2/review_site/git/Juniper/
contrail-controller.git
C
Hi,
We have a similar continuous integration (CI) as in openstack
ci.openstack.org
In such a setup, we have different projects (repositories) against which
the developers commit the patches.
My query is how to handle the dependencies between projects?
At times the developers might have changes a
Wed, Mar 5, 2014 at 7:43 PM, Jay Pipes wrote:
> On Wed, 2014-03-05 at 17:10 +0530, Vinay Mahuli wrote:
> > Hi,
> >
> > From the link, http://ci.openstack.org/puppet.html#id2,
> >
> > The command "puppet apply
> > --modulepath='/opt/con
Hi,
>From the link, http://ci.openstack.org/puppet.html#id2,
The command "puppet apply
--modulepath='/opt/config/production/modules:/etc/puppet/modules' -e
'include openstack_project::puppetmaster' " doesn't work.
It says,
err:
/Stage[main]/Puppetdb::Master::Config/Puppetdb_conn_validator[pup
18 matches
Mail list logo
