-
Notifications
You must be signed in to change notification settings - Fork 2.9k
[CI] - Snapshot Deployment #12111
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
Comments
Build fixed:
|
Unfortunately, the build failed:
|
Seems to be failing with an intermittent maven issue: Could not find artifact io.quarkus:quarkus-hibernate-validator-deployment:jar:999-SNAPSHOT |
The build is still failing:
|
Another weird Aerther issue on the same artifact: 2020-09-18T02:33:53.4887793Z Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact io.quarkus:quarkus-hibernate-validator-deployment:jar:999-SNAPSHOT @gsmet it seems that a build from scratch does not work anymore. |
The build is still failing:
|
The build is still failing:
|
Making some progress... now failing with another resolution issue in SmallRye Health: Most probably a missing -deployment test dependency on smallrye-openapi-common-deployment. @radcortez can you check? |
The build is still failing:
|
So, the missing dependency issue is fixed. Now we are back to a Gradle test issue:
@aloubyansky @ia3andy Any idea? Important details, it's a from scratch build, which means that nothing is available. If the projects requires specific dependency, they must be declared in the |
The build is still failing:
|
I reproduced it. Will have a look later today. |
Thanks @aloubyansky |
Build fixed:
|
Thanks @aloubyansky ! |
Unfortunately, the build failed:
|
The build is still failing:
|
@iocanel @geoand Soemthing wrong with Kubernetes:
|
The build is still failing:
|
Looking into it |
@geoand What I don't get is how it does not fail on the master build... |
Unfortunately it does... See #12366 |
@geoand At least, it's logic :-) |
Indeed :) |
Unfortunately, the build failed:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
Build fixed:
|
Unfortunately, the build failed:
|
Build fixed:
|
Unfortunately, the build failed:
|
The build is still failing:
|
The build is still failing:
|
The build is still failing:
|
Build fixed:
|
Uh oh!
There was an error while loading. Please reload this page.
This issue reports the status of the daily cron job that runs deploys Quarkus Snapshot artifacts to https://s01.oss.sonatype.org/content/repositories/snapshots/io/quarkus/.
Don't close this issue manually. This issue will be closed when the build gets fixed. It will be re-opened if it fails again later. You can subscribe to be notified of the status.
To use the snapshots, add the following repository to your
pom.xml
file or Gradle project:Use snapshots are your own risk. Because of the Maven resolution mechanism, they may be 24h old (even more) and in the Quarkus world, it can be 100 commits behind. If you have issues with snapshots, try to build a fresh version of Quarkus using the instructions from https://github.com/quarkusio/quarkus/blob/master/CONTRIBUTING.md
The text was updated successfully, but these errors were encountered: