-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrapper script enhancements #4655
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've found one scenario which produces an error which should probably be replaced by a warning.
Otherwise seems reasonable to read, and test manually.
… flow version (e.g. cylc-8.0.0-1) Ensure workflows always run under fixed environments rather than symlinked versions which could change Provide legacy support for rose edit & cylc review (partially address cylc#4555)
# Releases should be installed into environments in the ROOT location, named | ||
# cylc-$CYLC_VERSION. We recommend using the cylc-flow version plus an additional |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A small change would be handy at NIWA, to avoid having to edit some code down in the guts of the wrapper:
CYLC_ENV_NAME_PREFIX="cylc-" # editable prefix
# ...
${CYLC_ENV_NAME_PREFIX}${CYLC_VERSION}
Our HPC admins use this convention: .../share/cylc/8.0rc1
etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(However, not a biggie)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this idea. However, I think it also means making the name of the default version configurable (also like the idea of this). Do you mind if we do this in a separate PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #4555 (comment)
Is there any reason why this has stopped? |
Probably my fault - I had meant to approve, aside from the change suggestion above that I agreed (via 👍 ) to punt to another issue. |
Support the use of environments with names that do not match the cylc flow version (e.g. cylc-8.0.0-1)
Ensure workflows always run under fixed environments rather than symlinked versions which could change
Provide legacy support for rose edit & cylc review (partially address #4555)