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

Package and publish on release #2

Closed
thekaveman opened this issue Oct 13, 2021 · 0 comments · Fixed by #8
Closed

Package and publish on release #2

thekaveman opened this issue Oct 13, 2021 · 0 comments · Fixed by #8
Assignees
@thekaveman
Milestone
November 2021

Comments

@thekaveman
Copy link
Member

thekaveman commented Oct 13, 2021 •
edited
Loading

dotnet publish can be used to generate assets to deploy to the hosting system (e.g. a binary or executable file).

We have an example of this defined in the devcontainer publish task and in the sample Dockerfile.deploy

We should have a workflow that runs on (tag, release?) and:

  1. Runs a process similar to the Dockerfile.deploy to generate an out/ directory with executable + extras?
  2. Zip that out/ directory
  3. Upload the zip as a Release Asset
  4. For N different deploy targets? Windows, Linux??

See https://github.com/softprops/action-gh-release for a possible solution that can do some/all of the above
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thekaveman thekaveman

Labels
None yet
Projects
None yet
Milestone
November 2021
Development

Successfully merging a pull request may close this issue.

Workflow: package and release on tag cal-itp/hashfields
1 participant
@thekaveman