DOI: 10.5281/zenodo.1183244
title: (No) Influence Of Continuous Integration On The Development Activity In Github Projects — Dataset

description: This dataset is based on the TravisTorrent dataset released 2017-01-11 (https://travistorrent.testroots.org), the Google BigQuery GHTorrent dataset accessed 2017-07-03, and the Git log history of all projects in the dataset, retrieved 2017-07-16 and 2017-07-17.

We selected projects hosted on GitHub that employ the Continuous Integration (CI) system Travis CI. We identified the projects using the TravisTorrent data set and considered projects that:


	used GitHub from the beginning (first commit not more than seven days before project creation date according to GHTorrent),
	were active for at least one year (365 days) before the first build with Travis CI (before_ci),
	used Travis CI at least for one year (during_ci),
	had commit or merge activity on the default branch in both of these phases, and
	used the default branch to trigger builds.


To derive the time frames, we employed the GHTorrent Big Query data set. The resulting sample contains 113 projects. Of these projects, 89 are Ruby projects and 24 are Java projects. For our analysis, we only consider the activity one year before and after the first build.

We cloned the selected project repositories and extracted the version history for all branches (see https://github.com/sbaltes/git-log-parser). For each repo and branch, we created one log file with all regular commits and one log file with all merges. We only considered commits changing non-binary files and applied a file extension filter to only consider changes to Java or Ruby source code files. From the log files, we then extracted metadata about the commits and stored this data in CSV files (see https://github.com/sbaltes/git-log-parser).

We also retrieved a random sample of GitHub project to validate the effects we observed in the CI project sample. We only considered projects that:


	have Java or Ruby as their project language
	used GitHub from the beginning (first commit not more than seven days before project creation date according to GHTorrent)
	have commit activity for at least two years (730 days)
	are engineered software projects (at least 10 watchers)
	were not in the TravisTorrent dataset


In total, 8,046 projects satisfied those constraints. We drew a random sample of 100 projects from this sampling frame and retrieve the commit and merge data ni the same way as for the CI sample.

This dataset contains the following files:

<strong>tr_projects_sample_filtered_2.csv</strong><br>
A CSV file with information about the 113 selected projects.

<strong>tr_sample_commits_default_branch_before_ci.csv<br>
tr_sample_commits_default_branch_during_ci.csv</strong><br>
One CSV file with information about all commits to the default branch before and after the first CI build. Only commits modifying, adding, or deleting Java or Ruby source code files were considered. Those CSV files have the following columns:

project: GitHub project name ("/" replaced by "_").<br>
branch: The branch to which the commit was made.<br>
hash_value: The SHA1 hash value of the commit.<br>
author_name: The author name.<br>
author_email: The author email address.<br>
author_date: The authoring timestamp.<br>
commit_name: The committer name.<br>
commit_email: The committer email address.<br>
commit_date: The commit timestamp.<br>
log_message_length: The length of the git commit messages (in characters).<br>
file_count: Files changed with this commit.<br>
lines_added: Lines added to all files changed with this commit.<br>
lines_deleted: Lines deleted in all files changed with this commit.<br>
file_extensions: Distinct file extensions of files changed with this commit.

<strong>tr_sample_merges_default_branch_before_ci.csv<br>
tr_sample_merges_default_branch_during_ci.csv</strong><br>
One CSV file with information about all merges into the default branch before and after the first CI build. Only merges modifying, adding, or deleting Java or Ruby source code files were considered. Those CSV files have the following columns:

project: GitHub project name ("/" replaced by "_").<br>
branch: The destination branch of the merge.<br>
hash_value: The SHA1 hash value of the merge commit.<br>
merged_commits: Unique hash value prefixes of the commits merged with this commit.<br>
author_name: The author name.<br>
author_email: The author email address.<br>
author_date: The authoring timestamp.<br>
commit_name: The committer name.<br>
commit_email: The committer email address.<br>
commit_date: The commit timestamp.<br>
log_message_length: The length of the git commit messages (in characters).<br>
file_count: Files changed with this commit.<br>
lines_added: Lines added to all files changed with this commit.<br>
lines_deleted: Lines deleted in all files changed with this commit.<br>
file_extensions: Distinct file extensions of files changed with this commit.<br>
pull_request_id: ID of the GitHub pull request that has been merged with this commit (extracted from log message).<br>
source_user: GitHub login name of the user who initiated the pull request (extracted from log message).<br>
source_branch : Source branch of the pull request (extracted from log message).

<strong>comparison_project_sample_100.csv</strong><br>
A CSV file with information about the 100 projects in the comparison sample.

<strong>commits_default_branch_before_mid.csv<br>
commits_default_branch_after_mid.csv</strong><br>
One CSV file with information about all commits to the default branch before and after the medium date of the commit history. Only commits modifying, adding, or deleting Java or Ruby source code files were considered. Those CSV files have the same columns as the commits tables described above.

<strong>merges_default_branch_before_mid.csv<br>
merges_default_branch_after_mid.csv</strong><br>
One CSV file with information about all merges into the default branch before and after the medium date of the commit history. Only merges modifying, adding, or deleting Java or Ruby source code files were considered. Those CSV files have the same columns as the merge tables described above.