Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add three new sast scans to required tasks #95

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

simonbaird
Copy link
Contributor

@simonbaird simonbaird commented Dec 18, 2024

Use an effective on date of March 1st to give people time to get them added them to their pipeline definitions.

Note the tests will be required, meaning if they're not included EC will produce a "required task not found" violation, but they are "informative" only, meaning if they produce a failure status, EC will not produce a violation.

I didn't add the new tasks to the fbc pipeline required task list since I think sast scans are likely not useful there, and because the existing sast-snyk-check scan is already not required for fbc.

Handy queries to help confirm this change:

yq '.pipeline-required-tasks | to_entries[].value |[.[0].tasks - .[1].tasks]' data/required_tasks.yml
yq '.required-tasks|[.[0].tasks - .[1].tasks]' data/required_tasks.yml

Ref: https://issues.redhat.com/browse/EC-887
Ref: https://issues.redhat.com/browse/EC-888
Ref: https://issues.redhat.com/browse/EC-889

Use an effective on date of March 1st to give people time to get
them added them to their pipeline definitions.

Note the tests will be required, meaning if they're not included EC
will produce a "required task not found" violation, but they are
"informative" only, meaning if they produce a failure status, EC
will not produce a violation.

I didn't add the new tasks to the fbc pipeline required task list
since I think sast scans are likely not useful there, and because
the existing sast-snyk-check scan is already not required for fbc.

Handy queries to help confirm this change:
  yq '.pipeline-required-tasks | to_entries[].value |[.[0].tasks - .[1].tasks]' data/required_tasks.yml
  yq '.required-tasks|[.[0].tasks - .[1].tasks]' data/required_tasks.yml

Ref: https://issues.redhat.com/browse/EC-887
Ref: https://issues.redhat.com/browse/EC-888
Ref: https://issues.redhat.com/browse/EC-889
@simonbaird
Copy link
Contributor Author

I didn't remove the stale entries yet.

@simonbaird
Copy link
Contributor Author

I didn't remove the stale entries yet.

Actually I'll save that for another PR.

@simonbaird
Copy link
Contributor Author

This might need a rebase on #96 (or vice versa).

@p-rog
Copy link

p-rog commented Jan 8, 2025

+1 to this change

@kdudka
Copy link

kdudka commented Jan 9, 2025

@simonbaird Is there any automation that will add the new tasks to existing build pipelines of projects that do builds in Konflux already? Or do we expect engineers to update all the pipeline definitions manually to insert the new tasks?

@lcarva
Copy link
Collaborator

lcarva commented Jan 9, 2025

@simonbaird Is there any automation that will add the new tasks to existing build pipelines of projects that do builds in Konflux already? Or do we expect engineers to update all the pipeline definitions manually to insert the new tasks?

https://issues.redhat.com/browse/EC-1063

@simonbaird
Copy link
Contributor Author

FWIW I'd like to merge it, if only to close out the three Jiras on my scrum board.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants