Working with JUBE

Last updated on 2025-02-11 | Edit this page

Estimated time: 12 minutes

Overview

Questions

  • Which steps need to be taken when running JUBE?

Objectives

  • Explain how to use markdown with The Carpentries Workbench
  • Demonstrate how to include pieces of code, figures, and nested challenge blocks

JUBE workflows are started with the command jube run <jube-spec>. The configuration file can be either an XML or a YAML file.

A minimal configuration in XML contains the tags <jube> and <benchmark>.

XML

<?xml version="1.0" encoding="UTF-8"?>
<jube>
  <benchmark name="hello_world" outpath="bench_run">
    <!-- further configuration goes here -->
  </benchmark>
</jube>

YAML

name: hello_world
outpath: bench_run

Running a workflow


A JUBE workflow is started by the run command, putting this workflow into the running state. Any defined tasks When no asynchronous tasks are defined (See Running an application) the steps wi.

The JUBE workflow with `run`, `continue`, `analysis`, and `result` commands.
The JUBE workflow with run, continue, analysis, and result commands.

Key Points

  • A JUBE workflow is started with jube run
  • A JUBE workflow is completed when all defined steps completed.