In our previous post we have gone through the introduction of Jenkins Getting started with Jenkins for .Net developers and started looking how to create first job in Jenkins Create your first job in Jenkins - Part 1. In this post we will continue our discussion about some advanced options of Jenkins jobs.
1. Quiet Period
If this value is set, a build waits for that many seconds before actually being built. There may be many reasons why you want this option and those are shown in the diagram below.
2. Retry Count
Suppose there is a network problem and Jenkins is not able to checkout the repository, then using this you can specify the retry number.
3. Use custom workspace
Jenkins allocate a workspace(unique) directory for each job but using this option you can set your own custom workspace.
Now we will check the Source Code management available for us in Jenkins. They are CVS, CVS Projectset, Git, Subversion, Team Foundation Server etc.
When connectiong using Git, you have to specify the Repository URL, Credentials and the Branches to build.
When connecting using Team Foundation Server, you have to specify Server URL, Project Path, Login name, User password, Local Workfolder, Worksapce name.
After the connection with the Source Code Management, you have to specify the Project Solution file which you have to build using MSBuild. At first you have to specify the MSBuild Version, in our case it is v4.5. Then you have to give the path of the solution file which you want to build using MSBuild.
After that the last step is to specify Post-build Actions, if you want any action to be performed after the build and they are :
So we have created our first job in Jenkins. In your home page you can see the job instructions as
Please Like and Share the Blog, if you find it interesting and helpful.
1. Quiet Period
If this value is set, a build waits for that many seconds before actually being built. There may be many reasons why you want this option and those are shown in the diagram below.
2. Retry Count
Suppose there is a network problem and Jenkins is not able to checkout the repository, then using this you can specify the retry number.
3. Use custom workspace
Jenkins allocate a workspace(unique) directory for each job but using this option you can set your own custom workspace.
When connectiong using Git, you have to specify the Repository URL, Credentials and the Branches to build.
When connecting using Team Foundation Server, you have to specify Server URL, Project Path, Login name, User password, Local Workfolder, Worksapce name.
After the connection with the Source Code Management, you have to specify the Project Solution file which you have to build using MSBuild. At first you have to specify the MSBuild Version, in our case it is v4.5. Then you have to give the path of the solution file which you want to build using MSBuild.
After that the last step is to specify Post-build Actions, if you want any action to be performed after the build and they are :
So we have created our first job in Jenkins. In your home page you can see the job instructions as
Please Like and Share the Blog, if you find it interesting and helpful.
No comments:
Post a Comment