We are still working on this KnowledgeBase!
Cool DevOps Release Notes
V3.5.4
Bug fixes
- [Deployment] When the pipeline now says the pipeline is done, we can continue with the next deployment plan. Even is there is still some job running in ADO
V3.5.3
New features
- [Release plan] The release plan can now be made up front in draft mode
Changes
- [Data] Storage of work items has changed. Instead of static entities, we now save everything in an aggregate. This means there has to be a data fix if you’ve used the release plan feature. See timers in DevOps_Core
- [Release plan detail] Unknown applications and known applications are now divided between lists. If there are no unknown applications, the list isn’t shown
- [Stage group] Changed the design, so it’s easier to change the names
Bug fixes
- [Application configuration] Extra safety measures so you can’t edit an application which you have no access to
- [Settings and configuration] Remove invalid messages when going from one instance to the other
- [Settings] It was not clear which settings are mandatory
- [Dashboard] New release plan button hidden when release plan functionality isn’t active
- [Dashboard] Scheduling message now shows only for scheduling
- [Dashboard] The build queue results are now shown for every team you’re in
- [Deployment plan] When activating a deleted deployment plan, you can now immediately edit the plan
- [Deployment plan] Fixed that you can’t have plans without applications
- [Global] Minor styling fixes
V3.5.2
New features
- [Release Plan detail] Now all work items which are direct children of the features are shown
Changes
- [Release plan detail] In release docs, the feature work items got the same look as the work items
- [Release plan detail] The workitems are now behind each other instead of beneath each other
- [LifeTime sync] The LifeTime sync now always looks at the site properties. If they are filled, the setting values are updated to the site property values.
Bug fixes
- [Deployment plan detail] Dependency between plans fixed
- [Deployment plan detail] In a non-edit mode, you see now the actual target environment of the deployment plan or the default target environment
- [Deployment plan detail] Page automatically refreshes when editing pipeline details
- [Deployment plan detail] Fixed the check if parent plan is high priority
- [Deployment plan detail] Can’t edit the dependencies on a plan you can’t edit
- [Dashboard] You can only see your own plans
- [Dashboard] Shortened all event blocks to a maximum of 100 characters
- [New release plan] You can’t save a release plan when you have a feature id without a start date
- [Dashboard] When settings dashboard refresh is set at 0, the dashboard won’t refresh
- [Pipeline detail] Fixed getting the stages in the pipeline screen
- [Menu] Hide release plan menu item when release plan functionality isn’t active
- [Data] Truncated some data, so it will never go over the allowed size
- [Data] Adjusted the delete rule, so a release pipeline can be run again when it errors
- [Global] Typo’s
- [Global] Removed empty error messages
- [Global] Minor CSS changes
V3.5.1
New features
- [Pipeline detail] Work items have been added to the release plan
Changes
- [Data] BuildIds are now stored when a certain stage is completed successfully. This can be set in the pipeline itself
- [Pipeline details] Moved stages to the pipeline page
Bug fixes
- [Global] Minor style changes
- [Global] Minor bug fixes
3.5.0
New features
- [Deployment plan detail] Target environment per deployment plan
Changes
- [Settings] Added settings for scope/subscope for release documentation
Bug fixes
- [Release plan detail] Fixed testresultid, now showing the correct id
V3.4.4
New features
- Target environment per deployment plan
Changes
- Improved performance of Dashboard
- Added ‘show deleted’ to pipeline-servers
- It’s now impossible to add ‘EndOfPipeline’ to a GroupStage
- Made advanced sql accessible for Oracle
- History in deploymentplan detail now shows the start date of the plan itself
- Grouping of the result is now stored after the pipeline finishes. Old plans will not be fixed, so those will have incorrect data.
- New releaseplan now asks for a simple date instead of a release tag to make it more clear
- Moved http_log to audit_module
- You can’t delete a pipeline server if it’s used in a deployment plan
Bug fixes
- Fixed Buildqueue monitor, when the module is deleted we might have a process still active
- Fixed order in dropdown list in stages
- Fixed pagination in application overview
- Fixed the possibility to have a high prio plan dependent on a low-prio plan
- Fixed some typos
- Fixed new release plan start
- Made sure the detail page doesn’t fire of actions twice
V3.4.3
New features
Changes
- Refactored application versions sync, so we reduce the amount of webservice calls if possible
- Removed external tinyMCE dependencies
Bug fixes
V3.4.2
New features
Changes
- Removed Traceability Log page. You can find it in the normal logging page as well
- Even if log response is turned off, errors will be logged in http-calls
- Reviewed the timer-usage and reduced the number of wakeTimer-calls
- Changed log level in settings from integer to dropdown
- Removed ‘add new release plan’ restriction
- Removed ‘delete release plan’ button
- Additional evidence now uses the TinyMCE as editor, so it will be a rich text editor
- Improved dashboard performance
- Improved timeline updates performance
- Many more minor refactoring to reduce database calls
Bug fixes
- Improved purging of logging data
- Fixed false stage group status
- Minor UX improvements
V3.4.1
New features
Changes
Bug fixes
- Improved performance on dashboard
- Fixed bootstrap timer for configuration
V3.4
New features
- [Pipeline settings] Toggle added to a pipeline to include/exclude the scope in the request
- You are now able to create a releaseplan. This will generate a release document and will tag the repository. In a next release you will also be able to approve it or not and have more information in the releasedoc
- [Teams] A template of evidence can be edited for a team
- [Settings] Some new settings added
Changes
- [Pipeline settings] The pipelines now have pipeline types: release and deployment
Bug fixes
- Configuration values will now be set to empty/false or -1 if it does not exist yet
- Minor bug fixes
V3.3
New features
- [Application overview] You can now see if the deployment plan in which the application resides is deleted.
- [Lifetime sync] A message will appear when the sync hasn’t run for more than a day
Changes
Bug fixes
- [Application overview] Filter in application is now working as intended
- Minor bug fixes
v3.2
New features
- [Deployment plan detail] You can now set the target environment in Deployment Plan as well
- [Dashboard] When there is a problem with the LifeTime sync, you’ll see an event block on the dashboard screen
- [Settings] As admin you can now set a message to be shown on the dashboard for all users to see
- [Deployment plan detail] When starting an ad hoc deployment, the deployment plan detail screen is now refreshed
Changes
- Non-functional site properties have been removed
Bug fixes
- [Settings] When there are no more than 3 environments, the 4th default environment won’t be shown
- [LifeTime sync] Inactive environments are now automatically deleted, if they’re not a target environment
- [LifeTime sync] Zones, Catalogs and Database Connections for inactive environments are now automatically deleted
- [Deployment plan detail] Application list only shows the application once
- There is a timer to remove all duplicated application versions
- AI Mentor Studio update
- Typo’s
- Minor bug fixes
v3.1
New features
- As admin you can now select up to 4 default filter environments
- [Pipeline administration] You can now see which plans use which pipelines
- [Dashboard] As an admin you can now see if the build queue monitor is active or not
- [Dashboard] You can now see if the LifeTime sync is running or has an error
- [Settings] You can set all settings on this page
- [Deployment detail] You can look into the deployment detail of a deleted plan. You can also reactivate it here
- [Application overview] You can now filter on planless applications
- Added some micro-animations
Changes
- The deployment plan overview page is split up between dashboard and pipeline administration screens. Deployment plan overview page is deleted
- Because of the new warning icon, the currently running icon is turned blue
- Site properties are now changed to settings. The site property values can be transferred on the Settings screen.
- [Deployment detail] Validation is done in the background, so you won’t have to stay on the same page
- All logging pages are sorted from newest to oldest
- [Dashboard] Pipeline timeline in pop up ‘show timeline’ is now refreshing automatically
Bug fixes
- [Dashboard] Result at dashboard fixed failed counter
- [Deployment Detail] Feedback box: error message and CSS styling
- [Schedule] Missing plan shows the right plan
- Changed a huge image for a smaller one
- Fixed problem with settings
- Audit purge timer SQL fixed
- Minor bugfixes
- Minor style fixes
v3.0.1
New features
- OnHover for high priority now on whole cel
- Clicking outside of popups will close them. NOTE: they won’t save anything, it functions as a cancel
- Search fields are now searchable with keys and ids
- Page build queue detail now has automatic refresh every 5 minutes and a button to refresh
- On the dashboard, you will see last schedule results for each team you are a member off. Admins will always see the last schedule result
Changes
- Release notes moved to DevOps
- Version number moved to DevOpsData
- In schedule an icon is shown when outdated modules aren’t redeployed
Bug fixes
- Pipelines now uses display name when possible
- Ordering in team-ddl in applications fixed
- Now plans wait for their parent or high priority to finish deploying before they start
- Login logic
- Removed doubles from schedule
- Cursor pointer on all popup cross icons
- Cursor pointer applications when adding applications to plan
v3.0.0
New features
- New Look&Feel. The whole application has been reviewed to provide the best UX possible
- [Dashboard] complete overhaul
- [Deploymentplan detail] complete overhaul
- [Applications overview] complete overhaul
- [Schedule] improved
- Logging, generalize action to purge data by category and parentid
- Added link in applications overview, so you can go to the configuration for that application
- Added teams + filter on the overview pages applications/deployment plans
- [Auditlogging] added crudtypes: softdelete
- [Auditlogging] added attribute IsBulk, so we know if the operation was a bulk operation (and the jsons are not filled)
Changes
- Configuration, removed unused parameters
- Improved the AzureStatusPoller
- Removed some containers in screens
- moved link in menu of deployment plans from operation to overview
- Links in weekly overview now go to the buildqueuedeploymentplandetail page
- [auditlogging] changed functionality
- [auditlogging] replaced FK configurationtype for a textfield called source, so we are tight to auditg anymore when we need to audit a new thing
- [auditlogging] created specific audit actions for de crudtypes.
- [auditlogging] changed the audit-logging screens
- [Weekly overview] removed
- [Statistics] removed
Bug fixes
- LifeTimeSync, fixed the timer-schedules
- Fixed new pipeline action
- Lots of typos fixed
- Many more small bugs
v2.1.7
Changes
- Overhaul of screens, creating a consistent way of showing date(time)s by using custom functions in client/server
- Enabled several pages to see for non-admins.
- Refactored Azure services actions
- Refactored AzureStatusPoller
- AzureTrigger will now return a more detailed error if it fails to fire up.
- Pipeline Stages will now have a more detailed information, when the stage failed
- [Page] Deployment plan
- Deploy now is able to refresh the latest state of the pipeline when the plan is running/queued
- Changed the deploy tab
- History-tab, you can now go to the detailed information of that specific run.
- [Page] build-queue pages
- overall improvements
- now includes loglevel
- added some links
- misc ux
- [Page] Applications & Deployment plans overview
- Search keyword instead of dropdown
- Now shown all applications with or without deployment plans
- Changed styling
- Added paging
- Logging
- Added logging where needed
- Consolidated audit and custom logging into one table
- Removed a log-table from cooldevops_core, since it was not useful, and the information is also stored in the customlog
- Added timer to cleanup logging
- AzureLogging now also stores checkpoints,jobs,tasks and their issues
- Added new screen to see all buildqueue-deployment plans
- Site Properties
- Added ‘BuildQueue_TimeslotCheck’, default is false, so no check if it’s possible to run the plan inside the timeslot.
- Removed ‘BuildQueue_ParallelDeploymentsActive’, BuildQueue_ParallelDeploymentsMaximum=1 will mimic the old way.
- Removed ‘IsBackwardsCompatible’, Removed backwards-compatibe stuff that was behind that same property
- Wrapped integer site-properties in cooldevops_core, to clamp the values to prevent runtime errors
- Added AzureStatus_MaxTries, AzureStatus_SleepInSecs for the AzureStatusPoller
v2.1.6
Changes
- Improved the applications screen
- Added a button group for configuring the application type
- Added tags for normal, bdd and forge components to easily identify
- Hidden the application key (only needed for debugging)
- Changed the text to make it more clear what it is
- Choose Zone and Catalog from dropdown, environment specific values will be inherited from (administator) definitions
- Show extension modules in application on separate tab, opportunity to choose Database connection when applicable
- Added the same tags to edit deployment plan – tab applications
- Added BDD component selection to support migrating from BDD to Core Layer Testing
- Build Queue Process Version 2
- Version Number determined by new site property (CoolDevops_Core, BuildQueueProcessVersion)
- Queued Deployment Plans and Timeslots are monitored by new process
- For the one Build Queue that is to be executed a new process is started to execute the requested deployment via the pipeline
- Changed menu items (Overview, Configuration, Operation)
- Menu items only visible for admin (Zones, Catalogs, Pipelines, Pipeline servers, schedule, Queue Timeslots, DeploymentplanScope)
- Version number of CoolDevOps determined with action f_VersionNumber_Get from CoolDevOps_TH module.
- List-item change to reduce padding moved from application page to CoolDevOps theme to apply to all lists in the application
- Deployment window with multiple deployment plans will be processed in parallel when possible
- Administrators can mark deployment plan as high priority, these plans will be deployed first, before any non-high priority plans will be deployed
- Plans can be made dependent of other plans. Depending plans will be deployed only after preceding plans have been deployed successfully
- Screen with build queues, build queue deployments and audit & Logs are expanded to show dependencies and clearer views
- Deployment screen
- button ‘Start Deployment’ (ad hoc) will pass through a popup window (extra confirmation), that will show some extra information when available
> whether the plan is part of next deployment window
> whether next deployment window is already running or will be started within short amount of time
- extra tab added to define plan dependencies
- extra checkbox on Advanced configuration to mark plan as High Priority
- button ‘Start Deployment’ (ad hoc) will pass through a popup window (extra confirmation), that will show some extra information when available
- Audit Configuration
- Every configuration setting in Applications will be logged.
- New screen Audit configuration
- Detailed screen to see what is changed
- Restricted time slot
- New screen with overview of the restrictions
- possible to schedule a restriction on a specific date or schedule on a specific day that repeats every week
- Restrictions are visible in weekly overview
- check on restricted timeslot before ad hoc deployment starts. If the timeslot is blocked, a pop-up shows up with the question to continue. The deployment will start as soon as possible (after the restricted timeslot)
- Checks if restricted timeslot is active before starting a new deployment.
- show previous restrictions limited to ten records
- input Test repository name moved to ‘add new deployment plan’
- input is removed from tab ‘general configuration’ in deployment plan
- repository name is visible in the header of the deployment plan
- Schedule
- Changed lay out of overview
- Restrictions added to the overview
- Weekly restrictions are marked blue and one time restrictions are marked red
- position of tooltip changed to bottom
- Weekly overview : Text ‘window’ added to the deployment window
- Deployment plan tab execution : description about dependencies changed, title of list of dependencies changed
- Deployment tab deploy: batch and text removed
v2.1.5
Changes
- Removed the LifetimeSDK from _Core by removing the lt_application dependency. We now use the Lifetime_API as it should have been This prevents from looking at outdated version that has been one time synced by lifetimesdk
v2.1.4
Changes
- Changed the validation errors and different states to properly inform the user of the state
- Reformatted the validation errors to make it more readable
v2.1.3
New Features
- Added cooldevops_th module to get aligned with coolconfigurator architecture and support SSO, LDAP or outsystems login flows
Changes
- Changed the teams dropdown in the application details so that the user can only assign the teams he/she is a member off. Admins can select any team
- Changed the start_sync action to check for isFirstTime after installing CoolDevOps. If that’s the case we import the site properties to set the configuration for the sync
- Changed the finish_sync action to throw an exception but not rollback the data since when we reach this point it has been successfully synced. We do log the error of the LTM_Sync table
- Removed isContinueWithError from the Configuration table. This needs to be on deployment plan level not config level
- Changed Extract_Scope to use the deploymantplan.isContinueWithErrors value instead of Configuration
- CoolDevOps_Azure_IS -> continuwitherrors removed from logic. This was a bad interpretation of the usage for this attribute
v2.1.2
Changes
- LifeTime sync has been made more robust to handle corrupted data from LifeTime
- LifeTime sync logging has been added to see be able to analyze the sync (loglevel 0: debug, 1: error, 2: info)
v2.1
- Configuration on Deployment Plan level
- Redeploy of outdated applications
- Added favicon
- Minor bugfixes
v2.0 June 12, 2023
- Changing the application from LifeTime to development
- Syncing all LifeTime data
- Saving on pseudo-LifeTime database
- Added database connection to configurable data
- Added “test”-tab for repository alignment
- Application settings configurable by everyone
- Minor bugfixes
- CSS fixes
- Core Layer Testing applied
v1.3 June 2022
- Removed unnecessary settings
- SAST now places files in the zip-folder with a folder structure
- Dashboard made semi-responsive
- Added timer to remove orphans (manual trigger)
- Update ProcessId sooner than usual
- Minor bugfixes
v1.2 May 26, 2022
- Added Help-page
v1.1 May 12, 2022
- All users access to LifeTime can validate Deployment Plans
- Added confirmation when saving a Deployment Plan
- Minor bugfixes
Version 1.0 May 1, 2022
- Initial Release