-
Notifications
You must be signed in to change notification settings - Fork 52
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
Nightly release snapshot #910
Comments
@squakez I'm on it. |
The task has been created, but I think we need to limit the number of versions added to the snapshot repository. I get the feeling it there will quickly be to many of them. |
IIRC it should 48 hours |
Is it supposed to be configured by the repository nexus or the project ? Because when I look here it is definitly more : https://repository.apache.org/content/repositories/snapshots-group/org/apache/camel/k/camel-k-catalog/3.6.0-SNAPSHOT/ |
It's on nexus side, so it is something managed by apache infra |
Right now the publish of Camel K runtime on snapshot always happen when a new commit is pushed to the
main
orrelease
branches. If we make sure to double check any error when we merge, then, we should have a guarantee that the latest changes are in the snapshot. However it would be a nice addition a nightly build that takes care of publishing the latest results as a snapshot, just in case the merged commit fail and we don't get any notification about that failure.Originally posted by @squakez in apache/camel-k#3764 (comment)
The text was updated successfully, but these errors were encountered: