Fix Connext license use in the CI tests - #887
Conversation
…s in AMD and ARM too
|
Tick the box to add this pull request to the merge queue (same as
|
|
@ahcorde can you launch the following validations?
|
|
Hmm sadly I see the same issues still as reported ros2/rmw_connextdds#246 so seems not to have solved it I'm afraid. |
|
@knmcguire thank you for launching these validations! These are exactly the ones I need to test this. That is strange. It seems either the environment variable |
|
Perhaps we have to also set the NNDSHOME variable?
And also this seems related? Here is the part that might be interesting from the logs but you can also check it from the ci logs if you are able to get those? |
|
Indeed, the license has already expired. It seems the non-debian build is fine because it is using Connext Pro, which does not need a license for the core libraries. However, the Debian packages do need a license, and the one provided inside them does not support security. I will check internally this issue and will come back with a solution. Thank you @knmcguire! |
Description
Currently, tests related to security require a special license not publicly available. This license is only used when running the CI installing Connext through RTI packages and only in x64 architectures.
This change allows the CI to use that same license when testing with Debian pacakges too in both x64 and aarch64.
Fixes ros2/rmw_connextdds#246
Is this user-facing behavior change?
Security tests using the Connext RMW can now be run using Connext Debian packages in both x64 and aarch64.
Did you use Generative AI?
No
Additional Information