You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If two developers merge in their builds at the same time and two travis requests kick off, the resultant PDF/MD builds are entirely dependent on Travis Timing conditions. This means an earlier commit which could take longer to build gets pushed to head. Solution
The later commit encapsulates all changes so ideally what happens is the clone happens first with a metadata file. If the time of the latest head commit is older than the time of the deploy commit version, exit the build a success, the changes were pushed out to prod.
The text was updated successfully, but these errors were encountered:
Describe the bug
If two developers merge in their builds at the same time and two travis requests kick off, the resultant PDF/MD builds are entirely dependent on Travis Timing conditions. This means an earlier commit which could take longer to build gets pushed to head.
Solution
The later commit encapsulates all changes so ideally what happens is the clone happens first with a metadata file. If the time of the latest head commit is older than the time of the deploy commit version, exit the build a success, the changes were pushed out to prod.
The text was updated successfully, but these errors were encountered: