activepieces / activepieces

Your friendliest open source all-in-one automation tool ✨ Workflow automation tool 100+ integration / Enterprise automation tool / Zapier Alternative

Home Page:https://www.activepieces.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[BUG]: build image with dockerfile always fails

ahmad-swanblocks opened this issue · comments

Describe the bug
When trying to build the image using GitHub action it always fails.
After tracking and reviewing the dockerfile, I've found that the failure is in building the UI Core project.
I've tried to build the UI Core locally and also failed.

To Reproduce
Steps to reproduce the behavior:

  1. Run this command: npx nx run-many --target=build --projects=ui-core --configuration production
  2. See error

Expected behavior
It should build successfully the same as the server api project, trying to build the server locally works fine with this command: npx nx run-many --target=build --projects=server-api --configuration production

Screenshots
image

Additional context
Run the app with "npm start" works fine.
Building the server with command "npx nx run-many --target=build --projects=server-api --configuration production" also works fine

Hi,

We do use github actions to build and it works, Is there any steps to reproduce?

https://github.com/activepieces/activepieces/blob/main/.github/workflows/release-rc.yml

Hi @abuaboud,
I will try with this file but I have a question, should I use depot to build the docker image or it should also work with the standard docker build action in GitHub actions?

Thanks!

@abuaboud Thanks a lot, it works :).
I've discovered that it is all about typescript strict rules on initialization of variables, locally (with npm start) works fine but the issue appears when I try to build the docker image. Basically, I've ignored the TS warnings and that's why :).

So we can close the issue, many thanks again!

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If this issue is continuing with the latest stable version of Activepieces, please open a new issue that references this one.