Appveyor or Github CI #59
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chcg
force-pushed
the
appveyor
branch
2 times, most recently
from
fc2981f to
0b15311
Compare
chcg
force-pushed
the
appveyor
branch
2 times, most recently
from
cd8e2c5 to
2e42f4d
Compare
chcg
force-pushed
the
appveyor
branch
2 times, most recently
from
4c51ed5 to
3b2d7cf
Compare
chcg
force-pushed
the
appveyor
branch
5 times, most recently
from
c184ea3 to
869e032
Compare
chcg
commented
Apr 15, 2022
builder/builder/Nuspec.cs
Outdated
| p.WaitForExit(); | ||
| if (p.ExitCode != 0) { | ||
| Environment.Exit(p.ExitCode); | ||
| //Environment.Exit(p.ExitCode); |
Author
There was a problem hiding this comment.
Just commented out to check CI runs could create all packages as github action and appveyor fail on first upload due to missing api key
chcg
force-pushed
the
appveyor
branch
2 times, most recently
from
ea6f126 to
30ac949
Compare
chcg
force-pushed
the
appveyor
branch
3 times, most recently
from
bddd1a7 to
677a620
Compare
chcg
force-pushed
the
appveyor
branch
2 times, most recently
from
32f37a0 to
6b35646
Compare
chcg
force-pushed
the
appveyor
branch
3 times, most recently
from
831b782 to
79994c7
Compare
chcg
force-pushed
the
appveyor
branch
6 times, most recently
from
2382728 to
3c9fab9
Compare
chcg
commented
Dec 14, 2023
chcg
force-pushed
the
appveyor
branch
2 times, most recently
from
7401937 to
ccf7cb7
Compare
chcg
force-pushed
the
appveyor
branch
2 times, most recently
from
6c60188 to
faf8b93
Compare
chcg
force-pushed
the
appveyor
branch
2 times, most recently
from
a0d0537 to
d7aa2d4
Compare
Author
|
@sergey-shandar Boost 1.87.0 is available and also the corresponding win libs. CI run seems to be ok with it https://github.com/chcg/getboost/actions/runs/12302927946 |
chcg
force-pushed
the
appveyor
branch
2 times, most recently
from
4fa22b9 to
529ebaa
Compare
chcg
force-pushed
the
appveyor
branch
4 times, most recently
from
5e3f900 to
711c7bc
Compare
- update NuGet.CommandLine -> NuGet.CommandLine.6.13.2 - add initial appveyor.yml CI config - prepare for boost 1.88.0 - disabled upload of nuget to avoid upload quota exceeded with appveyor - added dummy ApiKey.cs - avoid nuget warnings about: WARNING: NU5125: The 'licenseUrl' element will be deprecated. Consider using the 'license' element instead. WARNING: NU5128: Some target frameworks declared in the dependencies group of the nuspec and the lib/ref folder do not have exact matches in the other location. Consult the list of actions below: - Add a dependency group for native0.0 to the nuspec
Author
|
@sergey-shandar 1.88.0 is available and seem to be ok. |
Author
|
@sergey-shandar 1.89.0 is available |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@sergey-shandar Is that something you are interested in? Most likely the gh actions or the appveyor config could be extended to upload the resulting nuget packages to github and/or nuget package repo.
Should the readme be updated that the versions boost binaries used are not build on your own but taken from boost (e.g. https://archives.boost.io/release/1.88.0/binaries/) and build via https://github.com/teeks99/boost-release-windows.