Tasks are the update jobs created by Drop Guard to process a single or a group of related updates, depending on the configuration. For performing your desired update process, Drop Guard creates update tasks which can be processed manually (by executing them from the platform’s interface), or automatically as soon as the update is detected.
Drop Guard created a task successfully but did not start to process it yet.
The update execution just started.
The update was executed successfully. The individual information about the branch for testing will be displayed here.
This icon marks a passed test of a task.
The task is closed now.
Make sure the update task status is “Closed” or “Test passed” before checking the same module for updates. Drop Guard won’t create a task for the new version of the module if the task is in any other status than “Closed” or “Test passed”.
Drop Guard will close the update task automatically when a new version of the module is released, but there is still an open task for a previous version.
If you want to change some settings (for example, the branch where the updates should be committed to) simply change your settings, your existing task will be adapted, just like upcoming tasks in the future.
The “Updated branch” column on the Project overview page indicates whether the update got committed and if yes - to which branch. The module version will be displayed on the Project overview until it’s deployed.
On the image below we can see that the first update can be found in “master” branch already, and the second wasn’t executed yet.
Modules and tasks view
On the “Modules and tasks” screen, the modules with update tasks are listed at the top, and modules without tasks are listed at the bottom. You can also “Exclude” modules from updates on this page.