Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

[CD] Add COMMIT_ID param to release job #16202

Merged
merged 8 commits into from
Sep 24, 2019
Merged

[CD] Add COMMIT_ID param to release job #16202

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
c4c72f7
Removes unnecessary parameter
perdasilva Sep 18, 2019
410065a
Adds revision parameter to release job
perdasilva Sep 18, 2019
da7976c
Update documentation
perdasilva Sep 18, 2019
b675d16
Changes RELEASE_JOB_TYPE to string parameter
perdasilva Sep 18, 2019
0cc4c6f
Adds variant and release job type checks
perdasilva Sep 19, 2019
1a11cb7
Adds release job update to CD pipeline
perdasilva Sep 19, 2019
03b9e0e
Disable concurrent builds for CD pipeline
perdasilva Sep 19, 2019
6668aae
Updates documentation with new release job mechanics
perdasilva Sep 19, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Updates documentation with new release job mechanics
  • Loading branch information
@perdasilva
perdasilva committed Sep 19, 2019
commit 6668aaecbee2baa98d6f0a35b2e59552a34319c0
2 changes: 2 additions & 0 deletions cd/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,8 @@ The release job executes, in parallel, the release pipeline for each of the vari

NOTE: The **COMMIT_ID** is a little tricky and we must be very careful with it. It is necessary to ensure that the same commit is built through out the pipeline, but at the same time, it has the potential to change the current state of the release job configuration - specifically the parameter configuration. Any changes to this configuration will require a "dry-run" of the release job to ensure Jenkins has the current (master) version. This is acceptable as there will be few changes to the parameter configuration for the job, if any at all. But, it's something to keep in mind.

To avoid potential issues as much as possible, the CD pipeline executes this "dry run" and ensures that Jenkins' state of the release job matches what is defined for the release job in the specified COMMIT_ID. This is done by setting the **RELEASE_JOB_TYPE** to *Status Update*.

It should be noted that the 'Pipeline' section of the configuration should use the *$COMMIT_ID* parameter as the specifier and 'lightweight checkout' unchecked. For example:

![job setup example](img/job_setup.png)
Expand Down