Build #511

Plan branch:

Stages & jobs

  1. Default Stage

  2. Release

    Requires a user to start manually

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
27 minutes
Labels
None
Revisions
SDK
2623cd97af4e912744a93b01e238c9a2a80d8077
Release scripts
ced9ff00825ca1cb8c744547be4ba8ff994bd71b
Failing since
#510 (Changes by Daniel Kayiwa – )
Fixed in
#512 (Changes by Wikum Weerakutti <wikum@linuxdeveloper.space>)
No failed test found. A possible compilation error occurred.

Responsible

  • Daniel Kayiwa Daniel Kayiwa Automatically assigned

Code commits

SDK
Author Commit Message Commit date
Wikum Weerakutti <wikum@linuxdeveloper.space> Wikum Weerakutti <wikum@linuxdeveloper.space> 2623cd97af4e912744a93b01e238c9a2a80d8077 SDK-321: Optimizing SDK Cache Management (#255)
* 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

Configuration changes

Plan configuration has changed since the last successful build. See the plan audit log for more details.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeSDK-321Could not obtain issue details from Jira