The LabVIEW Continuous Integration Project

[endeavor]

Hi Brandyn,  thanks for your answer. I can test it for you then 🙂  The problem is that my job list is absolutely empty. What could I try to reinstall? I'm not sure who exactly puts these scripts to Jenkins.

[Brandyn]

That should have be installed when you install the CI Service (its a part of the same installer).  This is kind of "jenky" pardon the pun, but the build scripts folder should be apart of the source.  You can copy the files in the Jenkins jobs folder, restart jenkins and they should show up in your list of jobs.

[Elaine_R.]

Just a quick comment from my initial round of downloads for this on a new network. The CEF doesn't appear to be up on the Tools Network at the moment. It's still available via VI Package Manager though!

[rik_aspinall]

Hello again niACS,

I'm having trouble downloading the file...any ideas?

UPDATE: I read the other posts more carefully! Sorry about the redundant posts, issue fixed I think...

[Bas.v.E]

Hi all,

I've been trying to get the whole CI thing working. So far I have:

- A working Jenkins Server with the Labview CI Service Running

- A working Alfred node on another VM

- A Development VM (which is not yet working)

So when I try to build a very clean CI Project on the developement VM I'm getting the following error:

Error 5242 occurred at Jenkins - Run Script.vi

Possible reason(s):
Timeout Error. Jenkins was not responsive.

The project only consist a initialize and a run VI.

The hostname is filled in correctly: 192.168.178.93:8080

The Root Workspace folder on the Server has Full Control for the User account

When I go to the Jenkins webpage I see a folder named _Build Scripts and it contains 4 scripts. So this part is installed correctly.

I don't know what i'm doing wrong.

[justACS]

We haven't tried running an Alfred slave node on  *different* computer or VI - it has always been colocated with the Jenkins and CI servers.

I've also seen this timeout when the user had enabled login credentials for Jenkins.  We don't support those yet.

---

[Bas.v.E]

Alright. 

I've got 2 other questions:

1. the CI server connects with the jenkins server or with the alfred node? 

2. Can the CI project builder run on a different computer or VM?

[justACS]

---

@Bas.v.E wrote:

Alright. 

I've got 2 other questions:

1. the CI server connects with the jenkins server or with the alfred node? 

2. Can the CI project builder run on a different computer or VM?

---

The Alfred slave node exists to handle CI project build requests from the project builder, so those requests can't bog down your actual build process.  Jenkins connects directly to the CI Server through its web client.

The CI Project Builder is intended to run remotely, from any work station.

[justACS]

---

@Bas.v.E wrote:

Error 5242 occurred at Jenkins - Run Script.vi

Possible reason(s):
Timeout Error. Jenkins was not responsive.

I shoud have asked this earlier:  does this happen when you try to build the CI project (i.e. when you run Build from the CI Project Builder) or when you try to run the CI Project in Jenkikns?

[Bas.v.E]

his happens when i try to build the project in the CI project builder on the development system