glossary

Glossary

Some useful glossary

Job aka Sparky project

Raku scenario gets executed on some event and does some useful job

Sparky scenario

Implementation of Sparky job written on Raku

Build

A specific instance of Sparky job. Usually reports are visible though UI and might have some artifacts

Report

Log of Sparky job execution

Artifact

Some byproducts ( technically are files) attached to a build and visible through UI

UI aka Sparky web UI

Web application to run Sparky jobs and get their reports

Sparrowdo

A client to run Sparky jobs on (remote) hosts and docker containers

Sparrow

Underlying automation framework to execute Sparky job

sparky.yaml

YAML definition of Sparky job meta information, like input parameters, UI controls, triggering logic, etc. Every Sparky job has a sparky.yaml file

root directory

Directory where scheduler looks for job scenarios, by default:

~/.sparky/projects/

work directory

Directory where scheduler keeps internal jobs data:

~/.sparky/work

Sparky v0.2.32

Sparky is a flexible and minimalist continuous integration server and distribute tasks runner written in Raku

Authors

  • Alexey Melezhik

License

Artistic-2.0

Dependencies

YAMLishDBIishDBIish::PoolJSON::FastHTTP::TinySparrow6:ver<0.0.90+>Sparrowdo:ver<0.1.54+>Sparky-Job-Api:ver<0.0.12+>Time::CrontabFile::Directory::TreecroCro::HTTP:ver<0.8.9+>Cro::HTTP::ServerCro::HTTP::RouterCro::WebApp::TemplateData::Dump:ver<0.0.12+>Text::Markdown

Test Dependencies

Provides

  • Sparky
  • Sparky::HTML
  • Sparky::Job
  • Sparky::Security
  • Sparky::Utils

The Camelia image is copyright 2009 by Larry Wall. "Raku" is trademark of the Yet Another Society. All rights reserved.

Built with Podlite — the markup and publishing tools behind this site.