commit | 39c092dedf70543ef7486ecdf34f2a55a27d6a5b | [log] [tgz] |
---|---|---|
author | Tiago Bento <tiagobentofernandes@gmail.com> | Tue Sep 21 15:06:33 2021 -0300 |
committer | Tiago Bento <tiagobentofernandes@gmail.com> | Tue Sep 21 15:06:33 2021 -0300 |
tree | dab583372f9d3c7260018e8d21050ac7ec0d82e4 | |
parent | aa7e9409c4cf203bb728ca1e1ee32d7ed5c0cbf5 [diff] |
Add --concurrency 1 to the staging build
Kogito is the next generation of business automation platform focused on cloud-native development, deployment and execution.
This repository contains all the tooling artifacts of the Kogito project.
To start building the KIE Tooling Core project, you're going to need:
>= 16.2.0
(To install, follow these instructions: https://nodejs.org/en/download/package-manager/)1.22.10
(To install, run npm install -g yarn@1.22.10
)4.0.0
(To install, run npm install -g lerna@4.0.0
)3.8.1
11
1.16
After installing the tools above, you'll need to download the dependencies and link the packages locally. Simply run:
yarn bootstrap
To build it, you'll have two choices:
yarn build:dev
- This is fast, but not as strict. It skips tests, linters, and some type checks. Be prepared for the CI to fail on your PRs.yarn build:prod
- The default command to build production-ready packages. Use that to make sure your changes are correct.NOTE: The Kogito Tooling build is parameterized by several Environment Variables. For an extensive list of these variables, please see packages/build-env/README.md
(link).
Final artifacts will be on packages/*/dist
directories.
kogito-editors-java
While kogito-editors-java
is not integrated in this monorepo, we have dedicated environment variables to configure where to copy the Editors from. If those environment variables are empty, the Editors are copied from the installed NPM package on node_modules
.
export EXTERNAL_RESOURCE_PATH__bpmnEditor=/Users/tiago/redhat/kogito-editors-java/kie-wb-common-stunner/kie-wb-common-stunner-sets/kie-wb-common-stunner-bpmn/kie-wb-common-stunner-bpmn-kogito-runtime/target/kie-wb-common-stunner-bpmn-kogito-runtime/
export EXTERNAL_RESOURCE_PATH__dmnEditor=/Users/tiago/redhat/kogito-editors-java/kie-wb-common-dmn/kie-wb-common-dmn-webapp-kogito-runtime/target/kie-wb-common-dmn-webapp-kogito-runtime/
export EXTERNAL_RESOURCE_PATH__scesimEditor=/Users/tiago/redhat/kogito-editors-java/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-runtime/target/drools-wb-scenario-simulation-editor-kogito-runtime
The Kogito Tooling project contains several applications. To develop each one of them individually, refer to the instructions below.
packages/vscode-extension-pack-kogito-kie-editors
folder on VS Code. Use a new VS Code window so that the packages/vscode-extension-pack-kogito-kie-editors
folder shows up as root in the VS Code explorer.Debug
menu/section. You can also use the respective shortcuts (F5 to start debugging, for instance).webpack
and webpack-cli
to be globally installed on NPM. Normally you can do that with npm install -g webpack@4.41.2 webpack-cli@3.3.10
, but sudo
may be required depending on your installation.packages/vscode-extension-pack-kogito-kie-editors
, you have to manually rebuild them before relaunching the extension on VS Code.packages/chrome-extension-pack-kogito-kie-editors
folder on your favourite IDE. You can import the entire repo as well if you want to make changes to other packages.yarn build:dev
on packages/chrome-extension-pack-kogito-kie-editors
. This will create a version of the Chrome Extension that fetches the envelope locally.yarn run serve-envelope
on packages/chrome-extension-pack-kogito-kie-editors
. This will start a webpack serve
instance with the editors and their envelope. We use that because we don't pack the Chrome Extension bundle with the editors inside. Instead, we fetch them from GitHub pages.chrome://flags/#allow-insecure-localhost
in your Chrome browser and enable this flag. Alternativelly, you can go to https://localhost:9001
and add an exception.chrome://extensions
. Enable “Developer mode” in the top-right corner and click on “Load unpacked”. Choose the packages/chrome-extension-pack-kogito-kie-editors/dist
folder.packages/online-editor
.yarn start
. This will start a webpack serve
instance with the Online Editor resources.https://localhost:9001
.packages/desktop
or packages/hub
. They work exactly the same.yarn start
. If you make changes and want to reload the app, run yarn run build:dev && yarn start
. This will recompile the module and restart the Electron app. Remember: if you make changes to other modules, you have to build them too!yarn run build:prod
. This will pack the application for the current OS. If you want to pack the application for a different OS, run yarn run pack:linux
, for example. See package.json
for more details.packages/kie-editors-standalone
.yarn start
. This will start a webpack serve
instance with the Standalone Editors test page.https://localhost:9001/resources/dmn
and the Standalone BPMN Editor by accessing https://localhost:9001/resources/bpmn
.