... | ... | @@ -60,6 +60,16 @@ This file will be loaded by the Jenkins master job and executed. |
|
|
|
|
|
**During a Merge-Request, if modifications to this particular file are made, they WON'T be taken into account.**
|
|
|
|
|
|
Last important point: on the Jenkins web interface, there is a **replay** button for a job. This mechanism works when it is a push event to `develop`. **It does not work when it is a merge request event.** The best way to replay a Merge-Request build is to:
|
|
|
|
|
|
- Go to the GitLab Integration page of the repository
|
|
|
- Select the *Merge Request Hook* event that triggered the job
|
|
|
- Click on *View Details*
|
|
|
- Make sure it is the correct event by examining the payload
|
|
|
- Click on the *Resend Request*
|
|
|
|
|
|
Another way is to push a new commit to the source branch.
|
|
|
|
|
|
# 3. Declarative Pipeline Script #
|
|
|
|
|
|
The script is written in `Groovy`, a Java-derivative language, using the Declarative Pipeline syntax. It does not prevent us to use some Scripted Pipeline syntax elements when needed.
|
... | ... | |