Open Luxcium opened 5 years ago
I decided to try in my insiders (because it was easier to uninstall all other extensions) and I was unable to click on the app 3 dots icons to add the token «...» (clicking was doing nothing) so I did shift+cmd+P and I have been able to enter the token but got: "command 'theTravisClient.setToken' not found"
I installed a fresh and clean VSCode without extensions using a script I made: How to Install Luxcium's Vscode Portable (macOS) loading a project folder containing a .travis.yml file: Questrade-ts and I am still getting an error message in the lower right corner of my VSCODE:
The only extensions I have installed are in fact theses :
I am kind of a newbie and I tried to look at your well-writen code (it's interesting (and inspiring) to learn by the example)... the base base: 'com'
for enterprise AccountType
is indicating me that I should be using the enterprise version as my URL is the following: https://travis-ci.com/Luxcium/questrade-ts/builds/
...
Finally, I have logged on https://travis-ci.org/
instead of https://travis-ci.com/
and got a different token ... dRI_3ge-PRIVATE-RhJmXQ instead of UxRWBLB-PRIVATE-mdcUCQ but I don't have any usage of that Travis profile that I probably have created a long time ago since it was already created ...
I would prefer to log with the https://travis-ci.com/
if it would be loading all my repos activated on my profile (maybe its because it is using Comic Sans
it is a font that is presumably was the cause of the dot.com bubble burst at the beginning of the 2000's)
with the dot.org
token the only repo showing is the current project I am working on
by switching to a different project (Luxcium's Questrade-ts) I have it empty even after re-entering the dot.org
token (I don't know about the CSS-converter project I assume it is one of yours... if it is then why do I need a token in the first place probably to have write access instead of only reading access ?)
Hi, I have fixed issue, workspace.rootPath was deprecated so an extension was not activating, please check now by updating the-travis-client v0.1.4 if you still facing the same problem, uninstall and install again, after adding token refresh or restart extension if it was not working.
I have tested only for a community account, if you have a pro account please let me know is set enterprise token works or not.
I don't have either a pro/enterprise or community account ...
@Luxcium are you able set token now?
I got the same authentication error when login to my travis enterprise.
I login via travis
command line with these parameters. So I believe the api-endpoint
and github-token
are also needed.
travis login --api-endpoint https://travis.<my domain>.com/api \
--user <my user> --token <my travis token> \
--debug --debug-http -X travis.<my domain>.com \
--github-token <my github enterprize token>
Similar to #8 (I am not using insiders nor I am not on WSL/remote) I am sad to inform you that I kind of having the same issue. My Travis API authentication token UxRWBLB-PRIVATE-mdcUCQ is not working ... to be sure I have tried both Set Comunity and Set Enterprise token...