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.

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

Build Pipeline for Releases #60

Closed
denelon opened this issue Sep 10, 2021 · 1 comment
Closed

Build Pipeline for Releases #60

denelon opened this issue Sep 10, 2021 · 1 comment
Assignees
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Milestone

Comments

@denelon
Copy link
Contributor

denelon commented Sep 10, 2021

Build Pipeline for Releases

As a part of #34 I mentioned having the release artifacts published so the deploy process can be made even more simple. It has a dependency on the .zip file produced when building the project.

Proposed technical implementation details (optional)

Create a build pipeline and publish a release 😊.

@denelon denelon added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Sep 10, 2021
@RDMacLachlan
Copy link
Member

The script assumes that the location of the *.zip is in the "Src/WinGet.RestSource.Infrastructure" and that the file name is "CompiledFunctions.zip".

These values are set at the parameter inputs, and can be overwritten by the user. However I'd like to make this more friendly to just generic usage and update the expected paths and file names.

@denelon denelon added this to the v1.2-REST milestone Oct 1, 2021
@denelon denelon added this to To Do in REST-Current Oct 1, 2021
@denelon denelon closed this as completed Nov 3, 2021
@denelon denelon moved this from To Do to Done in REST-Current Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Projects
Development

No branches or pull requests

3 participants