Config. xml of Jenkins

Jenkins has two types of config. xml:

Config. xml under Jenkins home is the configuration file of the Jenkins server.

In addition, there is a config. xml file in the directory of each job or project. It contains the configuration information of this job.

The Jenkins home directory contains all the details of your Jenkins server configuration, details that you configure in the manage Jenkins screen.

A user appearing in this list cannot necessarily log on to Jenkins.

SCM user

(People who make changes to code in a source code repository that Jenkins is monitoring)

It is a good idea for developers to use their SCM username here: in
This case, Jenkins will be able to work out what users contributed to the SCM changes
That triggered a particle build.

Post-build actions corresponds to <publishers> in config. xml

Builder corresponds to build

Source code management <SCM class = "Hudson. SCM. subversionscm">

Trigger <triggers class = "vector">

Portfolio controller builder-Maven, publishers: ant merge. Results

Portfolio package: builder-ant target: portfolio. packaging. Publishers does not exist.

Each job has a workspace with all ant scripts required by hudson_migration.

At the same time, workspace/trunk has two files for a project:

Portfolio

Portfolio_pom.xml

Https://sami.cdt.int.thomsonreuters.com/svn/searchandnavigation_searchandnavigation/Development/CP1.5/trunk/SourceCode/Controller/portfolio

Indeed, continuous delivery can be viewed as continuous deployment
With the final step (deployment into production) being a manual one dictated
The business rather than the development team.