Class: DatadogAPIClient::V2::CIAppPipelineEventStep

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

Overview

Details of a CI step.

Instance Attribute Summary collapse

Method Summary

Methods included from BaseGenericModel

included

Instance Attribute Details

#_endObject

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



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

def _end
  @_end
end

#errorObject

Contains information of the CI error.



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

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.



32
33
34
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_step.rb', line 32

def git
  @git
end

#idObject

UUID for the step. It has to be unique within each pipeline execution.



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

def id
  @id
end

#job_idObject

The parent job UUID (if applicable).



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

def job_id
  @job_id
end

#job_nameObject

The parent job name (if applicable).



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

def job_name
  @job_name
end

#levelObject

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



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

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.



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

def metrics
  @metrics
end

#nameObject

The name for the step.



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

def name
  @name
end

#nodeObject

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



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

def node
  @node
end

#parametersObject

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



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

def parameters
  @parameters
end

#pipeline_nameObject

The parent pipeline name.



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

def pipeline_name
  @pipeline_name
end

#pipeline_unique_idObject

The parent pipeline UUID.



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

def pipeline_unique_id
  @pipeline_unique_id
end

#stage_idObject

The parent stage UUID (if applicable).



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

def stage_id
  @stage_id
end

#stage_nameObject

The parent stage name (if applicable).



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

def stage_name
  @stage_name
end

#startObject

Time when the step run started. The time format must be RFC3339.



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

def start
  @start
end

#statusObject

The final status of the step.



74
75
76
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_step.rb', line 74

def status
  @status
end

#tagsObject

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



77
78
79
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_step.rb', line 77

def tags
  @tags
end

#urlObject

The URL to look at the step in the CI provider UI.



80
81
82
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_step.rb', line 80

def url
  @url
end