openmw.org

On GL appveyor is triggered per merge into master

A few posts ago (although not in this sudden flurry of posts today) you said this. It might be better to use this automatic trigger rather than a nightly cron job as it makes bisecting issues either if there's one build per PR.

I'd much rather try to get things building and hosting on AppVeyor. Trigger coming either from GL or from GH on merge into master. Either way, I think AV is the way to go.

AnyOldName3 wrote: ↑16 Oct 2018, 21:35 I'm pretty sure Travis does artefacts if you tell it to. I think that's how Dolphin Emulator does its Ubuntu and OSX builds.

https://docs.travis-ci.com/user/uploading-artifacts/

psi29a wrote: ↑16 Oct 2018, 22:56 I'd much rather try to get things building and hosting on AppVeyor. Trigger coming either from GL or from GH on merge into master. Either way, I think AV is the way to go.

Speaking of GL, didn't it have automated builds for Linux @ https://gitlab.com/OpenMW/openmw/pipelines?

Weirdly enough it stopped producing build artifacts.

Edit:
It seems to have some build artifacts from recent PRs/MRs, but strangely enough the gitlab pipeline has been running 2 jobs for over 3 months.

Edit 2:
So it seems those 2 jobs are stuck on AppVeyor building, even though appveyor already built successfully?

Also, the pipeline only decides to start building and saving artifacts for commits coming from Gitlab, and not Github, even though a few months ago it was building artifacts from commits that originated from GitHub.

GL doesn't act like GH, I've been tracking two issues (feature requests)... that is running pipelines on merge requests.

https://gitlab.com/gitlab-org/gitlab-ce/issues/23902
https://gitlab.com/gitlab-org/gitlab-ee/issues/7380

GL pipeline hook to AV after a MR has been merged into master is fine.

Many ways to skin this particular cat:
travis-ci -> upload artifacts to our FTP
appveyor -> host our artifacts for us

Travis-CI has MacOS and Ubuntu 14.04 support only ATM (16.04 and higher only in restricted docker containers, can't use them)
AppVeyor has MSVC and Ubuntu 16.04 and 18.04 support with MacOS coming soon.

Either of which can be triggered by a cron job or after each merge to master.

PSA: macOS nightlies are disabled until I rewrite upload script to use SCP instead of FTP.

So this is probably a stupid question, but where can I find these artifacts? If we're not doing these nightlies anymore, I'd like to know where I can download them.

"Artifacts" is something AppVeyor produces... at the moment we only have windows. Just look at any PR on github, and follow the green check mark to AppVeyor and there will be a download button or something labeled artifacts.

For example, the recast branch:
Click on 'details' of AppVeyor to take you here:
https://ci.appveyor.com/project/psi29a/ ... s/19861310

drill down to msvc2017 (or msvc2015 if you want) then you click on artifacts and land here:

https://ci.appveyor.com/project/psi29a/ ... /artifacts

It is my intention to eventually have these being produced for the major 3 and maybe upload them to our downloads.openmw.org