camel-tooling / vscode-wsdl2rest

Deprecated - VS Code extension that provides access to the jboss-fuse/wsdl2rest utility to generate a Camel Rest DSL configuration
Apache License 2.0
1 stars 7 forks source link

Enable travis CI #12

Closed bfitzpat closed 5 years ago

bfitzpat commented 5 years ago

Looks like I don't have permissions to enable travis on this repo -https://travis-ci.org/camel-tooling/vscode-wsdl2rest

@apupier or @lhein ?

lhein commented 5 years ago

yeah, I lack rights both on github and also on travis.

apupier commented 5 years ago

I added you admin rights. Strange that Brian didn't have it as he created the repository. I need to change a configuration in the Organization for future repo creation (when i will find why...)

bfitzpat commented 5 years ago

It may have been something in the way I moved the repo from my personal one to camel-tools. I'm not sure. I didn't create it from scratch. I used "Transfer Ownership" in the repo settings

image

bfitzpat commented 5 years ago

Just updated the deploy task here - https://github.com/camel-tooling/vscode-wsdl2rest/pull/20

bfitzpat commented 5 years ago

Not sure what this means, but suspect that maybe the token isn't around? Ideas? @lhein ? @apupier ?

Script failed with status 127
failed to deploy
apupier commented 5 years ago

Not sure what this means, but suspect that maybe the token isn't around?

Not sure about the exact meaning but as the VS Code token is nto available, it seems to be an high probability that it is the case. The token needs to be passed as TRAVIS environment variables.

from https://travis-ci.org/camel-tooling/vscode-wsdl2rest More Options -> Settings image

the environment variable needs to be called VSCODE_TOKEN https://github.com/camel-tooling/vscode-wsdl2rest/blob/master/.travis.yml#L27

The token can be retrieved as explained here https://code.visualstudio.com/api/working-with-extensions/publishing-extension#get-a-personal-access-token (it is the same than what you did for vscode-yeoman)

bfitzpat commented 5 years ago

Ok. Token generated. Token stashed in Travis. Still getting error 127 - https://travis-ci.org/camel-tooling/vscode-wsdl2rest/builds/498262396

apupier commented 5 years ago

just noticed that the vsix is not built. the step "vsce package" is missing https://github.com/camel-tooling/camel-lsp-client-vscode/blob/8b8b1f912bd07d3e4987c60b6df0958015e930ce/.travis.yml#L15 it requires to install vsce globally https://github.com/camel-tooling/camel-lsp-client-vscode/blob/8b8b1f912bd07d3e4987c60b6df0958015e930ce/.travis.yml#L14

bfitzpat commented 5 years ago

Ok, so the token is there and I'm getting

Publishing camel-tooling.vscode-wsdl2rest@0.0.3...
 ERROR  Failed Request: Unauthorized(401) - https://marketplace.visualstudio.com/_apis/gallery
 ERROR  Be sure to use a Personal Access Token which has access to **all accessible accounts**.
See https://code.visualstudio.com/api/working-with-extensions/publishing-extension#publishing-extensions for more information.
Script failed with status 1

https://travis-ci.org/camel-tooling/vscode-wsdl2rest/builds/498361725

bfitzpat commented 5 years ago

looks like I also need to get a sonar key for the project...

ERROR: Error during SonarQube Scanner execution
ERROR: You must define the following mandatory properties for 'Unknown': sonar.projectKey

https://travis-ci.org/camel-tooling/vscode-wsdl2rest/builds/498367743

apupier commented 5 years ago

looks like I also need to get a sonar key for the project...

yes, it is due to this configuration: https://github.com/camel-tooling/vscode-wsdl2rest/blob/4cda22a6d6a9bd0f433798f3c05a86a9ef8e8ce4/.travis.yml#L36-L40

and that there is configuration for Sonar project either through Travis yml file or via sonar-project.properties https://github.com/camel-tooling/camel-lsp-client-vscode/blob/master/sonar-project.properties

created https://github.com/camel-tooling/vscode-wsdl2rest/issues/26

apupier commented 5 years ago

Ok, so the token is there and I'm getting

Publishing camel-tooling.vscode-wsdl2rest@0.0.3...
 ERROR  Failed Request: Unauthorized(401) - https://marketplace.visualstudio.com/_apis/gallery
 ERROR  Be sure to use a Personal Access Token which has access to **all accessible accounts**.
See https://code.visualstudio.com/api/working-with-extensions/publishing-extension#publishing-extensions for more information.
Script failed with status 1

I think it is because the token doesn't have all the correct rights. It seems to mention that the organization selected was not the "All accessible organizations: https://code.visualstudio.com/assets/api/working-with-extensions/publishing-extension/token3.png

apupier commented 5 years ago

I created a new Token and updated it in travis settings. Then I re-triggered a build of the 0.0.3 tag build https://travis-ci.org/camel-tooling/vscode-wsdl2rest/builds/498361725 The extension has been published successfully: https://marketplace.visualstudio.com/items?itemName=camel-tooling.vscode-wsdl2rest

bfitzpat commented 5 years ago

@apupier Can we close this one as done?

apupier commented 5 years ago

@apupier Can we close this one as done?

I think yes :-)