Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] New maven sign and upload pipeline fail since 1.3.0 #1893

Closed
peterzhuamazon opened this issue Apr 2, 2022 · 1 comment · Fixed by #1954
Closed

[BUG] New maven sign and upload pipeline fail since 1.3.0 #1893

peterzhuamazon opened this issue Apr 2, 2022 · 1 comment · Fixed by #1954
Assignees
Labels
bug Something isn't working release v2.0.0

Comments

@peterzhuamazon
Copy link
Member

+ /var/jenkins/workspace/opensearch-maven-sign-and-stage/publish/stage-maven-release.sh /var/jenkins/workspace/opensearch-maven-sign-and-stage/artifacts/distribution-build-opensearch/1.3.0/1362/linux/x64/builds/maven-signed
Invalid directory /var/jenkins/workspace/opensearch-maven-sign-and-stage/artifacts/distribution-build-opensearch/1.3.0/1362/linux/x64/builds/maven-signed does not exist
usage: /var/jenkins/workspace/opensearch-maven-sign-and-stage/publish/stage-maven-release.sh [-h] [dir]
  dir     parent directory containing artifacts to org/opensearch namespace.
          example: dir = ~/.m2/repository where repository contains /org/opensearch
  -h      display help
Required environment variables:
SONATYPE_USERNAME - username with publish rights to a sonatype repository
SONATYPE_PASSWORD - password for sonatype
BUILD_ID - Build ID from CI so we can trace where the artifacts were built
STAGING_PROFILE_ID - Sonatype Staging profile ID
REPO_URL - repository URL without path, ex. https://aws.oss.sonatype.org/

After migrating the maven publish from internal infra repo to this build repo, the new pipeline is having issues in the last publish step. This forced us to keep using the old pipeline.

Needs to get this fixed soon.

Thanks.

@zelinh
Copy link
Member

zelinh commented Apr 18, 2022

This issue should have been fixed with PR #1954. Closing this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working release v2.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants