Closed almalki closed 7 years ago
maurrysonn
commented
8 years ago Hi, I encounter exactly the same problem... My settings allows me to deploy the release build on the stage repo but impossible to download catalog.txt from the same stage repo.
Is it possible that artifactResolver.resolveArtifact(...) call from AbstractGitflowBasedRepositoryMojoattachExistingArtifacts() method doesn't care about auth settings ?
bvarner
commented
8 years ago Did you have the uniqueVersion of your stage URI (the last boolean) set to ::false, as you would your release repository?
maurrysonn
commented
8 years ago Hi,
The uniqueVersion property is well set to false for my release and stage repos.
And the resulting error is : Access denied to http://(stage repo)/..../my-artefact-version-catalog.txt
Cause : Error code 401, Unauthorized (with exceptions explained earlier)
My configuration :
<configuration>
<developmentBranchPattern>develop</developmentBranchPattern>
<releaseBranchPattern>release/(.*)</releaseBranchPattern>
<hotfixBranchPattern>hotfix/(.*)</hotfixBranchPattern>
<masterBranchPattern>master</masterBranchPattern>
<gitBranchExpression>${scmBranch}</gitBranchExpression>
<releaseDeploymentRepository>nexus::default::http://.../releases/::false</releaseDeploymentRepository>
<stageDeploymentRepository>nexus-Stage::default::http://.../stages/::false</stageDeploymentRepository>
<snapshotDeploymentRepository>nexus-Snapshot::default::http://.../snapshots/::true</snapshotDeploymentRepository>
<gitURLExpression>${project.scm.connection}</gitURLExpression>
</configuration>Thanks for your time !
bvarner
commented
8 years ago @maurrysonn If you wanted to play around in the code, or if you could provide details on your nexus setup (user account rights / roles / ssl vs. no ssl, repo setup) that would be super helpful.
On our jenkins server we use the same job to build all branches(using Folders Plugin), which means we use the same maven settings for all branches. The build for release branches are successfully deployed to artifactory (libs-stage-local) repo, which means the user has write access to the repo, however, when it comes to building the master branch, and when the plugin tries to promote-master, it fails with "Unauthorized" error when trying to get the artifact from the same repo..
In artifactory logs, it shows that the request is not authenticated:
20160823153848|2|REQUEST|[[redacted]]|non_authenticated_user|GET|/libs-stage-local/[[redacted]]-1.3-catalog.txt|HTTP/1.0|401|0
while the other request that are part of the deploy phase for release branches are authenticated:
20160823134403|180|REQUEST|[[redacted]]|jenkins|PUT|/libs-stage-local/[[redacted]]-1.3-catalog.txt.md5|HTTP/1.0|201|32
Here is the exception stacktrace: