Remove custom UI package build steps from workflows

The UI package now uses the standard backstage-cli build, so there's
no need for separate build steps in CI workflows.

Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Patrik Oldsberg
2026-02-09 17:21:53 +01:00
parent 34b11e16c8
commit a1c11eef03
4 changed files with 0 additions and 12 deletions
-4
View File
@@ -126,10 +126,6 @@ jobs:
- name: build all packages
run: yarn backstage-cli repo build --all
# For now BUI has a custom build script and needs to be built separately
- name: build BUI
run: yarn --cwd packages/ui build
# Build docs-ui to ensure documentation site builds successfully
- name: install docs-ui dependencies
working-directory: docs-ui
-4
View File
@@ -110,10 +110,6 @@ jobs:
- name: build
run: yarn backstage-cli repo build --all
# For now BUI has a custom build script and needs to be built separately
- name: build BUI
run: yarn --cwd packages/ui build
- name: verify type dependencies
run: yarn lint:type-deps
-2
View File
@@ -66,8 +66,6 @@ jobs:
- run: yarn tsc
- run: yarn backstage-cli repo build
# BUI has a custom build script and needs to be built separately
- run: yarn --cwd packages/ui build
- name: run E2E test
run: |
sudo sysctl fs.inotify.max_user_watches=524288
-2
View File
@@ -86,8 +86,6 @@ jobs:
- run: yarn tsc
- run: yarn backstage-cli repo build
# BUI has a custom build script and needs to be built separately
- run: yarn --cwd packages/ui build
- name: run E2E test
run: yarn e2e-test run
env: