Class: DatadogAPIClient::V2::CIAppPipelineEventStage

Inherits:
Object
  • Object
show all
Includes:
BaseGenericModel
Defined in:
lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb

Overview

Details of a CI stage.

Instance Attribute Summary collapse

Method Summary

Methods included from BaseGenericModel

included

Instance Attribute Details

#_endObject

Time when the stage run finished. The time format must be RFC3339.



28
29
30
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 28

def _end
  @_end
end

#additional_propertiesObject

Returns the value of attribute additional_properties.



73
74
75
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 73

def additional_properties
  @additional_properties
end

#dependenciesObject

A list of stage IDs that this stage depends on.



25
26
27
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 25

def dependencies
  @dependencies
end

#errorObject

Contains information of the CI error.



31
32
33
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 31

def error
  @error
end

#gitObject

If pipelines are triggered due to actions to a Git repository, then all payloads must contain this. Note that either ‘tag` or `branch` has to be provided, but not both.



35
36
37
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 35

def git
  @git
end

#idObject

UUID for the stage. It has to be unique at least in the pipeline scope.



38
39
40
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 38

def id
  @id
end

#levelObject

Used to distinguish between pipelines, stages, jobs and steps.



41
42
43
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 41

def level
  @level
end

#metricsObject

A list of user-defined metrics. The metrics must follow the ‘key:value` pattern and the value must be numeric.



44
45
46
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 44

def metrics
  @metrics
end

#nameObject

The name for the stage.



47
48
49
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 47

def name
  @name
end

#nodeObject

Contains information of the host running the pipeline, stage, job, or step.



50
51
52
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 50

def node
  @node
end

#parametersObject

A map of key-value parameters or environment variables that were defined for the pipeline.



53
54
55
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 53

def parameters
  @parameters
end

#pipeline_nameObject

The parent pipeline name.



56
57
58
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 56

def pipeline_name
  @pipeline_name
end

#pipeline_unique_idObject

The parent pipeline UUID.



59
60
61
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 59

def pipeline_unique_id
  @pipeline_unique_id
end

#queue_timeObject

The queue time in milliseconds, if applicable.



62
63
64
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 62

def queue_time
  @queue_time
end

#startObject

Time when the stage run started (it should not include any queue time). The time format must be RFC3339.



65
66
67
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 65

def start
  @start
end

#statusObject

The final status of the stage.



68
69
70
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 68

def status
  @status
end

#tagsObject

A list of user-defined tags. The tags must follow the ‘key:value` pattern.



71
72
73
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_stage.rb', line 71

def tags
  @tags
end