Documentation
Bayer's Gitlab Documentation
Git Dashboard
Overview
Introduction
This Git Dashboard is meant to show metrics and visualisations for the git-systems in use at Bayer.
These git-systems are included:
The content shown here is currently Work-In-Progress. Meaning that some functionalites can be subject to change or might not yet be properly integrated
For questions regarding content, processes, or if you have remarks / suggestions feel free to get in contact.
These git-systems are included:
|
|
|
| GitLab | GitHub |
|---|
The content shown here is currently Work-In-Progress. Meaning that some functionalites can be subject to change or might not yet be properly integrated
For questions regarding content, processes, or if you have remarks / suggestions feel free to get in contact.
User & Project History
Shows the history of project and user numbers starting on 2016-04-19 (Creation date of the GitHub instance). The GitLab instance was created on 2017-03-02.
Projects are the term used by GitLab to describe the comparabale construct of a repository in GitHub. GitHub projects (which are for actual project management) are not described.
Projects are the term used by GitLab to describe the comparabale construct of a repository in GitHub. GitHub projects (which are for actual project management) are not described.
|
Project Distribution
This doughnut chart shows the absolute and relative numbers of different kinds of projects.
Active: Recent activity within the last 90 days Inactive: No activity for at least 90 days CI: Makes use of the GitLab-CI functionality No-CI: Does not make use of the GitLab-CI functionality Private: Within a users personal namespace or within a private organization Internal: Available to see for every authenticated GitLab users of the instance |
User Distribution
This doughnut chart shows the absolute and relative numbers of different kinds of users.
Active: Login or recent activity within the last 90 days Deactivated: Temporarily deactivated because of insufficient activity. Can be reactivated with login Blocked: Former user that was actively blocked, because they left the company or contract ended Internal: Bayer users External: Partners and accounts for automation Bot: Account for automation |
|
|---|---|---|
Frequently used terms in GitLab-CI
This word cloud gives abstract insight into some trends in GitLab-Ci automation practives.
The size of a word shows how often the keyword is mentioned in GitLab-CI configuration files in relation to orher words. Hovering over a word gives the absolute number of how many times the keyword was found.
The keywords mentioned in this diagram have not been automatically generated. They are hand-picked.
The size of a word shows how often the keyword is mentioned in GitLab-CI configuration files in relation to orher words. Hovering over a word gives the absolute number of how many times the keyword was found.
The keywords mentioned in this diagram have not been automatically generated. They are hand-picked.
CI Minutes (past 30 days)
The CI-Minutes bar graph shows the number of minutes a project has consumed within the last 30 days.
Commits per project
The Commits/Project bar graph shows how many commits are currently present in a project.
Commit:
A commit is a bundle of changes of source code inside of a repository. They are used to simplify exchange of the current code-version between developers and systems. CI/Automation jobs are generally started whenever a new commit is added.
Commit:
A commit is a bundle of changes of source code inside of a repository. They are used to simplify exchange of the current code-version between developers and systems. CI/Automation jobs are generally started whenever a new commit is added.
Proportion of Projects with Commits
The Commits/Project stacked bar graph shows how many projects have how many commits.
Commit:
A commit is a bundle of changes of source code inside of a repository. They are used to simplify exchange of the current code-version between developers and systems. CI/Automation jobs are generally started whenever a new commit is added.
Commit:
A commit is a bundle of changes of source code inside of a repository. They are used to simplify exchange of the current code-version between developers and systems. CI/Automation jobs are generally started whenever a new commit is added.
Runners
This table shows how many and which types of runners are available in GitLab.
Group Runner:
Shared runner for specific group/organization
Project Runner:
Dedicated runners for a single project/repository
Instance Runner:
Shared runners for everybody
Online:
Currently available to accept CI/Automation jobs
Paused:
Online but not available
Offline:
Registered but not reachable
Not connected:
Not properly registered
Runner: A runner is a compute instance (e.g. EC2, ...) that processes CI/Automation jobs that are triggered from within GitLab.
Group Runner:
Shared runner for specific group/organization
Project Runner:
Dedicated runners for a single project/repository
Instance Runner:
Shared runners for everybody
Online:
Currently available to accept CI/Automation jobs
Paused:
Online but not available
Offline:
Registered but not reachable
Not connected:
Not properly registered
Runner: A runner is a compute instance (e.g. EC2, ...) that processes CI/Automation jobs that are triggered from within GitLab.
Bayer Resources
Auto-generated