![]() The training is in San Francisco, and then immediately followed up with a July 30th co-location in Boulder, Colorado. After that took 2 weeks off before my training begins for Doximity on July 16th. I put in my notice with Influence Health at the beginning of June, and served through the end of the month. # $ API_TOKEN=xxx GITHUB_USERNAME=bsimpson GITHUB_PROJECT=some-project TARGET_JOB=lighthouse ARTIFACT=averages_pageload ruby. # Finds a CircleCI job of a given name, and retrieves an artifact from a given CircleCI project build Should be easily adaptable to other languages. ![]() The specifics of how to automate this script, and what to do with its output is outside the scope of this post, but I will share our Ruby script for interacting with CircleCI. From here we can put this information into our company Slack, or even push it to a collaborate spreadsheet that the team routinely reviews. We now have the output from our artifact. We now have the URL for a given artifact, and it is just a matter of downloading the file by suffixing the CircleCI token to our URL: This allows us to get the container information and paths of any artifacts produced by the job. Once we have found a specific build for a given project we can use the API again to ask about its artifacts. In our case the type is the pageload times from Lighthouse. From here we now have the build number from the most recent build of a given type. Some scripting allows us to narrow our results down to just the build types we are interested in. We can fetch up to 100 builds a given project a time. Fortunately CircleCI has an API that lets us automate the task of trying to find a build and view the artifacts from the run: Unfortunately it can be difficult to find a build in the CircleCI UI for a given project since there is no search, and only 20 builds at a time are shown in order of most recently run. Do you use CircleCI for your continuous workflows? Do you use their scheduled jobs? Recently we had a need to retrieve some performance benchmarking via a Lighthouse service that records page load times out to a text file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |