enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-12-19 09:31:47 +03:00
Code Issues Projects Releases Wiki Activity
0c7e79cccf
enso/build
History
James Dunkerley 4194e1fafa
Conditionally trigger AMI build. (#11680) 
Disabling causing the rebuild of AMIs so we can control the release in the cloud.
Nightlies pushed to the ECR but not AMI built.
Manual releases will be built and become the image run.
To be improved later.
2024-11-27 14:59:50 +00:00
..
base Rust bump, reduce dependencices (#10803) 2024-08-13 23:16:55 +00:00
build Add traces to integration tests + suppress one flaky assertion. (#11595) 2024-11-27 14:09:59 +00:00
ci_utils Build Ydoc on CI (#11517) 2024-11-26 16:51:27 +00:00
ci-gen Split ydoc server into separate module (#10735) 2024-08-08 12:12:05 +00:00
cli Conditionally trigger AMI build. (#11680) 2024-11-27 14:59:50 +00:00
enso-formatter Rust bump, reduce dependencices (#10803) 2024-08-13 23:16:55 +00:00
install Build Ydoc on CI (#11517) 2024-11-26 16:51:27 +00:00
macros/lib Build Ydoc on CI (#11517) 2024-11-26 16:51:27 +00:00
.gitignore Build script merge (#3743) 2022-10-10 23:38:48 +02:00
README.md Build Script Post-Gui1 Cleanup (#9376) 2024-03-12 20:25:51 +01:00

README.md


Enso Language

[WIP] Enso CI Build Scripts

The code under this directory is under ongoing intensive development. As such it has not been reviewed or cleaned up yet.

General principles

  • Written in Rust.
  • Portable. Works on any platform that Enso targets.
  • Do not duplicate functionality that is already available in tools being part of our tech stack.
  • Supports both developers and CI use-cases (and environments). Developers can call it locally to do anything that CI does.
  • Does not require much setup work. Where feasible sets things up for the user.

Concepts

Target

  • Can be built locally from sources. Building yields artifacts.
  • Artifacts are self-contained to a single filesystem directory.
  • Artifacts can be downloaded from a remote location rather than built with the same effect.
  • Can contain other targets.
  • Artifacts can be platform-specific.
  • Artifacts must be releasable as CI run artifacts or release assets.

Usage

While the script is invoked using cargo run, the convenience run script is provided in the repository root.

The general usage form is:

./run <command> [options]

The command itself is usually a combination of target name and subcommand, like ide build or backend test.

At every layer, the --help command can be used to get more information. Note that the information depends on the command, so running ./run --help will not give you the same information as ./run ide --help nor ./run ide build --help.

Targets

IDE

IDE is the top level target for our project. It consists of GUI and Backend targets.

Sources consist mostly of TS code for the Electron client and packaging.

Artifacts are platform specific and consist of the single image file.

GUI

GUI is the front-end part of the project. It also packages WASM-compiled parser written in rust.

Artifacts are portable across the platforms and consist of the web page that can be served either using Electron client (as IDE does) or using a web server (like the Cloud version of Enso).

Backend

Backend is the back-end part of the project, as seen from the IDE perspective. It contains a Project Manager bundle that includes:

  • Project Manager native image;
  • Enso Engine distribution (with the Standard Library);
  • GraalVM distribution.

These components are not represented as "Targets" (in terms of build script) but could be and likely will be in the future.