Exclude certain targets from Github release publishing

[jwheare]

• Version: 5.11.3

• Target: windows, linux (deb+appimage), mac (dmg, zip, mas)

I'd like to be able to e.g. build for MAS on CI but not then publish to a Github release. Could you add a publish_filter build option to exclude certain targets?

I suppose a workaround for this right now would be to exclude MAS from the package.json default build options, and then run a separate build process with --target=mas --publish=never, but that would slow down the builds somewhat.

[develar]

MAS will be excluded from publishing by default.

[jwheare]

Thinking about this some more, what I actually want is for the MAS version to be published on CI so that I can download it for separate submission, but not published to Github.

Am I right in thinking this can be achieved by using Travis' built in support for uploading artifacts to S3? Does the electron-builder process support this parallel usage?

[develar]

@jwheare Travis uploading is not good because of travis-ci/travis-ci#2577 If you want to publish MAS to s3 — it can be implemented.

[jwheare]

@develar Looks like that issue is actually resolved in the comments (though not closed) and also it looks like you can customise the addons.artifacts.paths with custom commands.

I am not particularly attached to S3, and in fact it may be overcomplicating matters. I just want to be able to easily download it from somewhere. Maybe the Github release is after all the best place for it, since I am already downloading artifacts from there to perform final sanity testing. I just have to remember to remove it from the release before publishing it.

[develar]

Set build.mas.publish to null to disable publishing or set to bintray to publish to bintray ("to easily download it from somewhere."). Bintray — set package name to github repository name, bintray repository — standard generic.