v5.1.0

This version introduces a new web-based user interface, more HTTP endpoints, and many other useful features.

New features:

• New web-based user interface (!)
  • Modern look
  • Responsive (works on mobile devices)
  • Filters for workflows, process chains, etc. (e.g. show only failed process chains)
  • ... many more features
• Add possibility to configure a pool of remote agents for which to create VMs
• Cloud VMs are now kept in the database
• Add HTTP endpoint for VMs
  • Access information about created VMs
  • Get reason why a VM was destroyed
  • Fetch VMs by status
• Improved HTTP endpoint for workflows
  • Add possibility to fetch workflows by status
  • Provide required capabilities of workflows
• Add support for Cross-Origin Resource Sharing (CORS)
• Allow multiple SSH commands to be executed in parallel while creating new VMs
• Add possibility to disable controller
• Log agent capabilities on startup
• Add interface for initializer plugins

Maintenance:

• Speed up discovery of plugins and service metadata
• Update Gradle to 6.3
• Update Kotlin to 1.3.72

Bug fixes:

• Include conf directory in distribution
• Allow the Steep start script to be run from anywhere
• Include results of partially succeeded submissions in the HTTP response

v5.1.0-beta.8

New features:

• Add interface for initializer plugins

v5.1.0-beta.7

New features:

• Add maximum number of agents per capability set to agent pool configuration

Bug fixes:

• Fix build number and commit SHA in version info
• Fix placement of labels when they are wrapped

v5.1.0-beta.6

New features:

• HTTP endpoints
  • Add possibility to fetch workflows and VMs by status
  • Provide required capabilities of workflows
• Web-based UI
  • Add filters for workflows and VMs
  • Add more filters for process chains
  • Show more details about VMs
  • Add favicons

Maintenance:

• Better code reuse in web-based UI
• Update Gradle to 6.3
• Update Kotlin to 1.3.72

v5.1.0-beta.5

New features:

• New web-based user interface
  • Modern look
  • Responsive (works on mobile devices)
  • Possibility to only show failed process chains
  • ... many more nice features
• Cloud VMs are now kept in the database
• Add HTTP endpoint for VMs
  • Access information about created VMs
  • Get reason why a VM was destroyed
• Add support for Cross-Origin Resource Sharing (CORS)
• Add possibility to disable controller
• Log agent capabilities on startup

Maintenance:

• Speed up discovery of plugins and service metadata

Bug fixes:

• Include conf directory in distribution
• Allow the Steep start script to be run from anywhere
• Include results from partially succeeded submissions in the HTTP response

v5.1.0-beta.3

Bug fixes:

• Keep remote agents in pool alive

v5.1.0-beta.2

New features:

• When deploying CloudManager, only destroy orphaned VMs but do not create new ones

v5.1.0-beta.1

New features:

• Add possibility to configure a pool of remote agents to create VMs for
• Allow multiple SSH commands to be executed in parallel while creating new VMs

v5.0.1

Maintenance:

• Remove unused Graal libraries

Bug fixes:

• Really send keep-alive to the configured number of VMs
• Only request a new agent from the CloudManager if there are process chains that require one

v5.0.0

New features:

• The JobManager has a new name: Steep!
• Steep is now Open-Source!
• Execute process chains in the order they have been added to the registry
• New capability-based scheduling algorithm (see below)
• Do not keep temporary process chain results in memory if not needed
• Allow user to disable scheduler
• Do not log errors while trying to connect to new VM via SSH
• Add possibility to specify a minimum number of VMs per setup
• Allow alternative setups with similar provided capabilities to be specified
• New process chain adapter plugins

Maintenance:

• Migrate to GitHub Actions
• Reduce log output in CI
• Update Gradle to 6.1.1

Breaking changes:

• Remove deprecated store action and update workflow API to 4.0.0. Please use the store flag on output parameters instead.
• Replace rule system with process chain adapter plugins
• Move configuration of availability zones to setups

New capability-based scheduling algorithm:

With the old scheduling algorithm, workflow execution could stall if there was a process chain that could not be executed because of a missing agent, even if there were other agents that would have been able to execute the remaining process chains. The new algorithm executes process chains in the order they were added to the registry and always fetches as many of them as possible from the registry if there are enough agents available that can execute them. Process chains that cannot be executed because they require capabilities none of the agents can provide are skipped but resumed immediately as soon as an agent with matching capabilities joins the cluster.