Source tracking allows you to investigate the code used for running the experiment.
Source tracking automatically connects the revision of the code to the experiment. This connection is made without having to actually copy the code to MissingLink servers. Once you have source tracking active on your experiments, you can view the actual code from the experiment and also compare the code changes between experiments.
The following image shows the panes below the Overview tab of an experiment that uses code. The link under Code Revision is to a Git repository.
Clicking the highlighted link opens a window in your associated Git repository. It displays the version of the code that was used in the experiment and highlights the diff from the previous version. Something like this:
Source tracking integrates with all common Git repositories: GitHub, Bitbucket, GitLab, Git LFS, and others.
Source tracking modes
There are two source tracking modes:
- Simplified: Assumes that the code is committed to your source control repository before the experiment begins to run. On condition that you use Git, this feature is active by default. MissingLink watches your Git repo, the Git branch, and the commits and records them along with the experiment. Using this mode, whenever a change has been made in the code, MissingLink detects only that there is some incompatibility between the files and the code that is running.
Advanced: In addition to the capabilities it provides in simplified mode, advanced source tracking can also track the exact changes in files that were used for the experiment, even though they have not yet been committed to source control.
In order to run a new job using MissingLink's resource management, you must configure the Advanced mode.
For instructions in configuring this connection, see Setting up Code Tracking in MissingLink.