|
|
|
[
Permlink
| « Hide
]
Robin Shen [15/Apr/24 11:28 AM]
Please specify artifatory server url as "https://<artifactory server url>/artifactory" to see if it works.
Can you please specify url using below format, the above you mentioned is confusing:
my url is as below: https://artifactory.dev/ Specify url as "https://artifactory.dev/artifactory".
okay, I tried this its having same error with below html details
publish_to_fis_dev_artifactory' is failed: Failed to deploy artifacts: <!doctype html><html lang="en"><head><title>HTTP Status 400 - Bad Request</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 400 - Bad Request</h1></body></html> I tried again and checked on artifactory, its uploading the folder but not all contents of the folder.
There are 2 folders and 2 files under the source path. Also getting below error at the end of the step: java.net.SocketException: Software caused connection abort: socket write error caused by: Software caused connection abort: socket write error Thanks for the update. Will investigate the issue and let you know the result.
Please check if QB14 works at your side. I tested with Artifactory 7.77.9 version and it can publish artifacts without any issues here.
I am using QB12.0.12, can you please try to check on this version of QB. Because for upgrading to QB14 will take some time for us.
I tried on a test instance where QB 13.0.40 is installed and the issue is same as above
java.net.SocketException: Software caused connection abort: socket write error caused by: Software caused connection abort: socket write error
Are you able to choose repository as indicated by attached screenshot?
Yes, I am able to choose repository.
Also there are 2 folders in source directory out of which only 1 is getting uploaded
Get this reproduced at my side with large files. And the problem is now fixed in QB 14.0.9:
https://build.pmease.com/build/5885 |