Skip to content

Conversation

@BillyWooo
Copy link
Collaborator

  • create litentry/omni-executor docker image
  • add skeleton for CI test
  • update Makefile, move executable and manifest with same folder level, as well as signature file.
  • use Alice as default sign account. Will update this later with predefined account; or randomly generated account for testing purpose.

@linear
Copy link

linear bot commented Nov 19, 2024

Copy link
Collaborator

@Kailai-Wang Kailai-Wang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general it looks good

shell: bash
run: |
for d in . identity/enclave-runtime bitacross/enclave-runtime; do
for d in . identity identity/enclave-runtime; do
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm why this change?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

previously tee-check checks enclave-runtime from both identity and bitacross. But didn't check other files within identity and bitacross.
I changed it to two jobs, each of them check files both within enclave-runtime and outside.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it does.

for d in . identity/enclave-runtime bitacross/enclave-runtime; do

does the workspace-wide check as they belong to the same workspace

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. You are right they are in the same workspace. I reverted the changes.

# see https://docs.docker.com/build/drivers/
driver: docker

- name: Build local builder
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we don't need this intermediate image while still having two stages in Dockerfile

It's built for other two workers for cache purpose

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we still need two stages. Actually I tried to merge them into one step. But the builder stage uses rust:1.82-bookworm, which is quite big. The final image pushed is also very big. That's the reason I revert back to two stages.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We still have two stages in Dockerfile, but we don't need to build a local-builder first IMO

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have removed the local-builder.

timeout-minutes: 40
run: |
docker compose -f docker-compose.yml
# docker compose -f docker-compose.yml -f ${{ matrix.test_name }}.yml up --no-build --exit-code-from ${{ matrix.test_name }} ${{ matrix.test_name }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can remove commented lines

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😂 These lines I left there on purpose. The above line is just placeholder. So it can easily to extend in the future.

45, 219, 105, 155, 49, 74, 164, 131, 153, 192, 15, 213, 225, 179, 167, 129, 12, 160,
229, 37, 133, 168, 141, 233, 98, 117, 254, 112, 139, 210, 76, 6,
229, 190, 154, 80, 146, 184, 27, 202, 100, 190, 129, 210, 18, 231, 242, 249, 235, 161,
131, 187, 122, 144, 149, 79, 123, 118, 54, 31, 110, 219, 92, 10,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's better to use explict expression than magic numbers

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah. I will improve it.

@BillyWooo BillyWooo self-assigned this Nov 19, 2024
@BillyWooo BillyWooo force-pushed the p-1139-omniexecutor-ci-and-deployment-for-dev branch from f54d5ec to b34749c Compare November 20, 2024 13:31
@BillyWooo
Copy link
Collaborator Author

tested on tee-dev.

@BillyWooo BillyWooo merged commit 8759aea into dev Nov 20, 2024
24 checks passed
@BillyWooo BillyWooo deleted the p-1139-omniexecutor-ci-and-deployment-for-dev branch November 20, 2024 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants