Skip to content

Latest commit

 

History

History
149 lines (109 loc) · 6.58 KB

DAY-z-15.md

File metadata and controls

149 lines (109 loc) · 6.58 KB
Raw

DAY-15 | Azure Artifacts

Azure Artifacts is a package management solution provided by Microsoft Azure. It enables you to create, host, and share packages within your organization. These packages can include libraries, frameworks, modules, or any other components required by your software projects.

Click Below to watch the video Tutorial

Watch the video

Getting Started For Maven & Nugget Packages

To start using Azure Artifacts and gain hands-on experience, follow these steps:

Azure Artifacts with Maven Packages

  1. Create an Azure Artifacts feed

Start by creating an Azure Artifacts feed in your Azure DevOps organization or Azure DevOps project. This feed will serve as a repository for your Maven packages.

  1. Generate Maven package credentials

To authenticate with your Azure Artifacts feed, you need to generate a Personal Access Token (PAT) in Azure DevOps. Follow these steps to generate the token:

  • Go to your Azure DevOps organization or project.
  • Click on your profile picture in the top-right corner and select "Personal access tokens".
  • Click on "New Token" and provide a name for the token.
  • Under "Scopes", select the appropriate permissions for your Maven packages (e.g., "Packaging (read, write, manage)").
  • Click on "Create" and make sure to copy the generated token value. You will need this later.
  1. Configure Maven settings.xml

In your Maven project, you need to configure the settings.xml file with the necessary Azure Artifacts feed information and credentials. Here's an example of how to configure it:

  • Open the settings.xml file located in your Maven installation's conf directory or in your user's .m2 directory.

  • Add a <servers> section if it doesn't exist already:

    <servers>
  <server>
    <id>azure-artifacts</id>
    <username>USERNAME</username>
    <password>PAT</password>
  </server>
</servers>

    Replace USERNAME with any value (it doesn't matter), and replace PAT with the Personal Access Token you generated in the previous step.

  • Add a <repositories> section if it doesn't exist already:

    <repositories>
  <repository>
    <id>azure-artifacts</id>
    <url>https://pkgs.dev.azure.com/ORGANIZATION/_packaging/FEEDNAME/maven/v1</url>
  </repository>
</repositories>

    Replace ORGANIZATION with your Azure DevOps organization name, and FEEDNAME with the name of your Azure Artifacts feed.

  1. Publish and consume Maven packages

With the configuration in place, you can now publish and consume Maven packages from your Azure Artifacts feed.

  • To publish a package, build your Maven project and execute the mvn deploy command. This will upload your package to the Azure Artifacts feed.

  • To consume a package, simply include the appropriate dependency in your pom.xml file. For example:

    <dependencies>
  <dependency>
    <groupId>com.example</groupId>
    <artifactId>my-package</artifactId>
    <version>1.0.0</version>
  </dependency>
</dependencies>

    Replace com.example, my-package, and 1.0.0 with the actual coordinates of the package you want to consume.

That's it! You have now configured Azure Artifacts to work with Maven packages. Make sure to replace the placeholder values with your actual Azure DevOps organization, feed name, and credentials.

Azure Artifacts with NPM Packages

Step 1: Create an Azure Artifacts feed

  1. Sign in to the Azure portal using your Azure account.
  2. Open the Azure Artifacts service.
  3. Click on "New feed" to create a new feed.
  4. Provide a name for your feed, select the appropriate organization, and choose a project to associate with the feed.
  5. Configure other settings such as visibility, upstream sources, etc., based on your requirements.
  6. Click on "Create" to create the feed.

Step 2: Configure package sources

  1. After creating the feed, navigate to its settings page.
  2. Click on "Connect to feed" to obtain the package source URL and authentication details.
  3. Make a note of the URL as you will need it for configuring your project to use the feed.

Step 3: Publish packages

  1. Choose the package manager that aligns with your project's technology stack (e.g., npm, NuGet, Maven).
  2. For npm, use the following command to publish packages to your Azure Artifacts feed: 
    npm publish --registry=<feed-url> --scope=@<organization-scope>
    Replace <feed-url> with the package source URL obtained in the previous step and <organization-scope> with the appropriate scope for your organization.

Step 4: Consume packages

To consume packages from your Azure Artifacts feed, configure your project to use the feed as a package source. The configuration steps vary depending on the package manager:

  • npm: Create or update a .npmrc file in your project's root directory and add the following line:

    registry=<feed-url>

    Replace <feed-url> with the package source URL.

  • NuGet: Add a NuGet configuration file (NuGet.config) to your project and specify the package source as follows:

    <configuration>
  <packageSources>
    <add key="<source-name>" value="<feed-url>" />
  </packageSources>
</configuration>

    Replace <source-name> with a name for the package source and <feed-url> with the package source URL.

  • Maven: Add the package source to your project's settings.xml file, typically located in your .m2 directory. Add the following section:

    <settings>
  <profiles>
    <profile>
      <repositories>
        <repository>
          <id><source-name></id>
          <url><feed-url></url>
        </repository>
      </repositories>
    </profile>
  </profiles>
</settings>

    Replace <source-name> with a name for the package source and <feed-url> with the package source URL.

Step 5: Install and use packages

Once your project is configured to use Azure Artifacts as a package source, you can install and use packages from the feed. Refer to the documentation of your specific package manager for instructions on installation and usage.

Please note that these steps provide a general overview of working with Azure Artifacts and package management. The process may vary depending on your project's requirements and the package manager you are using. For more detailed instructions, consult the official documentation and guides specific to your chosen package manager and Azure Artifacts.