Skip to content

Hyrax version refactor 2#286

Open
ndp-opendap wants to merge 8 commits intomasterfrom
hyrax-version-refactor-2
Open

Hyrax version refactor 2#286
ndp-opendap wants to merge 8 commits intomasterfrom
hyrax-version-refactor-2

Conversation

@ndp-opendap
Copy link
Contributor

@ndp-opendap ndp-opendap commented Mar 11, 2026

This PR changes the OLFS so that it no longer injects Hyrax version information into the code base. The result is that the Hyrax version is set to Not.A.Release and the hyrax-docker CICD will determine the version and build numbers and inject them into the server when it runs.

This should be merged AFTER OPENDAP/hyrax-docker#126 is merged.

@ndp-opendap ndp-opendap requested review from hannahilea and jgallagher59701 and removed request for jgallagher59701 March 12, 2026 00:58
Copy link
Collaborator

@hannahilea hannahilea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comments:

  • there's one change that has to happen before this PR merges or it will fail on master when running trigger-hyrax-docker.sh
  • consider adding the tagging behavior to hyrax-docker before merging this PR

Approving b/c I think those are trivial changes and not worth blocking over!

";
git status;

export hyrax_tag="hyrax-${HYRAX_BUILD_VERSION}"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hrm, interesting. Is hyrax-docker now responsible for tagging itself upon building? I don't remember that being updated in the previous hyrax-docker PR (although maybe it was) so it's probably worth making that change before we merge this PR, or we'll end up with a few untagged builds (in hyrax-docker)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that I have made and merged the changes to hyrax-docker that handle this tagging I'll drop it from the build recipes created by the OLFS

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the tagging in hyrax-docker was specifically the docker hub tagging. In this PR, we're removing the github tagging. So I think we still need to add github tagging at the hyrax-docker level (i.e., copy the lines removed here and move them over there)?

Copy link
Contributor Author

@ndp-opendap ndp-opendap Mar 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that's right we basically want to tag the hyrax-docker project with the current Hyrax version tag.

hmmmm - ticket time.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here is the issue: OPENDAP/hyrax-docker#136
Here is the PR: OPENDAP/hyrax-docker#137

@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants