-
-
Notifications
You must be signed in to change notification settings - Fork 261
Conversation
Hi, I ran your PR in gitlab CI (which is not triggered automatically for 3rd party)
But all good, we don't need to run it in gitlab that much. It actually makes best sense in github (which is triggered for 3rd party) as these plugins are develop mostly by 3rd party. |
07fc004
to
118e6b3
Compare
Hi @mroz22, Thanks for trying to fix the GitLab issues! It looks like https://gitlab.com/satoshilabs/trezor/connect/-/jobs/2099096538 was just running on a generic
I've added Lines 210 to 212 in 118e6b3
If it still doesn't work (and since you said GitLab CI isn't as important as GitHub CI), I |
This is to ensure that nobody with publish permissions at @trezor accidentally publishes the ethereum plugin and overwrites the actual connect package See: https://docs.npmjs.com/cli/v8/configuring-npm/package-json#private
Each test now has a unique name, taken from the fixture name.
Enabled CI tests on GitHub Actions runner for Ethereum Plugin.
Enabled CI tests on GitLab for Ethereum plugin. Co-authored-by: mroz <[email protected]>
118e6b3
to
c69f0ba
Compare
Hello, these tests are already part of trezor-suite monorepo so we can close it here. Thanks for contribution! |
Adds CI tests for the Ethereum plugin (as discussed in #1033 (comment))
I've added the test to both GitHub Actions and GitLab CI. However, I've never used GitLab CI before, so I'm not 100% sure if this would work.