[JIRA] (JENKINS-38452) imageName() drops registry prefix outside of withRegistry() block

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title

Andrew Bayer resolved as Not A Defect   So first, the reason you're able to do anything with img when you reference it for the first time inside the withRegistry(...) block is that you defined it as img = ... - welcome to Groovy script variable scoping. =) If a variable is defined without a type or def ... in a Groovy script, it's global to the entire script. So for all intents and purposes, img = ... within the withRegistry(...) block works the same as def img before the withRegistry(...) block and then img = ... inside the block. However, if you did def img = ... inside the block, you would not be able to reference the img variable anywhere outside the block. Good times. Second, putting the Groovy scoping fun aside, yeah, this is expected behavior. withRegistry(...) alters behavior of Docker Pipeline methods/variables used inside its block, but only while you're in the block. So if you defined img before the withRegistry(...) block, img.imageName() called before the block wouldn't have the registry prefix, img.imageName() called inside the block would have the registry prefix, and img.imageName() called after the block wouldn't have the registry prefix. This is how this is supposed to work. Jenkins / JENKINS-38452 imageName() drops registry prefix outside of withRegistry() block Change By: Andrew Bayer Status: Open Resolved Resolution: Not A Defect Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.