-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CTS was failing -> now fixed -> URL update todo #3
Comments
Update Checking my k8s run, I had specified a parm to use 3.15 . However :
What is happening is that the 'init' container is using 3.15, whilst the 'platform' (the real test) used latest ! So this cts failure is likely specific to main/v4 |
Update - egeria 4.0 (main) requires xtdb connector 4.0. |
…nector Signed-off-by: Nigel Jones <[email protected]>
PR updates xtdb version to 'latest' |
The change I made to the cts did not work -- wrong URL, 'latest' isn't available seemingly from the snapshot repo. I'd misinterpreted the docs. I only get latest release. Raising a Q with sonatype. The other option is to add more logic to the scripting to determine the latest xtdb version (including development versions) and then set the connector download string to that specific version |
Raised odpi/egeria-connector-xtdb#466 Once fixed, need to return here to verify the correct URL to use, which is probably If so need to update etc/cts.yaml with this URL. But will leave until proven, once the xtdb artifact is correctly published |
^cc: @cmgrote |
XTDB is now published CTS is clean with main/main However this uses a hardcoded 4.0-SNAPSHOT reference for the connector, which needs to be updated when we branch Issue opened at Sonatype community to determine a better URL to use -> https://community.sonatype.com/t/retrieving-the-latest-snapshot/10311/2 |
XTDB connector is now at 4.0 (release) Will update the connector to use the 'latest' release connector
The charts would need modifying to more easily support selection of connector The easiest way of managing this would be to allow shell expansion of variables in the downloads, or perhaps just allowing a user script to be run. Note that the connector download currently fails with: |
See also #7 |
CTS test
Config:
Also the automated cts at https://github.com/odpi/egeria-test-cts/actions is currently failing (this uses egeria 'main')
See https://github.com/odpi/egeria-test-cts/actions
Specifically the latest test run shows identical results to above https://github.com/odpi/egeria-test-cts/actions/runs/4249004030
cc: @cmgrote @mandy-chessell
The text was updated successfully, but these errors were encountered: