-
Notifications
You must be signed in to change notification settings - Fork 346
add vsx-registry to ci builds #330
add vsx-registry to ci builds #330
Conversation
Closes #325 Signed-off-by: Emanuel Fonseca <emdfonseca@gmail.com>
Signed-off-by: Emanuel Fonseca <emdfonseca@gmail.com>
- updated rust channel to nightly-2020-04-10 Signed-off-by: Emanuel Fonseca <emdfonseca@gmail.com>
I updated the rust channel to "nightly-2020-04-10" in order to build successfully. If this needs to move out of the PR just let me know. |
Signed-off-by: Emanuel Fonseca <emdfonseca@gmail.com>
Build tests frequently timeout on theia-rust. Build is running fine locally. Should we first merge #323 before approving this one? |
done |
…dd-vsx-registry Signed-off-by: Emanuel Fonseca <emdfonseca@gmail.com>
@@ -41,6 +41,7 @@ | |||
"@theia/userstorage": "next", | |||
"@theia/variable-resolver": "next", | |||
"@theia/workspace": "next", | |||
"@theia/vsx-registry": "next", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems low-risk to keep this change in this untested image, so I am ok to leave this as-is
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I built the rust image locally without any issues so the vsx-registry does not cause any issues. I guess the problem on travis was related to system performance which was causing the tests to take longer than 30s. I didn't investigate into this issue though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I built the rust image locally without any issues so the vsx-registry does not cause any issues. I guess the problem on travis was related to system performance which was causing the tests to take longer than 30s. I didn't investigate into this issue though.
I think I found the issue: we are still including a deprecated extension for this image: @theia/editorconfig
. Long story short, this causes the app never to start, which eventually fails CI.
I'm removing this extension in this WIP PR: #343
@emdfonseca Thanks for the updates. Looks good to me. The only one I am not sure is |
I'd accept this one cause it already adds value to the theia-apps repo without any issues. We can bring rust image back again later. |
I triggered the build again just because the status of the travis build was not updated in the PR. Is this normal or did I do something wrong? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @emdfonseca
I noticed that earlier too - I do not see that it's related to your PR. |
I should probably have asked for the commits to be squashed into one, but too late now :) |
@emdfonseca if you'd like to have a look at this follow-up PR . It builds-up from your update of the rust channel and fixes a couple of other things so that the image starts and |
What it does
Add @theia/vsx-registry dependency to latest and next package.json files of every app that is part of the CI pipeline (theia-cpp-docker theia-dart-docker theia-docker theia-full-docker theia-go-docker theia-java-docker theia-python-docker theia-rust-docker theia-swift-docker).
Closes #325
How to test
Trigger a build and let it finish. Everything builds without any issue.
Review checklist
Reminder for reviewers
Signed-off-by: Emanuel Fonseca emdfonseca@gmail.com