Pueue is a command-line task management tool for sequential and parallel execution of long-running tasks.
Simply put, it's a tool that processes a queue of shell commands. On top of that, there are a lot of convenient features and abstractions.
Since Pueue is not bound to any terminal, you can control your tasks from any terminal on the same machine. The queue will be continuously processed, even if you no longer have any active ssh sessions.
pueued daemon runs in the background. No need to be logged in.log and status for external scripting.wait subcommand to allow external scripts to wait for a group (or everything) to finish.There are a few different ways to install Pueue.
The preferred way to install Pueue is to use your system's package manager.
This will usually deploy service files and completions automatically.
Pueue has been packaged for quite a few distributions, check the table on the right for more information.
Statically linked (if possible) binaries for Linux (incl. ARM), Mac OS and Windows are built on each release. \
You can download the binaries for the client and the daemon (pueue and pueued) for each release on the release page. \
Just download both binaries for your system, rename them to pueue and pueued and place them in your \$PATH/program folder.
Pueue is built for the current stable Rust version.
It might compile on older versions, but this isn't tested or officially supported.
bash
cargo install --locked pueue
This will install Pueue to $CARGO_HOME/bin/pueue (default is ~/.cargo/bin/pueue)
Pueue is built for the current stable Rust version.
It might compile on older versions, but this isn't tested or officially supported.
bash
git clone git@github.com:Nukesor/pueue
cd pueue
cargo build --release --locked --path .
The final binaries will be located in target/release/{pueue,pueued}.
Check the wiki to get started :).
There are also detailed sections for (hopefully) every important feature:
On top of that, there is a help option (-h) for all commands.
```text Pueue client 2.0.0 Arne Beer contact@arne.beer Interact with the Pueue daemon
USAGE: pueue [OPTIONS] [SUBCOMMAND]
OPTIONS:
-c, --config
SUBCOMMANDS: add Enqueue a task for execution clean Remove all finished tasks from the list completions Generates shell completion files. This can be ignored during normal operations edit Edit the command or path of a stashed or queued task. The command is edited by default. enqueue Enqueue stashed tasks. They'll be handled normally afterwards follow Follow the output of a currently running task. This command works like tail -f format-status Accept a list or map of JSON pueue tasks via stdin and display it just like "status". A simple example might look like this: pueue status --json | jq -c '.tasks' | pueue format-status group Use this to add or remove groups. By default, this will simply display all known groups help Print this message or the help of the given subcommand(s) kill Kill specific running tasks or whole task groups. Kills all tasks of the default group when no ids are provided log Display the log output of finished tasks. When looking at multiple logs, only the last few lines will be shown. If you want to "follow" the output of a task, please use the "follow" subcommand parallel Set the amount of allowed parallel tasks. By default, adjusts the amount of the default group pause Either pause running tasks or specific groups of tasks. By default, pauses the default group and all its tasks. A paused queue (group) won't start any new tasks. remove Remove tasks from the list. Running or paused tasks need to be killed first reset Kill all tasks, clean up afterwards and reset EVERYTHING! restart Restart task(s). Identical tasks will be created and by default enqueued. By default, a new task will be created send Send something to a task. Useful for sending confirmations such as 'y\n' shutdown Remotely shut down the daemon. Should only be used if the daemon isn't started by a service manager start Resume operation of specific tasks or groups of tasks. By default, this resumes the default group and all its tasks. Can also be used force-start specific tasks. stash Stashed tasks won't be automatically started. You have to enqueue them or start them by hand status Display the current status of all tasks switch Switches the queue position of two commands. Only works on queued and stashed commands wait Wait until tasks are finished. This can be quite useful for scripting. By default, this will wait for all tasks in the default group to finish. Note: This will also wait for all tasks that aren't somehow 'Done'. Includes: [Paused, Stashed, Locked, Queued, ...] ```
Pueue is designed to be a convenient helper tool for a single user.
It's supposed to work stand-alone and without any external integration. The idea is to keep it simple and to prevent feature creep.
Hence, these features won't be included as they're out of scope:
There seems to be the need for some solution that satisfies all these points mentioned above, but that isn't Pueue's job.
GNU Parallel
A robust and featureful parrallel processor with text-based joblog and n-retries. GNU Parallel is able to scale to multi-host parallelization and has complex code to have deep integration across different tools and shells, as well as other advanced features. Pueue differentiates itself from GNU Parallel by focusing more on visibility across many different long running commands, and creating a central location for commands to be stored, rather than GNU Parallel's focus on chunking a specific task.
nq
A very lightweight job queue systems which require no setup, maintenance, supervision, or any long-running processes. \ Link to project
task-spooler
task spooler is a Unix batch system where the tasks spooled run one after the other. \ Links to ubuntu manpage and a fork on Github. The original website seems to be down.
Feature requests and pull requests are very much appreciated and welcome!
Anyhow, please talk to me a bit about your ideas before you start hacking! It's always nice to know what you're working on and I might have a few suggestions or tips :)
Depending on the type of your contribution, you should branch of from either the main branch or the development branch.
main and be merged into main.
New patch level releases will be published for this kind of issues.
Any patches in main will also regularily be merged into development.development and be merged into development.
Once a new minor or major version has been published, development will then be merged into main.There's also the Architecture Guide, which is supposed to give you a brief overview and introduction to the project.
Copyright © 2019 Arne Beer (@Nukesor)