Is your feature request related to a problem? Please describe.
After introducing a build pipeline succefully now,
the next step should be an automated release/marketplace publish workflow.
Describe the solution you'd like
A new Release should be triggered from the BUild Pipeline manually or via GitHub Release here.
A new tag should be created and the coresponding build should fire a publish trigger which then would publish the newest release to the vscode marketplace via our pipeline environment.
Describe alternatives you've considered
I have considered doing it the manual way as i must currently,
but i don't think that we should keep it this way.
Additional context
The azure pipeline extension itself provides a nice structure for this and can be handled completely through devops.
I have checked the config files and it seems to be very straight forward.
Confectrician
commented
4 years ago
Is your feature request related to a problem? Please describe. After introducing a build pipeline succefully now, the next step should be an automated release/marketplace publish workflow.
Describe the solution you'd like A new Release should be triggered from the BUild Pipeline manually or via GitHub Release here. A new tag should be created and the coresponding build should fire a publish trigger which then would publish the newest release to the vscode marketplace via our pipeline environment.
Describe alternatives you've considered I have considered doing it the manual way as i must currently, but i don't think that we should keep it this way.
Additional context The azure pipeline extension itself provides a nice structure for this and can be handled completely through devops. I have checked the config files and it seems to be very straight forward.
Reference: https://github.com/microsoft/azure-pipelines-vscode