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

Figure out why we analyzed reports from previous build #159

Closed
gsmet opened this issue Feb 1, 2024 · 1 comment
Closed

Figure out why we analyzed reports from previous build #159

gsmet opened this issue Feb 1, 2024 · 1 comment

Comments

@gsmet
Copy link
Member

gsmet commented Feb 1, 2024

We need to ignore Build scans from the report:
quarkusio/quarkus#38516

https://github.com/quarkusio/quarkus/actions/runs/7737744659/job/21102380625

Also, we need to figure out why we ended up with quickstart errors from the previous build. This is not expected...

@gsmet
Copy link
Member Author

gsmet commented Feb 2, 2024

The problem is that when you do a second run, it's still the same workflow run so artifacts stay attached to it. The fact that we will always push the artifacts now even in case of success should overwrite the previous ones... If we are lucky enough that they are available quickly... Not sure how things will go.

I fixed the ignore rule.

@gsmet gsmet closed this as completed Feb 2, 2024
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

No branches or pull requests

1 participant