Closed jeremy-kubota closed 11 months ago
1. Which hashes/tags of `ROSConDemo`, `o3de`, and `o3de-extras` are compatible?
I had success with:
o3de(debian release "o3de_2310_0.deb" or main branch) o3de-extras(main branch with 3b212e3 reverted) ROSConDemo(development branch)
I think https://github.com/o3de/o3de-extras/commit/3b212e3dd96e05bd44ff8ca690966c46ebfae0ae should not have gone into o3de-extras(main).
Sorry for the problem and confusion with the branches. We are waiting for the official release of 2310.1 before we clean this mess up (it should happen this Thursday). There were multiple breaking changes lately in o3de and it is difficult to keep it updated in all Gems/Demos due to our limited resources.
I recently tested the following configuration and it worked correctly:
o3de: point-release/23101
dc6e2f7a23 (I believe the head of this branch should work as well)
o3de-extras: main
f21f4812 (2310.1 was already released and it is available in main
)
ROSConDemo: development
@jeremy-kubota
I tested the most recent code of #272 a8f7ced after the 2310.1
release and I managed to build all three docker images: Dockerfile
, Dockerfile.NavStack
, and Dockerfile.Simulation
. I will close the issue now. Please reopen this issue if you find any problems.
I think the real problem is that it may work one day and not the other because the default args are set to be branch heads instead of a fixed hash or tagged version. I still think there is a problem here if either the o3de
or o3de
main branches are updated in a way that's not compatible with the ROSConDemo. You need specific versions rather than branch HEADs for this to be a permanent fix.
Thank you for the reply. I agree with your comment and with your solution. We use tags in the other demo
There is no agreement for this demo though. We will switch all branches to main
(we will merge development
->main
after #272 is completed) and keep updating the code at every o3de release.
While building the latest on
development
using the docker instructions , I get the following error:I suspect that because the docker build is using branches and the versions are not locked, that an update to these branches has resulted in a build incompatibility.
ROSConDemo
,o3de
, ando3de-extras
are compatible?Dockerfile
instead of branches to avoid loss of compatibility?