add GH CI action to build vs2022 versions

teeks99 / boost-release-windows

Scripts for building the windows binary releases of each build.

1 stars 2 forks source link

add GH CI action to build vs2022 versions #4

Open chcg opened 1 year ago

chcg commented 1 year ago

added --type=release as not yet committed
could be extended to check also other VS versions on older docker images

teeks99 commented 1 year ago

The more I think about this, the less I think there is a benefit to adding this:

There isn't any feedback when a build fails, it is a manual check
A big part of what is happening is the packaging, which is really designed to do all of them at once
- Getting the inno setup builds would also take some additional work

I think instead it would be more interesting and useful to create a new repo, or maybe a pull request to boostorg/boost to add a VS2022 windows build there.

Long term, I'd like to re-architect this release process to make separate builds for each VS version, then pull them together. That would be much more amenable to CI, but would require a major reworking of the release script.

teeks99 commented 1 year ago

One question, what is driving your desire to have CI in this repo? I'd like to try to understand your use case.

chcg commented 1 year ago

No specific interest, just to see how the build is working and use the CI script as some kind of docu.

chcg commented 1 year ago

Available tool updates:

https://github.com/madler/zlib/releases/tag/v1.3
https://www.7-zip.org/ , 7-Zip 23.01 (2023-06-20)

chcg commented 11 months ago

@teeks99

Regarding:

There isn't any feedback when a build fails, it is a manual check

That is not correct, see e.g. my repo where the actions are running (https://github.com/chcg/boost-release-windows/actions) The build status is visible at the checkin e.g. for https://github.com/chcg/boost-release-windows/tree/gh_action and you get a GH notification if a build fails.

I think instead it would be more interesting and useful to create a new repo, or maybe a pull request to boostorg/boost to add a VS2022 windows build there.

I think windows builds aleady exist for boostorg/boost, see:

https://github.com/boostorg/boost/actions/runs/6799467446/job/18485847539 https://github.com/boostorg/boost/actions/runs/6799467446/job/18485846400

but just for VS2019 and VS2022.