The document discusses configuring Jenkins for continuous integration by polling the source code repository. It recommends setting Jenkins to trigger a build whenever new changes are detected in the source code. It also provides details on how to specify cron schedules, noting that each line contains five fields separated by tabs or whitespace and that multiple values can be specified using commas, ranges with hyphens, or asterisks as wildcards. The document concludes by looking forward to the next lecture.
The document discusses configuring Jenkins for continuous integration by polling the source code repository. It recommends setting Jenkins to trigger a build whenever new changes are detected in the source code. It also provides details on how to specify cron schedules, noting that each line contains five fields separated by tabs or whitespace and that multiple values can be specified using commas, ranges with hyphens, or asterisks as wildcards. The document concludes by looking forward to the next lecture.
The document discusses configuring Jenkins for continuous integration by polling the source code repository. It recommends setting Jenkins to trigger a build whenever new changes are detected in the source code. It also provides details on how to specify cron schedules, noting that each line contains five fields separated by tabs or whitespace and that multiple values can be specified using commas, ranges with hyphens, or asterisks as wildcards. The document concludes by looking forward to the next lecture.