Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

GrimoireLab

grimoirelab-showcase

GrimoireLab is a CHAOSS toolset for software development analytics. It includes a coordinated set of tools to retrieve data from systems used to support software development (repositories), store it in databases, enrich it by computing relevant metrics, and make it easy to run analytics and visualizations on it.

You can learn more about GrimoireLab in the GrimoireLab tutorial, or visit the GrimoireLab website.

Metrics available in GrimoireLab are, in part, developed in the CHAOSS project. For more information regarding CHAOSS metrics, see the latest release at: https://chaoss.community/metrics/

Getting started

To ease the newcomer experience we are providing a default setup to analyze git activity for this repository. For this set up, there are several options to run GrimoireLab:

Using Docker Compose

Requirements:

Steps:

  1. Clone this project:
git clone https://github.com/chaoss/grimoirelab
  1. Go to docker-compose folder and run the following command:
cd grimoirelab/docker-compose
docker compose up -d

Your data will be ready after a while. The waiting time depends on the amount of data to fetch from a repo, for small repositories you can expect your data to be available after 10-15 minutes.

To view the data you can access OpenSearch Dashboards at http://localhost:8000 or use the OpenSearch API directly at https://localhost:9200. The API requires HTTPS and the admin user with the password set in docker-compose.yml (GrimoireLab.1 by default), and it uses a self-signed certificate, e.g.:

curl -k -u admin:GrimoireLab.1 https://localhost:9200

To manage the identities you can access SortingHat at http://localhost:8000/identities/.

By default, OpenSearch Dashboards doesn't contain any visualization, but we have a set of default dashboards. To import them, open OpenSearch Dashboards, go to Management > Dashboards Management > Saved Objects and import the files you want.

More details or troubleshooting in the docker-compose folder.

Using docker run

Requirements:

root@test-68b8628f:~# git --version
git version 2.17.1
root@test-68b8628f:~# docker --version
Docker version 19.03.1, build 74b1e89
  • Hardware: 2 CPU cores, 8GB memory RAM and enough virtual memory for OpenSearch (vm.max_map_count)
  • OpenSearch (or Elasticsearch) up and running at http://localhost:9200 without authentication, as set in setup-docker.cfg. OpenSearch Dashboards (or Kibana) is optional, for viewing the data.
  • SortingHat up and running

Steps:

  1. Clone this project:
git clone https://github.com/chaoss/grimoirelab
  1. Go to the project folder and run the following command:
cd grimoirelab
docker run --net=host \
    -v $(pwd)/default-grimoirelab-settings/projects.json:/home/grimoire/conf/projects.json \
    -v $(pwd)/default-grimoirelab-settings/setup-docker.cfg:/home/grimoire/conf/setup.cfg \
    -t grimoirelab/grimoirelab

Your dashboard will be ready after a while at http://localhost:8000. The waiting time depends on the amount of data to fetch from a repo, for small repositories you can expect your data to be visible in the dashboard after 10-15 minutes.

More details in the docker folder.

Using on FreeBSD

Recently FreeBSD has adopted Grimoirelab for their Bugzilla Analysis and have deployed Grimoirelab in their cluster. FreeBSD Foundation has been kind enough to share the process of running Grimoire on FreeBSD which is available here. This guide will also help who are interested in running Grimoirelab from source instead of deploying them with Docker.

Breaking changes

GrimoireLab 1.3.0. SortingHat permission groups.

Starting from GrimoireLab 1.3.0, creating new users in SortingHat requires assigning them to a permission group. By default, they will have read-only permissions. Please refer to the following documentation for instructions on how to update permissions: assign users to permission groups

GrimoireLab components

Currently, GrimoireLab toolkit is organized in the following repositories:

There are also some components built by the GrimoireLab community, which can be useful for you. Other related repositories are:

Contents of this repository

This repository is for content relevant to GrimoireLab as a whole. For example:

  • Issues for new features or bug reports that affect more than one GrimoireLab module. In this case, let's open an issue here, and when implementing the fix or the feature, let´s comment about the specific tickets in the specific modules that are used. For example, when supporting a new datasource, we will need patches (at least) in Perceval, GrimoireELK and panels. In this case, we would open a feature request (or the user story) for the whole case, an issue (and later a pull request) in Perceval for the data retriever, same for GrimoireELK for the enriching code, and same for panels.

  • Release notes for most GrimoireLab components (directory releases).

  • Docker container for showcasing GrimoireLab (directory docker). Includes a Dockerfile and configuration files for the GrimoireLab containers that can be used to demo the technology, and can be the basis for real deployments. See more information in the docker README.md file.

  • If you feel more comfortable with docker-compose, the docker-compose folder includes instructions and configuration files to deploy GrimoireLab using docker-compose command.

  • Source code of the GrimoireLab components is available in src. Each directory is a Git submodule, so its contents will not be available after cloning the repository. To fetch all the data, and get the latest version, you can run the following command:

git submodule update --init --remote
  • How releases of GrimoireLab are built and tested: Building

Citation

If you use GrimoireLab in your research papers, please refer to GrimoireLab: A toolset for software development analytics:

APA style:

Dueñas S, Cosentino V, Gonzalez-Barahona JM, del Castillo San Felix A, Izquierdo-Cortazar D, Cañas-Díaz L, Pérez García-Plaza A. 2021. GrimoireLab: A toolset for software development analytics. PeerJ Computer Science 7:e601 https://doi.org/10.7717/peerj-cs.601

BibTeX / BibLaTeX:

@Article{duenas2021:grimoirelab,
  author = 	 {Dueñas, Santiago and Cosentino, Valerio and Gonzalez-Barahona, Jesus M. and del Castillo San Felix, Alvaro and Izquierdo-Cortazar,  Daniel and Cañas-Díaz, Luis and Pérez García-Plaza, Alberto},
  title = 	 {GrimoireLab: A toolset for software development analytics},
  journaltitle = {PeerJ Computer Science},
  date = 	 {2021-07-09},
  volume = 	 7,
  number = 	 {e601},
  doi = 	 {10.7717/peerj-cs.601},
  url = 	 {https://doi.org/10.7717/peerj-cs.601}}

Contributing

Contributions are welcome, please check the Contributing Guidelines.

Metadata

Release files for grimoirelab 1.23.0rc1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for grimoirelab 1.23.0rc1
File Size Uploaded Provenance Actions
grimoirelab-1.23.0rc1.tar.gz 17.9 kB Without provenance Details for grimoirelab-1.23.0rc1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for grimoirelab 1.23.0rc1
File Interpreter ABI Platform Actions
grimoirelab-1.23.0rc1-py3-none-any.whl Python 3 none any Details for grimoirelab-1.23.0rc1-py3-none-any.whl

Total release size: 38.1 kB

Release files / grimoirelab-1.23.0rc1.tar.gz

Download URL grimoirelab-1.23.0rc1.tar.gz
Size 17.9 kB
Tags Source
SHA-256 checksum
How to use checksums
503fc5ecdb876d2444af37d64f2bb8fbaf8adee6b52a4859647dca67cdd90fbe
BLAKE2b-256 checksum
How to use checksums
178f20dc6c1e29b579e1c8f995f8962df5b0f6e79e60e94df0ee1fa3dda6d2d4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/2.5.1 CPython/3.14.4 Linux/7.0.0-1017-azure

Release files / grimoirelab-1.23.0rc1-py3-none-any.whl

Download URL grimoirelab-1.23.0rc1-py3-none-any.whl
Size 20.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f4704dd8e3ad21ced8980e8a971d34225b47a75ac782b1dec7b8299cca1453a3
BLAKE2b-256 checksum
How to use checksums
3f59338f5f79902aa23a223d3bfe7d9358cff929faedcebd15b363e444f8f7ec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/2.5.1 CPython/3.14.4 Linux/7.0.0-1017-azure

Security for grimoirelab 1.23.0rc1

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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page