TRAVIS CI and GitHub

Travis Splits Release
I have a cross plattform build of an electron app. The build runs fine, but I can’t get it to make a combined release. Windows will always be in a separate Github-Release. This also means a clash of tags if I generate a tag. That’s the reason it is an untagged build. Any examples for this?
FG Airports



so that your OS jobs will create build artifacts and the deploy stage job collects these artifacts to create a release.
1 Like