deploy_pin 1.7.0 → 1.7.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ced30166491b43cb26d26c837ca1276e9825d3b48631cea70f3095e0a8590d01
-  data.tar.gz: '0538bf5ea753ba70a2daa8e2104939d38d8605f8ae72d284417bcbe249659a4f'
+  metadata.gz: 92739dddf68cb804a3d4e76873afcaa11bcf5481ebcf8dd45d277ae992616eb7
+  data.tar.gz: 729e8e6401392109892d868613e996517a56e476a01f74ed968a6fd79d5c9f0f
 SHA512:
-  metadata.gz: f16f07130b5544236e0a17d0658e2c1b5ec2eb2103a5321c4f11ef391492f87c056b69e8b8498553f686e1523989f6723bec205147760fc2c12062f266c3a27e
-  data.tar.gz: 64424aa72c121603c5ddd23f9e15051fca979b4e3393b1ed942b0319aadd3d441515d24203201148c8c125aed4c6dcb0e43b4c2079466e430f7681a56c5700e8
+  metadata.gz: 4655ced6a71eec2d98aa92e30cd5a16584c50b02b7d3757b8bd7a5c6898d6b93a904944d8e9ce478a80889e62f76ac78c6808b533ff004546cab4e33965a4e02
+  data.tar.gz: 105bef59cd93ba4a9c2fe88e8c60c75ce000439810c346359fcb9f823cdb025cf989137216a5f74c8aa5f212672ebc06df42feac1c2247dee745ea40b36e8d4a

data/MIT-LICENSE

@@ -1,4 +1,4 @@
-Copyright 2019 rafael
+Copyright 2019 Viktor Sych
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

data/README.md

@@ -178,7 +178,7 @@ To use a different formatting value than the default, you need to specify it exp
 
 ## Resumable Tasks
 
-When working with long-running code that processes a large dataset, it makes sense to store progress in the database to allow resuming the task later. You can do this by using the `DeployPin::Task` instance methods: `#progress` and `#increment_progress(num)`.
+When working with long-running code that processes a large dataset, it makes sense to store progress in the database to allow resuming the task later. You can do this by using the `DeployPin::Task` instance methods: `#progress`, `#save_progress!(num)` and `#increment_progress!(num)`.
 
 Here is an example of how to use these methods:
 
@@ -190,16 +190,14 @@ Here is an example of how to use these methods:
 # The progress is 0 by default
 Users.where(id: progress..).find_each do |user|
   # Do some work
-  increment_progress(1) # Increment progress by 1 and store it in the database so you can resume the task from this point
+  increment_progress!(1) # Increment progress by 1 and store it in the database so you can resume the task from this point
+  # or save_progress!(user.id) # Save the progress as the user id
 end
 ```
 
 This allows your task to resume from where it left off, minimizing the risk of repeating work.
 
 
-
-```bash
-
 ## Recurring Tasks
 If you want to generate a recurring task, you can use the `--recurring` option. Make sure to set a correct `--identifier`, which should be a numeric value. Positive and negative numbers are possible here. The identifier affects the order of task execution, allowing you to customize the sequence as desired.
 
@@ -236,6 +234,8 @@ bundle exec rake deploy_pin:run[I, II, III] - # enters to ongoing state before "
 bundle exec rake deploy_pin:run[rollback] - # enters "pending state"
 ```
 ## Similar Gems
+- https://github.com/ilyakatz/data-migrate
+- https://github.com/Shopify/maintenance_tasks
 - https://github.com/theSteveMitchell/after_party
 
 ## Contributing

data/lib/deploy_pin/task.rb

@@ -54,6 +54,12 @@ module DeployPin
       record.increment!(:progress, incrementor)
     end
 
+    def save_progress!(value)
+      raise NotImplementedError, 'Recurring tasks do not support progress yet.' if recurring
+
+      record.update(progress: value)
+    end
+
     def done?
       return if recurring
       return unless record

data/lib/deploy_pin/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module DeployPin
-  VERSION = '1.7.0'
+  VERSION = '1.7.2'
 end

data/lib/generators/deploy_pin/upgrade/templates/upgrade_deploy_pins.rb

@@ -4,5 +4,8 @@ class UpgradeDeployPins < ActiveRecord::Migration[7.0]
   def change
     add_column :deploy_pins, :progress, :integer, default: 0, if_not_exists: true
     add_column :deploy_pins, :completed_at, :datetime, default: nil, if_not_exists: true
+
+    # set completed_at to created_at for all completed deploy_pins
+    DeployPin::Record.update_all('completed_at = created_at')
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: deploy_pin
 version: !ruby/object:Gem::Version
-  version: 1.7.0
+  version: 1.7.2
 platform: ruby
 authors:
 - Viktor Sych
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2024-10-10 00:00:00.000000000 Z
+date: 2024-10-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: colorize