This is a creation in Article, where the information may have evolved or changed. 1. Create pipeline1.1 find the agentresource that satisfies the job execution needs is the plain text tag, the user can define according to own custom. Go executes the job, when the agent is selected, the agent's system information is not known or whether the agent satisfies the conditions of the job execution. Users need to determine whether the agent satisfies the requirements according to the resource they define. We can define resource, "RHEL", "Mysql", "Windows XP", just for the user to identify.
Note:resource Sensitive to letter case
Create Pipeline Process
- Set Pipeline Name
- set the materials. You can set the version library (SCM) Source control Management (SCM or version control) repository, or the package repo, or other pipeline.
currently supports the following SCMS:
Subversion Mercurial Git Team Foundation Server.
1.2. Configuration Stagepipeline can have one or more stages
1.3. Configuring the jobs (i.e., task) Ant, NAnt, rake all need to pre-install the appropriate software on the agent and make the COMMD execution path
2. Configure blacklist in materials if repo only the files in the path specified in the Balcklist, then the change of these files will not automatically trigger pipeline
2. Configuring the Package Repohttp://www.go.cd/documentation/user/current/extension_points/yum_repository_ Poller.html for the Yum source, the operation is as follows: (1) Pre-installation of Repoquery, which is included in the Yum-utils package Ubuntu system: Apt-get install Yum-utils (2) Edit/ETC/YUM.REPOS.D
