Skip to main content
To use artifacts during snapshot setup, you will need to authenticate with them during repository configuration. If you need to store secrets for artifact authentication, you can either save them directly to the machine file system (e.g., in a file or by exporting environment variables) or use Devin’s Secret Manager. Below are sections for AWS, Azure, and Jfrog If your artifacts are on a private network, please see Deployment Options

Devin Machine Setup

To integrate with your artifact repositories, you’ll need to configure your Devin machine with the appropriate credentials and tools. There are two main ways to accomplish this:
  1. Use the integrated Terminal within Devin to install and configure artifact repository tools directly on the machine.
  2. Use the Setup Agent tab (located in the center column of Devin’s Machine during repo setup) and prompt Devin to assist with the setup.
Example of using Jfrog Repo Setup

Jfrog Artifactory

Step 1: Downloading CLI

Step 2: Download Artifact

AWS Code Artifact

Step 1: Downloading CLI

Step 2: Downloading Artifact

Azure Artifacts

Step 1: Downloading CLI

Step 2: Generating a PAT

Next, you’ll need to generate a personal access token (PAT).
  1. Log in to your Azure DevOps portal.
  2. In the top-right corner, click on your profile and select Security.
  3. In the Personal Access Tokens section, click on New Token.
  4. Set the scopes for the token. You’ll need at least the “Packaging (read)” scope to access Azure Artifacts.
  5. Save your PAT securely, as you will not be able to view it again.

Step 3: Configure .npmrc file

If you’re working with NuGet, you will need the following:
If you need Docker artifacts from Azure:
To get started with Devin Enterprise, contact our enterprise sales team.