Hi Alex,
I had some trouble figuring out how to do this as well. The docs here show
what is possible for docker.image using scripted pipeline (and thus inside
of a script{} block):
https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#docker-workflow
I ended up with something like this:
script {
def image = docker.build("image-name:test", '-f Dockerfile.dev .')
// can then call methods like image.push() here, or run a command with
image.inside():
image.inside('--net=host -v /mount:/mount:ro') {
sh 'some-command.sh'
}
}
- Ari
On Monday, September 11, 2017 at 3:57:23 PM UTC-6, Alex B wrote:
>
> Hi Drew,
>
> Could you post where you found the example using script{} block? I'm
> looking into building Docker images in ephemeral jenkins agents but having
> difficulty finding proper documentation for the syntax.
>
> -Alex
>
> On Thursday, June 1, 2017 at 1:23:11 AM UTC-5, drew....@computecanada.ca
> wrote:
>>
>> Hello Andrew and Thomas,
>>
>> I ran in this exact problem and used a script{} block, but I am wondering
>> if there are updates to this issue. All of the documentation/examples I
>> have seen use scripted syntax, but sometimes the documentation is behind
>> the code. :)
>>
>> Cheers,
>> Drew.
>>
>> On Tuesday, February 14, 2017 at 1:35:19 PM UTC-8, Andrew Bayer wrote:
>>>
>>> Right now, we don't have a great answer for this other than to use
>>> Scripted Pipeline docker.build(...) within a script { } block - we don't
>>> allow "foo.bar()" or "foo = bar()" syntax in steps blocks in Declarative
>>> unless they're within a script block. Anything within a script block
>>> doesn't go through validation, so you can use the full Scripted Pipeline
>>> syntax there. That said, we are thinking about how to make this clearer in
>>> the future so that you can build/deploy images without having to use script
>>> {}.
>>>
>>> A.
>>>
>>> On Tue, Feb 14, 2017 at 2:32 PM, Thomas Fjellstrom <tfjel...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm brand new to jenkins, and have been reading a lot about the
>>>> pipeline plugin. I think I have a basic grasp of it, but I haven't been
>>>> able to figure out the proper syntax to build docker images in a pipeline
>>>> stage. I don't want to run the steps IN a docker container, but rather
>>>> build containers (multiple containers) in a pipeline Jenkinsfile. I also
>>>> have some other requirements, like accessing credentials setup in the
>>>> jenkins interface, and a private docker registry.
>>>>
>>>> Any help would be appreciated.
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Jenkins Users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to jenkinsci-use...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-users/fff6ea30-6b51-4f46-8516-8da8026c4241%40googlegroups.com
>>>>
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/fff6ea30-6b51-4f46-8516-8da8026c4241%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/575efaf0-b077-4cf9-b6c5-62e3126970f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
