The Jenkins Registry had its first successful end-to-end run! ๐
That triggeredโfor the first timeโa Jenkins Deep Archive run, which failed ๐
But the fix should be easy. There are two problems:
The Jenkins Deep Archive is using the default API at https://pds.nasa.gov/api/search/1.0/ instead of the Jenkins Registry at http://localhost:8080
The Jenkins Deep Archive is testing with urn:nasa:pds:mer1_navcam_sci_calibrated::1.0 which isn't in the harvested test data; it should use urn:nasa:pds:insight_rad::2.1.
Checked for duplicates
No - I haven't checked
๐ Describe the bug
The Jenkins Registry had its first successful end-to-end run! ๐
That triggeredโfor the first timeโa Jenkins Deep Archive run, which failed ๐
But the fix should be easy. There are two problems:
https://pds.nasa.gov/api/search/1.0/
instead of the Jenkins Registry athttp://localhost:8080
urn:nasa:pds:mer1_navcam_sci_calibrated::1.0
which isn't in the harvested test data; it should useurn:nasa:pds:insight_rad::2.1
.๐ต๏ธ Expected behavior
I expected it to work
๐ To Reproduce
Wait 24 hours then check back on Jenkins
๐ฅ Environment Info
pds-expo.jpl.nasa.gov
๐ Version of Software Used
registry@main
deep-archive@main
๐ฉบ Test Data / Additional context
No response
๐ฆ Related requirements
๐ฆ #xyz
โ๏ธ Engineering Details
No response