[jbosstools-issues] [JBoss JIRA] (JBIDE-23013) Pull Docker Tooling bits into JBT builds more frequently

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-23013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438160#comment-13438160 ] 

Martin Malina commented on JBIDE-23013:
---------------------------------------

I'm not really testing docker anymore, but reading through the comments, it doesn't seem like anything has really changed since when I created the JIRA, am I wrong? So I think it would still be a good idea.
But whether it's worth the effort, that's another question. [~jkopriva], do you have an opinion on this? Does it happen often nowadays that this is a problem and we would benefit from more frequent updates of Docker Tooling in JBT?

> Pull Docker Tooling bits into JBT builds more frequently
> --------------------------------------------------------
>
>                 Key: JBIDE-23013
>                 URL: https://issues.jboss.org/browse/JBIDE-23013
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build, target-platform
>    Affects Versions: 4.4.1.AM3
>            Reporter: Martin Malina
>            Assignee: Jeff Johnston
>             Fix For: LATER
>
>
> It would be cool if we could update the Docker Tooling bits in our TP more frequently, i.e. weekly or even nightly. I know that currently it is quite a big effort to update TP. So we would need to simplify this somehow.
> So this is a suggestion, but I don't know how we would do it or if it's doable at all.
> Here's a bit of background:
> Today I spotted this blocking bug in docker tooling:
> https://issues.jboss.org/browse/JBIDE-23011
> It was probably brought into JBT TP in the last update of the TP - this JIRA:
> https://issues.jboss.org/browse/JBIDE-22885 - 4 days ago.
> Jeff Maury suggested, that it's a bad idea to update our TP this close to our release (AM3 in this case). But currently we don't have any other option.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)