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:8080urn:nasa:pds:mer1_navcam_sci_calibrated::1.0which 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@maindeep-archive@main🩺 Test Data / Additional context
No response
🦄 Related requirements
🦄 #xyz
⚙️ Engineering Details
No response