Re: [openstack-dev] [all][infra] revert new gerrit

[Zaro]

There is a new web and android interface that's being developed by
guys at Google however it's not available on our version of Gerrit.  I
think it probably won't be ready until Gerrit ver 2.13+

web interface (polymer+gerrit = polygerrit):
This interface is already very usable in Gerrit 2.12.  Currently it's
only available on the gerrit-review.googlesource.com server.  If you
like you can try it out by creating an account there and access this
new UI is "https://gerrit-review.googlesource.com/?polygerrit";.  I'm
sure they would welcome your feedback.

The android interface will be announced soon it's still in early
development at this time.

__
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] [OpenStack-Infra] Gerrit Upgrade to ver 2.11, completed.

[Zaro]

On Tue, Dec 22, 2015 at 4:51 PM, Carl Baldwin  wrote:
> I noticed another thing.  I'm working with a chain of three patches.
> I just updated the patch in the middle [1] to patch set 37.  I noticed
> that the list of "Related Changes" (in the upper right of the page)
> didn't look right.  The change above it in the list (the one that
> depends it) looked strange.  Looking closer, I realized that the
> dependent patch was linking to patch set 4 [2] which is really old.
> Go here [1] and take a look.
>
> The latest patch set in 212669 (24) depends on a slightly out of date
> version of 192032 (36 of 37).  So, gerrit decides to navigate me to
> version 4 of 212669?  Seems arbitrary to me.  Why doesn't it navigate
> me to the latest version of 212669?  That would be much more useful.

I believe what Gerrit is doing is linking to the PS that was based off
of the one you are currently on.  You can see this by checking the
parent and next commit SHA.  So it looks like 212669/4 is based on
192032/10 therefore I'm guessing that you were actually looking at
192032/10 when you clicked on the link.  I'm not sure that Gerrit took
you to the wrong PS I'm guessing that you were on a newer 212669 PS
than you thought?   I find this disorienting as well and always have
to remind myself to look at the "Patch Sets" indicator to get on the
right page.

>
> Over the last few days, this "Related Changes" table has confused me.
> This is the first time I took the time to pinpoint why it is confusing
> me.
>
> Carl
>
> PS  I'm trying to document these issues in this thread so that they
> don't get lost.  I suppose at some point we need to be feeding this
> stuff up to gerrit.  I was hoping to get other stuff done before
> vacation and so I'm hesitant to stop what I'm doing and shift my
> thinking toward filling out bug reports against gerrit.  What should
> we do?  Should we individually go file bugs against gerrit?  Or,
> should we funnel it through someone working on gerrit in openstack?

Thanks for keeping the openstack infra team updated about issues
you're having with Gerrit, it's good feedback and will help improve
Gerrit going forward.  Unless it's something that requires immediate
attention I would recommend entering a bug/feature request yourself on
upstream Gerrit issue tracker. You can CC me on the issues and I will
try to determine whether it's openstack specific or a general upstream
issue.

>
> [1] https://review.openstack.org/#/c/192032/37
> [2] https://review.openstack.org/#/c/212669/4
>

__
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] [OpenStack-Infra] Gerrit Upgrade to ver 2.11, completed.

[Zaro]

These look like upstream issues.  Best thing to do is report these
bugs upstream: https://code.google.com/p/gerrit/issues/list


On Tue, Dec 22, 2015 at 11:25 AM, Aishwarya Thangappa
 wrote:
> Hi there,
>
> I noticed a couple of things which I would like to see fixed.
> 1. When you try to reply to a review comment, it jumps to the previous or
> next comment and you have to scroll again to get back to it.
> 2. When you scroll down through a file, the Patch Set bar gets hidden. You
> have to scroll all the way up to see it again.
> I saw this behavior with both chrome and firefox.
>
> Aish.
>

__
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] [OpenStack-Infra] Gerrit Upgrade to ver 2.11, completed.

[Zaro]

Hit '?' and it says '/' is find, give that a try.

Looks like in Gerrit 2.11 the 'f' to get a popup of the list of files
is only available in unified diff view.  I don't remember if it was
available in side-by-side view on Gerrit 2.8.

-Khai


On Mon, Dec 21, 2015 at 5:04 PM, Carl Baldwin  wrote:
> I also really miss being able to pull up the list of files in diff
> view with the 'f' key.  Any equivalent?
>
> Carl
>
> On Mon, Dec 21, 2015 at 4:07 PM, Carl Baldwin  wrote:
>> I noticed a couple of things today while reviewing a largish page [1].
>> First, when I search for something using the browser's builtin search
>> (Chrome, Mac OSX Yosemite), it doesn't seem to find occurrences that
>> are not in the visible portion of the page.  For example, when I
>> search for DNSDOMAIN, I get 1 hit from the top of the file.  The file
>> actually has almost 30 hits for this string.  For example, scroll down
>> to about L310 in the file.  You'll see them all over the place (and
>> now Chrome's search finds these hits if you try again).  I use to use
>> search within a file with the old gerrit and never noticed this
>> problem.
>>
>> The other thing that I found annoying is when I scroll the page with
>> my trackpad, it now jumps around sometimes to a different part of the
>> page.  For example, I'll scroll up to find a spot in the file and when
>> I think I've arrived, it will jump back down the file a bit.  It is
>> disorienting.  Of course, now it isn't doing it anymore so it doesn't
>> seem to be all the time.  It was behaving this way for a good 20
>> minutes trying to get through this file.
>>
>> Carl
>>
>> Carl
>>
>> [1] https://review.openstack.org/#/c/212213/36/neutron/db/dns_db.py
>>
>> On Thu, Dec 17, 2015 at 8:17 PM, Brian Haley  wrote:
>>> On 2015-12-16 16:24, openstack-dev-requ...@lists.openstack.org wrote:

 Thanks to everyone for their patience while we upgraded to Gerrit
 2.11.  I'm happy to announce that we were able to successfully
 completed this task at around 21:00 UTC.  You may hack away once more.

 If you encounter any problems, please let us know here or in
 #openstack-infra on Freenode.
>>>
>>>
>>> I'm still undecided on 2.11, have to give it more time, but I have noticed
>>> one thing that's annoying...
>>>
>>> Trying to copy text from a review no longer works easily.  When I highlight
>>> text there's a little "bubble" pop-up of {press c to comment}, which seems
>>> to interfere with both my three-button mouse copy buffer, as well as Ctrl-C.
>>> Call me a nitpicker, but having to highlight text, right-button click, Copy,
>>> right-button click, Paste, is a pain.
>>>
>>> Maybe someone has a simple work-around for that.
>>>
>>> -Brian
>>>
>>> __
>>> 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] Gerrit Upgrade to ver 2.11 completed.

[Zaro]

forgot this one as well: https://review.openstack.org/241278

On Thu, Dec 17, 2015 at 7:02 AM, Zaro  wrote:
> On Thu, Dec 17, 2015 at 12:31 AM, Andrea Frittoli
>  wrote:
>> Thanks for the upgrade, and for all the effort you folks put into keeping
>> our gerrit close to upstream!
>>
>> One thing that I find inconvenient in the new UI is the size of the middle
>> (test results) column: it's too narrow, no matter how large my browser
>> window is, or what browser I use - which causes the name of some of the jobs
>> to wrap to a second line, making it really hard to read test results. At
>> least that's my experience on tempest reviews, where we have a lot of jobs,
>> and rather long names - see [0] for instance.
>>
>> Is there any chance via configuration to make that column slightly wider?
>>
>
> There are a few proposals already:
>   https://review.openstack.org/258751
>   https://review.openstack.org/258744
>
>
>> thank you!
>>
>> andrea
>> [0] https://review.openstack.org/#/c/254274/
>>

__
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] [OpenStack-Infra] Gerrit Upgrade to ver 2.11 completed.

[Zaro]

On Thu, Dec 17, 2015 at 12:31 AM, Andrea Frittoli
 wrote:
> Thanks for the upgrade, and for all the effort you folks put into keeping
> our gerrit close to upstream!
>
> One thing that I find inconvenient in the new UI is the size of the middle
> (test results) column: it's too narrow, no matter how large my browser
> window is, or what browser I use - which causes the name of some of the jobs
> to wrap to a second line, making it really hard to read test results. At
> least that's my experience on tempest reviews, where we have a lot of jobs,
> and rather long names - see [0] for instance.
>
> Is there any chance via configuration to make that column slightly wider?
>

There are a few proposals already:
  https://review.openstack.org/258751
  https://review.openstack.org/258744


> thank you!
>
> andrea
> [0] https://review.openstack.org/#/c/254274/
>

__
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] [OpenStack-Infra] Gerrit Upgrade to ver 2.11 completed.

[Zaro]

We have identified this and will look into it soon.  Thanks for
reporting the issue.

On Wed, Dec 16, 2015 at 2:02 PM, Michał Dulko  wrote:
> On 12/16/2015 10:22 PM, Zaro wrote:
>> Thanks to everyone for their patience while we upgraded to Gerrit
>> 2.11.  I'm happy to announce that we were able to successfully
>> completed this task at around 21:00 UTC.  You may hack away once more.
>>
>> If you encounter any problems, please let us know here or in
>> #openstack-infra on Freenode.
>>
>> Enjoy,
>> -Khai
>>
>
> Good job! :)
>
> In Cinder we have an impressive number of Third-Party CIs. Even with
> "Toggle CI" option set to not-showing CIs comments, the comment frame is
> displayed. E.g. [1]. This makes reading reviewers comments harder. Is
> there any way of disabling that? Or any chances of fixing it up in
> Gerrit deployment itself?
>
> [1] https://review.openstack.org/#/c/248768/
>
> ___
> OpenStack-Infra mailing list
> openstack-in...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

__
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] [OpenStack-Infra] Gerrit Upgrade to ver 2.11 completed.

[Zaro]

On Tue, Dec 1, 2015 at 6:38 PM, Spencer Krum  wrote:
> Hi All,
>
> The infra team will be taking gerrit offline for an upgrade on December
> 16th. We
> will start the operation at 17:00 UTC and will continue until about
> 21:00 UTC.
>
> This outage is to upgrade Gerrit to version 2.11. The IP address of
> Gerrit will not be changing.
>
> There is a thread beginning here:
> http://lists.openstack.org/pipermail/openstack-dev/2015-October/076962.html
> which covers what to expect from the new software.
>
> If you have questions about the Gerrit outage you are welcome to post a
> reply to this thread or find the infra team in the #openstack-infra irc
> channel on freenode. If you have questions about the version of Gerrit
> we are upgrading to please post a reply to the email thread linked
> above, or again you are welcome to ask in the #openstack-infra channel.
>


Thanks to everyone for their patience while we upgraded to Gerrit
2.11.  I'm happy to announce that we were able to successfully
completed this task at around 21:00 UTC.  You may hack away once more.

If you encounter any problems, please let us know here or in
#openstack-infra on Freenode.

Enjoy,
-Khai

__
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] [infra][all] Reviews with a prio label?

[Zaro]

Upstream Gerrit has been working on a tagging feature for a while now.
Take a look at the gerrit discussion thread[1] if you want more info
on how it came about.   They decided to call it 'hashtag' or '#' (the
name being very controversial).Looks like some of the feature is
in Gerrit 2.11 already[2] but it's definitely still work in progress
with sparse documentation thus far.  I believe it should be fully
available in the 2.12 release and you can track it with
topic:hashtag[3] on upstream.

[1] https://groups.google.com/d/msg/repo-discuss/-dHTaWt_LJA/JwUGeCPDpTUJ
 and  https://groups.google.com/d/msg/repo-discuss/jZ0raMyuiG0/YlntREKG0FgJ
[2] 
https://review-dev.openstack.org/Documentation/config-hooks.html#_hashtags_changed
[3] https://gerrit-review.googlesource.com/#/q/topic:hashtags


On Tue, Oct 20, 2015 at 9:40 AM, Markus Zoeller  wrote:
> "Daniel P. Berrange"  wrote on 10/20/2015 06:21:05
> PM:
>
>> From: "Daniel P. Berrange" 
>> To: "OpenStack Development Mailing List (not for usage questions)"
>> 
>> Date: 10/20/2015 06:21 PM
>> Subject: Re: [openstack-dev] [infra][all] Reviews with a prio label?
>> What you're describing is really just a special-case of allowing
>> arbitrary user tagging of changes. If gerrit had a free-format
>> keyword tag facility that users could use & query, it'd open up many
>> possible options for improving our general workflow, and letting
>> users customize their own workflow.
>>
>> Regards,
>> Daniel
>
> True. My proposal is indeed a poor man's way of tagging. My research,
> if Gerrit provides such a feature, didn't bring up any results.
>
> Regards, Markus Zoeller (markus_z)
>
>
> __
> 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] [infra] Upgrade to Gerrit 2.11

[Zaro]

Thanks for the suggestion Markus.  I think the path for those types of
suggestions would be thru a spec:
http://specs.openstack.org/openstack-infra/infra-specs/


Thanks for reporting these Yuriy.  I've created a checklist[1] to
track things to verify before we actually do anything.  I think at
this point, the etherpad might be the most appropriate place to track
these types of issues.
>
> Where should I direct issues I find in review-dev.openstack.org? I've found
> two so far:
> - "Unified diff" button in diff view (next to navigation arrows) always
> leads to Internal Server Error;

Known issue, fixed here: https://gerrit-review.googlesource.com/#/c/71500/

> - cgit links in change screen have "%2F" in URL instead of "/" which leads
> to Apache's Not Found instead of cgit's one.

I believe the fix for this is to just disable the gitweb.urlEncode
configuration: 
https://gerrit-review.googlesource.com/Documentation/config-gerrit.html
Will try it out shortly.


[1] https://etherpad.openstack.org/p/test-gerrit-2.11

__
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] [infra] Upgrade to Gerrit 2.11

[Zaro]

Hello All,

The openstack-infra team would like to upgrade from our Gerrit 2.8 to
Gerrit 2.11.  We are proposing to do the upgrade shortly after the
Mitaka summit.  The main motivation behind the upgrade is to allow us
to take advantage of some of the new REST api, ssh commands, and
stream events features.  Also we wanted to stay closer to upstream so
it will be easier to pick up more recent features and fixes.

We want to let everyone know that there is a big UI change in Gerrit
2.11.  The change screen (CS), which is the main view for a patchset,
has been completely replaced with a new change screen (CS2).  While
Gerrit 2.8 contains both old CS and CS2, I believe everyone in
Openstack land is really just using the old CS.  CS2 really wasn't
ready in 2.8 and really should never be used in that version.  The CS2
has come a long way since then and many other big projects have moved
to using Gerrit 2.11 so it's not a concern any longer.  If you would
like a preview of Gerrit 2.11 and maybe help us test it, head over to
http://review-dev.openstack.org.  If you are very opposed to CS2 then
you may like Gertty (https://pypi.python.org/pypi/gertty) instead.  If
neither option works for you then maybe you can help us create a new
alternative :)

We are soliciting feedback so please let us know what you think.

Thanks You.

__
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] Infra needs Gerrit developers

[Zaro]

Hello All,

I believe you are all familiar with Gerrit.  Our community relies on it
quite heavily and it is one of the most important applications in our CI
infrastructure. I work on the OpenStack-infra team and I've been hacking on
Gerrit for a while. I'm the infra team's sole Gerrit developer. I also test
all our Gerrit upgrades prior to infra upgrading Gerrit.  There are many
Gerrit feature and bug fix requests coming from the OpenStack community
however due to limited resources it has been a challenge to meet those
requests.

I've been fielding some of those requests and trying to make Gerrit better
for OpenStack.  I was wondering whether there are any other folks in our
community who might also like to hack on a large scale java application
that's being used by many corporations and open source projects in the
world.  If so this is an opportunity for you to contribute.  I'm hoping to
get more OpenStackers involved with the Gerrit community so we can
collectively make OpenStack better.  If you would like to get involved let
the openstack-infra folks know[1] and we will try help get you going.

For instance our last attempt to upgrading Gerrit failed due to a bug[2]
that makes repos unusable on a diff timeout.   This bug is still not fixed
so a nice way to contribute is to help us fix things like this so we can
continue to use never versions of Gerrit.

[1] in #openstack-infra or on openstack-in...@lists.openstack.org
[2] https://code.google.com/p/gerrit/issues/detail?id=3424


Thank You.
- Khai (AKA zaro)
__
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] [CI] Jenkins jobs are not executed when setting up a new CI system.

[Zaro]

Tang, Have you tried to look at the function registrations and gearman
queue on the gearman server as i suggested?  The instructions are in the
wiki i referenced (in 'Starting the gearman workers' section).  What you
are seeing from the gear_client could also be from passing in a function
name that does not exist.  Unfortunately the simple gear_client does not
check whether the passed in functions are valid so what you want to do is
verify that the gearman functions have been registered by using the
'workers' command.



On Fri, Jul 24, 2015 at 1:09 AM, Tang Chen  wrote:

>
> On 07/24/2015 03:36 PM, Tang Chen wrote:
>
> Hi Zaro,
>
> Thanks to reply.
>
> On 07/24/2015 03:06 PM, Zaro wrote:
>
>  That is correctly, the Jenkins UI will not show any info about the
> gearman queue.  If job is pending in Jenkins that means it's been added to
> the gearman queue and has been moved to the jenkins build queue.  The
> jenkins UI will only show the job once it's in the jenkins queue.
>
>  Hmm.  What happens when you manually start a build by click on the build
> icon in the jenkins UI?
>
>
> If I click the build icon in the jenkins UI, the job can run. Wired, isn't
> it ?
>
> Thanks.
>
>
>   I'm wondering if maybe your labels are configured correctly for your
> jobs and slaves.  Are there any labels on the job or the nodes (master or
> slaves)? I think the jobs would be in a pending state if there are labels
> on nodes and jobs but they do not match.  I would check to see if there are
> any labels on the jobs and if there are then I would remove all of the
> labels and try again.  There are step by step directions on how to setup
> the gearman-plugin in the jenkins wiki[1] which also shows you how to debug
> by viewing the gearman server queue and function registrations.  Try to
> make sure the functions are registered correctly and that the job is in the
> queue after you run the gear-client command.
>
>  A couple of questions:
> What version of Jenkins are you running?  I think openstack runs on 1.565.3
> Also I don't think we've ever tested Jenkins and the gearman server
> running on the same machine or VM.  Maybe one thing you can try is to run
> them on separate VMs?
>
>
> I don't have any label, and only a master, no slave.
>
> My jenkins is 1.609.1.
>
> The whole problem is described here:
>
> http://paste.openstack.org/show/405051/
>
> Please help to check and see.
>
>
> BTW, I post the problem to #openstack-infra IRC channel. You can join into
> that meeting if you'd like to.
>
>
> Thanks.
>
>
>  [1] https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin
>
>
>
__
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] [CI] Jenkins jobs are not executed when setting up a new CI system.

[Zaro]

That is correctly, the Jenkins UI will not show any info about the gearman
queue.  If job is pending in Jenkins that means it's been added to the
gearman queue and has been moved to the jenkins build queue.  The jenkins
UI will only show the job once it's in the jenkins queue.

Hmm.  What happens when you manually start a build by click on the build
icon in the jenkins UI?  I'm wondering if maybe your labels are configured
correctly for your jobs and slaves.  Are there any labels on the job or the
nodes (master or slaves)? I think the jobs would be in a pending state if
there are labels on nodes and jobs but they do not match.  I would check to
see if there are any labels on the jobs and if there are then I would
remove all of the labels and try again.  There are step by step directions
on how to setup the gearman-plugin in the jenkins wiki[1] which also shows
you how to debug by viewing the gearman server queue and function
registrations.  Try to make sure the functions are registered correctly and
that the job is in the queue after you run the gear-client command.

A couple of questions:
What version of Jenkins are you running?  I think openstack runs on 1.565.3
Also I don't think we've ever tested Jenkins and the gearman server running
on the same machine or VM.  Maybe one thing you can try is to run them on
separate VMs?

[1] https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin


On Thu, Jul 23, 2015 at 11:20 PM, Tang Chen  wrote:

>
> On 07/24/2015 12:59 PM, Zaro wrote:
>
>  Hello Tang,  Openstack slaves only have a single executor so what you
> are probably seeing is due to using build slaves that have multiple
> executors.  There were a few bugs[1] that was fixed recently around these
> types of deadlock issues.   The new gearman-plugin release[2] contains
> fixes for those issues.  Also if you want to test the gearman-plugin with
> Jenkins independently of zuul you can use the simple
> gearman-plugin-client[3] to send jobs your gearman server to see if the
> jobs get built.
>
>  [1] https://issues.jenkins-ci.org/browse/JENKINS-28891 and
> https://issues.jenkins-ci.org/browse/JENKINS-25867
> [2]
> http://repo.jenkins-ci.org/repo/org/jenkins-ci/plugins/gearman-plugin/0.1.2/
> [3] https://github.com/zaro0508/gearman-plugin-client
>
>
> Hi Zaro,
>
> Thanks for the reply.
>
> But I updated the gearman plugin to 0.1.2, and used the
> gearman-plugin-client to submit jobs.
>
> # python gear_client.py -s localhost
> --function=build:noop-check-communication
>
> Sat Jul 25 14:16:57 2015
> Sending job: build:noop-check-communication to localhost with
> params={'OFFLINE_NODE_WHEN_COMPLETE': 'false', 'uuid':
> '08ad7a195237493d91eea55789e76128'}
>
> Waiting for jobs to finish.
>
>
> It doesn't work. The job submitted by the client is also pending.
>
> BTW, I cannot see the job submitted by client in my Jenkins GUI. Is that
> correct ?
>
> Thanks.
>
>
__
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] [CI] Jenkins jobs are not executed when setting up a new CI system.

[Zaro]

Hello Tang,  Openstack slaves only have a single executor so what you are
probably seeing is due to using build slaves that have multiple executors.
There were a few bugs[1] that was fixed recently around these types of
deadlock issues.   The new gearman-plugin release[2] contains fixes for
those issues.  Also if you want to test the gearman-plugin with Jenkins
independently of zuul you can use the simple gearman-plugin-client[3] to
send jobs your gearman server to see if the jobs get built.

[1] https://issues.jenkins-ci.org/browse/JENKINS-28891 and
https://issues.jenkins-ci.org/browse/JENKINS-25867
[2]
http://repo.jenkins-ci.org/repo/org/jenkins-ci/plugins/gearman-plugin/0.1.2/
[3] https://github.com/zaro0508/gearman-plugin-client

-Khai

On Thu, Jul 23, 2015 at 9:13 PM, Tang Chen  wrote:

>
> On 07/24/2015 12:00 PM, Tang Chen wrote:
>
>>
>> On 07/24/2015 10:08 AM, Tang Chen wrote:
>>
>>>
>>> On 07/23/2015 11:44 PM, Asselin, Ramy wrote:
>>>
 Are you running on 'master' nodes? I remember seeing an issue where
 with a recent version of Jenkins or a plugin where it doesn't execute jobs
 on the master node.
 But when run on non-master jenkins slaves, it works fine.

>>>
>>> I checked my configuration, and made sure these things:
>>> 1. I have only a master node, no slave node.
>>> 2. I have 20 idle executors on master node.
>>> 3. My master node is online.
>>> 4. My master node is set to "Utilize this node as much as possible".
>>> 5. zuul is able to be notified by Gerrit, and tell Jenkins to start jobs.
>>>
>>> But the jobs are always pending.
>>>
>>
>> And my Gearman reports this error sometimes.
>>
>> 2015-07-25 10:50:44,914 ERROR gear.Server: Exception in poll loop:
>> Traceback (most recent call last):
>>   File "/usr/local/lib/python2.7/dist-packages/gear/__init__.py", line
>> 2614, in _doPollLoop
>> self._pollLoop()
>>   File "/usr/local/lib/python2.7/dist-packages/gear/__init__.py", line
>> 2626, in _pollLoop
>> ret = self.poll.poll()
>> IOError: [Errno 4] Interrupted system call
>>
>> Not sure if it has anything to do with this problem.
>>
>> In Jenkins GUI, Gearman connection is tested successfully on
>> 127.0.0.1:4730.
>>
>
> Seeing from zuul debug log, Gearman has successfully submitted the jobs.
>
> 2015-07-25 11:42:09,255 DEBUG zuul.Scheduler: Adding trigger event:
> 
> 2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Done adding trigger event:
> 
> 2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Run handler awake
> 2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Fetching trigger event
> 2015-07-25 11:42:09,256 DEBUG zuul.Scheduler: Processing trigger event
> 
> 2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager: Event
>  for
> change  matched  patchset-created> in pipeline 
> 2015-07-25 11:42:09,257 INFO zuul.Scheduler: Adding openstack-dev/sandbox,
>  to 
> 2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager: Considering
> adding change 
> 2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager: Checking
> for changes needed by :
> 2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager:   No
> changes needed
> 2015-07-25 11:42:09,257 DEBUG zuul.IndependentPipelineManager: Adding
> change  to queue  openstack-dev/sandbox>
> 2015-07-25 11:42:09,258 DEBUG zuul.IndependentPipelineManager: Event
>  for
> change  matched  patchset-created> in pipeline 
> 2015-07-25 11:42:09,258 INFO zuul.Scheduler: Adding openstack-dev/sandbox,
>  to 
> 2015-07-25 11:42:09,258 DEBUG zuul.IndependentPipelineManager: Considering
> adding change 
> 2015-07-25 11:42:09,258 DEBUG zuul.IndependentPipelineManager: Unable to
> find change queue for change  in project
> openstack-dev/sandbox
> 2015-07-25 11:42:09,306 DEBUG zuul.IndependentPipelineManager: Starting
> queue processor: check
> 2015-07-25 11:42:09,306 DEBUG zuul.IndependentPipelineManager: Checking
> for changes needed by :
> 2015-07-25 11:42:09,306 DEBUG zuul.IndependentPipelineManager:   No
> changes needed
> 2015-07-25 11:42:09,306 DEBUG zuul.IndependentPipelineManager: Preparing
> ref for: 
> 2015-07-25 11:42:09,307 INFO zuul.IndependentPipelineManager: Change
>  depends on changes []
> 2015-07-25 11:42:09,307 DEBUG zuul.MergeClient: Submitting job  0x7ff518325490 handle: None name: merger:merge unique:
> b425daae0cec4ff3b0d4920ee5533c9c> with data {'items': [{'oldrev': None,
> 'newrev': None, 'refspec': u'refs/changes/60/205360/1', 'merge_mode': 2,
> 'number': u'205360', 'project': 'openstack-dev/sandbox', 'url': 'ssh://
> f...@review.openstack.org:29418/openstack-dev/sandbox', 'branch':
> u'master', 'patchset': u'1', 'ref': 'Z81183af13086459d9d9fb8c06af86c09'}]}
> 2015-07-25 11:42:09,308 DEBUG zuul.IndependentPipelineManager: Finished
> queue processor: check (changed: False)
> 2015-07-25 11:42:09,309 DEBUG zuul.IndependentPipelineManager: Starting
> queue processor: silent
> 2015-07-25 11:42:09,309 DEBUG zuul.IndependentPipelineManager: Finished
> queue processor: silent (changed: False)
> 2015-07-25

Re: [openstack-dev] [infra] how to trigger a set of jenkins jobs

[Zaro]

I would encourage you to take a look at zuul but if you prefer not to use
it then I believe you can also achieve your use case just using Jenkins by
setting up multiple jobs with the same trigger.  The jenkins job builder
tool will help you setup and manage those jobs.

-Khai
__
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] Please stop reviewing code while asking questions

[Zaro]

To follow up on Robert's post, Gerrit's query command [1] supports the
retrieval of comments for each patchset so maybe we just need to add the
'--comments' option when requesting changes [2] ?

Since I've posted, I'll just provide my own opinion on this topic.  I have
no problems with a -1 ask a question vote for any reason but I do think
that it's irresponsible to _not_ follow up.  So it's the follow up that I
would like to see fixed not the restriction on reviews because I feel that
it would discourage reviews.

[1] https://review.openstack.org/Documentation/cmd-query.html
[2]
https://git.openstack.org/cgit/openstack-infra/reviewstats/tree/reviewstats/utils.py#n170


On Fri, Apr 24, 2015 at 9:04 PM, Robert Collins 
wrote:

>
> I believe we'll need to switch to the REST JSON API, which gertty uses
> and gets comments -> some nontrivial refactoring implied, and I
> shudder to think about the performance impact.
>
> I've wanted to rewrite reviewstats for a while... this might be the
> trigger...
>
> -Rob
>
>
> --
> Robert Collins 
> Distinguished Technologist
> HP Converged Cloud
>
> __
> 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] [all] need help with my first commit: The branch 'master' does not exist on the given remote 'gerrit'

[Zaro]

Hello.  I think there might be something wrong with git-review in your
env.  You might want try in another env, preferably linux if its handy.  I
noticed your origin is from github?  you should clone from here instead:
http://git.openstack.org/cgit/stackforge/congress

Here's what you should get when you run the commands to setup the remotes:

~/temp/congress$ git review -s
Creating a git remote called "gerrit" that maps to:
ssh://zaro0...@review.openstack.org:29418/stackforge/congress.git
~/temp/congress$ git remote -v
gerrit ssh://zaro0...@review.openstack.org:29418/stackforge/congress.git
(fetch)
gerrit ssh://zaro0...@review.openstack.org:29418/stackforge/congress.git
(push)
origin https://git.openstack.org/stackforge/congress (fetch)
origin https://git.openstack.org/stackforge/congress (push)



On Mon, Jan 26, 2015 at 9:09 PM, Tran, Steven  wrote:

>  Hi,
>
>Can someone point out what I miss that results in the following warning?
>
>
>
> $ git review
>
> The branch 'master' does not exist on the given remote 'gerrit'. If
>
> these changes are intended to start a new branch, re-run with the '-R'
>
> option enabled.
>
>
>
>
>
> I believe I shouldn’t do “git review -R” because it prompts me to submit
> multiple commits.
>
> I can do “git review -s” without any errors.
>
> I follow the steps at
> http://docs.openstack.org/infra/manual/developers.html#starting-a-change
>
> I’m using Cygwin.
>
>
>
> $ git status
>
> On branch bp/murano-driver
>
> nothing to commit, working directory clean
>
>
>
> $ git branch
>
> * bp/murano-driver
>
>   master
>
>
>
> $ git config --list
>
> core.repositoryformatversion=0
>
> core.filemode=true
>
> core.bare=false
>
> core.logallrefupdates=true
>
> core.ignorecase=true
>
> remote.origin.url=https://github.com/stackforge/congress.git
>
> remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
>
> branch.master.remote=origin
>
> branch.master.merge=refs/heads/master
>
> remote.gerrit.url=ssh://
> steven...@review.openstack.org:29418/stackforge/congress.git
>
> user.name=Steven Tran
>
> user.email=steven.tr...@hp.com
>
> gitreview.username=stevenldt
>
>
>
> $ git log
>
> commit 5567b6e4622246ad86cdb9d6c0643427573e8d13
>
> Author: Steven Tran 
>
> Date:   Mon Jan 26 17:19:38 2015 -0800
>
>
>
> Change-Id: Idc4abf32a7aa25231a7a6df511df998a0a3a50ad
>
> Implements: blueprint murano-driver
>
>
>
> Thanks,
>
> -Steven
>
> __
> 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] [infra] [storyboard] Nominating Yolanda Robla for StoryBoard Core

[Zaro]

+1

On Tue, Dec 23, 2014 at 2:34 PM, Michael Krotscheck 
wrote:

> Hello everyone!
>
> StoryBoard is the much anticipated successor to Launchpad, and is a
> component of the Infrastructure Program. The storyboard-core group is
> intended to be a superset of the infra-core group, with additional
> reviewers who specialize in the field.
>
> Yolanda has been working on StoryBoard ever since the Atlanta Summit, and
> has provided a diligent and cautious voice to our development effort. She
> has consistently provided feedback on our reviews, and is neither afraid of
> asking for clarification, nor of providing constructive criticism. In
> return, she has been nothing but gracious and responsive when improvements
> were suggested to her own submissions.
>
> Furthermore, Yolanda has been quite active in the infrastructure team as a
> whole, and provides valuable context for us in the greater realm of infra.
>
> Please respond within this thread with either supporting commentary, or
> concerns about her promotion. Since many western countries are currently
> celebrating holidays, the review period will remain open until January 9th.
> If the consensus is positive, we will promote her then!
>
> Thanks,
>
> Michael
>
>
> References:
>
> https://review.openstack.org/#/q/reviewer:%22yolanda.robla+%253Cinfo%2540ysoft.biz%253E%22,n,z
>
> http://stackalytics.com/?user_id=yolanda.robla&metric=marks
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [CI]Setup CI system behind proxy

[Zaro]

Could you please clarify?  Do you mean you want to setup everything behind
a proxy?  or do you mean you want to setup just gerrit behind a proxy?

On Mon, Dec 1, 2014 at 6:26 PM, thanh le giang 
wrote:

> Dear all
>
> I have set up a CI system successfully with directly access to internet.
> Now I have another requirement which requires setting up CI system behind
> proxy but i can't find any way to configure zuul to connect to gerrit
> through proxy.
>
> Any advice is appreciated.
>
> Thanks and Regards
>
> --
> L.G.Thanh
>
> Email: legiangt...@gmail.com 
> lgth...@fit.hcmus.edu.vn
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [infra] Nominating Anita Kuno for project-config-core

[Zaro]

+1

On Sun, Sep 28, 2014 at 4:25 PM, Joshua Hesketh <
joshua.hesk...@rackspace.com> wrote:

> Absolutely. +1.
>
> Rackspace Australia
>
>
> On 9/27/14 1:34 AM, James E. Blair wrote:
>
>> I'm pleased to nominate Anito Kuno to the project-config core team.
>>
>> The project-config repo is a constituent of the Infrastructure Program
>> and has a core team structured to be a superset of infra-core with
>> additional reviewers who specialize in the area.
>>
>> Anita has been reviewing new projects in the config repo for some time
>> and I have been treating her approval as required for a while.  She has
>> an excellent grasp of the requirements and process for creating new
>> projects and is very helpful to the people proposing them (who are often
>> creating their first commit to any OpenStack repository).
>>
>> She also did most of the work in actually creating the project-config
>> repo from the config repo.
>>
>> Please respond with support or concerns and if the consensus is in
>> favor, we will add her next week.
>>
>> Thanks,
>>
>> Jim
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [infra] Nominations for jenkins-job-builder core

[Zaro]

Looks like there are no objections to this nomination so I have made Marc
and Darragh Jenkins Job Builder Core reviewers.  Congrats guys and keep the
reviews rolling.


On Mon, Jun 30, 2014 at 10:52 AM, Darragh Bailey 
wrote:

>
>
> On 20 June 2014 22:01, James E. Blair  wrote:
>
>> Hi,
>>
>> The Jenkins Job Builder project (part of the Infrastructure program) is
>> quite popular even outside of OpenStack and has a group of specialist
>> core reviewers supplemental to the rest of the Infrastructure program.
>>
>> To that group I would like to add Darragh Bailey:
>>
>>
>> https://review.openstack.org/#/q/reviewer:%22Darragh+Bailey%22+project:openstack-infra/jenkins-job-builder,n,z
>>
>> -Jim
>>
>>
> Thanks for the nomination Jim, I'm enjoying working on JJB immensely and
> hope that I can continue to contribute in a way that others appreciate.
>
> --
> Darragh Bailey
> "Nothing is foolproof to a sufficiently talented fool"
>
> ___
> OpenStack-Infra mailing list
> openstack-in...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] 3rd Party CI vs. Gerrit

[Zaro]

David did suggest adding REST api endpoints to get data for each channel so
it doesn't necessarily require you to even use the gerrit web ui.  However
the web UI's old screen is pretty much dead so I assume the presentation
would only be available in new change screen.  I know Openstackers have had
reservations about the new change screen but please don't judge it by
trying the gerrit 2.8.x implementation.  It has improved quite a bit.  I
have been using it on the https://gerrit-review.googlesource.com and do
prefer it over the old change screen :)

-Khai

On Fri, Jun 27, 2014 at 6:38 PM, Sean Dague  wrote:

> On 06/27/2014 02:19 PM, Zaro wrote:
> >
> > Sean, there is a proposal[1] in upstream gerrit to fix this issue.
> >  David's proposal is to make Gerrit handle multiple notifications
> > channels per project which would allow us to treat bot notifications
> > differently than human notifications.  He has the same problem as we do,
> > most of his builds are done using 'third party' CI so he has many more
> > third party systems reporting to his gerrit instance than we do.  Please
> > take a look and provide feedback.
> >
> > [1] _https://code.google.com/p/gerrit/issues/detail?id=2465_
>
> That seems to require the new Change Screen?
>
> -Sean
>
> --
> Sean Dague
> http://dague.net
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] 3rd Party CI vs. Gerrit

[Zaro]

Sean, there is a proposal[1] in upstream gerrit to fix this issue.  David's
proposal is to make Gerrit handle multiple notifications channels per
project which would allow us to treat bot notifications differently than
human notifications.  He has the same problem as we do, most of his builds
are done using 'third party' CI so he has many more third party systems
reporting to his gerrit instance than we do.  Please take a look and
provide feedback.

[1] *https://code.google.com/p/gerrit/issues/detail?id=2465
*
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] [infra] Nominations for jenkins-job-builder core

[Zaro]

+1 for both Marc and Darragh

On Mon, Jun 23, 2014 at 6:54 PM, Clark Boylan  wrote:
> On Mon, Jun 23, 2014 at 1:35 AM, Antoine Musso  wrote:
>> Le 23/06/2014 01:47, Jeremy Stanley a écrit :
>>> On 2014-06-20 14:01:01 -0700 (-0700), James E. Blair wrote:
 > The Jenkins Job Builder project [...] core reviewers [...] I would
 > like to add Darragh Bailey [...] and Marc Abramowitz
>>> [...]
>>>
>>> I'm very much in favor of both Darragh and Marc as additions to the
>>> openstack-infra/jenkins-job-builder project core reviewer team.
>>> Their knowledge of the project internals and support of its existing
>>> core reviewers has been invaluable.
>>
>> Hello,
>>
>> As Jeremy said, I definitely support both nominations.  They both have
>> been a huge asset to the JJB project.
>>
> I completely agree. It has been great to see people take an interest
> in JJB as a general tool and drive it with less and less input from
> OpenStack Infra. +1 to both nominations from me.
>
> Clark
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [All] Disabling Pushes of new Gerrit Draft Patchsets

[Zaro]

Just to let you know, there have been requests to run builds/tests on
drafts changes in the past[1] so it seems like there's been mixed
feelings on running CI on changes that are not ready for human review.
  You are correct, making WIP sticky would not work because it is a
per user vote.  If someone (besides the change owner) sets the WIP
vote then the change becomes WIP and the change owner will not be able
to unset the WIP state.  Also to note, the WIP plugin is only
available on version 2.9 so an upgrade would be required.

[1] https://bugs.launchpad.net/openstack-ci/+bug/1255166

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [infra] Nominating Joshua Hesketh for infra-core

[Zaro]

I concur, +1 for Josh.

On Wed, May 21, 2014 at 2:57 PM, James E. Blair  wrote:
> The Infrastructure program has a unique three-tier team structure:
> contributors (that's all of us!), core members (people with +2 ability
> on infra projects in Gerrit) and root members (people with
> administrative access).  Read all about it here:
>
>   http://ci.openstack.org/project.html#team
>
> Joshua Hesketh has been reviewing a truly impressive number of infra
> patches for quite some time now.  He has an excellent grasp of how the
> CI system functions, no doubt in part because he runs a copy of it and
> has been doing significant work on evolving it to continue to scale.
> His reviews of python projects are excellent and particularly useful,
> but he also has a grasp of how the whole system fits together, which is
> a key thing for a member of infra-core.
>
> Please respond with any comments or concerns.
>
> Thanks, Joshua, for all your work!
>
> -Jim
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [infra] Nominating Sergey Lukjanov for infra-root

[Zaro]

I concur, +1

On Wed, May 21, 2014 at 2:42 PM, James E. Blair  wrote:
> The Infrastructure program has a unique three-tier team structure:
> contributors (that's all of us!), core members (people with +2 ability
> on infra projects in Gerrit) and root members (people with
> administrative access).  Read all about it here:
>
>   http://ci.openstack.org/project.html#team
>
> Sergey has been an extremely valuable member of infra-core for some time
> now, providing reviews on a wide range of infrastructure projects which
> indicate a growing familiarity with the large number of complex systems
> that make up the project infrastructure.  In particular, Sergey has
> expertise in systems related to the configuration of Jenkins jobs, Zuul,
> and Nodepool which is invaluable in diagnosing and fixing operational
> problems as part of infra-root.
>
> Please respond with any comments or concerns.
>
> Thanks again Sergey for all your work!
>
> -Jim
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Gerrit downtime and upgrade on 2014-04-28

[Zaro]

Do you mean making it default to WIP on every patchset that gets
uploaded?  That isn't possible with Gerrit version 2.8 because it
doesn't allow you to set a default score.  Also I don't think that
would be appropriate because I definitely would not want that as the
default setting for my workflow.  I think it would be more appropriate
to build that into git-review, maybe a configuration setting that
would set every patchset to WIP upon upload.

Gerrit 2.8 does allow you to carry the same label score forward[1] if
it's either a trivial rebase or no code has changed.  We plan to set
these options for the 'Code-Review' label, but not the Workflow label.

[1] https://gerrit-review.googlesource.com/Documentation/config-labels.html

On Fri, Apr 25, 2014 at 11:58 AM, Yuriy Taraday  wrote:
> On Fri, Apr 25, 2014 at 8:10 PM, Zaro  wrote:
>>
>> Gerrit 2.8 allows setting label values on patch sets either thru the
>> command line[1] or REST API[2].  Since we will setup WIP as a -1 score
>> on a label this will just be a matter of updating git-review to set
>> the label on new patchsets.  I'm no sure if there's a bug entered in
>> our the issue tracker for this but you are welcome to create one.
>>
>> [1] https://review-dev.openstack.org/Documentation/cmd-review.html
>> [2]
>> https://review-dev.openstack.org/Documentation/rest-api-changes.html#set-review
>
>
> Why do you object making it a default behavior on the Gerrit side?
> Is there any issue with making this label pass on to new patch sets?
>
> --
>
> Kind regards, Yuriy.
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Gerrit downtime and upgrade on 2014-04-28

[Zaro]

Gerrit 2.8 allows setting label values on patch sets either thru the
command line[1] or REST API[2].  Since we will setup WIP as a -1 score
on a label this will just be a matter of updating git-review to set
the label on new patchsets.  I'm no sure if there's a bug entered in
our the issue tracker for this but you are welcome to create one.

[1] https://review-dev.openstack.org/Documentation/cmd-review.html
[2] 
https://review-dev.openstack.org/Documentation/rest-api-changes.html#set-review


On Fri, Apr 25, 2014 at 1:56 AM, Ricardo Carrillo Cruz
 wrote:
> It would be nice to have a switch on git-review to push patchsets on WIP,
> the same way you can do with Draft.
>
> Anyone knows if there is an enhancement request/bug opened against Gerrit so
> we could implement it?
>
> Regards
>
>
> 2014-04-25 10:49 GMT+02:00 Roman Podoliaka :
>
>> Hi all,
>>
>> >>> Wouldn't it be better to make this label more persistent?
>>
>> +1. It's really annoying to press "Work in Progress" button every time
>> you upload a new patch set.
>>
>> Thanks,
>> Roman
>>
>> On Fri, Apr 25, 2014 at 11:02 AM, Yuriy Taraday 
>> wrote:
>> > Hello.
>> >
>> > On Wed, Apr 23, 2014 at 2:40 AM, James E. Blair 
>> > wrote:
>> >>
>> >> * The new "Workflow" label will have a "-1 Work In Progress" value
>> >> which
>> >>   will replace the "Work In Progress" button and review state.  Core
>> >>   reviewers and change owners will have permission to set that value
>> >>   (which will be removed when a new patchset is uploaded).
>> >
>> >
>> > Wouldn't it be better to make this label more persistent?
>> > As I remember there were some ML threads about keeping WIP mark across
>> > patch
>> > sets. There were even talks about changing git-review to support this.
>> > How about we make it better with the new version of Gerrit?
>> >
>> > --
>> >
>> > Kind regards, Yuriy.
>> >
>> > ___
>> > OpenStack-dev mailing list
>> > OpenStack-dev@lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Need help to understand Jenkins msgs

[Zaro]

then jenkins failure seems to indicate that jenkins xUnit plugin could
not find any test result files for processing.  it could be that the
test didn't get run or that it ran but didn't generate the rest
results required for the plugin to pick up?  that's probably where i
would check.

On Thu, Apr 17, 2014 at 10:16 AM, Deepak Shetty  wrote:
> Hi,
>   Can someone help me understand why Jenkins build shows failures
> for some of the tests for my patch @
> https://review.openstack.org/#/c/86888/
>
> I really couldn't understand it even after clicking those links
> TIA
>
> thanx,
> deepak
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Gerrit downtime and upgrade on 2014-04-28

[Zaro]

Hello All.  The OpenStack infra team has been working to put
everything in place so that we can upgrade review.o.o from Gerrit
version 2.4.4 to version 2.8.4  We are happy to announce that we are
finally ready to make it happen!

We will begin the upgrade on Monday, April 28th at 1600 UTC (the
OpenStack recommended 'off' week).

We would like to advise that you can expect a couple hours of downtime
followed by several more hours of automated systems not quite working
as expected.  Hopefully you shouldn't notice anyway because you should
all be on vacation :)

Please let us know if you have any concerns about this upgrade.

Thank You,

-Khai

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Gerrit 2.8 upgrade coming

[Zaro]

Hello All.  The Openstack infra team has been planning a gerrit upgrade (to
ver 2.8.x) to review.openstack.org for a while now and we are getting close
to pulling the trigger.  We need to get a few more changes approved, test
those changes on review-dev.o.o and then do the upgrade on review.o.o.   We
have tentatively planned the upgrade for May 1st-7th (the Openstack 'off'
week).   Please let us know whether this will be too much of an
inconvenience for you fine hackers.  Thanks.  -Khai
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Code review (Jenkins-job-builder / sbt-plugin)

[Zaro]

I believe we are waiting for Mathieu Gagné re-review before approving.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev