Class: DatadogAPIClient::V2::CIAppPipelineEventInProgressPipeline

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

Overview

Details of a running pipeline.

Instance Attribute Summary collapse

Method Summary

Methods included from BaseGenericModel

included

Instance Attribute Details

#additional_properties ⇒ Object

Returns the value of attribute additional_properties.



84
85
86
 
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_in_progress_pipeline.rb', line 84

def additional_properties
  @additional_properties
end

#error ⇒ Object

Contains information of the CI error.



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

def error
  @error
end

#git ⇒ Object

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.



29
30
31
 
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_in_progress_pipeline.rb', line 29

def git
  @git
end

#is_manual ⇒ Object

Whether or not the pipeline was triggered manually by the user.



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

def is_manual
  @is_manual
end

#is_resumed ⇒ Object

Whether or not the pipeline was resumed after being blocked.



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

def is_resumed
  @is_resumed
end

#level ⇒ Object

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



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

def level
  @level
end

#metrics ⇒ Object

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



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

def metrics
  @metrics
end

#name ⇒ Object

Name of the pipeline. All pipeline runs for the builds should have the same name.



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

def name
  @name
end

#node ⇒ Object

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



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

def node
  @node
end

#parameters ⇒ Object

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



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

def parameters
  @parameters
end

#parent_pipeline ⇒ Object

If the pipeline is triggered as child of another pipeline, this should contain the details of the parent pipeline.



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

def parent_pipeline
  @parent_pipeline
end

#partial_retry ⇒ Object

Whether or not the pipeline was a partial retry of a previous attempt. A partial retry is one which only runs a subset of the original jobs.



57
58
59
 
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_in_progress_pipeline.rb', line 57

def partial_retry
  @partial_retry
end

#pipeline_id ⇒ Object

Any ID used in the provider to identify the pipeline run even if it is not unique across retries. If the pipeline_id is unique, then both unique_id and pipeline_id can be set to the same value.



61
62
63
 
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_in_progress_pipeline.rb', line 61

def pipeline_id
  @pipeline_id
end

#previous_attempt ⇒ Object

If the pipeline is a retry, this should contain the details of the previous attempt.



64
65
66
 
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_in_progress_pipeline.rb', line 64

def previous_attempt
  @previous_attempt
end

#queue_time ⇒ Object

The queue time in milliseconds, if applicable.



67
68
69
 
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_in_progress_pipeline.rb', line 67

def queue_time
  @queue_time
end

#start ⇒ Object

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



70
71
72
 
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_in_progress_pipeline.rb', line 70

def start
  @start
end

#status ⇒ Object

The in progress status of the pipeline.



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

def status
  @status
end

#tags ⇒ Object

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



76
77
78
 
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_in_progress_pipeline.rb', line 76

def tags
  @tags
end

#unique_id ⇒ Object

UUID of the pipeline run. The ID has to be the same as the finished pipeline.



79
80
81
 
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_in_progress_pipeline.rb', line 79

def unique_id
  @unique_id
end

#url ⇒ Object

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



82
83
84
 
# File 'lib/datadog_api_client/v2/models/ci_app_pipeline_event_in_progress_pipeline.rb', line 82

def url
  @url
end