Merging changes synced from https://github.com/MicrosoftDocs/azure-devops-docs-pr (branch live)

Author: Learn Build Service GitHub App

docs/pipelines/ecosystems/android.md

@@ -73,26 +73,28 @@ For more information about using Gradle tasks, see [Using tasks](https://docs.gr
 
 To run on a device instead of an emulator, the Android Application Package (APK) must be signed. Zipaligning reduces the RAM the application consumes. If your build doesn't already [sign and zipalign](https://developer.android.com/studio/publish/app-signing) the APK, add the [Android Signing](/azure/devops/pipelines/tasks/reference/android-signing-v3) task to the pipeline. For more information, see [Sign a mobile app](../apps/mobile/app-signing.md).
 
-For security, store the `jarsignerKeystorePassword` and `jarsignerKeyPassword` in [secret variables](../process/variables.md#secret-variables) and use those variables in your pipeline.
+For security, store the `apksignerKeystorePassword` and `apksignerKeyPassword` in [secret variables](../process/variables.md#secret-variables) and use those variables in your pipeline.
 
 ```yaml
-- task: AndroidSigning@2
+- task: AndroidSigning@3
   inputs:
-    apkFiles: '**/*.apk'
-    jarsign: true
-    jarsignerKeystoreFile: 'pathToYourKeystoreFile'
-    jarsignerKeystorePassword: '$(jarsignerKeystorePassword)'
-    jarsignerKeystoreAlias: 'yourKeystoreAlias'
-    jarsignerKeyPassword: '$(jarsignerKeyPassword)'
-    zipalign: true
+    apkFiles: '**/*.apk' # Specify the APK files to sign
+    apksignerKeystoreFile: 'pathToYourKeystoreFile' # Path to the keystore file
+    apksignerKeystorePassword: '$(apksignerKeystorePassword)' # Use a secret variable for security
+    apksignerKeystoreAlias: 'yourKeystoreAlias' # Alias for the keystore
+    apksignerKeyPassword: '$(apksignerKeyPassword)' # Use a secret variable for security
+    apksignerVersion: 'latest' # Use the latest version of apksigner
+    apksignerArguments: '--verbose' # Optional: Additional arguments for apksigner
+    zipalign: true # Enable zipalign to optimize APK
+    zipalignVersion: 'latest' # Use the latest version of zipalign
 ```
 
 ### Test on the Android emulator
 
 To install and run the Android emulator, add the [Bash](/azure/devops/pipelines/tasks/reference/bash-v3) task to your pipeline, and paste in the following code. The emulator starts as a background process and is available in later tasks. Arrange the emulator parameters to fit your testing environment.
 
 > [!IMPORTANT]
-> If you're using a [Microsoft-hosted agent](../agents/hosted.md), use the MacOS agent image with the Android emulator. Current Android emulators require hardware acceleration to start. Azure DevOps hosted Ubuntu agents do not support hardware acceleration. 
+> If you're using a [Microsoft-hosted agent](../agents/hosted.md), use the macOS agent image with the Android emulator. Current Android emulators require hardware acceleration to start. Azure DevOps hosted Ubuntu agents do not support hardware acceleration. 
 
 ```yaml
 - task: Bash@3

docs/pipelines/ecosystems/java.md

@@ -12,16 +12,16 @@ monikerRange: "<=azure-devops"
 
 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
 
-Use Azure Pipelines to automate the build, test, and deployment of Java applications. This article shows you how to set up a pipeline for Java projects using tools like Maven, Gradle, or Ant. You'll also learn how to deploy your app to Azure services such as App Service, Functions, or Kubernetes.
+Use Azure Pipelines to automate the build, test, and deployment of Java applications. This article explains how to set up a pipeline for Java projects using tools like Maven, Gradle, or Ant. You also learn how to deploy your app to Azure services like App Service, Functions, or Kubernetes.
 
-Use a pipeline to automatically:
+Use a pipeline to:
 
 * Build your project with [Maven](https://maven.apache.org/), [Gradle](https://gradle.org/), or [Ant](https://ant.apache.org/).
 * Run tests and code analysis tools.
 * Publish your app using a pipeline and Azure Artifacts.
 * Deploy your app to [Azure App Service](java-webapp.md), [Azure Functions](java-function.md), or [Azure Kubernetes Service](kubernetes/aks-template.md).
 
-If you're working on an Android project, see [Build, test, and deploy Android apps](android.md).
+If you work on an Android projects, see [Build, test, and deploy Android apps](android.md).
 
 ## Prerequisites
 
@@ -45,7 +45,7 @@ https://github.com/MicrosoftDocs/pipelines-java
 
 1. Follow the wizard steps, starting by selecting **GitHub** as the location of your source code. You might be redirected to GitHub to sign in. If so, enter your GitHub credentials.
 
-1. Select your repository. You might be redirected to GitHub to install the Azure Pipelines app. If so, select **Approve & install**.
+1. Select your repository. You might be redirected to GitHub to install the Azure Pipelines app. If so, select **Approve & install** to proceed.
 
 1. When you see the **Configure your pipeline** tab, select **Maven**, **Gradle**, or **Ant** depending on how you want to [build your code](#build-your-code).
 
@@ -95,9 +95,9 @@ You now have a working YAML pipeline (`azure-pipelines.yml`) in your repository
 
 ::: moniker range=">= azure-devops"
 
-Use Azure Pipelines to build Java apps without setting up any infrastructure. Build on Windows, Linux, or macOS images. The Microsoft-hosted agents in Azure Pipelines have modern JDKs and other tools for Java preinstalled. To check which versions of Java are installed, see [Microsoft-hosted agents](../agents/hosted.md).
+Use Azure Pipelines to build Java apps without setting up infrastructure. Build on Windows, Linux, or macOS images. Microsoft-hosted agents in Azure Pipelines have modern JDKs and other tools for Java preinstalled. To check which versions of Java are installed, see [Microsoft-hosted agents](../agents/hosted.md).
 
-To select the appropriate image, update the following snippet in your `azure-pipelines.yml` file.
+Select the appropriate image by updating the following snippet in your `azure-pipelines.yml` file.
 
 ```yaml
 pool:
@@ -106,17 +106,17 @@ pool:
 
 See [Microsoft-hosted agents](../agents/hosted.md) for a complete list of images.
 
-As an alternative to using Microsoft-hosted agents, set up [self-hosted agents](../agents/agents.md#install) with Java installed. You can also use self-hosted agents to save more time if you have a large repo or you run incremental builds.
+As an alternative to Microsoft-hosted agents, set up [self-hosted agents](../agents/agents.md#install) with Java installed. Use self-hosted agents to save time if you have a large repo or run incremental builds.
 
 ::: moniker-end
 
 ::: moniker range="< azure-devops"
 
-Builds run on a [self-hosted agent](../agents/agents.md#install). Ensure Java and the tools needed to build with your chosen method are installed on the agent's host.
+Builds run on a [self-hosted agent](../agents/agents.md#install). Ensure Java and the tools required for your chosen build method are installed on the agent's host.
 
 You can select your agent pool and the agent capabilities in the **Agent pool** and **Agent Specification** sections of the **Options** tab in the pipeline editor.
 
-For example to specify the agent pool and an agent with the Maven capability, add the following snippet to your `azure-pipelines.yml` file.
+For example, specify the agent pool and an agent with the Maven capability by adding the following snippet to your `azure-pipelines.yml` file.
 
 ```yaml
 pool: 
@@ -164,7 +164,7 @@ For a Gradle build, add the following task to the `azure-pipelines.yml` file. Fo
 
 ```yaml
 steps:
-- task: Gradle@2
+- task: Gradle@3
   inputs:
     workingDirectory: ''
     gradleWrapperFile: 'gradlew'

docs/pipelines/ecosystems/ruby.md

@@ -7,23 +7,23 @@ ms.author: vijayma
 author: vijayma
 ms.reviewer: dastahel
 ms.custom: freshness-fy22q2, kr2b-contr-experiment
-ms.date: 01/20/2022
+ms.date: 06/09/2025
 monikerRange: azure-devops
 ---
 
 # Build and test Ruby apps
 
 [!INCLUDE [version-eq-azure-devops](../../includes/version-eq-azure-devops.md)]
 
-This article explains how to automatically build Ruby projects.
+Learn how to use Azure Pipelines to build, test, and deploy your Ruby application. 
 
 ## Create the Azure Pipelines
 
-Do the following steps to set up a pipeline for a Ruby app.
+Follow these steps to set up a pipeline for a Ruby app.
 
 1. Sign in to your Azure DevOps organization and go to your project.
 
-1. Select **Pipelines** > **New pipeline**.
+1. Go to **Pipelines** > **New pipeline**.
 
 1. Select **GitHub** as the location of your source code.
 
@@ -33,14 +33,14 @@ Do the following steps to set up a pipeline for a Ruby app.
 
 1. Select the `Ruby` template for your pipeline.
 
-1. A YAML file gets generated. Select **Save and run** > **Commit directly to the main branch**, and then choose **Save and run** again.
+1. A YAML file is generated. Select **Save and run** > **Commit directly to the main branch**, and then select **Save and run** again.
 
 1. Wait for the run to finish.
 
 You have a working YAML file (`azure-pipelines.yml`) in your repository that's ready for you to customize.
 
 > [!TIP]
-> To make changes to the YAML file as described in this article, select the pipeline in the **Pipelines** page, and then **Edit** the `azure-pipelines.yml` file.
+> To make changes to the YAML file described in this article, select the pipeline on the **Pipelines** page, and then select **Edit** for the `azure-pipelines.yml` file.
 
 ## Build environment
 
@@ -50,18 +50,18 @@ For the exact versions of Ruby that are preinstalled, refer to [Microsoft-hosted
 
 ### Use a specific Ruby version
 
-Add the [Use Ruby Version](/azure/devops/pipelines/tasks/reference/use-ruby-version-v0) task to set the version of Ruby used in your pipeline. This snippet adds Ruby 2.4 or later to the path and sets subsequent pipeline tasks to use it.
+Add the [Use Ruby Version](/azure/devops/pipelines/tasks/reference/use-ruby-version-v0) task to set the Ruby version in your pipeline. This snippet adds Ruby 3.4 or later to the path and sets subsequent pipeline tasks to use it.
 
 ```yaml
-# https://learn.microsoft.com/azure/devops/pipelines/ecosystems/ruby
 pool:
-  vmImage: 'ubuntu-latest' # other options: 'macOS-latest', 'windows-latest'
+  vmImage: 'ubuntu-latest' 
 
 steps:
-- task: UseRubyVersion@0
+- task: UseRubyVersion@0 
   inputs:
-    versionSpec: '>= 2.5'
+    versionSpec: '>= 3.4' 
     addToPath: true
+  displayName: 'Set Ruby version'
 ```
 
 ### Install Rails
@@ -70,18 +70,18 @@ To install Rails, add the following snippet to your `azure-pipelines.yml` file.
 
 ```yaml
 - script: gem install rails && rails -v
-  displayName: 'gem install rails'
+  displayName: 'Install Rails'
 ```
 
 ### Install dependencies
 
-To use Bundler to install dependencies, add the following snippet to your `azure-pipelines.yml` file.
+Use Bundler to install dependencies by adding the following snippet to your `azure-pipelines.yml` file.
 
 ```yaml
 - script: |
-    CALL gem install bundler
+    gem install bundler
     bundle install --retry=3 --jobs=4
-  displayName: 'bundle install'
+  displayName: 'Install dependencies with Bundler'
 ```
 
 ### Run Rake
@@ -95,9 +95,9 @@ To execute Rake in the context of the current bundle (as defined in your Gemfile
 
 ### Publish test results
 
-The sample code includes unit tests written using [RSpec](https://rspec.info/). When Rake is run by the previous step, it runs the RSpec tests. The RSpec RakeTask in the Rakefile has been configured to produce JUnit style results using the RspecJUnitFormatter. 
+The sample code includes unit tests written with [RSpec](https://rspec.info/). When Rake runs in the previous step, it executes the RSpec tests. The RSpec RakeTask in the Rakefile is configured to produce JUnit-style results using the RspecJUnitFormatter. 
 
-Add the [Publish Test Results](/azure/devops/pipelines/tasks/reference/publish-test-results-v2) task to publish JUnit style test results to the server. You get a rich test reporting experience that you can use for troubleshooting any failed tests and for test timing analysis.
+Add the [Publish Test Results](/azure/devops/pipelines/tasks/reference/publish-test-results-v2) task to publish JUnit-style test results to the server. 
 
 ```yaml
 - task: PublishTestResults@2
@@ -110,16 +110,17 @@ Add the [Publish Test Results](/azure/devops/pipelines/tasks/reference/publish-t
 
 The sample code uses [SimpleCov](https://github.com/colszowka/simplecov) to collect code coverage data when unit tests get run. SimpleCov is configured to use Cobertura and HTML report formatters. 
 
-Add the [Publish Code Coverage Results](/azure/devops/pipelines/tasks/reference/publish-code-coverage-results-v1) task to publish code coverage results to the server. When you do so, coverage metrics can be seen in the build summary and HTML reports can be downloaded for further analysis.
+Add the [Publish Code Coverage Results](/azure/devops/pipelines/tasks/reference/publish-code-coverage-results-v2) task to publish code coverage results to the server. This lets you view coverage metrics in the build summary and download HTML reports for further analysis.
 
 ```yaml
-- task: PublishCodeCoverageResults@1
+- task: PublishCodeCoverageResults@2
   inputs:
     codeCoverageTool: Cobertura
     summaryFileLocation: '$(System.DefaultWorkingDirectory)/**/coverage.xml'
     reportDirectory: '$(System.DefaultWorkingDirectory)/**/coverage'
+    failIfCoverageEmpty: true 
 ```
 
 ## Build an image and push to container registry
 
-For your Ruby app, you can also [build an image](containers/build-image.md) and [push it to a container registry](containers/push-image.md).
+For your Ruby app, you can [build an image](containers/build-image.md) and [push it to a container registry](containers/push-image.md).