GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption, please take a look at our documentation.
Adding the BTagging configuration of VRtrack jets for 201903 re-training: SUSY1 and SUSY11
We were missing the 201903 BTagging retraining for VRtrack jets. Added it only to the formats that previously stored the VR-track jets. Adding @salderwe and @janders to follow the request