[JENKINS-62040] pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan - Jenkins Jira

XML

Word

Printable

Details

Type: Bug
Status: Reopened (View Workflow)
Priority: Trivial
Resolution: Unresolved
Component/s: anchore-container-scanner-plugin
Labels:
None
Environment:
openstack, linux

Enterprise Client Version: 0.6.0
Anchore Engine Version: 0.6.0
Anchore DB Version: 0.0.12

Similar Issues:

Show

Description

1. Jenkins anchore plugin scan docker image,
then archive artifacts: '**/*.json',
But no anchore.json archived, this anchore.json is missing

2. Jenkins anchore plugin scan docker image,
then archive artifacts: 'AnchoreReport.${JOB_BASE_NAME}_${BUILD_NUMBER}/*.json',
No artifacts found that match the file pattern "AnchoreReport.CSF-Anchore-Scan_82/*.json". Configuration error?

13:07:39 ‘anchore*.json’ doesn’t match anything*

13:07:39* No artifacts found that match the file pattern "anchore*.json". Configuration error?

So, how to archive the anchore.json file?

Enterprise Client Version: 0.6.0
Anchore Engine Version: 0.6.0
Anchore DB Version: 0.0.12

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

csfAnchoreScan.groovy
3 kB
2020-04-26 03:03
Jenkinsfile.txt
2 kB
2020-04-26 02:59

Activity

Ascending order - Click to sort in descending order

Anthony Guo created issue - 2020-04-24 08:02

Marky Jackson added a comment - 2020-04-24 12:08

Can you kindly share your jenkinsfile

Marky Jackson added a comment - 2020-04-24 12:08 Can you kindly share your jenkinsfile

Marky Jackson made changes - 2020-04-24 12:08

Field	Original Value	New Value
Status	Open [ 1 ]	In Progress [ 3 ]

Anthony Guo made changes - 2020-04-26 02:59

Attachment

Jenkinsfile.txt [ 51073 ]

Anthony Guo made changes - 2020-04-26 03:00

Attachment

csfAnchoreScan.groovy [ 51074 ]

Anthony Guo made changes - 2020-04-26 03:03

Attachment

csfAnchoreScan.groovy [ 51074 ]

Anthony Guo made changes - 2020-04-26 03:03

Attachment

csfAnchoreScan.groovy [ 51075 ]

Anthony Guo added a comment - 2020-04-26 03:03

uploaded Jenkinsfile and csfAnchoreScan.groovy jequals5

Anthony Guo added a comment - 2020-04-26 03:03 uploaded Jenkinsfile and csfAnchoreScan.groovy jequals5

Marky Jackson added a comment - 2020-04-26 04:45

What version of Jenkins are you on?

Marky Jackson added a comment - 2020-04-26 04:45 What version of Jenkins are you on?

Anthony Guo added a comment - 2020-04-26 05:00

Jenkins ver. 2.204.2

Anthony Guo added a comment - 2020-04-26 05:00 Jenkins ver. 2.204.2

Anthony Guo added a comment - 2020-04-26 06:22 - edited

No artifacts found that match the file pattern "**/anchore*.json" . Configuration error?
No artifacts found that match the file pattern "anchore*.json" . Configuration error?

No artifacts found that match the file pattern "*.json" . Configuration error?

Anthony Guo added a comment - 2020-04-26 06:22 - edited No artifacts found that match the file pattern "** /anchore *.json" . Configuration error? No artifacts found that match the file pattern "anchore*.json" . Configuration error? No artifacts found that match the file pattern "*.json" . Configuration error?

Anthony Guo made changes - 2020-04-26 06:25

Description

1. Jenkins anchore plugin scan docker image,
then archive artifacts: '**/*.json',
But no anchore.json archived, this anchore.json is missing

2. Jenkins anchore plugin scan docker image,
then archive artifacts: 'AnchoreReport.${JOB_BASE_NAME}_${BUILD_NUMBER}/*.json',
No artifacts found that match the file pattern "AnchoreReport.CSF-Anchore-Scan_82/*.json". Configuration error?

So, how to archive the anchore.json file?

Enterprise Client Version: 0.6.0
Anchore Engine Version: 0.6.0
Anchore DB Version: 0.0.12

1. Jenkins anchore plugin scan docker image,
then archive artifacts: '***/**.json',
But no anchore.json archived, this anchore.json is missing

2. Jenkins anchore plugin scan docker image,
then archive artifacts: 'AnchoreReport.${JOB_BASE_NAME}_${BUILD_NUMBER}/*.json',
No artifacts found that match the file pattern "AnchoreReport.CSF-Anchore-Scan_82/*.json". Configuration error?

So, how to archive the anchore.json file?

Enterprise Client Version: 0.6.0
Anchore Engine Version: 0.6.0
Anchore DB Version: 0.0.12

Anthony Guo added a comment - 2020-04-26 06:33 - edited

From jenkins console log:
.....
20:49:05 Archiving artifacts
20:49:05 ‘anchore*.json’ doesn’t match anything
20:49:05 No artifacts found that match the file pattern "anchore*.json". Configuration error?
.....

But then ====>>>>>> From job summary page: (sometimes there are build artifacts, sometimes no)

Build Artifacts
anchore_gates.json 51.93 KB view
anchore_security.json 31.12 KB view
anchoreengine-api-response-evaluation-1.json 58.77 KB view
anchoreengine-api-response-evaluation-2.json 60.36 KB view
anchoreengine-api-response-evaluation-3.json 22.36 KB view
anchoreengine-api-response-vulnerabilities-1.json 54.31 KB view
anchoreengine-api-response-vulnerabilities-2.json 57.44 KB view
anchoreengine-api-response-vulnerabilities-3.json 3.32 KB view

https://build8.cci.myCompany.net/job/CTO/job/CSF/job/Common/job/CSF-CHARTS-PROMOTE/2648/artifact/AnchoreReport.CSF-CHARTS-PROMOTE_2648/anchore_security.json
https://build8.cci.myCompany.net/job/CTO/job/CSF/job/Common/job/CSF-CHARTS-PROMOTE/2648/artifact/AnchoreReport.CSF-CHARTS-PROMOTE_2648/anchore_gates.json

Anthony Guo added a comment - 2020-04-26 06:33 - edited From jenkins console log: ..... 20:49:05 Archiving artifacts 20:49:05 ‘anchore*.json’ doesn’t match anything 20:49:05 No artifacts found that match the file pattern "anchore*.json". Configuration error? ..... But then ====>>>>>> From job summary page: (sometimes there are build artifacts, sometimes no) Build Artifacts anchore_gates.json 51.93 KB view anchore_security.json 31.12 KB view anchoreengine-api-response-evaluation-1.json 58.77 KB view anchoreengine-api-response-evaluation-2.json 60.36 KB view anchoreengine-api-response-evaluation-3.json 22.36 KB view anchoreengine-api-response-vulnerabilities-1.json 54.31 KB view anchoreengine-api-response-vulnerabilities-2.json 57.44 KB view anchoreengine-api-response-vulnerabilities-3.json 3.32 KB view https://build8.cci.myCompany.net/job/CTO/job/CSF/job/Common/job/CSF-CHARTS-PROMOTE/2648/artifact/AnchoreReport.CSF-CHARTS-PROMOTE_2648/anchore_security.json https://build8.cci.myCompany.net/job/CTO/job/CSF/job/Common/job/CSF-CHARTS-PROMOTE/2648/artifact/AnchoreReport.CSF-CHARTS-PROMOTE_2648/anchore_gates.json

Anthony Guo made changes - 2020-04-26 07:00

Description

1. Jenkins anchore plugin scan docker image,
then archive artifacts: '***/**.json',
But no anchore.json archived, this anchore.json is missing

2. Jenkins anchore plugin scan docker image,
then archive artifacts: 'AnchoreReport.${JOB_BASE_NAME}_${BUILD_NUMBER}/*.json',
No artifacts found that match the file pattern "AnchoreReport.CSF-Anchore-Scan_82/*.json". Configuration error?

*13:07:39* ‘anchore*.json’ doesn’t match anything*13:07:39* No artifacts found that match the file pattern "anchore*.json". Configuration error?

So, how to archive the anchore.json file?

Enterprise Client Version: 0.6.0
Anchore Engine Version: 0.6.0
Anchore DB Version: 0.0.12

Anthony Guo made changes - 2020-04-26 07:00

Description

1. Jenkins anchore plugin scan docker image,
then archive artifacts: '***/**.json',
But no anchore.json archived, this anchore.json is missing

2. Jenkins anchore plugin scan docker image,
then archive artifacts: 'AnchoreReport.${JOB_BASE_NAME}_${BUILD_NUMBER}/*.json',
No artifacts found that match the file pattern "AnchoreReport.CSF-Anchore-Scan_82/*.json". Configuration error?

*13:07:39* ‘anchore*.json’ doesn’t match anything*13:07:39* No artifacts found that match the file pattern "anchore*.json". Configuration error?

So, how to archive the anchore.json file?

Enterprise Client Version: 0.6.0
Anchore Engine Version: 0.6.0
Anchore DB Version: 0.0.12

1. Jenkins anchore plugin scan docker image,
then archive artifacts: '***/**.json',
But no anchore.json archived, this anchore.json is missing

2. Jenkins anchore plugin scan docker image,
then archive artifacts: 'AnchoreReport.${JOB_BASE_NAME}_${BUILD_NUMBER}/*.json',
No artifacts found that match the file pattern "AnchoreReport.CSF-Anchore-Scan_82/*.json". Configuration error?

*13:07:39* ‘anchore*.json’ doesn’t match anything*

13:07:39* No artifacts found that match the file pattern "anchore*.json". Configuration error?

So, how to archive the anchore.json file?

Enterprise Client Version: 0.6.0
Anchore Engine Version: 0.6.0
Anchore DB Version: 0.0.12

Marky Jackson added a comment - 2020-04-26 07:04

I will attempt to duplicate your setup later this AM

Marky Jackson added a comment - 2020-04-26 07:04 I will attempt to duplicate your setup later this AM

Anthony Guo added a comment - 2020-04-28 08:36

any update?

any clue?

Thanks!

Anthony Guo added a comment - 2020-04-28 08:36 any update? any clue? Thanks!

Marky Jackson added a comment - 2020-04-28 13:36

My apologies for the delayed reply.

I tried reproducing this and could not. In looking at your Jenkinsfile, I see that you are using a library, that could be suspect. Can you provide the logs from Managed Jenkins>System Logs

Marky Jackson added a comment - 2020-04-28 13:36 My apologies for the delayed reply. I tried reproducing this and could not. In looking at your Jenkinsfile, I see that you are using a library, that could be suspect. Can you provide the logs from Managed Jenkins>System Logs

Tony Wen added a comment - 2020-04-30 01:58

From anchore plugin src, seems anchore plugin itself does archiving some json results, and in then end, clear the anchor folder, could it be the cause? If it is, why we can see them sometime?

Tony Wen added a comment - 2020-04-30 01:58 From anchore plugin src, seems anchore plugin itself does archiving some json results, and in then end, clear the anchor folder, could it be the cause? If it is, why we can see them sometime?

Marky Jackson added a comment - 2020-04-30 02:29

walthhy you are correct. A directory with all the vulnerability data is what you are referring to, in most cases you should not see that because of the clean up that takes place. In some edge cases, that clean up doesn't happen and that is why you see it.

Marky Jackson added a comment - 2020-04-30 02:29 walthhy you are correct. A directory with all the vulnerability data is what you are referring to, in most cases you should not see that because of the clean up that takes place. In some edge cases, that clean up doesn't happen and that is why you see it.

Marky Jackson added a comment - 2020-04-30 12:43

I will leave.this open in till Friday. I think the main answer is mine from yesterday.
Let me know if I am misinterpreting

Marky Jackson added a comment - 2020-04-30 12:43 I will leave.this open in till Friday. I think the main answer is mine from yesterday. Let me know if I am misinterpreting

Tony Wen added a comment - 2020-05-01 01:12

jequals5, thanks. we still have questions, forgive me not familiar with plugin code.

Could you help us identifying under which condition we will have aritifacts.

which artifacts/json report will be archived automatically under which condition
when clean up case will be executed and when not?
is it possible to keep those json output always?

Tony Wen added a comment - 2020-05-01 01:12 jequals5 , thanks. we still have questions, forgive me not familiar with plugin code. Could you help us identifying under which condition we will have aritifacts. which artifacts/json report will be archived automatically under which condition when clean up case will be executed and when not? is it possible to keep those json output always?

Marky Jackson added a comment - 2020-05-01 01:16

The scan keeps a report of vulnerabilities and policy evaluations. This happens during each scan
Clean up should always take place unless there was some edge case that stopped that from happening. Network latency, Jenkins hiccup, etc.
Depending on how your scan job is configured, all jobs should retain the output of the report and there is a historical linkage in your workspace.

Hope that helps

Marky Jackson added a comment - 2020-05-01 01:16 The scan keeps a report of vulnerabilities and policy evaluations. This happens during each scan Clean up should always take place unless there was some edge case that stopped that from happening. Network latency, Jenkins hiccup, etc. Depending on how your scan job is configured, all jobs should retain the output of the report and there is a historical linkage in your workspace. Hope that helps

Marky Jackson made changes - 2020-05-05 02:09

Resolution		Cannot Reproduce [ 5 ]
Status	In Progress [ 3 ]	Closed [ 6 ]

Anthony Guo added a comment - 2020-05-06 03:02

Hi jequals5 , How to config the job to keep the output report (*.json files) ?

Anthony Guo added a comment - 2020-05-06 03:02 Hi jequals5 , How to config the job to keep the output report (*.json files) ?

Anthony Guo made changes - 2020-05-07 06:40

Resolution	Cannot Reproduce [ 5 ]
Status	Closed [ 6 ]	Reopened [ 4 ]

Marky Jackson made changes - 2020-05-07 08:19

Priority

Blocker [ 1 ]

Trivial [ 5 ]

Marky Jackson added a comment - 2020-05-07 08:21

I would need to test that. I can do that but it will be a couple of days due to other priorities.

i changed the severity of this because saving the data is not the intended use case.

i will update in a day of 2

Marky Jackson added a comment - 2020-05-07 08:21 I would need to test that. I can do that but it will be a couple of days due to other priorities. i changed the severity of this because saving the data is not the intended use case. i will update in a day of 2

Marky Jackson made changes - 2020-05-15 19:20

Assignee

Marky Jackson [ jequals5 ]

Tony Wen made changes - 2020-05-18 04:22

Comment

[ Hi, [~jequals5], I found more interesting things on our system.

Anchore reports related artifacts got published and desplayed well, however when there's a new scan/build finished on the same jenkins jobs, previous artifacts are missing. we can only see the details for the latest scan, it is exepected? i thought artifacts should be maintained per build, should not over-writed/deleted by other builds. ]

People

Assignee:: Unassigned

Reporter:: Anthony Guo

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2020-04-24 08:02

Updated:: 2020-05-18 04:22