News time: Dashboard, Composer, Jira support
Our existing users may have already noticed a few changes and improvements in Drop Guard. However, not everything is visible enough, so we decided to make a short list with the recent updates.
Drop Guard is now capable of managing your composer.json and composer.lock files, in the same fashion as you would do it normally via CLI.
When executing the update task, Drop Guard modifies the composer.json to accommodate the recommended module or core version and runs "composer update" command to keep the composer.lock in sync. Both files get pushed to the repository, and the only thing you need to take care about is running "composer install" to receive the updated packages.
We are providing personal assistance for those having trouble with the setup or configuration. Just drop us a note and we will arrange a personal onboarding and setup session.
We encourage everyone who's in love with Composer to test this feature and give us your generous feedback. As always, we're looking for both positive and negative thoughts - don't be shy!
Not long ago the only way to manage update tasks and statuses across multiple projects was to inspect each project connected to Drop Guard separately. Things have changed now - you have a sleek dashboard-like interface where tasks from all projects are collected. You can adjust the Dashboard to fit your needs by rearranging widgets or adding new ones.
The Activities page and widget give you a bird's-eye view of everything going on under the hood - all update attempts, patches application, changing statuses - arranged in chronological order.
Latest release date
Smallish, but a long-awaited feature (we take the responsibility for you waiting so long for it) - you can see the date of the recommended release next to the project version on all pages.
Project management systems support
We have started implementing project management systems support, starting from Jira (Redmine will follow shortly, as well as other popular services). Here's a little background on how it works:
On the project edit screen, you can provide your Jira/Redmine credentials (we recommend to create a separate user with the correct permissions for that), and map Drop Guard tasks statuses to the corresponding statuses in your system.
Once it's done, Drop Guard will start establishing connections between its own tasks and the tasks in the project management system. All you need to do is to create the Action reacting to the "New updates are available" event.
Next, when Drop Guard creates the update task, it will create the appropriate task in your system, listing the modules, their versions and everything you'd like to be included in such task.
Both tasks will be kept in sync, so once all tests and checks for an update are performed, and you close the project management task (or give it another status), the corresponding Drop Guard task will be also closed (or the status will be changed).
It allows you to manage Drop Guard tasks from the external system without ever visiting Drop Guard itself. How cool is that!
And as always, due to Drop Guard's extensible nature, you may choose to fire up the external task only if there's an error or the updates are ready to test, just make it work according to your established workflow.
You use another system? Send us a note with your favourite one and it may happen it will be added soon. Can't wait to hear from you!
A lot of speed and stability improvements were made as well, so don't forget to check your existing account (or create a new one), to see it by yourself.
We have more exciting news to come. Keep your ears open!