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

Standardize build scripts for extensions #44

Closed
CharliePoole opened this issue Sep 9, 2021 · 3 comments · Fixed by #45
Closed

Standardize build scripts for extensions #44

CharliePoole opened this issue Sep 9, 2021 · 3 comments · Fixed by #45
Assignees
Labels
Milestone

Comments

@CharliePoole
Copy link
Contributor

CharliePoole commented Sep 9, 2021

The extension build scripts have evolved independently so they are somewhat uneven.Although they work well, it would be convenient for maintenance of the extensions if they were reasonably parallel.

The current "ideal" CI script would use the following:

  • Use of loaded cake files such that the same name is used for the same purpose in each project
  • Use of typed Cake context in most tasks (BuildParameters)
  • Use of GitVersion to determine build version
  • Inclusion of package tests using multiple console versions
  • Publication of dev packages to myget
  • Publication of production packages to nuget and chocolatey
  • Creation of draft and final releases on GitHub
  • Ability to run publication and release steps independently in case a re-run is needed.

The vs project loader scripts will be reviewed to see which of the above items need to be added.

@CharliePoole CharliePoole added this to the 3.9 milestone Sep 9, 2021
@CharliePoole CharliePoole self-assigned this Sep 9, 2021
@CharliePoole
Copy link
Contributor Author

CharliePoole commented Sep 10, 2021

Status of the VS Project Loader package...

  • Separate cake files
  • Typed cake context
  • Use GitVersion
  • Package Tests
  • Publish dev packages
  • Publish production packages
  • Create GitHub draft and final releases
  • Independent rerun of publication and release steps

@CharliePoole
Copy link
Contributor Author

Last two steps will be done as separate issues

@CharliePoole
Copy link
Contributor Author

🎉 This issue has been resolved in version 3.9.0 🎉

The release is available on:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant