Jolt
Jolt is a task execution tool designed for software development tasks. It can build your C/C++ applications and React frontends, run tests, deploy your web services, and much more.
Tasks are defined in Python scripts. They may be executed locally by developers or by automation software such as Jenkins in a continuous integration pipeline. In both cases, tasks may be distributed and executed in parallel in a server cluster. The output of each task is cached to reduce overall execution times on repeat attempts. In one real world deployment, Jolt shortend the CI build duration from 10 hours to 10 minutes on average.
Example C++ application task:
class CppApp(CXXExecutable):
""" Builds a C++ application """
arch = Parameter(values=["arm", "x64"])
requires = [
"git:url=https://github.com/org/cppapp.git",
"gcc:arch={arch},version=9.1.1",
]
sources = ["cppapp/include/*.hpp", "cppapp/src/*.cpp"]$ jolt build cppapp:arch=x64Example Node.js tasks:
class NodeJS(Download):
""" Downloads and publishes Node.js. Adds binaries to PATH. """
version = Parameter("14.16.1")
url = "https://nodejs.org/dist/v{version}/node-v{version}-win-x64.zip"
def publish(self, artifact, tools):
super(publish).publish(artifact, tools)
artifact.environ.PATH.append("node-v{version}-win-x64")
class WebApp(Task):
""" Builds a really cool WebApp """
requires = [
"git:url=https://github.com/org/webapp.git",
"nodejs"
]
def run(self, deps, tools):
with tools.cwd("webapp"):
tools.run("npm ci")
tools.run("npm build")$ jolt build webappA common command line interface for all tasks enables developers from different disciplines to quickly run each others tasks without in-depth knowledge of the underlying technology - a C++ developer doesn’t have to learn NPM and a React developer doesn’t have to know anything about CMake, Make, MSBuild, etc. Required tools and dependencies are also provisioned automatically.
For full documentation, please visit http://jolt.readthedocs.io/
Installing
Jolt is available in the Python Package Index:
$ pip install jolt
$ joltAnd as a Docker image:
$ docker run robrt/joltA thin Python wrapper is available for the Docker images. By using it, multiple versions of Jolt can coexist on the host since the version used is selected during runtime rather than install time. To use a specific version in a project, add a version attribute in the Jolt manifest. By always using a specific version cache hits become more likely.
$ pip install jolt_docker
$ jolt1 maintainer
Metadata
1 maintainer
Release files for jolt 0.10.65
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| jolt-0.10.65.tar.gz | 17.0 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jolt-0.10.65-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.1 MB
Release files / jolt-0.10.65.tar.gz
| Download URL | jolt-0.10.65.tar.gz |
|---|---|
| Size | 17.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e1185dd234970e869044356d04ac251cf08a9e23da5e556b9a848bab7d591b6
|
|
BLAKE2b-256 checksum How to use checksums |
553da61ccd29e8fcc6d042a6059746f2e18d6f24dda0ca5c86d4fb7c7f6a024b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Release files / jolt-0.10.65-py3-none-any.whl
| Download URL | jolt-0.10.65-py3-none-any.whl |
|---|---|
| Size | 17.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1c0e648fc5fcefca794f739d1baa9c0e3703b55fa5f37ad5dbca71fd0baac713
|
|
BLAKE2b-256 checksum How to use checksums |
db73cf74bb05795863d6a0db86219c9e295e185e4d17d4aa13f713a41e91de1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Security for jolt 0.10.65
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
