Use and configuration of the automation package deployment of Jenkins

(Not write a complete, be continued ...)

Glossary:

1.Jenkins in to svn operate, plug-ins and scripts can be carried out by two ways.

  •  Plug-ins

    Installation "Subversion Plug-in" plug-in management, you can configure SVN in the task of "Source Management".

    

    Module: refers to the module on the svn. A task can have as many different sources svn module.

    Repository URL: svn address code repository.

    Credentials: the code required to access the svn repository account password.

    Local module directory: svn checked out to the native folder path

    Repository depth: need to check out the folder depth, usually set to infinity (all configuration files folder, including sub-folders) specify the visible plug-in help.

    Ignore externals / Additional Credentials: unused, without explanation.

    Check-out Strategy: svn update to the local ways. Recommended Use 'svn update' as much as possible, with 'svn revert' before update (first discard all local modifications, then svn update as far as possible avoid local modifications lead to inconsistencies in the local project with the code repository)

2. Construction of the flip-flop

     Build periodically: periodic project to build, this is the time specified must trigger a build task

     Poll SCM: Regularly check the source code changes (depending on the version number of the software SCM), if there are updates to checkout the latest code down, and then execute a build action

Guess you like

Origin www.cnblogs.com/jmy520/p/11769237.html