Unable to pull GO package after publishing about project-examples HOT 2 CLOSED

Greetings,

Regarding point 1, while publishing build information is not obligatory, it can prove beneficial for future reference, aiding in identifying distinctions among other published builds. For detailed insights into builds, kindly refer to the following link: https://www.buildinfo.org/#

Point 2 emphasizes that the JSON serves as the actual build information.
You can view its content under “builds” tab in the UI or via a REST
As for point 3, the choice of repository type depends on your requirements. If resource retrieval from a remote repository or registry is essential, a remote repository is advisable. Alternatively, for internal packages, especially private ones, a local repository is recommended. A viable approach is to employ a virtual repository, enabling a centralized point capable of fetching both internal and external packages.

In point 4, have you appropriately configured your remote repository on the virtual repository?

Best regards.

from project-examples.

@yonarbel ,

Thank you for responding. The answers were somewhat helpful.
Regrading your question about point 4, I am not sure what would be correct remote repository URL, I tried several. I am reaching out to engineering team to get the answer.

Although this raises another question. Is there a way to resolve all dependencies locally and then use those inside package(zip) file before publishing to artifactory? I am not asking about or looking for vendoring. In fact, whole idea is to avoid that.

from project-examples.