Hi Tang,
Please use a new thread for this new question. I'd like to keep the current
thread focused on How to set a proxy for zuul.
Ramy
From: Tang Chen [mailto:tangc...@cn.fujitsu.com]
Sent: Tuesday, July 21, 2015 12:23 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev]
hi Asselin,
On 07/21/2015 11:52 PM, Asselin, Ramy wrote:
Tang,
#openstack-meeting is for people to come together for officially
scheduled meetings [1]
Did you try to join the 3^rd party meeting on Monday[2]? I was
chairing the meeting but did not see you. That would be a great forum
to
Tang,
#openstack-meeting is for people to come together for officially scheduled
meetings [1]
Did you try to join the 3rd party meeting on Monday[2]? I was chairing the
meeting but did not see you. That would be a great forum to ask these questions.
Otherwise, you can ask in #openstack-infra.
On 07/21/2015 11:42 PM, Asselin, Ramy wrote:
Hi Tang,
Please use a new thread for this new question. I'd like to keep the
current thread focused on How to set a proxy for zuul.
Sure, will start a new thread if I cannot get it through.
Thanks. :)
Ramy
*From:*Tang Chen
Hi Tang,
Can you please send me the whole job snippet you wrote.
On Tue, Jul 21, 2015 at 12:52 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
Hi Asselin, Abhishek,
I got some problems when I was trying to write a jenkins job.
I found that when zuul received the notification from gerrit,
On 07/21/2015 03:35 PM, Abhishek Shrivastava wrote:
Hi Tang,
Can you please send me the whole job snippet you wrote.
In /etc/jenkins_jobs/config/ examples.yaml, that's all.
- job-template:
name: 'noop-check-communication'
node: '{node}'
builders:
- shell: |
Hi Asselin, Abhishek,
I got some problems when I was trying to write a jenkins job.
I found that when zuul received the notification from gerrit, jenkins
didn't run the test.
I added something to noop-check-communication in
/etc/jenkins_jobs/config/ examples.yaml,
just touched a file under
If you want to create a new job then refer *dsvm-cinder-driver.yaml.sample*,
and regarding *noop-check-communication* its just for testing the first
time don't modify it.
On Tue, Jul 21, 2015 at 1:19 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
On 07/21/2015 03:35 PM, Abhishek Shrivastava
Its just because what kind of file are you creating, as touch
/tmp/noop-check-communication doesn't makes any sense to it.
On Tue, Jul 21, 2015 at 2:48 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
On 07/21/2015 04:05 PM, Abhishek Shrivastava wrote:
If you want to create a new job then refer
On 07/21/2015 04:05 PM, Abhishek Shrivastava wrote:
If you want to create a new job then refer
*dsvm-cinder-driver.yaml.sample*, and regarding
*noop-check-communication* its just for testing the first time don't
modify it.
Well, I understand. But I don't think this little change will
For writing a Jenkins Job you can refer *dsvm-cinder-driver.yaml.sample*
as a reference.
On Mon, Jul 20, 2015 at 12:04 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
Hi Abhishek,
On 07/20/2015 02:09 PM, Abhishek Shrivastava wrote:
..
Quite a nice explanation +1 for all the things
Hi Tang,
On Mon, Jul 20, 2015 at 11:18 AM, Tang Chen tangc...@cn.fujitsu.com wrote:
Hi Asselin, Abhishek,
Thanks for the reply. :)
On 07/19/2015 02:41 AM, Asselin, Ramy wrote:
HI Abhi Tang,
Sorry I missed this thread. Let me know if you’ve resolved your issues.
My repo is
Hi Abhishek,
On 07/20/2015 02:09 PM, Abhishek Shrivastava wrote:
..
Quite a nice explanation +1 for all the things you have done. Just one
more thing to ask, have you made your slave node static?
Not yet. And I haven't made my nodepool. :)
These are my next step.
But before I start
On 07/19/2015 02:41 AM, Asselin, Ramy wrote:
HI Abhi Tang,
Sorry I missed this thread. Let me know if you've resolved your issues.
My repo is undergoing migrations to reuse components in
openstack-infra/puppet-openstackci.
For single-use-nodes, the file you need has been removed here
I found that paramiko does support proxies [1].
I remember looking at this a long time ago and you should be able to update
zuul code to use it [2].
Ramy
[1] http://blog.adimian.com/2014/10/paramiko-and-corporate-proxies/
[2]
Pull Requests are welcomed.
I think you’re referring to [1], but it shouldn’t make a functional difference
since ‘name’ is not being referenced anywhere.
[1]
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/projects.yaml#L2
From: Tang Chen
Hi Asselin, Abhishek,
Thanks for the reply. :)
On 07/19/2015 02:41 AM, Asselin, Ramy wrote:
HI Abhi Tang,
Sorry I missed this thread. Let me know if you've resolved your issues.
My repo is undergoing migrations to reuse components in
openstack-infra/puppet-openstackci.
For
HI Tang,
I just pushed the file [1]. Please read the migration instructions in the
README.md.
Let me know of any issues [2].
[1]
https://github.com/rasselin/os-ext-testing/commit/9b39bb3c9a3532e753763d5e65241eeff2a20a06
[2] https://github.com/rasselin/os-ext-testing/issues/new
Thanks,
Ramy
HI Abhi Tang,
Sorry I missed this thread. Let me know if you’ve resolved your issues.
My repo is undergoing migrations to reuse components in
openstack-infra/puppet-openstackci.
For single-use-nodes, the file you need has been removed here [1]: But I see
now that it is still needed, or a
On 07/14/2015 01:46 PM, Abhishek Shrivastava wrote:
Instead of it use reusable_node option.
Thanks. Problem resolved. :)
BTW, single_use_node is written in layout.yaml by default.
If it doesn't exist anymore, do we need a patch to fix it ?
For someone who uses CI for the first time, it is
Also if you want to change it you will need to talk with Asselin Ramy who
is the owner of the repo you followed.
On Tue, Jul 14, 2015 at 12:18 PM, Abhishek Shrivastava
abhis...@cloudbyte.com wrote:
Basically it is not required, and if you see /etc/jenkins_jobs/config
folder you will find one
Basically it is not required, and if you see /etc/jenkins_jobs/config
folder you will find one dsvm-cinder-tempest.yaml which is to be used
basically not examples.yaml. So its not an issue.
On Tue, Jul 14, 2015 at 12:07 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
On 07/14/2015 01:46 PM,
Updating jobs using sudo jenkins-jobs --flush-cache update
/etc/jenkins_jobs/config/. Also update the myvendor in examples.yaml
On Mon, Jul 13, 2015 at 1:45 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
On 07/13/2015 03:50 PM, Abhishek Shrivastava wrote:
Use tester or something, also are
On 07/13/2015 04:35 PM, Abhishek Shrivastava wrote:
Updating jobs using sudo jenkins-jobs --flush-cache update
/etc/jenkins_jobs/config/. Also update the myvendor in examples.yaml
Sorry, I updated the jobs, restart the whole machine. But it still
doesn't work.
By the way, there is no
Instead of it use reusable_node option.
On Tue, Jul 14, 2015 at 9:12 AM, Tang Chen tangc...@cn.fujitsu.com wrote:
Hi Abhishek, All,
I found the problem.
My /etc/zuul/layout/layout.yaml has the following config:
jobs:
- name: ^dsvm-tempest.*$
parameter-function: single_use_node
Hi Abhishek,
I printed the self.layout.projects in zuul/scheduler.py, it is empty.
So the project was not found.
But I did do the jenkins-jobs --flush-cache update /etc/jenkins_jobs/config/
And I did configure openstack-dev/sandbox in layout.yaml.
Do you have any idea what's wrong here ?
Hi Abhishek, All,
I found the problem.
My /etc/zuul/layout/layout.yaml has the following config:
jobs:
- name: ^dsvm-tempest.*$
parameter-function: single_use_node
But in _parseConfig() in zuul/scheduler.py, it failed to find
single_use_node().
fname =
Hi all,
I have constructed my CI system.
When I tested it with sandbox project, I posted a patch to Gerrit.
https://review.openstack.org/201002
But I got this error in zuul scheduler:
2015-07-14 14:07:24,921 DEBUG zuul.Scheduler: Run handler awake
2015-07-14 14:07:24,921 DEBUG zuul.Scheduler:
First of all, change the vendor to your vendor name in
/etc/jenkins_jobs/config/projects.yaml file. Also, restart the zuul and
zuul merger.
On Mon, Jul 13, 2015 at 12:29 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
Hi all,
I have constructed my CI system.
When I tested it with sandbox
Also check that Gearman is connecting or not through Jenkins UI.
On Mon, Jul 13, 2015 at 12:45 PM, Abhishek Shrivastava
abhis...@cloudbyte.com wrote:
First of all, change the vendor to your vendor name in
/etc/jenkins_jobs/config/projects.yaml file. Also, restart the zuul and
zuul merger.
Hi Abhishek,
Thanks for the quick reply.
On 07/13/2015 03:16 PM, Abhishek Shrivastava wrote:
Also check that Gearman is connecting or not through Jenkins UI.
On Mon, Jul 13, 2015 at 12:45 PM, Abhishek Shrivastava
abhis...@cloudbyte.com mailto:abhis...@cloudbyte.com wrote:
First of all,
Use tester or something, also are you updating the jobs or not?
On Mon, Jul 13, 2015 at 1:16 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
Hi Abhishek,
Thanks for the quick reply.
On 07/13/2015 03:16 PM, Abhishek Shrivastava wrote:
Also check that Gearman is connecting or not through
On 07/13/2015 03:50 PM, Abhishek Shrivastava wrote:
Use tester or something, also are you updating the jobs or not?
I used tester as my vendor. It doesn't work.
And what do you mean by updating the jobs ? I built the
noop-check-cimmunitication
job once in Jenkins UI. Does it matter ? All
33 matches
Mail list logo
