On Wed, Aug 12, 2015 at 6:39 PM, nicolas de loof <[email protected]> wrote: > Let's say I have slave with 2 executors, and two jobs running docker push to > registry, with distinct credentials, running concurrently > - job 1 do set .docker/config.json with credentials c1 > - job 2 do set .docker/config.json with credentials c2 > - job 1 do run docker push, expecting c1 well set for registry - push fails, > as c2 does not allow to push to this repository
AFAIK this is not an issue in the current plugin because the registry URL is a key in the JSON. Unless you mean that they are both trying to access the _same_ registry, and this registry has some accounts which are read-only and some which allow push. Theoretically possible though it seems unlikely. Anyway if we can use the 1.8 feature then of course we should do it. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1yoW5K%2BhKMgTsZL0ig3V0hhrRQ_DTTXnbDsjMuXDeBwQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
