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

Explore publishing Remote-Containers through CI/CD #5069

Closed
chrmarti opened this issue May 18, 2021 · 2 comments
Closed

Explore publishing Remote-Containers through CI/CD #5069

chrmarti opened this issue May 18, 2021 · 2 comments
Assignees
@chrmarti
Labels
containers Issue in vscode-remote containers plan-item A plan item
Milestone
June 2021

Comments

@chrmarti
Copy link
Contributor

No description provided.

@chrmarti chrmarti added containers Issue in vscode-remote containers plan-item A plan item labels May 18, 2021
@chrmarti chrmarti added this to the May 2021 milestone May 18, 2021
@chrmarti chrmarti self-assigned this May 18, 2021
@egamma egamma mentioned this issue May 25, 2021
Closed
9 tasks
@chrmarti chrmarti removed this from the May 2021 milestone Jun 1, 2021
@kieferrm kieferrm mentioned this issue Jun 13, 2021
Closed
5 tasks
@chrmarti
Copy link
Contributor Author

@JacksonKearl Thanks for putting the sample for the gated workflow together! While studying that I realized that I regularly test a VSIX and then have to add another commit to fix or polish something. Due to that I also only add a version tag after testing, when I'm ready to publish the VSIX.

I have now put together a workflow triggered on a version tag, that then downloads and publishes the VSIX built earlier. (Not tested on the actual extension yet.) That turned out reasonably simple, let me know if you have any feedback, thanks! https://github.com/microsoft/vscode-remote-containers/blob/main/.github/workflows/publish-remote-containers.yml

@chrmarti chrmarti added this to the June 2021 milestone Jun 25, 2021
@JacksonKearl
Copy link
Contributor

Neat trick, makes sense to me!

@github-actions github-actions bot locked and limited conversation to collaborators Aug 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@chrmarti chrmarti

Labels
containers Issue in vscode-remote containers plan-item A plan item
Projects
None yet
Milestone
June 2021
Development

No branches or pull requests
2 participants
@JacksonKearl @chrmarti