Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Che Plugin Registry VSX Daily Check #17014

Closed
l0rd opened this issue May 26, 2020 · 5 comments
Closed

Che Plugin Registry VSX Daily Check #17014

l0rd opened this issue May 26, 2020 · 5 comments
Labels
area/plugin-registry kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Milestone
7.x (Later, Futur...

Comments

@l0rd
Copy link
Contributor

l0rd commented May 26, 2020 •
edited
Loading

Is your enhancement related to a problem? Please describe.

We do not have any report of how many VS Code Extensions are supported by Che, their list and how fresh they are (che registry version vs msft marketplace version). These information are useful and would encourage contribution.

Describe the solution you'd like

Generate a VSX daily report (on gh pages for example) with the list of extensions that are supported (included in our registry) and for each one provide:

ITERATION N.1

  • id
  • github repo
  • version in che plugin registry
  • version in vscode marketplace

ITERATION N.2

  • version in gh master branch package.json
  • sidecar container image

ITERATION N.3

  • % of API call supported in Che Theia
  • smoke test (enable / disable) result (pass/fail)

Included in epic #15819
@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. area/plugin-registry labels May 26, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label May 26, 2020
@l0rd l0rd added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels May 26, 2020
@gorkem
Copy link
Contributor

gorkem commented May 26, 2020

This is not so much about the report but automation of the intake of the extensions. Basically we need to automate the intake to the level that we keep a list of github repositories and branches. An automated job goes through this list at least once a day. Builds the vsx, runs automated checks in Che context and if all checks pass, issues an update to plugin registry.

@l0rd l0rd mentioned this issue May 27, 2020
Closed
18 tasks
@l0rd
Copy link
Contributor Author

l0rd commented May 27, 2020

We already have an epic about plugin update automation and we have a script too that 1) checks if there is a new version of a vsx 2) files a gh issue if the plugin is not updated.

Hence I have updated the original epic with the following subtasks to improve current script and make it easier to contribute a new vs code extension to our registry:

  1. Run the script daily and provide a report --> this issue
  2. Automatically submit PR (instead of opening issue)
  3. PR check to validate new/updated vs code extensions Add plugin-registry PR check to validate new/updated vsx #17027
  4. In plugin-checker fall back to repo/branch package.json when there are no GH releases
  5. Automatically generate meta.yaml given a vsx repo+branch+dockerfile Automatically generate meta.yaml given a vsx repo+branch+dockerfile #17029
  6. Build and publish a vsx when there is no corresponding GH release

@ericwill ericwill mentioned this issue Jun 15, 2020
Merged
@ericwill ericwill mentioned this issue Jun 24, 2020
Closed
31 tasks
ericwill added a commit to eclipse-che/che-plugin-registry that referenced this issue Jul 3, 2020
@ericwill
Contribute a vscode-extensions.json file (#499)
c640416 
Contribute a vscode-extensions.json file

This file lists all extensions in the che-plugin-registry. By extension,
I mean those Che plugins that use VS Code Extensions.

The fields are basic (for now) but are as follows:
* revision: the tag or SHA1 ID of the upstream repository, capturing a certain version of the extension
* directory (optional): the sub-directory where the extension is located (some repositories have multiple extensions in multiple folders)
* repository: the location of the upstream repository

This file is needed for eclipse-che/che#17014, which is part of a greater epic eclipse-che/che#15819.

Signed-off-by: Eric Williams <ericwill@redhat.com>
@ericwill ericwill mentioned this issue Jul 15, 2020
Closed
38 tasks
@ericwill ericwill added this to the 7.x milestone Jul 15, 2020
ericwill added a commit to ericwill/che-theia that referenced this issue Jul 17, 2020
@ericwill
Generate automatic che-theia built-in report
4f2feee 
Generate an automatic report about the update status of che-theia built-in extensions

See eclipse-che/che#17328
See eclipse-che/che#17014

Signed-off-by: Eric Williams <ericwill@redhat.com>
ericwill added a commit to ericwill/che-theia that referenced this issue Jul 17, 2020
@ericwill
Generate automatic che-theia built-in report
fae7cc9 
Generate an automatic report about the update status of che-theia built-in extensions

See eclipse-che/che#17328
See eclipse-che/che#17014

Signed-off-by: Eric Williams <ericwill@redhat.com>
ericwill added a commit to ericwill/che-theia that referenced this issue Jul 17, 2020
@ericwill
Generate automatic che-theia built-in report
41012ce 
Generate an automatic report about the update status of che-theia built-in extensions

See eclipse-che/che#17328
See eclipse-che/che#17014

Signed-off-by: Eric Williams <ericwill@redhat.com>
ericwill added a commit to ericwill/che-theia that referenced this issue Jul 17, 2020
@ericwill
Generate automatic che-theia built-in report
48bdb58 
Generate an automatic report about the update status of che-theia built-in extensions

See eclipse-che/che#17328
See eclipse-che/che#17014

Signed-off-by: Eric Williams <ericwill@redhat.com>
@ericwill ericwill mentioned this issue Jul 17, 2020
Merged
@ericwill ericwill mentioned this issue Jul 30, 2020
Closed
29 tasks
@ericwill
Copy link
Contributor

Apart from % API calls and smoke test coverage, the report iterations are done. Plugin registry and che-theia reports are generated nightly. We are working on testing API (#15797) to start providing PR checks and smoke tests.

@che-bot
Copy link
Contributor

che-bot commented Feb 24, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 24, 2021
@ericwill
Copy link
Contributor

I'm going to close this. We can handle the API display in a separate issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/plugin-registry kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
7.x (Later, Future, Never)
Development

No branches or pull requests
4 participants
@gorkem @l0rd @ericwill @che-bot