Pipeline as a Code with Jenkinsfile

donquijotedelasnubes

I just finished this lesson, but there is one thing that I don't understand @gouravshah @luisviveropena, and that is: we created a Jenkins file, by creating a new branch and then commiting, making a pull request and then approving it from another user account. But later, we did nothing with the Jenkins file. How can we configure the Jenkins file to be taken into account for making the build steps, using the tools that we configured it to use?

Peace

gouravshah

When you merge it using the Pull Request + Approval process, you would have the Jenkinsfile available in the trunk. With the subsequent lessons/chapters you would be updating the Jenkinsfile to add/update stages and do more things with it.