Gitlab CI Scripts and Hardware-in-the-Loop

BP
Brian Padalino
Tue, Oct 20, 2020 1:42 PM

I am looking at the CI scripts for OpenCPI which use the gitlab-runner and
I am wondering if there are currently, or plans in the future, to utilize
these scripts to have hardware-in-the-loop testing?

If so, is there a recommended way for an out-of-tree project to adopt/use
the same CI testing/scripts/framework for hardware-in-the-loop tests?

Thanks,
Brian

I am looking at the CI scripts for OpenCPI which use the gitlab-runner and I am wondering if there are currently, or plans in the future, to utilize these scripts to have hardware-in-the-loop testing? If so, is there a recommended way for an out-of-tree project to adopt/use the same CI testing/scripts/framework for hardware-in-the-loop tests? Thanks, Brian
JK
James Kulp
Tue, Oct 20, 2020 2:26 PM

CI-based hardware in the loop testing is being worked and is nearly
ready.  It has been a priority for a while, but has proven a stubborn
adversary.
It requires a particular "test server and lab network and connected
hardware" with appropriate isolation as well as the connection to the CI
system.

When it rolls out, the next challenge it to provide the template for 3rd
parties.

When OpenCPI supports new hardware "officially" we will try and populate
the CI lab with the hardware for inclusion in every-day CI.

On 10/20/20 9:42 AM, Brian Padalino wrote:

I am looking at the CI scripts for OpenCPI which use the gitlab-runner and
I am wondering if there are currently, or plans in the future, to utilize
these scripts to have hardware-in-the-loop testing?

If so, is there a recommended way for an out-of-tree project to adopt/use
the same CI testing/scripts/framework for hardware-in-the-loop tests?

Thanks,
Brian

CI-based hardware in the loop testing is being worked and is nearly ready.  It has been a priority for a while, but has proven a stubborn adversary. It requires a particular "test server and lab network and connected hardware" with appropriate isolation as well as the connection to the CI system. When it rolls out, the next challenge it to provide the template for 3rd parties. When OpenCPI supports new hardware "officially" we will try and populate the CI lab with the hardware for inclusion in every-day CI. On 10/20/20 9:42 AM, Brian Padalino wrote: > I am looking at the CI scripts for OpenCPI which use the gitlab-runner and > I am wondering if there are currently, or plans in the future, to utilize > these scripts to have hardware-in-the-loop testing? > > If so, is there a recommended way for an out-of-tree project to adopt/use > the same CI testing/scripts/framework for hardware-in-the-loop tests? > > Thanks, > Brian >
BP
Brian Padalino
Tue, Oct 20, 2020 2:37 PM

On Tue, Oct 20, 2020 at 10:27 AM James Kulp jek@parera.com wrote:

CI-based hardware in the loop testing is being worked and is nearly
ready.  It has been a priority for a while, but has proven a stubborn
adversary.
It requires a particular "test server and lab network and connected
hardware" with appropriate isolation as well as the connection to the CI
system.

When it rolls out, the next challenge it to provide the template for 3rd
parties.

When OpenCPI supports new hardware "officially" we will try and populate
the CI lab with the hardware for inclusion in every-day CI.

OK.  So what I take from this is:

  • Hardware-in-the-loop testing isn't quite ready, but being worked on
  • Out-of-tree templates are not being worked on, but will be once it's
    rolled out

Is there a current branch with the hardware-in-the-loop CI stuff?  Do you
have a prospective timeline for when it'll be initially released?

Thanks,
Brian

On Tue, Oct 20, 2020 at 10:27 AM James Kulp <jek@parera.com> wrote: > CI-based hardware in the loop testing is being worked and is nearly > ready. It has been a priority for a while, but has proven a stubborn > adversary. > It requires a particular "test server and lab network and connected > hardware" with appropriate isolation as well as the connection to the CI > system. > > When it rolls out, the next challenge it to provide the template for 3rd > parties. > > When OpenCPI supports new hardware "officially" we will try and populate > the CI lab with the hardware for inclusion in every-day CI. > OK. So what I take from this is: - Hardware-in-the-loop testing isn't quite ready, but being worked on - Out-of-tree templates are not being worked on, but will be once it's rolled out Is there a current branch with the hardware-in-the-loop CI stuff? Do you have a prospective timeline for when it'll be initially released? Thanks, Brian