-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Affects Version/s: 6.5.0
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Severity:Critical
-
Regression:Yes
Scenario:
- Selected repository for indexing in Xray
- Created Watch with policy
- In policy, checked 'Block Unscanned Artifacts' field (see screenshot)
- Executed build with Docker Image against Artifactory
Push stage in Jenkins Pipeline ****************************** stage('Deploy'){ steps { script { buildInfo = rtDocker.push "${privateDockerRegistry}/${params.DOCKER_REPO}/build-${JOB_NAME}:${BUILD_NUMBER}", "docker" } } }
- Build Info is not properly deployed to Artifactory
Pushing image: 10.70.30.220:8081/docker/build-docker-example:188 Could not find corresponding manifest.json file in Artifactory. Could not find docker image: 10.70.30.220:8081/docker/build-docker-example:188in Artifactory. Successfully pushed docker image: 10.70.30.220:8081/docker/build-docker-example:188
- When creating the build-info.json file, is not possible to get the manifest.json file (blocking policy configured in Xray):
Artifactory logs **************** 2018-10-07 13:21:14,694 [http-nio-8081-exec-11] [WARN ] (o.a.r.ArtifactoryResponseBase:107) - Sending HTTP error code 403: Artifact download request rejected: build-docker-example/188/manifest.json was not downloaded due to the download blocking policy configured in Xray for docker-local. Artifactory 'request.log' ************************* 20181007135354|60|REQUEST|10.70.30.5|admin|PUT|/api/docker/docker/v2/build-docker-example/manifests/193|HTTP/1.1|201|949 20181007135355|875|REQUEST|10.70.30.5|admin|GET|/docker/docker/build-docker-example/193/manifest.json|HTTP/1.1|404|0 20181007135355|479|REQUEST|10.70.30.5|admin|GET|/docker/build-docker-example/193/manifest.json|HTTP/1.1|403|0
- Build appears with 0 (zero) artifacts in Artifactory (see screenshots)
- Build appears disconnected from it's children in Xray (see screenshots)