Having installed  CasC and docker-build-step plugins, there is no (obvious way) to set the dockerUrl setting via CasC. The only setting that is shown in the CasC documentation is the `unclassified.dockerBuilder` step. Trying to set `unclassified.dockerBuilder.dockerUrl` results in error. I have tried other combinations as well, but I have not succeeded. If this is possible, it should be documented. If it is no supported, it would be great if support was added.

          [JENKINS-65340] Cannot set dockerUrl with CasC

          hi,

          I think this is related to:
          https://issues.jenkins.io/browse/JENKINS-64976

          Will this fix fix that too?

          I tried to understand why the specific error I got occurs, but it's not clear to me so far although to my best understanding it is the global.jelly file and how that maps to the new way of how the GUI is rendered on the global settings screen.

          I saw status fixed but unreleased but I do not see anything in the github repo.
          It would be great if this plugin has that fixed, then I know also if the google container auth plugin works or if it needs fixing.
          thanks for your contributions and help!

          Vincent Gerris added a comment - hi, I think this is related to: https://issues.jenkins.io/browse/JENKINS-64976 Will this fix fix that too? I tried to understand why the specific error I got occurs, but it's not clear to me so far although to my best understanding it is the global.jelly file and how that maps to the new way of how the GUI is rendered on the global settings screen. I saw status fixed but unreleased but I do not see anything in the github repo. It would be great if this plugin has that fixed, then I know also if the google container auth plugin works or if it needs fixing. thanks for your contributions and help!

          Kala added a comment -

          This is a duplicate of JENKINS-64206, there is no code that comes with this issue being closed, "fixed but unreleased" is just bad wording in this case. I recommend you vote and watch JENKINS-64206 so that it has a chance to be fixed.

          Kala added a comment - This is a duplicate of JENKINS-64206 , there is no code that comes with this issue being closed, "fixed but unreleased" is just bad wording in this case. I recommend you vote and watch JENKINS-64206 so that it has a chance to be fixed.

          hi, thanks for the clarification.
          I actually found the cause for the bug I linked to and trying to get the maintainer to merge my fix, or adopt it.
          Check it out if you may be affected, I may be wrong in my assumption because that bug shows errors all over plugins that seemed fine.
          Thanks

          Vincent Gerris added a comment - hi, thanks for the clarification. I actually found the cause for the bug I linked to and trying to get the maintainer to merge my fix, or adopt it. Check it out if you may be affected, I may be wrong in my assumption because that bug shows errors all over plugins that seemed fine. Thanks

            vjuranek vjuranek
            nkakouros Kala
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: