|
Well, so let's get this party started
On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github.
There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until I can debug it farther in my inner server.
In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far.
toggle quoted messageShow quoted text
-----Original Message----- From: Kumar Gala [mailto:kumar.gala@...] Sent: Thursday, March 9, 2017 1:49 AM To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky <inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...> Cc: Matthew Locke <matthew.locke@...> Subject: zephyr-infrastructure@... We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc. https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure- k
|
|
|
What is the status of the bootstrap? Should we have a meeting to discuss next steps?
Anas
toggle quoted messageShow quoted text
-----Original Message----- From: Perez-Gonzalez, Inaky Sent: Thursday, March 9, 2017 12:37 PM To: Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>; zephyr-infrastructure@... Cc: Matthew Locke <matthew.locke@...> Subject: RE: zephyr-infrastructure@... Well, so let's get this party started On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github. There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until I can debug it farther in my inner server. In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far. -----Original Message----- From: Kumar Gala [mailto:kumar.gala@...] Sent: Thursday, March 9, 2017 1:49 AM To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky <inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...> Cc: Matthew Locke <matthew.locke@...> Subject: zephyr-infrastructure@... We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc. https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure- k
|
|
|
I have seen a bunch of emails coming from github, but haven't heard anything else; I need to get back to cleaning the Jenkins job that I paused a couple of weeks ago--those can be reused.
toggle quoted messageShow quoted text
-----Original Message----- From: Nashif, Anas Sent: Monday, March 20, 2017 5:24 AM To: Perez-Gonzalez, Inaky <inaky.perez-gonzalez@...>; Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>; zephyr-infrastructure@... Cc: Matthew Locke <matthew.locke@...> Subject: RE: zephyr-infrastructure@... What is the status of the bootstrap? Should we have a meeting to discuss next steps? Anas -----Original Message----- From: Perez-Gonzalez, Inaky Sent: Thursday, March 9, 2017 12:37 PM To: Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>; zephyr-infrastructure@... Cc: Matthew Locke <matthew.locke@...> Subject: RE: zephyr-infrastructure@... Well, so let's get this party started On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github. There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until I can debug it farther in my inner server. In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far. -----Original Message----- From: Kumar Gala [mailto:kumar.gala@...] Sent: Thursday, March 9, 2017 1:49 AM To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky <inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...> Cc: Matthew Locke <matthew.locke@...> Subject: zephyr-infrastructure@... We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc. https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure- k
|
|
|
Hi Everyone; The master and the builder are deployed and running and github authentication has been configured. Tyler is working on enabling some initial use cases; i.e. Running checkpatch and sanitycheck on pull requests. We need a final URL for the Jenkins master so we don't have update oauth applications, call-back urls, etc...
Something like a DNS entry
Alan
What is the status of the bootstrap? Should we have a meeting to discuss next steps?
Anas
-----Original Message-----
From: Perez-Gonzalez, Inaky
Sent: Thursday, March 9, 2017 12:37 PM
To: Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>; zephyr-infrastructure@...
Cc: Matthew Locke <matthew.locke@...>
Subject: RE: zephyr-infrastructure@...
Well, so let's get this party started
On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github.
There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until I can debug it farther in my inner server.
In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far.
-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@...]
Sent: Thursday, March 9, 2017 1:49 AM
To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky <inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>
Cc: Matthew Locke <matthew.locke@...>
Subject: zephyr-infrastructure@...
We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc.
https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure
- k
|
|
|
I’ll put an IT request in for getting DNS setup to that IP for right now. We can switch it over once we have Zephyr Project systems in place.
So I think a write up about all what Fathi & Tyler should hopefully get us close to wrapping up this phase. This will allow everyone to digest what was done, and than we can setup maybe a call for questions to be asked.
Thanks
- k
toggle quoted messageShow quoted text
On Mar 22, 2017, at 5:21 PM, Alan Bennett <alan.bennett@...> wrote:
Hi Everyone;
The master and the builder are deployed and running and github authentication has been configured. Tyler is working on enabling some initial use cases; i.e. Running checkpatch and sanitycheck on pull requests.
We need a final URL for the Jenkins master so we don't have update oauth applications, call-back urls, etc...
Something like a DNS entry
zephyrci.zephyrproject.org --> 88.99.149.141
We are staging on http://zephyrci.linaro.org , but I'd like to get things setup under zephyrproject.org asap to reduce hand over complexity.
Alan
On Mon, Mar 20, 2017 at 6:24 AM Nashif, Anas <anas.nashif@...> wrote:
What is the status of the bootstrap? Should we have a meeting to discuss next steps?
Anas
-----Original Message-----
From: Perez-Gonzalez, Inaky
Sent: Thursday, March 9, 2017 12:37 PM
To: Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>; zephyr-infrastructure@...
Cc: Matthew Locke <matthew.locke@...>
Subject: RE: zephyr-infrastructure@...
Well, so let's get this party started
On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github.
There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until I can debug it farther in my inner server.
In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far.
-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@...]
Sent: Thursday, March 9, 2017 1:49 AM
To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky <inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>
Cc: Matthew Locke <matthew.locke@...>
Subject: zephyr-infrastructure@...
We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc.
https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure
- k
|
|
|
zephyrci.zephyrproject.org should now be setup so we can change scripts/URLs/etc to point to it.
- k
toggle quoted messageShow quoted text
On Mar 22, 2017, at 5:21 PM, Alan Bennett <alan.bennett@...> wrote:
Hi Everyone;
The master and the builder are deployed and running and github authentication has been configured. Tyler is working on enabling some initial use cases; i.e. Running checkpatch and sanitycheck on pull requests.
We need a final URL for the Jenkins master so we don't have update oauth applications, call-back urls, etc...
Something like a DNS entry
zephyrci.zephyrproject.org --> 88.99.149.141
We are staging on http://zephyrci.linaro.org , but I'd like to get things setup under zephyrproject.org asap to reduce hand over complexity.
Alan
On Mon, Mar 20, 2017 at 6:24 AM Nashif, Anas <anas.nashif@...> wrote:
What is the status of the bootstrap? Should we have a meeting to discuss next steps?
Anas
-----Original Message-----
From: Perez-Gonzalez, Inaky
Sent: Thursday, March 9, 2017 12:37 PM
To: Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>; zephyr-infrastructure@...
Cc: Matthew Locke <matthew.locke@...>
Subject: RE: zephyr-infrastructure@...
Well, so let's get this party started
On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github.
There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until I can debug it farther in my inner server.
In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far.
-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@...]
Sent: Thursday, March 9, 2017 1:49 AM
To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky <inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>
Cc: Matthew Locke <matthew.locke@...>
Subject: zephyr-infrastructure@...
We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc.
https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure
- k
|
|
|
Guys, can we have a call to coordinate all this and understand what is happening?
Are you planning on reusing some of the scripts we had for the Jenkins infrastructure? there is a lot of knowledge in there that come from all the rocks people stumbled upon before.
toggle quoted messageShow quoted text
From: Alan Bennett [alan.bennett@...]
Sent: Wednesday, March 22, 2017 3:21 PM
To: Nashif, Anas; Perez-Gonzalez, Inaky; Kumar Gala; Tyler Baker; Fathi Boudra; zephyr-infrastructure@...
Cc: Matthew Locke
Subject: Re: zephyr-infrastructure@...
Hi Everyone;
The master and the builder are deployed and running and github authentication has been configured. Tyler is working on enabling some initial use cases; i.e. Running checkpatch and sanitycheck on pull requests.
We need a final URL for the Jenkins master so we don't have update oauth applications, call-back urls, etc...
Something like a DNS entry
Alan
What is the status of the bootstrap? Should we have a meeting to discuss next steps?
Anas
-----Original Message-----
From: Perez-Gonzalez, Inaky
Sent: Thursday, March 9, 2017 12:37 PM
To: Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>;
Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>;
zephyr-infrastructure@...
Cc: Matthew Locke <matthew.locke@...>
Subject: RE:
zephyr-infrastructure@...
Well, so let's get this party started
On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github.
There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until
I can debug it farther in my inner server.
In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far.
-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@...]
Sent: Thursday, March 9, 2017 1:49 AM
To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky
<inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>
Cc: Matthew Locke <matthew.locke@...>
Subject:
zephyr-infrastructure@...
We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc.
https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure
- k
|
|
|
Hi Inaky, Currently we aren't necessarily looking that far into the testing yet, but nothing we are doing will prevent the use of the work or scripts that have been done previously. I think we'll be ready to discuss the setup early next week. It is looking like Wednesday 30 minutes after the Zephyr TSC meeting might be ideal from our end. I'll send out an invite, let me know if it doesn't work.
Alan
Guys, can we have a call to coordinate all this and understand what is happening?
Are you planning on reusing some of the scripts we had for the Jenkins infrastructure? there is a lot of knowledge in there that come from all the rocks people stumbled upon before.
Hi Everyone;
The master and the builder are deployed and running and github authentication has been configured. Tyler is working on enabling some initial use cases; i.e. Running checkpatch and sanitycheck on pull requests.
We need a final URL for the Jenkins master so we don't have update oauth applications, call-back urls, etc...
Something like a DNS entry
Alan
What is the status of the bootstrap? Should we have a meeting to discuss next steps?
Anas
-----Original Message-----
From: Perez-Gonzalez, Inaky
Sent: Thursday, March 9, 2017 12:37 PM
To: Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>;
Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>;
zephyr-infrastructure@...
Cc: Matthew Locke <matthew.locke@...>
Subject: RE:
zephyr-infrastructure@...
Well, so let's get this party started
On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github.
There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until
I can debug it farther in my inner server.
In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far.
-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@...]
Sent: Thursday, March 9, 2017 1:49 AM
To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky
<inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>
Cc: Matthew Locke <matthew.locke@...>
Subject:
zephyr-infrastructure@...
We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc.
https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure
- k
|
|
|
Thanks Alan
I am on vacation starting Tue next week (spring break) -- can we do it Monday?
toggle quoted messageShow quoted text
From: Alan Bennett [alan.bennett@...]
Sent: Wednesday, March 22, 2017 4:52 PM
To: Perez-Gonzalez, Inaky; Nashif, Anas; Kumar Gala; Tyler Baker; Fathi Boudra; zephyr-infrastructure@...
Cc: Matthew Locke
Subject: Re: zephyr-infrastructure@...
Hi Inaky,
Currently we aren't necessarily looking that far into the testing yet, but nothing we are doing will prevent the use of the work or scripts that have been done previously. I think we'll be ready to discuss the setup early next week. It is looking
like Wednesday 30 minutes after the Zephyr TSC meeting might be ideal from our end. I'll send out an invite, let me know if it doesn't work.
Alan
Guys, can we have a call to coordinate all this and understand what is happening?
Are you planning on reusing some of the scripts we had for the Jenkins infrastructure? there is a lot of knowledge in there that come from all the rocks people stumbled upon before.
Hi Everyone;
The master and the builder are deployed and running and github authentication has been configured. Tyler is working on enabling some initial use cases; i.e. Running checkpatch and sanitycheck on pull requests.
We need a final URL for the Jenkins master so we don't have update oauth applications, call-back urls, etc...
Something like a DNS entry
Alan
What is the status of the bootstrap? Should we have a meeting to discuss next steps?
Anas
-----Original Message-----
From: Perez-Gonzalez, Inaky
Sent: Thursday, March 9, 2017 12:37 PM
To: Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>;
Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>;
zephyr-infrastructure@...
Cc: Matthew Locke <matthew.locke@...>
Subject: RE:
zephyr-infrastructure@...
Well, so let's get this party started
On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github.
There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until
I can debug it farther in my inner server.
In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far.
-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@...]
Sent: Thursday, March 9, 2017 1:49 AM
To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky
<inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>
Cc: Matthew Locke <matthew.locke@...>
Subject:
zephyr-infrastructure@...
We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc.
https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure
- k
|
|
|
Ok, I've moved it to Monday. Without a day to summarize, the meeting may be a bit more of a raw discussion vs. having time to build a report, but I think it will be good to go over the system sooner, rather than later.
Alan
Thanks Alan
I am on vacation starting Tue next week (spring break) -- can we do it Monday?
Hi Inaky,
Currently we aren't necessarily looking that far into the testing yet, but nothing we are doing will prevent the use of the work or scripts that have been done previously. I think we'll be ready to discuss the setup early next week. It is looking
like Wednesday 30 minutes after the Zephyr TSC meeting might be ideal from our end. I'll send out an invite, let me know if it doesn't work.
Alan
Guys, can we have a call to coordinate all this and understand what is happening?
Are you planning on reusing some of the scripts we had for the Jenkins infrastructure? there is a lot of knowledge in there that come from all the rocks people stumbled upon before.
Hi Everyone;
The master and the builder are deployed and running and github authentication has been configured. Tyler is working on enabling some initial use cases; i.e. Running checkpatch and sanitycheck on pull requests.
We need a final URL for the Jenkins master so we don't have update oauth applications, call-back urls, etc...
Something like a DNS entry
Alan
What is the status of the bootstrap? Should we have a meeting to discuss next steps?
Anas
-----Original Message-----
From: Perez-Gonzalez, Inaky
Sent: Thursday, March 9, 2017 12:37 PM
To: Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>;
Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>;
zephyr-infrastructure@...
Cc: Matthew Locke <matthew.locke@...>
Subject: RE:
zephyr-infrastructure@...
Well, so let's get this party started
On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github.
There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until
I can debug it farther in my inner server.
In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far.
-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@...]
Sent: Thursday, March 9, 2017 1:49 AM
To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky
<inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>
Cc: Matthew Locke <matthew.locke@...>
Subject:
zephyr-infrastructure@...
We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc.
https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure
- k
|
|
|
Do we have details for logistics?
toggle quoted messageShow quoted text
On Mar 22, 2017, at 18:07, Alan Bennett < alan.bennett@...> wrote:
Ok, I've moved it to Monday. Without a day to summarize, the meeting may be a bit more of a raw discussion vs. having time to build a report, but I think it will be good to go over the system sooner, rather than later.
Alan
Thanks Alan
I am on vacation starting Tue next week (spring break) -- can we do it Monday?
Hi Inaky,
Currently we aren't necessarily looking that far into the testing yet, but nothing we are doing will prevent the use of the work or scripts that have been done previously. I think we'll be ready to discuss the setup early next week.
It is looking like Wednesday 30 minutes after the Zephyr TSC meeting might be ideal from our end. I'll send out an invite, let me know if it doesn't work.
Alan
Guys, can we have a call to coordinate all this and understand what is happening?
Are you planning on reusing some of the scripts we had for the Jenkins infrastructure? there is a lot of knowledge in there that come from all the rocks people stumbled upon before.
Hi Everyone;
The master and the builder are deployed and running and github authentication has been configured. Tyler is working on enabling some initial use cases; i.e. Running checkpatch and sanitycheck on pull requests.
We need a final URL for the Jenkins master so we don't have update oauth applications, call-back urls, etc...
Something like a DNS entry
Alan
What is the status of the bootstrap? Should we have a meeting to discuss next steps?
Anas
-----Original Message-----
From: Perez-Gonzalez, Inaky
Sent: Thursday, March 9, 2017 12:37 PM
To: Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>;
Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>;
zephyr-infrastructure@...
Cc: Matthew Locke <matthew.locke@...>
Subject: RE:
zephyr-infrastructure@...
Well, so let's get this party started
On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github.
There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until
I can debug it farther in my inner server.
In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far.
-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@...]
Sent: Thursday, March 9, 2017 1:49 AM
To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky
<inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>
Cc: Matthew Locke <matthew.locke@...>
Subject:
zephyr-infrastructure@...
We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc.
https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure
- k
|
|
|
Hello, for the Zephyr bootstrap review, Time: 9:00 am Mountain (UTC-6) - see dial-in details at the bottom, if you are new to bluejeans, try it out before the meeting, or simply dial in to the phone number, that is trivial.
Proposed Agenda:
Fathi describe the infrastructure that was setup - Overview of what Hetzner is - Machine sizes, cost, rough overview of how Hetzner works - Jenkins Master - Jenkins Slave (currently only 1) - Use of Docker in Jenkins Tyler describe the github integration - authentication, - jenkins/github integration - the pull-request execution of checkpatch and sanitytest.
Next steps; * review the bootstrap; Go/no-go; changes needed or is this something we can build on? * Currently the builder is always busy - thoughts on optimization of the current load - thoughts on scaling up. How many slaves are recommended * Discuss How/who does this get managed in the future
=============== To join the Meeting:
To join via Browser:
To join via Room System: Video Conferencing System: bjn.vc -or-199.48.152.152 Meeting ID : 9702909053
To join via phone : 1) Dial: +1.408.740.7256 +1.888.240.2560 +1.408.317.9253 2) Enter Conference ID : 9702909053
Do we have details for logistics?
Ok, I've moved it to Monday. Without a day to summarize, the meeting may be a bit more of a raw discussion vs. having time to build a report, but I think it will be good to go over the system sooner, rather than later.
Alan
Thanks Alan
I am on vacation starting Tue next week (spring break) -- can we do it Monday?
Hi Inaky,
Currently we aren't necessarily looking that far into the testing yet, but nothing we are doing will prevent the use of the work or scripts that have been done previously. I think we'll be ready to discuss the setup early next week.
It is looking like Wednesday 30 minutes after the Zephyr TSC meeting might be ideal from our end. I'll send out an invite, let me know if it doesn't work.
Alan
Guys, can we have a call to coordinate all this and understand what is happening?
Are you planning on reusing some of the scripts we had for the Jenkins infrastructure? there is a lot of knowledge in there that come from all the rocks people stumbled upon before.
Hi Everyone;
The master and the builder are deployed and running and github authentication has been configured. Tyler is working on enabling some initial use cases; i.e. Running checkpatch and sanitycheck on pull requests.
We need a final URL for the Jenkins master so we don't have update oauth applications, call-back urls, etc...
Something like a DNS entry
Alan
What is the status of the bootstrap? Should we have a meeting to discuss next steps?
Anas
-----Original Message-----
From: Perez-Gonzalez, Inaky
Sent: Thursday, March 9, 2017 12:37 PM
To: Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>;
Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>;
zephyr-infrastructure@...
Cc: Matthew Locke <matthew.locke@...>
Subject: RE:
zephyr-infrastructure@...
Well, so let's get this party started
On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github.
There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until
I can debug it farther in my inner server.
In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far.
-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@...]
Sent: Thursday, March 9, 2017 1:49 AM
To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky
<inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>
Cc: Matthew Locke <matthew.locke@...>
Subject:
zephyr-infrastructure@...
We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc.
https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure
- k
|
|
|
Thanks for your attendance this morning to review the boot strap.
Thanks again Alan
Hello, for the Zephyr bootstrap review, Time: 9:00 am Mountain (UTC-6) - see dial-in details at the bottom, if you are new to bluejeans, try it out before the meeting, or simply dial in to the phone number, that is trivial.
Proposed Agenda:
Fathi describe the infrastructure that was setup - Overview of what Hetzner is - Machine sizes, cost, rough overview of how Hetzner works - Jenkins Master - Jenkins Slave (currently only 1) - Use of Docker in Jenkins Tyler describe the github integration - authentication, - jenkins/github integration - the pull-request execution of checkpatch and sanitytest.
Next steps; * review the bootstrap; Go/no-go; changes needed or is this something we can build on? * Currently the builder is always busy - thoughts on optimization of the current load - thoughts on scaling up. How many slaves are recommended * Discuss How/who does this get managed in the future
=============== To join the Meeting:
To join via Browser:
To join via Room System: Video Conferencing System: bjn.vc -or-199.48.152.152
To join via phone : 1) Dial:
Do we have details for logistics?
Ok, I've moved it to Monday. Without a day to summarize, the meeting may be a bit more of a raw discussion vs. having time to build a report, but I think it will be good to go over the system sooner, rather than later.
Alan
Thanks Alan
I am on vacation starting Tue next week (spring break) -- can we do it Monday?
Hi Inaky,
Currently we aren't necessarily looking that far into the testing yet, but nothing we are doing will prevent the use of the work or scripts that have been done previously. I think we'll be ready to discuss the setup early next week.
It is looking like Wednesday 30 minutes after the Zephyr TSC meeting might be ideal from our end. I'll send out an invite, let me know if it doesn't work.
Alan
Guys, can we have a call to coordinate all this and understand what is happening?
Are you planning on reusing some of the scripts we had for the Jenkins infrastructure? there is a lot of knowledge in there that come from all the rocks people stumbled upon before.
Hi Everyone;
The master and the builder are deployed and running and github authentication has been configured. Tyler is working on enabling some initial use cases; i.e. Running checkpatch and sanitycheck on pull requests.
We need a final URL for the Jenkins master so we don't have update oauth applications, call-back urls, etc...
Something like a DNS entry
Alan
What is the status of the bootstrap? Should we have a meeting to discuss next steps?
Anas
-----Original Message-----
From: Perez-Gonzalez, Inaky
Sent: Thursday, March 9, 2017 12:37 PM
To: Kumar Gala <kumar.gala@...>; Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>;
Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>;
zephyr-infrastructure@...
Cc: Matthew Locke <matthew.locke@...>
Subject: RE:
zephyr-infrastructure@...
Well, so let's get this party started
On our side, I've been cleaning up all the CI jobs that we currently have, with an eye of eventually plugging them to github.
There is a lot of JJB (Jenkins Job Builder) code which is convoluted and hard to follow--it's also hard to debug because we don't have access to the LF servers ot tell what's going on. So I have currently disabled the main new job (zephyr-phsaes-verify) until
I can debug it farther in my inner server.
In any case, I want to very much clean all that JJB, so it is easier to plug github and reap the benefits of what we found so far.
-----Original Message-----
From: Kumar Gala [mailto:kumar.gala@...]
Sent: Thursday, March 9, 2017 1:49 AM
To: Tyler Baker <tyler.baker@...>; Nashif, Anas <anas.nashif@...>; Perez-Gonzalez, Inaky
<inaky.perez-gonzalez@...>; Fathi Boudra <fathi.boudra@...>; Alan Bennett <alan.bennett@...>
Cc: Matthew Locke <matthew.locke@...>
Subject:
zephyr-infrastructure@...
We already have a zephyr-infrastructure list, so let use it for any discussion related to CI, etc.
https://lists.zephyrproject.org/mailman/listinfo/zephyr-infrastructure
- k
|
|
|
