Completing the script

So far, we know how to utilize the multibranch pipeline and we have most of a working script, but it is not completely what we configured earlier in classic Jenkins. So, let's complete the script so we have pretty much everything. We can now also easily differentiate between different branches. Basically, I want to get everything up and running as though we were building an actual product. We will fill in the final details on releasing the software in the final chapters of this book.

First, we are going to make a few edits to our gulpfile. It was fine earlier, but now that we are going to trigger three builds at the same time, it makes no sense to use PhantomJS every time. Also, we want to be able to trigger the test-min task without also triggering the regular test task. The change is pretty simple. Just change the browsers Karma configuration in the gulpfile. You can find the changed gulpfile in the GitHub repository for this book in the code samples for this chapter...