Skip to content

SRE-3742 ci: no_proxy for direct artifactory access in the Python Bandit check stage#18045

Merged
daltonbohning merged 1 commit intomasterfrom
grom72/SRE-3742-NO_PROXY-for-Bandit-check-docker-image
Apr 20, 2026
Merged

SRE-3742 ci: no_proxy for direct artifactory access in the Python Bandit check stage#18045
daltonbohning merged 1 commit intomasterfrom
grom72/SRE-3742-NO_PROXY-for-Bandit-check-docker-image

Conversation

@grom72
Copy link
Copy Markdown
Contributor

@grom72 grom72 commented Apr 20, 2026

In the Python Bandit check stage:
add no_proxy to access artifactory directly as an access via proxy does not work.

Signed-off-by: Tomasz Gromadzki tomasz.gromadzki@hpe.com

Steps for the author:

  • Commit message follows the guidelines.
  • Appropriate Features or Test-tag pragmas were used.
  • Appropriate Functional Test Stages were run.
  • At least two positive code reviews including at least one code owner from each category referenced in the PR.
  • Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

  • Gatekeeper requested (daos-gatekeeper added as a reviewer).

Add no_proxy to access artifactory directly as access via proxy does not
work.

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>

Priority: 2
Skip-build: true

Skip-unit-tests:true
Skip-unit-test: true
Skip-NLT: true
Skip-unit-test-memcheck: true

Skip-test: true
Skip-func-test: true

Skip-func-vm: true
Skip-fault-injection-test: true
Skip-test-el-9-rpms: true
Skip-test-leap-15-rpms: true

Skip-func-hw-test: true
@grom72 grom72 requested a review from JohnMalmberg April 20, 2026 12:01
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 20, 2026

Errors are Title of PR is too long,Unable to load ticket data
https://daosio.atlassian.net/browse/SRE-3742

@grom72
Copy link
Copy Markdown
Contributor Author

grom72 commented Apr 20, 2026

Neither Jenkins Build nor Tests stages are required as this change affects only the Python Bandit check stage.

@grom72 grom72 added the forced-landing The PR has known failures or has intentionally reduced testing, but should still be landed. label Apr 20, 2026
@grom72 grom72 changed the title SRE-3742 ci: no_proxy for direct artifactory access SRE-3742 ci: no_proxy for direct artifactory access in the Python Bandit check stage Apr 20, 2026
@ryon-jensen
Copy link
Copy Markdown
Contributor

Only changes the code scanning stages so doesn't need rest of testing.

@ryon-jensen ryon-jensen requested a review from a team April 20, 2026 16:45
@grom72 grom72 requested a review from a team April 20, 2026 20:17
@daltonbohning daltonbohning merged commit f2e4893 into master Apr 20, 2026
52 checks passed
@daltonbohning daltonbohning deleted the grom72/SRE-3742-NO_PROXY-for-Bandit-check-docker-image branch April 20, 2026 20:17
grom72 added a commit that referenced this pull request Apr 21, 2026
…dit check stage (#18045)

In the Python Bandit check stage:
add no_proxy to access artifactory directly as an access via proxy does not work.

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>

Priority: 2
Skip-build: true
Skip-unit-tests:true
Skip-unit-test: true
Skip-NLT: true
Skip-unit-test-memcheck: true
Skip-test: true
Skip-func-test: true
Skip-func-vm: true
Skip-fault-injection-test: true
Skip-test-el-9-rpms: true
Skip-test-leap-15-rpms: true
Skip-func-hw-test: true
phender pushed a commit that referenced this pull request Apr 21, 2026
…dit check stage (#18045) (#18063)

In the Python Bandit check stage:
add no_proxy to access artifactory directly as an access via proxy does not work.

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

forced-landing The PR has known failures or has intentionally reduced testing, but should still be landed.

Development

Successfully merging this pull request may close these issues.

4 participants