I am able to generate the Ontology SDK locally through the TypeScript CLI. So unsure why the cloud build fails.
Any tips on what to try next?
3 Likes
mpeteu, any resolution to this issue? I am experiencing the same problem
For no apparent reason, I was able to build the new SDK a few iterations after this post.
One thing I’m fairly certain about is that build failures have nothing to do with npm version chosen.
I don’t have much to offer here, other than make sure to remove any extraneous Objects or Functions and re-try with a “leaner” build.
For example, make sure to clean out unused or unknown object types - then click “Review Changes” at the bottom, and confirm:
Most importantly, follow the live Logs as your new SDK is being built, because after the build is complete, you don’t have access to them:
The logs do throw helpful, actionable errors, at least in my case.
The inability to view build logs after the fact seems like a Foundry bug.
Thanks, mpeteu for the info. I was able to build on Foundry Developer Console this morning without making any changes to what I previously had in the project 
Just noticed that any edits made to an Object’s ontology (eg: adding any new Links between Objects) don’t automatically show up unless you delete then re-add that Object.
Doesn’t break the build, it might affect you in other ways - eg: you won’t be able to query links to that object, and any exposed custom Queries (via @Query decorator) could fail as a result.
Oh wow. Ok good to know. Thank for that info!