Adding Private Repositories to Recon
Recon pro lets you scaffold and run jobs for private repositories
Introduction
With the free version of Recon you can build test handlers for any public Foundry repository. The pro version of Recon expands on this by allowing you to build a test handler for any private repository along with using webhooks to automatically run jobs on these repositories, among other things.
In this tutorial we’ll go over how to add private repositories to Recon so you can start building test handlers and running jobs with them.
Private Repos
First you’ll need to navigate to the Private Repos page after logging into Recon. There you’ll be greeted by the following Add Recon to your Repos button to add Recon as a GitHub app that has access to the repositories you choose:
This will redirect you to GitHub where you’ll be prompted to select the organizations you want to add Recon to.
On the next screen you’ll be asked which repositories you’d like to add Recon to. You can either add it to all of the repositories you have access to in your organization or only select repositories. For this tutorial we’ll just be adding Recon to a single repository but the process is the same for adding all repositories.
After clicking Install GitHub adds the Recon app to your repository and it will now show up on the Private Repos page under the Build From Private Repos section.
You can now build handlers for the private repositories you’ve added by clicking the repository name in the Build From Private Repos section. This will redirect you to the following page:
where you can build your handlers from a non-default branch (coming soon) or you can use the default branch of the repository by clicking Add Branch to Recon. This will give you a popup similar to the one below (depending on your browser) that indicates that the job to build handlers for your repo was submitted to the Recon cloud service.
Once the job is completed it will be added to your handlers on the left-hand side navigation menu under Build your Handlers at the bottom of the list.
You’re now all set to start building invariant/fuzz test handlers for your repository and running jobs in minutes!