[JIRA] (JENKINS-8424) Permission denied to upload artifacts to Nexus

15 views
Skip to first unread message

camposabates@gmail.com (JIRA)

unread,
Oct 28, 2019, 9:50:03 AM10/28/19
to jenkinsc...@googlegroups.com
pau sabats updated an issue
 
Jenkins / Bug JENKINS-8424
Permission denied to upload artifacts to Nexus
Change By: pau sabats
Priority: Major Critical
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

camposabates@gmail.com (JIRA)

unread,
Oct 28, 2019, 10:01:05 AM10/28/19
to jenkinsc...@googlegroups.com
pau sabats commented on Bug JENKINS-8424
 
Re: Permission denied to upload artifacts to Nexus

Same problem of access denied both using maven or curl in order to upload an artifact to Nexus from or bat() sentence using Jenkinsfile.

Using the curl command in a terminal works:

"> curl -v  -u user:passwd --upload-file c:\path\file.zip http://localnexus:80801/file.zip"

Nevertheless, the same command in a jenkinsfile returns access denied without any more information.

So...the problem is not just for maven uploads, because I was uploading a zip of a netcore raw artifact using 'curl'.

Weird part is that it worked some days ago.

Now all my jenkinsfiles uploading to nexus doesn't work so I augmented the priority of the issue to critical, because it can be even blocker.

 

 

camposabates@gmail.com (JIRA)

unread,
Oct 28, 2019, 11:32:03 AM10/28/19
to jenkinsc...@googlegroups.com
pau sabats started work on Bug JENKINS-8424
 
Change By: pau sabats
Status: Open In Progress

camposabates@gmail.com (JIRA)

unread,
Oct 28, 2019, 11:32:04 AM10/28/19
to jenkinsc...@googlegroups.com

camposabates@gmail.com (JIRA)

unread,
Oct 28, 2019, 11:50:03 AM10/28/19
to jenkinsc...@googlegroups.com
 
Re: Permission denied to upload artifacts to Nexus

Workaround solution:

(Reproduced the problem using the latest docker version of Jenkins using docker for windows.)

The problem is related with a misconfiguration of jenkins' connection with Nexus when various user sessions are connected to the machine.

I've tested that when two different users are using jenkins, each within their own session, the problem will occur and it will be reproduced in both users. So when the machine is restarted, this "internal bug configuration is cleaned", and the user can deploy to Nexus. But if another user logs-in, the problem may happen.

Waiting if someone who has this issue can test if restarting the machine (not just jenkins or nexus) solves the problem, and if various user sessions have used the machine.

 

 

 

 

camposabates@gmail.com (JIRA)

unread,
Nov 22, 2019, 5:26:04 AM11/22/19
to jenkinsc...@googlegroups.com
pau sabats assigned an issue to Unassigned
 
Change By: pau sabats
Assignee: pau sabats

camposabates@gmail.com (JIRA)

unread,
Nov 22, 2019, 6:16:08 AM11/22/19
to jenkinsc...@googlegroups.com
pau sabats stopped work on Bug JENKINS-8424
 
Change By: pau sabats
Status: In Progress Open

camposabates@gmail.com (JIRA)

unread,
Nov 22, 2019, 6:49:03 AM11/22/19
to jenkinsc...@googlegroups.com
pau sabats updated an issue
Change By: pau sabats
Priority: Critical Blocker
Reply all
Reply to author
Forward
0 new messages