XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Environment:
      Android & Docker, on Ubuntu 16.04

      Description

      Deploying from Bitrise CI platform results in the following:

      [19:04:23]: ▸ :algoliasearch:uploadArchives
      [19:04:23]: ▸ Ready to deploy with "algolia":"UULpJFttZ3s8Up" ...
      [19:04:24]: ▸ Could not transfer artifact com.algolia:algoliasearch-android:aar:3.20.6 from/to remote (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/algolia/algoliasearch-android/3.20.6/algoliasearch-android-3.20.6.aar. Return code is: 401, ReasonPhrase: Unauthorized.
      [19:04:24]: ▸ Could not transfer artifact com.algolia:algoliasearch-android:pom:3.20.6 from/to remote (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/algolia/algoliasearch-android/3.20.6/algoliasearch-android-3.20.6.pom. Return code is: 401, ReasonPhrase: Unauthorized.
      [19:04:24]: ▸ Could not transfer artifact com.algolia:algoliasearch-android:jar:javadoc:3.20.6 from/to remote (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/algolia/algoliasearch-android/3.20.6/algoliasearch-android-3.20.6-javadoc.jar. Return code is: 401, ReasonPhrase: Unauthorized.
      [19:04:24]: ▸ Could not transfer artifact com.algolia:algoliasearch-android:jar.asc:javadoc:3.20.6 from/to remote (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/algolia/algoliasearch-android/3.20.6/algoliasearch-android-3.20.6-javadoc.jar.asc. Return code is: 401, ReasonPhrase: Unauthorized.
      [19:04:24]: ▸ Could not transfer artifact com.algolia:algoliasearch-android:aar.asc:3.20.6 from/to remote (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/algolia/algoliasearch-android/3.20.6/algoliasearch-android-3.20.6.aar.asc. Return code is: 401, ReasonPhrase: Unauthorized.
      [19:04:25]: ▸ Could not transfer artifact com.algolia:algoliasearch-android:pom.asc:3.20.6 from/to remote (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/algolia/algoliasearch-android/3.20.6/algoliasearch-android-3.20.6.pom.asc. Return code is: 401, ReasonPhrase: Unauthorized.
      [19:04:25]: ▸ :algoliasearch:uploadArchives FAILED
      [19:04:25]: ▸ FAILURE: Build failed with an exception.
      [19:04:25]: ▸ * What went wrong:
      [19:04:25]: ▸ Execution failed for task ':algoliasearch:uploadArchives'.
      [19:04:25]: ▸ > Could not publish configuration 'archives'
      [19:04:25]: ▸ > Failed to deploy artifacts: Could not transfer artifact com.algolia:algoliasearch-android:aar:3.20.6 from/to remote (https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/local/staging/deploy/maven2/com/algolia/algoliasearch-android/3.20.6/algoliasearch-android-3.20.6.aar. Return code is: 401, ReasonPhrase: Unauthorized.
       

      I checked the blog post on the issue, the existing issues on your tracker, and various SO answers along the way. Nothing helped.

      Running our release script locally (both on Debian or MacOS) works fine, as running the workflow locally with bitrise CLI. So I wonder what could cause the issue, as bitrise runs on "Android & Docker, on Ubuntu 16.04" I would be surprised if the platform was not compatible with Sonatype in any way.

      Do you have an idea what could be the culprit here? Do you have other OSS-Sonatype users that successfully deployed from bitrise, or would we need to move from Sonatype to something else if our CI needs to stay on bitrise?

       

      Thanks for your help.

        Attachments

          Activity

            People

            Assignee:
            jorlina Joel Orlina
            Reporter:
            pln PLN
            Last Updated By:
            Joel Orlina
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title