The automation toolchain of continuous integration begins with continuous integration in the version control system. Continuous Integration is a confusing topic to some, because, most believe that it has something to do with initiating the resource deployment once the team has built the project. But the story doesn't start there, the story starts at the moment someone hits "git push" -- or any similar alternate resource versioning tool (such as SVN).
The main primary focus of continuous integration and continuous deployment is to automate the process of software release. Removing the wait times needed by the teams for operations team wait time in order to maximize the output of the development teams. Sometimes this is termed under the umbrella of DevOps. DevOps is a huge and complex concept in itself, and most of the time DevOps is also misunderstood just like continuous integration. In any case, continuous integration is only a single step in the long-running DevOps toolchain, and in this post, you will learn what continuous integration happens to be, how to set up Jenkins's environment for this process, and how to trigger it.

I will use Jenkins software to demonstrate the continuous integration workflow and how you can make the most out of it.
Jenkins Overview
Although this post will not cover everything about Jenkins, it is needed to give you at least an overview of what Jenkins has for continuous integration processes.
Now, other platforms, such as Visual Studio Team Services, contain everything inside them by default. Which is why the system knows when something happens. Jenkins, on the other hand, is an extension or a solution for your processes where you control everything as a job. In Jenkins, you have to manually set triggers to build the project. Whereas, on other platforms, you can set the trigger, which is controlled internally and keeps a track of what has changed.
Jenkins on the other hands, provides much-tailored solutions (but not as much as effective and efficient as a default event-driven one), in this format you what you do is you select an option from a really wide range of available options,

As seen in the image above, there are several options, such as,
- Timely build triggers
- Useful in offices
- Where you only build the project at the end of the day
- After other projects build
- Can be used in environments, where your project is a dependent project, and you have to check whether you can utilize the latest build artifacts.
- Poll the source control
- This is the one we are interested in;
- You can set a timer, after which the Jenkins system will poll the version control to check if the repository has been updated or not.
This way, Jenkins provides you the ability to run the build system and generate the artifacts for deployment. Jenkins is based on extensions, you install the extension for every kind of project. Jenkins itself is written in Java, thus for other project types, you would require consuming those extensions.
I will demonstrate usage of the .NET build system in Jenkins workflow to build your .NET apps, as soon as there are changes in the repository.
Setting up Jenkins
This was the most painful step for me, and I am sure there are many others out there who have faced the same problems; such as msbuild.exe not found, or Git does not work and much more. In this section, you will learn how to manage Jenkins.
Setting up the Jenkins environment requires that you configure the plugins first, and then create a build system. I will assume that you already have everything set up and ready to be used.









Ben LiPosted Sep 12, 2022, 11:38 AM
You are saying nothing to me.
Abid ShaikPosted Aug 3, 2021, 3:51 PM
Good one Iqra !!
aditya dubeyPosted Jul 6, 2021, 5:01 AM
Can you explain what command parameters did you pass to build a solution .And how do you store the build artifacts
Ajay kPosted Feb 7, 2019, 5:24 AM
Can you please explain on CD of .NET projects using jenkins. Also uploading the build artifact to artifactory server using jenkins.
Tridip BhattacharjeePosted Dec 11, 2017, 3:34 AM
Jenkins can be configure with Github or VSTS ? how to configure when anyone check-in change to source control then jenkins will compile the code and run the unit test and send a mail to admin. so how to configure jenkins in such a way it will always send mail if build success or fail?