Refine deployment from Jenkinsfile, add timestamps for access in Folo tracked entries#1399
Merged
jdcasey merged 3 commits intoCommonjava:masterfrom Oct 30, 2019
Merged
Refine deployment from Jenkinsfile, add timestamps for access in Folo tracked entries#1399jdcasey merged 3 commits intoCommonjava:masterfrom
jdcasey merged 3 commits intoCommonjava:masterfrom
Conversation
… so we can use Externalizable versioning for deser
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We're missing information about how many times a given file is accessed during a build, and what the time distribution looks like between file accesses. This isn't needed for normal production use cases, but having it will give us a much better ability to simulate build users without actually running builds. With the timing information, we can sort the download / upload lists into a single "script" of artifact accesses and sizes, the replay it in a simulated environment.
We'll need more tracking information on the metadata files that get used during build alignment, but this is a step in the right direction.
Also, in the Jenkinsfile I'm making artifact deployment conditional on having an image build configuration available. This will limit CI scenarios that build for non-Commonjava forks of the repository, since those user-based forks will not have corresponding image build configs in our CI system. We don't want these non-Commonjava artifacts to be deployed, since that would make it much harder to figure out where a given snapshot came from.