FHIR Chat · Da Vinci RA JIRA-Spec-Artifacts Warning · IG creation

Stream: IG creation

Topic: Da Vinci RA JIRA-Spec-Artifacts Warning


view this post on Zulip Rob Reynolds (Nov 23 2021 at 17:28):

The CI build for Risk Adjustment includes this Warning (https://build.fhir.org/ig/HL7/davinci-ra/qa.html):
"The jira specification file appears to be out of date with the versions, artifacts and pages currently defined in the IG. A proposed revised file to be reviewed and, if appropriate, submitted as a pull request against the XML folder in https://github.com/HL7/JIRA-Spec-Artifacts. To see the differences, perform a file compare on 'template/jira-current.xml' (a normalized view of what is in Github) and 'template/jira-new.xml' (reflects current IG content)"

The template/jira-current.xml and the template/jira-new.xml are identical on my local machine:
image.png

My local machine doesn't include the Warning:
image.png

Everything is committed on my local machine:
image.png

You can also see that I'm using the latest publisher in the image above ("My local machine doesn't include the Warning").

If I copy the contents of template/jira-new.xml into the JIRA-Spec-Artifacts/xml/FHIR-us-davinci-ra.xml there are no changes to be committed so there's nothing to update in the JIRA-Spec-Artifacts file.

The build of RA passed (but has the Warning):
image.png

Not sure how to fix the CI build.

view this post on Zulip Rob Reynolds (Nov 23 2021 at 18:09):

I may have a fix.

view this post on Zulip Rob Reynolds (Nov 23 2021 at 18:19):

@Lloyd McKenzie Please review my PR: https://github.com/HL7/JIRA-Spec-Artifacts/pull/359 when you get a chance.

I'm hoping that fixes it.

(and thanks for reviewing the other PRs today)

view this post on Zulip Lloyd McKenzie (Nov 23 2021 at 19:00):

Merged

view this post on Zulip Rob Reynolds (Nov 23 2021 at 19:08):

Thanks!

view this post on Zulip Rob Reynolds (Nov 23 2021 at 19:16):

That did fix it @Lloyd McKenzie . Thank you.

view this post on Zulip Rob Reynolds (Nov 23 2021 at 19:18):

For anyone who might have this issue in the future, it was the order of the entries in the package-list.json. The CI Build MUST come first.


Last updated: Apr 12 2022 at 19:14 UTC