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

Release Building #81

Open
8 of 12 tasks
gbakeman opened this issue Mar 1, 2023 · 1 comment
Open
8 of 12 tasks

Release Building #81

gbakeman opened this issue Mar 1, 2023 · 1 comment
Assignees
@gbakeman
Labels
🤖CI/CD Issues and PRs that concern continuous integration and deployment. enhancement New feature or request
Milestone
2.3 Stable Release

Comments

@gbakeman
Copy link
Contributor

gbakeman commented Mar 1, 2023 •
edited

The final step in having full CI/CD is to automate deploying (pre) releases of WinNUT on GitHub. The general structure of the workflow should look like:

  • Setup MSBuild
  • Checkout code
  • Restore packages
  • Install Multilingual App Toolkit extension
  • Build solution in Release configuration
  • Get version from Assembly
  • Finalize with automated release action on GitHub

Tasks

  • Complete multilingual automation Automate Multilingual App Toolkit Building #58
    • Not blocking release building
  • Full debug building
    • Artifact archive name follows format winnut-client-debug-[shortSHA]
    • Verify generated assemblies have correct version following msbuild format
  • Complete new updater and prepare client for production transition to ClickOnce - Depends on Modify WinNUT Update Routines (ClickOnce deployments) #97
  • Automated releases - Depends on New Setup/Installer Build System #85
    • Tags in the format v.major.minor.build trigger a new build in the Release configuration
    • Confirm languages integrated and installer package compiled
    • Upload archive of the build output, named WinNUT-Client-v[version]-noinstall.
    • Upload ClickOnce installer published artifacts to their destination
    • Automatically generate a Release post with a generic message, to be manually added to at a later time.
  • Update documentation
@gbakeman gbakeman added enhancement New feature or request 🤖CI/CD Issues and PRs that concern continuous integration and deployment. labels Mar 1, 2023
@gbakeman gbakeman added this to the 2.2 Stable Release milestone Mar 1, 2023
@gbakeman gbakeman self-assigned this Mar 1, 2023
@gbakeman gbakeman mentioned this issue Apr 4, 2023
Open
4 tasks
@gbakeman
Copy link
Contributor Author

gbakeman commented Apr 8, 2023

Made a breakthrough with the workflow design 61862cf; we now use a sub action specifically for building, that allows us to keep the same environment throughout a workflow without having to duplicate steps for both Debug and Release builds.

@gbakeman gbakeman mentioned this issue Apr 13, 2023
Open
8 tasks
@gbakeman gbakeman mentioned this issue Aug 3, 2023
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gbakeman gbakeman

Labels
🤖CI/CD Issues and PRs that concern continuous integration and deployment. enhancement New feature or request
Projects
None yet
Milestone
2.3 Stable Release
Development

When branches are created from issues, their pull requests are automatically linked.

81-release-building nutdotnet/WinNUT-Client
1 participant
@gbakeman