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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

Thanks for sticking with me on this. 馃槂 #2039

Closed
christiancanna opened this issue Dec 13, 2023 · 1 comment
Closed

Thanks for sticking with me on this. 馃槂 #2039

christiancanna opened this issue Dec 13, 2023 · 1 comment

Comments

@christiancanna
Copy link 

          Thanks for sticking with me on this. 馃槂

  1. Will skipping the database upload affect results or build checks in any way? I can't tell from the docs if this just affects the availability of a build artifact or if there's a functional impact.

  2. Yes. I've attached a anonymized version.
    codeql-scan-workflow.zip

  3. No, I don't technically need to do this. However, I'm attempting to ensure that all builds, tests, and static analysis tools are using the same environment and build artifacts so that we don't introduce (or miss) issues that might be dependent on these things.

  4. The GH runner downloads the image and prepares a fresh container each time it's executed. There is no state being persisted with each execution.

Originally posted by @futureviperowner in #1541 (comment)
@aeisenberg
Copy link
Contributor

Closing unless you can formulate this as a question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aeisenberg @christiancanna