It would be nice if one can publish VSCode Extensions directly from Travis.
The process is pretty similar to npm deployment: https://code.visualstudio.com/docs/extensions/publish-extension
Not sure if it helps, but did you look into this documentation?
I'm aware that it's possible to configure it the right way. However, in this FR, it is proposed to offer a similar experience like the npm publishing:
https://docs.travis-ci.com/user/deployment/npm/
As the deployment process is pretty similar to NPM packages (VSC extensions are like NPM packages), we could provide it directly as configuration.
If this is something the Travis team would like to have, I'd see if I can file a PR.
It would be nice. I am currently struggling getting my repo deployed in a proper way.
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues
I think this issue is still valid.
I'd like to take on this issue by adding a modified copy of the npm Provider. Is there anything to be aware of? How do I debug these deployment providers?
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues
It's still valid, I think.
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues
Still valid I guess
if it is, i guess it needs to be reopened :)
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues
oh no, don't close it
@mehrad77 would you like to take a shot at this? not using Visual Studio Code over here ...
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues