The LabVIEW Continuous Integration Project

[justACS]

We ran across this ourselves recently.  The solution in our case was to DISABLE "Restrict where this project can be run" in your individual steps.  For each step in your build process, select "Configure", and then UNCHECK this checkbox:

I'm not yet clear on why this works on some machines (like mine) but not others.  We've added this to our change list for the project.

[thel]

niACS is source code available somewhere on github? It would be easier to report and solve bugs. I have already found few and it would be nice to put fixed version somewhere.

[MattP]

We're currently transitioning the code base from an internal NI project to something we can post directly on Github.  Sorting out the legal stuff (NI Sample Code License vs Apache 2, how we'll handle submissions but still be able to use it internally, etc) is not awesome, but necessary.  Unfortunately, it also takes time.

Part of that process is also streamlining the plugin aspect (everything is in one repo now, want to split it into core code and repos for each plugin so others can extend without waiting for us).  

[MattP]

I should also note that I'll be doing a pair of sessions (one at Alliance Day, one for NI Week proper) on exactly how we're using parts of the LabVIEW CI Service along with Jenkins pipelines and Github tooling to get a continuous delivery system in place for the Distributed Control and Automation Framework (DCAF) project, with integrated unit testing, VIP builds, integration testing, etc.  We'll go into detail about how everything works, is chained together, and where to download all of the pieces to duplicate on your end.  We are aiming to have everything public, including all source code and ideally a tutorial guide up by NI Week.

Come visit!

[thel]

Hi,

We’ve came across a few nuisances concerning the CI project, some of what we think may be bugs. Please check attached document. 

[MattP]

The LabVIEW CI Service source code  is now posted online on Github here: https://github.com/NISystemsEngineering/LVCI

The current version has the project builder removed, since Jenkins Pipelines serve that purpose more effectively.  

The original version is located in the p4-export branch.  This branch is the source code used to generate the packages posted here earlier.

[thel]

Hi,

are you still doing there some major changes or are you planning to? 

I want to know because we put some effort to configure built system using CI client and now we can see that you have changed it to pipelines. It would be also useful if you could announce that you are changing something there so potential clients could wait for new release and avoid doing some useless work.

[MattP]

Currently, the major project internal to NI that was using the CI Service (DCAF) has transitioned to a build system based on James McNally's Command Line Interface for LabVIEW.  Since I'm the maintainer of DCAF, I will be focusing all of my efforts on improving that tool.  I will make no further edits to the LV CI Service repository, but if one of you is interested in taking it over I'll happily give you the appropriate privileges.

In terms of usage, it can do every operation that the CI Service can do, and is much easier to extend.  It also already supports invoking multiple versions of LabVIEW from the same interface.

You can download the tooling for that (including LabVIEW code for all build step types and the associated Groovy script wrappers to allow calling from Jenkins) by installing the LV-CLI Common Steps package from LabVIEW Tools Network.  This will install all necessary dependencies (LabVIEW CLI API, VIPM API, VI Tester, UTF to Junit converter, etc).  Currently, you also need to install the msi on James' Github page as well: https://github.com/JamesMc86/LabVIEW-CLI/releases/  (we're working to get this integrated into the CLI package itself in the next release).

[Gopi_123]

Hi,

Two months back, we started LabVIEW Jenkins CI automation. Now currently we running into an issue.

What happening is the the following:

1. I trigger the build and the source update via AccuRev(No problem).

2.Build.bat executes, it is hanging there only until we abort. But it is working fine in the local server.

Yesterday we changed the Jenkins user account, after that it worked fine for two builds and then again the same above issue came back, it is hanging in Jenkins, but it working in the windows server.

I observed that, when I build locally in the server in the the task manager LabVIEW use 25% CPU and  10 lakh kb memory, but when I trigger throw Jenkins at one point CPU % went to 0 and memory is hanging 1 ***** digit KB.

It would be great, if you can help on this. we get stucked her. Please help us.

[ElsDph]

Did anybody gained experiences about using that tool?