This document contains the roadmap for the development of the saker.build system. It is related only to build system features, other possible additions and doesn't include information for other packages. For roadmaps concerning language support and other build tasks see the associated packages.
This document contains the proposed features, improvements, and crucial bugfixes for the saker.build system. The targeted goals doesn't specify a release date, as due to the limited maintainer development resources, we currently can't estimate exact release dates.
The specified features, improvement and bugfixes will ship as they are implemented. Progress can bee seen in the associated GitHub issues. The priority of a goal is determined on a case-by-case basis.
See also: saker.nest roadmap
The build cache functionality for the build system is partially complete. A build cache server needs to be implemented that allows retrieving and publishing task results.
Optimally, the build cache shoulb be configureable to only allow publishing from specified sources, e.g. from Continuous Integration, and should allow publishing from local dev builds.
Based on the use-cases and feedback for the build system, the saker.standard packages should be improved to support commonly occurring scenarios. This goal should be based on user feedback.
Update: Basic implementation of the build trace is complete. Additional improvements are still to be developed. See Build trace.
Build tracing feature should be added to saker.build. A build trace is a recording of the build process. It allows the developer to visualize and examine the build process.
The build trace should provide access to the following related to build tasks:
- Tasks visualized on a timeline chart.
- Task dependencies on other tasks.
- Task environment and execution property dependencies.
- Task inner task executions.
- Task delta and incrementality information.
- Task remote dispatching information.
- Where the tasks were dispatched. Why they were dispatched there, and why not if not.
- Task file dependency information.
- Report possible file dependency conflicts.
- Other task related meta-datas.
The build trace should consist of two parts. First, a generated data that is produced by the build execution. Second, HTML pages that can be used to visualize the mentioned data. The build trace should be viewable offline.
The build trace recording should be non-intrusive to the build execution.
The saker.msvc package implements features for the MSVC C++ toolchain. Build task implementations for the
gcc compilers should be implemented as well.
Based on the saker.msvc build task implementations, modifying them to support the above compilers shouldn't be a hard task, but is not straightforward. The implementations should be published as a new package.
Common parts for C/C++ support may be exported to newly introduced packages if appropriate.
Support for using saker.build to develop for Android should be added. The implementation may be gradual, meaning that at start the build tasks should support creating basic Android applcations, and later it can be extended for more complex use-cases.
Support for using saker.build to develop for iOS & macOS should be added. The implementation may be gradual, meaning that at start the build tasks should support creating basic iOS & macOS applcations, and later it can be extended for more complex use-cases.
It shall be examined how developing for .NET, C# and related technologies can be integrated with the saker.build system. This goal is to be split up once the goal progresses.
Plugin support for other Integrated Development Environments should be added (other than Eclipse). It should be examined how popular IDEs can be integrated with, its feasibility, and possibility of the implementation.