Skip to navigation
Skip to content

Stages & jobs

Default Stage
- Default Job
Release
Requires a user to start manually
- Release to Maven

Build result summary

Details

Completed: 16 Oct 2023, 6:59:42 PM – 1 year ago
Queue duration: 1 second
Duration: 25 minutes
Labels: None

Revisions

SDK: 49f73c3a11e12c25da82fa7f3ed9e6e4853d88b2 49f73c3a11e12c25da82fa7f3ed9e6e4853d88b2
Release scripts: ced9ff00825ca1cb8c744547be4ba8ff994bd71b ced9ff00825ca1cb8c744547be4ba8ff994bd71b

First to pass since

#510 (Changes by Daniel Kayiwa – 1 week before)

Code commits

SDK
Author		Commit	Message	Commit date
	Wikum Weerakutti <wikum@linuxdeveloper.space>	49f73c3a11e12c25da82fa7f3ed9e6e4853d88b2 49f73c3a11e12c25da82fa7f3ed9e6e4853d88b2	Removing SDK_PROPERTIES_COMMENT variable (#257) * SDK-321: Optimizing SDK Cache Management Add the enableDataSaving parameter to the setup-sdk plugin. This parameter enables the data-saving mode. When using this mode, the SDK will reuse the existing cache folder rather than creating a new one. In normal mode, SDK will remove the cache folder after running the setup. * SDK-321: Optimizing SDK Cache Management Add the enableDataSaving parameter to the setup-sdk plugin. This parameter enables the data-saving mode. When using this mode, the SDK will reuse the existing cache folder rather than creating a new one. In normal mode, SDK will remove the cache folder after running the setup. * SDK-321: Optimizing SDK Cache Management * Removing SDK_PROPERTIES_COMMENT variable	16 Oct 2023

Jira issues

Issue		Description	Status
Unknown Issue Type	SDK-321	Could not obtain issue details from Jira