From the course: Learning Jenkins: Automating Software Development and System Administration
Unlock this course with a free trial
Join today to access over 24,900 courses taught by industry experts.
Build description and source code management - Jenkins Tutorial
From the course: Learning Jenkins: Automating Software Development and System Administration
Build description and source code management
- [Instructor] Let's take a closer look at the configuration page for the Hello Jenkins job. From the dashboard, I'll select the job and then select Configure. First of all, notice the tabs on the left side of the page. These outline the sections of the configuration. In the general section, one of the most important fields is the description field. Use this field to add freeform text describing the job and what it does. A good name for the job goes a long way, but the description can be used to provide any details someone running the job might need to know. The discard old builds option is also very important. Jenkins keeps a record of each build, along with any files generated by the build, including log files and artifacts. This is great if you want to review the history of a job, but old builds also take up disc space. You can manage this by only keeping builds for a certain period of time, or by only keeping a maximum number of builds. These options can be used together to make…
Contents
-
-
-
-
(Locked)
Your first jenkins job2m 50s
-
Job types1m 38s
-
(Locked)
Build description and source code management2m 1s
-
(Locked)
Build triggers2m 21s
-
(Locked)
The build environment3m 30s
-
(Locked)
Run and monitor jobs1m 58s
-
(Locked)
Run and monitor jobs using console output2m 50s
-
(Locked)
Monitor build trends35s
-
(Locked)
Solution: Automate system monitoring with Jenkins1m 36s
-
(Locked)
-
-
-