Class: Ci::Resource

Inherits:
ApplicationRecord show all
Defined in:
app/models/ci/resource.rb

Constant Summary

Constants inherited from ApplicationRecord

ApplicationRecord::MAX_PLUCK

Constants included from HasCheckConstraints

HasCheckConstraints::NOT_NULL_CHECK_PATTERN

Constants included from ResetOnColumnErrors

ResetOnColumnErrors::MAX_RESET_PERIOD

Class Method Summary collapse

Methods inherited from ApplicationRecord

model_name, table_name_prefix

Methods inherited from ApplicationRecord

===, cached_column_list, #create_or_load_association, current_transaction, declarative_enum, default_select_columns, delete_all_returning, #deleted_from_database?, id_in, id_not_in, iid_in, nullable_column?, primary_key_in, #readable_by?, safe_ensure_unique, safe_find_or_create_by, safe_find_or_create_by!, #to_ability_name, underscore, where_exists, where_not_exists, with_fast_read_statement_timeout, without_order

Methods included from Organizations::Sharding

#sharding_organization

Methods included from ResetOnColumnErrors

#reset_on_union_error, #reset_on_unknown_attribute_error

Methods included from Gitlab::SensitiveSerializableHash

#serializable_hash

Class Method Details

.stale_processables ⇒ Object

In some cases, state machine hooks in Ci::Build are skipped even if the job status transitions to a complete state. For example, ‘Ci::Build#doom!` (a.k.a data_integrity_failure) doesn’t execute state machine hooks. To handle these edge cases, we check the staleness of the jobs that currently assigned to the resources, and release if it’s stale. See gitlab.com/gitlab-org/gitlab/-/issues/335537#note_632925914 for more information.



19
20
21
22
23
 
# File 'app/models/ci/resource.rb', line 19

def stale_processables
  Ci::Processable.where(id: retained.select(:build_id))
                 .complete
                 .updated_at_before(5.minutes.ago)
end