You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i see that #1004 introduced a new way to name containers at run time, but i don't see any option to continue using a random container name at start up. is this still possible?
how else would i resolve container naming conflicts on my build server if i have two jobs that use the same container (via parent pom) configuration running at the same time?
The text was updated successfully, but these errors were encountered:
I see your point, but I wonder whether we should reintroduce it via a special placeholder or by other means. But would be happy to integrate the PR with some extra checks.
howdy! been a while, eh @rhuss?
i see that #1004 introduced a new way to name containers at run time, but i don't see any option to continue using a random container name at start up. is this still possible?
how else would i resolve container naming conflicts on my build server if i have two jobs that use the same container (via parent pom) configuration running at the same time?
The text was updated successfully, but these errors were encountered: