Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Anchor
2.2
2.2
Upgrading to 2.2

  • NOTE: Upgrading to Tractor 2.2 is "permanent" in the sense that you cannot revert to an older tractor-engine while also retaining your old jobs once the 2.2 job database upgrade has been performed. If you BACKUP your current job database before installing 2.2, then it is possible to revert to the older engine version along with jobs restored to their state at the time of the backup. Please refer to the guidelines described in Upgrading.
  • Upgrading to 2.2
  • Upgrading to 2.1
  • Upgrading from 1.x

...

Anchor
1714849
1714849
Changes in 2.2 1714849

  • Notes here

Anchor
1677499
1677499
Changes in 2.2 1677499

  • Custom menu items will cause a new window to be opened if there is any script output, even if the menu item is configured to normally suppress a new window. This enables problematic scripts to be more easily detected and debugged.
  • Custom menu items support "login" as a special entry in the "values" list, which will cause the Dashboard user name to be a part of the payload sent to the menu item's script.
  • Custom menu items will now observe user names and "@owner" in the crews attribute for job and forjoband task custom menu items.
  • Fixed bug in which selecting next task by state in bystatein Dashboard task list was not automatically scrolling to tasktotask.
  • Fixed the calculation of the elapsed time of a skipped task in the rollover of the Dashboard job graph.
  • Sorting of tasks in the Dashboard task list has been corrected.
  • Dashboard preview commands can now be displayed and run for archived jobs.
  • The kill operation is now supported in tq and intqand the query API. It is used to kill a running command and leaves the task in an error state.
  • tq has a new reloadconfig command tqhas a newreloadconfigcommand to enable the triggering of configuration file reloading from the command line.
  • The query API will only return non-registered blades when the archive flag is set to True.
  • tractor-dbctl--exec-sql now sqlnow emits error messages.
  • The blade caches user database entries in order to be more resilient against transient LDAP server outages.
  • The systemd configuration directory defaults to the Tractor installation config/ directory, consistent with the sysvinit setting.
  • systemd now starts tractor blade as root by default, consistent with the sysvinit setting.

...