Skip to content

[Improvement]: Optimize subsequent build times for unchanged Ballerina projects #44136

Open
@Thevakumar-Luheerathan

Description

@Thevakumar-Luheerathan

Description

Currently, every invocation of bal build, bal run, or bal test recompiles the entire project from scratch, even when there have been no changes to the source files since the last build. We need to introduce a mechanism to detect unchanged projects and skip redundant compilation steps for subsequent commands. This would significantly reduce build time when no code changes have been made since the last successful build.

Common use cases:

  • Executing bal build immediately followed by bal run
  • Executing bal build immediately followed by bal test

Implementing this optimization will improve the overall developer experience by making common workflows more efficient.

Describe your problem(s)

No response

Describe your solution(s)

No response

Related area

-> Compilation

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

Metadata

Metadata

Type

No type

Projects

Status

In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions