O'Reilly logo

Continuous Integration, Delivery, and Deployment by Sander Rossel

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Triggering a project pipeline

At this point, we can run our build on the Ubuntu master node or on the Windows slave node. Now, we want to build our code on Ubuntu and then, when the build succeeds, test it on Windows. We face a few problems though: we do not feel like repeating the entire build just to run some additional tests. Passing all the necessary files to the next job is quite a lot, but we do need pretty much all of our node modules. You may not like it, but to test our code using different browsers, we may as well just run the entire build again.

Let's create two new projects, one project to build our source on the master and another project to (build and) test on the slave. On the Jenkins home page, create a new item. Enter a name ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required