In this section of the guide, we will execute the CI pipeline. To save and run the script, follow these steps:
- Click Save in the top right, then Save & run. This will send you to a new page which records current and past runs.
Selecting the current run will show different stats, along with the overall results. You may need to refresh the page to see results in a timely manner.
If you are also building the virtual model on the Linux host machine, and following the steps for setting up the
simulation on the Linux host instead of Docker, the test will take 1-2 minutes.
This screenshot shows a run completed from running on the Linux host machine,
You can see in the preceding screenshot that:
- The pipeline with the name
PyCIran its 24th test successfully
- The expected output from the
output.txt0file is displayed
output.txt0 was not generated, the
Jenkins pipeline would stop at that step and give an error. This means that, in
our example, whenever the pipeline passes our code can be considered correct,
by outputting a "hello" message.
You can extend this type of test infrastructure to, for example, file existence checks, equivalence checks, content verification, customized test report analysis, and code coverage. You can also set up the Jenkins pipeline to:
- Run before any commit to a certain git branch, or
- Include merging branches when all tests pass, ensuring that certain branches are always working at a defined state.