Skip to content

wip: add prefetch-input to pipline to solve warnings - #2330

Closed
Dugowitch wants to merge 1 commit into
RedHatInsights:masterfrom
Dugowitch:pipeline-fix
Closed

wip: add prefetch-input to pipline to solve warnings#2330
Dugowitch wants to merge 1 commit into
RedHatInsights:masterfrom
Dugowitch:pipeline-fix

Conversation

@Dugowitch

@Dugowitch Dugowitch commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Secure Coding Practices Checklist GitHub Link

Secure Coding Checklist

  • Input Validation
  • Output Encoding
  • Authentication and Password Management
  • Session Management
  • Access Control
  • Cryptographic Practices
  • Error Handling and Logging
  • Data Protection
  • Communication Security
  • System Configuration
  • Database Security
  • File Management
  • Memory Management
  • General Coding Practices

Summary by Sourcery

Enhancements:

  • Enable hermetic builds and Go module dependency prefetching across pull-request and push Tekton pipelines.

@sourcery-ai

sourcery-ai Bot commented Sep 11, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The PR updates the Patchman engine push Tekton configuration to request Go module prefetching through the docker-build-oci-ta pipeline, intended to address pipeline warnings without changing the existing build or security-scan settings.

File-Level Changes

Change Details Files
Configure the Tekton pipeline to prefetch Go module inputs before the container build runs.
  • Add the prefetch-input parameter with the gomod value to the pipeline invocation.
  • Retain the existing build context and SAST configuration while extending pipeline inputs.
.tekton/patchman-engine-push.yaml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@codecov-commenter

codecov-commenter commented Sep 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.06%. Comparing base (45d633a) to head (57b9e9d).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2330   +/-   ##
=======================================
  Coverage   59.06%   59.06%           
=======================================
  Files         150      150           
  Lines        9615     9615           
=======================================
  Hits         5679     5679           
  Misses       3342     3342           
  Partials      594      594           
Flag Coverage Δ
unittests 59.06% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Dugowitch Dugowitch closed this Sep 11, 2026
@Dugowitch
Dugowitch deleted the pipeline-fix branch September 11, 2026 14:00
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.

2 participants