Jenkins+proget+windows Batch builds a fully automated internal package (NUGET) packaging and push and management platform

This article is an upgraded version of the http://www.cnblogs.com/EasonJim/p/5954155.html, because CCNet has already been the process, so I changed the packaging process of the CCNet tool to Jenkins to achieve, the batch of those have not changed.

At the same time this is the whole process of batch processing practice.

When reading, please refer to the implementation of the previous article ideas.

I. Configuration 1, New job

Note: Select "Build a free-style software project" above

2. Fill in the project information

3. Configure SVN to get the source code

This option is selected by default, which triggers the next action only if it is updated.

4. Configure the time to build the trigger

Here is the SVN check every minute. If you want a different time, click the question mark at the back.

5. Configure batch processing for MSBuild and push

Build first, then push to the internal package management platform, batch file: Https://github.com/easonjim/NuGetRun

6. Send mail

Then configure the trigger point and send the log at any time.

Finally, it's all done. When reading, please refer to the implementation of the previous article ideas.

Jenkins+proget+windows Batch builds a fully automated internal package (NUGET) packaging and push and management platform