Trigger nurax-dev deploy on commits to hyrax/main #4966
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Nurax is a testing environment for testing the state of Hyrax, hosted currently by Data Curation Experts (DCE). Currently, there are deploys to nurax-dev run on a cron job on the server once every 24 hours, and nurax-stable on each release.
When Hyrax development is going faster, going to the test environment once every 24 hours may be too slow, and deploying to nurax-dev on every commit to hyrax/main might help speed development on Hyrax.
In order to deploy to nurax-dev on commit to hyrax/main using CircleCI, the hook has to be on the hyrax/main git repository, necessitating a change to the Hyrax CircleCI config.
See also PR on Nurax - samvera-labs/nurax-pre2023#390
@samvera/hyrax-code-reviewers