Handle new jobID for scale sets
There seems to be a change in the scale set message. It now includes a jobID and sets the runner request ID to 0. This change adds separate job ID fields for workflow jobs and scaleset jobs. Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
This commit is contained in:
parent
d26973da2a
commit
a984782fd7
8 changed files with 107 additions and 59 deletions
|
|
@ -319,6 +319,12 @@ type User struct {
|
|||
type WorkflowJob struct {
|
||||
// ID is the ID of the job.
|
||||
ID int64 `gorm:"index"`
|
||||
|
||||
// WorkflowJobID is the ID of the workflow job.
|
||||
WorkflowJobID int64 `gorm:"index:workflow_job_id_idx"`
|
||||
// ScaleSetJobID is the job ID for a scaleset job.
|
||||
ScaleSetJobID string `gorm:"index:scaleset_job_id_idx"`
|
||||
|
||||
// RunID is the ID of the workflow run. A run may have multiple jobs.
|
||||
RunID int64
|
||||
// Action is the specific activity that triggered the event.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue