Hi, I found that 100 espace limit in a page was too few.
I usually maintained Platform Server once in a few months.
And it really a chore when deleting old versions of espace.
Maybe add a configurable paramater instead of static 100 entries.
As we work on the creating multiple versions with multiple applications, the outsystems platforms piles up all the different versions in the database creating a huge mass which is very difficult to maintain and clean up.
We gott suggestions from outsystems support team to use DBCleaner application or use Service Studio to clean up older versions but none of them work as they should.
For example DBCleaner lists all the older versions but it cannot delete them effectively and often leaves them without deleting the older version, even though we wanted to get rid of them.
Similary there are multiple issues with using Service Center's - "Check Old eSpace Versions to Delete". There are very limited options on the filters in this screen. We cannot choose any date range we want. We cannot select the individual versions to delete.
There is an absolute need for clearing all the older versions in a better way.
Overall it is becoming very difficult to get rid of the older versions as the companies builds the applications aggressively.
+1
Unfortunately, there are also several other features to better manage the platform that I think OutSystems is lacking. :(
Great idea.
Old espaces are the ones that we don't require any more (old versions). Right now it has got the option to remove the espaces in bulk for weekly/monthly etc. But when we talk about an individual espace, every individual espace should have the option to be deleted in bulk for old versions. That was my suggestion. Right now it is restricted to 10 at a time.
Actually I have a bit of a problem with the first response always being "delete old espaces" The only form of version control we have in the system is the old espaces and always deleting them basically means we have no version control. Rather than just making it easier to delete espaces I'd prefer to make the management of old espaces better and the handling of old espaces more efficient. Couple of options
* Allow a particular version to be marked as a checkpoint or major version. Then when deleting old espaces leave the checkpoint ones in place.
* Improve indexing and database handling of old espaces so that it doesn't slow the system down
* Compress or move old espace out of the main database but keep them accesible
+1 for John Williams
My wish list for this problem:
1. Allow a particular version to be marked as a checkpoint or major version. Then when deleting old espaces leave the checkpoint ones in place.
2. E.g. Weekly timer to delete versions older than X days. (excluding marked versions)
(X would be user defined separately for each in application level)
Please don't forget that if you tag a version using lifetime it won't be possible to remove them with DBCleaner (or using the current ServiceCenter functionality).
So when you are tagging and publishing versions (that are needed) you can keep them from being deleted. That will build a certain versioning history.
It would be nice if the platform manages this itself but for now the DBCleaner works ok. (But it won't be the first forge application that will be integrated into the platform :D)
I vote the idea. Similar concern here, I do the version-keeping per month.
Hi!
We are working on this idea :)
In terms of solution, in the first iteration, we are planning to deliver an API in LifeTime so you can remove tags for an application. Thus, you are able to remove the associated espace version in Service Center.
This could be later orchestrated using the DBCleaner forge component.
Hope this goes in line with your expectations.
We'd appreciate your feedback.
Thank you,
Joao Bento
Guys,
Since the LifeTime Feb version that is possible to delete application versions (LifeTime tags) using the new method "DELETE /applications/{ApplicationKey}/versions/{VersionKey}/" of LifeTime Deployment API v2. This feature will allow deleting in the environments the old module versions previously tagged by LifeTime. It requires Platform Server 10.0.912.0 (OutSystems 10 environments) or Platform Server 11 - Release Sep.2018 Cumulative Patch 1 (OutSystems 11 environments).
Would be nice to evolve now DBCleaner or other similar forge components to close this idea. Sounds good?
Cheers!
Hope this provides the solution for cleaning the OSLTM_MODULEVERSIONPRODUCERSIGModuleVersionProducerSignature (Module Version Producer Signature)
I like this idea, but I cannot get even the default 100 to delete. It gives a generic error, but it appears to be the same as when a process times-out. Is there a setting somewhere to raise the time-out? We are on a hosted system, and our dev / tst shared database is full...
Great idea!