Skip to content
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

Upgrade alert #3400

Closed
matthewrmshin opened this issue Oct 4, 2019 · 2 comments
Closed

Upgrade alert #3400

matthewrmshin opened this issue Oct 4, 2019 · 2 comments

Comments

@matthewrmshin
Copy link
Contributor

matthewrmshin commented Oct 4, 2019

Describe exactly what you would like to see in an upcoming release

There are 2 parts:

  1. The UI should inform/alert users when a new stable release of Cylc is available to use on site.
    • The UI should offer users an easy route to upgrade.
    • Similarly, the UI should inform users of new test releases of Cylc, and offer users an easy way to test out the new release.
    • Users are currently reliant on deployment/development team to chase them to upgrade.
  2. A running workflow should be aware of its source (e.g. version control system or package management system) and inform/alert the user if they are currently running an out-of-date version of the workflow.
    • In a recent conversation, a user told me that they have forgotten to reload their suite after doing some development and committing the changes 2 months ago.
    • The rose suite-cmp-vc command is a poor-person's way to address this problem.
    • Is there anything modern CI/CD principles can teach us when it comes to helping users manage their suites?

Additional context

I am sure we have discussed this offline in the past, but I don't recall ever raising an issue. A recent conversation with a user has reminded me of this. Aspects of this issue are UI and deployment issues, so please feel free to move this around.

Pull requests welcome!

@matthewrmshin matthewrmshin added this to the cylc-9 milestone Oct 4, 2019
@kinow
Copy link
Member

kinow commented Oct 4, 2019

Oh, yes, like Riot.im does when there is a new version. It must be interesting to implement this on both frontend and backend.

@oliver-sanders
Copy link
Member

oliver-sanders commented Dec 23, 2020

Migrating this as it is a UI issue (and one to be solved in Cylc8)

The first part can be addressed with a "click here to update" button (which really just refreshes the page).

The second part should be solved with the visualisation of source directories in the UI: cylc/cylc-ui#548. Currently I'm thinking we could display a blue dot or similar (like the Rose Edit GUI) next to run directories which have drifted from the source. The install and reinstall commands will be available from the UI. At present this issue is looking a little bare but expect some more sketches, ideas and discussions in due course.

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

No branches or pull requests

3 participants