Closed Onek8 closed 1 year ago
A minor observation, the workflows need to be run in order for the new demo to be built: https://github.com/armory3d/armory_examples_browser/actions
@tong Would it make sense to run the workflows for each release, or do the examples currently break too often for that? Also, even though the last workflow linked by @ RPaladin was run 16 days ago, the examples browser still says it was built on 2022-06-07.
@MoritzBrueckner that's because I linked the CI
workflow (I should have linked both perhaps). You're looking for the pages-built-development
workflow. There are also the individual tutorials
and template
workflows.
The examples in examples_browser are not built by the workflow but on my machine since blenders background mode wasn't working properly. Also the logic-nodes projects break regularly on changes, often just at the auto nodes-update check not the build itself, but it requires to save the updated blend file and rebuild it.
I've just updated the projects, built in background mode. Seems to work now, at least for html5.
And yes, the projects should be automatically built on every release, even better would be to trigger the related projects on every change in the ecosystem. But from what i read it would make sense to create a gh-app for such setups: https://docs.github.com/en/rest/checks?apiVersion=2022-11-28
For the people having trouble without documentation