Repository navigation
Conversation
| // resolveAqlRepo determines the correct repo to use for AQL queries. | ||
| // Remote repos store files in a "<repo>-cache" local repo, so AQL must target that. | ||
| // Virtual and local repos are used as-is. | ||
| func resolveAqlRepo(repo string, servicesManager artifactory.ArtifactoryServicesManager) string { |
There was a problem hiding this comment.
Each unique registry repo triggers a GetRepository API call. If the same repo appears in multiple batches, it's queried repeatedly.
Is that possible to cache the result in a map[string]string at the call site in batchedAQLFetch
There was a problem hiding this comment.
we only call resolveAqlRepo once per distinct repo when building batches. this unique repo is found just before this workflow
|
|
||
| if pic.collectBuildInfo { | ||
| if err = pic.collectAndSaveBuildInfo(); err != nil { | ||
| log.Warn("pnpm install completed successfully, but build info collection failed:", err.Error()) |
There was a problem hiding this comment.
When collectAndSaveBuildInfo fails, the error is logged as a warning and nil is returned.
Should we consider surface the failure via log.Warn with a note about how to re-collect, or consider adding a --strict-build-info flag that makes this a hard failure.
WDYT?
There was a problem hiding this comment.
command at the moment is fail safe, we are not failing the original command incase the build-info collection fails, we can have a flag accross all package manager that will revert this operation if required
| } | ||
|
|
||
| func runPnpmLs(workingDir string) ([]pnpmLsProject, error) { | ||
| pnpmLsArgs := []string{"ls", "-r", "--depth", "Infinity", "--json"} |
There was a problem hiding this comment.
--json is already there, I am talking about --long, without long flag is it omitting resolved packages?
Description:
Support pnpm command for jfrog cli
Depends on: