-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
depenabot is not upgrading docker-compose files #5552
Comments
Just a small doubt. I don't think there is a configuration option in dependabot to do this: Maybe one solution is to create a sub-directory for each of those files and give the name as |
if that's the case (seems like it) then we'd need to refactor your change to use standard file names and use directories for disambiguation, e.g. |
E.g. this is what we did for base images:
|
## Which problem is this PR solving? - Resolves #5552 ## Description of the changes - updated `dependabot.yml` and created sub-directories for docker-compose files ## How was this change tested? - ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits - [ ] I have added unit tests for the new functionality - [ ] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `yarn lint` and `yarn test` --------- Signed-off-by: FlamingSaint <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]>
it's still not working
In the sample file I only see |
## Which problem is this PR solving? - #5552 ## Description of the changes - try different config ## How was this change tested? - CI Signed-off-by: Yuri Shkuro <[email protected]>
@FlamingSaint turns out docker-compose files are not supported by dependabot. The issue there has a workaround of using Dockerfiles in combination with docker-compose. dependabot/dependabot-core#390 (comment) Longer term, we should probably switch to Mend's Renovate bot (used by OTEL project), but should confirm if it supports docker-compose. Perhaps we can enable it just for docker-compose initially, to cover the gap of dependabot. |
Oh I didn't check for that. My bad. Also looks like Renovate bot supports docker-compose. I could work on migrating from dependabot to renovate bot. Let me know if I should go ahead. |
Also now that the new bot can detect docker-compose files we can remove the unnecessary extra directories that are created. |
@FlamingSaint can you stamp this? #5566 |
## Which problem is this PR solving? - The `/` path is invalid since there is no Dockerfile in the root dir. Unfortunately, dependabot fails the whole run on this error, instead of working through all the dirs - Part of #5552 ## Description of the changes - Remove invalid path ## How was this change tested? - Only testable after merge Signed-off-by: Yuri Shkuro <[email protected]>
@FlamingSaint fyi - I enabled Renovate bot, it seems to be correctly discovering all dependencies (#5572). But we need to do some preparations first (for one, it does not add the label we use for dependencies) |
This is now working with Renovate bot, closing. |
This comment: https://github.com/jaegertracing/jaeger/pull/5520/files#r1633476406
The text was updated successfully, but these errors were encountered: