Project

General

Profile

Feature #39977

Avatar?id=14398&size=50x50

Revise update page in new UI

Added by Kris Moore almost 2 years ago. Updated over 1 year ago.

Status:
Done
Priority:
Expected
Assignee:
Dennis Mullen
Category:
GUI (new)
Target version:
Estimated time:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Description

For updating, we need to enhance the update code with a way to hide trains from the UI dropdowns. I suggest a third field in the trains.txt file which can bet set to hidden/visible.

This is so we can release a beta/rc on a new train and then choose at a later time when to make that magically show up in the UI.


Related issues

Related to FreeNAS - Bug #49095: Add release and prerelease tags to train descriptionsDone
Related to FreeNAS - Bug #40940: Add train descriptions and only display allowed trains in new UIDone
Related to FreeNAS - Bug #63360: Make use of new middleware reporting of train descriptions in new UIDone
Has duplicate FreeNAS - Bug #40568: Add linebreaks in change log window for 11.2-stable trainClosed
Has duplicate FreeNAS - Bug #40944: Download Update button is misleadingClosed
Has duplicate FreeNAS - Bug #51335: Labelling of trainsClosed

History

#1 Updated by Eric Loewenthal almost 2 years ago

Although it adds a little bit of complexity, an option in the GUI to access pre-release trains would be appreciated in conjunction with this.

#3 Updated by Dru Lavigne almost 2 years ago

  • Assignee changed from Release Council to William Grzybowski

#4 Updated by Dru Lavigne almost 2 years ago

  • Category changed from Middleware to OS
  • Assignee changed from William Grzybowski to Sean Fagan

#5 Updated by Dru Lavigne almost 2 years ago

  • Target version changed from Backlog to 11.3

#6 Updated by Sean Fagan almost 2 years ago

  • Assignee changed from Sean Fagan to Kris Moore

A train doesn't have to be in the trains.txt file to be used. Although it'll cause some problems with some of the consistency checking I can do on the server, the code on my level to check for updates doesn't care about that file. (All it does is look for ${SERVER}/${PRODUCT}/${TRAIN}/LATEST, and then compares the sequence string to what's currently running.)

Given that, I don't see that there is anything to do here, unless the GUI code has problems with the train being missing.

Hm, it's possible the release-processing code ("freenas-release" on the update server) may have some problems with it.

#7 Avatar?id=14398&size=24x24 Updated by Kris Moore almost 2 years ago

  • Subject changed from Need way to hide a train to Train details
  • Assignee changed from Kris Moore to Dru Lavigne

Updated subject. Dru and I discussed this, we want some ability in the train description to add a UI element showing that a train is PreRelease.

UI team, let's add some code so if the train description has a BETA in the text we get a visual indicator or warning when attempting to change to this train.

#8 Updated by Dru Lavigne almost 2 years ago

  • Subject changed from Train details to Revise update page in new UI
  • Category changed from OS to GUI (new)
  • Status changed from Unscreened to Not Started
  • Assignee changed from Dru Lavigne to Warren Block
  • Target version changed from 11.3 to 11.2-RC1

Goals:
1. provide a visual indicator for a pre-release update
2. provide a link to the latest Release Notes for the stable train (https://www.ixsystems.com/blog/knowledgebase_category/freenas/?latest=true)
3. indicate that the nightlies train is not for production use and display the commits since the last nightly
4. logically divide the page into settings, update information, and actions

#9 Updated by Dru Lavigne almost 2 years ago

  • Has duplicate Bug #40568: Add linebreaks in change log window for 11.2-stable train added

#10 Updated by Warren Block almost 2 years ago

  • Assignee changed from Warren Block to Dennis Mullen

#11 Updated by Dennis Mullen almost 2 years ago

  • Status changed from Not Started to In Progress

#13 Updated by Dru Lavigne almost 2 years ago

  • Related to Bug #49095: Add release and prerelease tags to train descriptions added

#14 Updated by Dru Lavigne almost 2 years ago

  • Status changed from In Progress to Ready for Testing
  • Needs Merging changed from Yes to No

#15 Updated by Bonnie Follweiler almost 2 years ago

  • Status changed from Ready for Testing to Failed Testing

Failed testing in the area where "This is not a production release, and should only be used for testing." there should be an additional sentence explaining the train choice

#16 Updated by Lola Yang almost 2 years ago

  • Status changed from Failed Testing to Ready for Testing

#18 Updated by Bonnie Follweiler over 1 year ago

  • Status changed from Ready for Testing to Passed Testing
  • Needs QA changed from Yes to No

Test Passed in FreeNAS-11.2-INTERNAL23

#19 Updated by Dru Lavigne over 1 year ago

  • Has duplicate Bug #40944: Download Update button is misleading added

#20 Updated by Dru Lavigne over 1 year ago

  • Has duplicate Bug #51335: Labelling of trains added

#21 Updated by Dru Lavigne over 1 year ago

  • Related to Bug #40940: Add train descriptions and only display allowed trains in new UI added

#22 Updated by Dru Lavigne over 1 year ago

  • Status changed from Passed Testing to Done
  • Needs Doc changed from Yes to No

#23 Updated by Dru Lavigne over 1 year ago

  • Related to Bug #63360: Make use of new middleware reporting of train descriptions in new UI added

Also available in: Atom PDF