Publish Windows artefacts #891
Merged
Conversation
This file contains 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
|
That's interesting, my last experience was that it was failing because of the secrets. And their fix was to not hide the secrets (i.e. publish the credentials required for releasing the artifact). Their thread is here. |
|
BTW note that the issue (and contact with Travis CI support team) I had was in May 2019, and your link above is "a year old". So I'm really not convinced that this is fixed 😕. |
This is required because MSVC complained: warning C4200: nonstandard extension used: zero-sized array in struct/union
julianoes
force-pushed
the
publish-windows
branch
from
7a8cd43
to
b6a4583
Compare
This seems to be the only way to make it work.
Hopefully this will help with build speed.
julianoes
force-pushed
the
publish-windows
branch
from
148728f
to
6d4327e
Compare
|
Merging because the Jenkins CI error is not related. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Let's give this a test.
Presumably this should be possible now:
https://changelog.travis-ci.com/windows-jobs-can-now-deploy-76366