Jenkins is an open-source automation server that is commonly used to perform Continuous Integration (CI) tasks, such as the building, testing, and delivery of an application. You may choose to use TestStand in combination with Jenkins or other CI systems for one or more of the following use cases:
By continuously testing and building your code, CI practices can help identify problems early in the development process. For example - consider a team that shares test development between several engineers. If a subVI is not checked into the shared repository, the test sequence will run with no problems on the original development machine, but when the team runs code from the repository, this sequence will have a broken VI. A problem like this could be caught immediately by a CI server and corrected, saving the team from last-minute troubleshooting.
TestStand can also be used as part of a larger CI system. For example - consider a mixed team of software and hardware engineers that are developing an embedded device. Unit tests can be written to test the embedded software, and TestStand sequences can be written to test hardware requirements and the software/hardware integration. TestStand can publish test results back to the same CI server as the software unit tests, allowing the entire team to adopt test-driven development and work together to resolve any failing tests.
The primary communication method between a CI server and a TestStand system is through the command line. The following TestStand utilities have command-line interfaces that can be used for this purpose
You will need a Windows computer or virtual machine on your network that can be used exclusively for building. It is not recommended to use this machine for software development purposes - doing so can cause copies of dependencies to exist in search directories that can be inadvertently pulled into a build. You will also need a licensed copy of all software and drivers required to build your test system.
Note: The TestStand Version Selector can reset DCOM settings. If you intend to manage multiple TestStand versions on a single build machine, consider automatically setting this property via the RunAs registry key.
Note: You will see HTTP Error 404 if the Jenkins service did not start properly. Port 8080 is the default port for LabVIEW web services and several other applications - if this port is already in use, Jenkins will not be able to start. To change the default port, open Jenkins.xml from the installation directory and modify the --httpPort attribute to an open port. If you still have problems starting the service, check the jenkins.err.log file in the installation directory for detailed error information.
Collaborate with other users in our discussion forums
A valid service agreement may be required, and support options vary by country.