[ 
https://issues.apache.org/jira/browse/CAMEL-20915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875593#comment-17875593
 ] 

Aurélien Pupier commented on CAMEL-20915:
-----------------------------------------

interesting workaround idea:
https://testcontainers.slack.com/archives/C04RM836XUP/p1724255963491499?thread_ts=1724252316.421289&cid=C04RM836XUP
{quote}
Put the versions in Dockerfiles, point Dependabot to the Dockerfiles, and have 
your Java code parse the first line of the Dockerfile.
{quote}

> test-infra: automate checking for container upgrades
> ----------------------------------------------------
>
>                 Key: CAMEL-20915
>                 URL: https://issues.apache.org/jira/browse/CAMEL-20915
>             Project: Camel
>          Issue Type: Task
>          Components: test-infra
>    Affects Versions: 4.7.0
>            Reporter: Otavio Rodolfo Piske
>            Priority: Major
>              Labels: help-wanted
>             Fix For: 4.x
>
>
> We use a lot of containers as part of our tests. With time, they become 
> outdated and we have to manually check for upgrades. 
> This tasks is to create a script to automate checking for new versions of the 
> containers.
> You can find all the containers used in Camel by running the following 
> command:
> {code:java}
> find . -iname 'container.properties' -ipath '*src*' -exec sh -c "cat {} | 
> grep container | cut -d = -f 2 "  \;
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to