title: How to ignore a Android build variant in Azure build pipeline?
body: <p>I ran into a bit of an issue today with our Android application and Azure Pipelines today. When in the office, we all use Windows machines for development. Today, I was using my Macbook Pro to do a quick bug fix and push it up to Azure. In our <code>build.gradle</code>:</p>
  <pre><code>android {
      signingConfigs {
          release {
              storeFile file('C:\\android_keystore\\app_keystore.jks')
              storePassword 'password'
              keyAlias 'app'
              keyPassword 'password'
          }
      }
  
      buildTypes {
          release {
              signingConfig signingConfigs.release
              minifyEnabled true
              proguardFiles 'proguard-rules.pro'
          }
      }
  }
  
  </code></pre>
  <p>On our PCs, we all have the <code>app_keystore.jks</code> file in that directory and this obviously works fine for Windows computers and for our Azure Build Pipeline. But you can see the issue of how this will not work with macOS because there is no C drive.</p>
  <p>My first thought was to add another signing config aptly named <code>dev_macos</code> and corresponding  build variant to use exclusively on macOS: <code>~\\android_keystore\\app_keystore.jks</code> which works when building and signing locally in Android Studio; however, when we try and run our build pipeline on Azure DevOps, we get this error:</p>
  <pre><code>FAILURE: Build failed with an exception.
  
  * What went wrong:
  Execution failed for task ':app:validateSigning'.
  &gt; Keystore file 'C:\agent_android\_work\1\s\app\~\android_keystore\app_keystore.jks' not found for signing config 'dev_macos'.
  </code></pre>
  <p>Any ideas?</p>