ean the graphical representation?
>
> Am Sonntag, 29. Mai 2016 19:47:40 UTC+2 schrieb Bartłomiej Sacharski:
>>
>> I'm really hyped about the Jenkinsfiles - they make it much much easier
>> to document and preserve project configuration.
>> However, all the exampl
Thanks. Will look into that.
On Monday, May 30, 2016 at 7:42:34 PM UTC+2, Norbert Lange wrote:
>
> So you have a git repository with pipeline (as script) and want to run
> them all?
>
> Its possible, but Its somewhat a messy syntax.
> # global variable
> def Myclosure
>
> Node {
> # has to be in
I'm really hyped about the Jenkinsfiles - they make it much much easier to
document and preserve project configuration.
However, all the examples that I've seen seem to use single pipeline.
I've tried to define different stages in separate node blocks, however they
still were seen as a single
ins can be pointed at an org, or just one repository,
> and multiple Jenkinsfiles can exist which define different Pipeline jobs.
>
> Bartłomiej and Alex, would something like this satisfy your use cases as
> well?
>
>
> - Michael
>
> On Sunday, May 29, 2016 at 12:47:40 PM UTC-5,
>
> (replies inline)
>
> On Wed, 17 May 2017, Bart??omiej Sacharski wrote:
>
> > Hello.
> >
> > I'm trying to mount specific directory to a stage-only agent that will
> use
> > docker in a declarative pipeline.
> > It looks like this:
> >
> > > agent {
> > > docker {
> > > image
Hello.
I'm trying to mount specific directory to a stage-only agent that will use
docker in a declarative pipeline.
It looks like this:
> agent {
> docker {
> image "myimage:latest"
> args "-v ${WORKSPACE}/out:/var/www/api/out"
> }
> }
>
However, this results in *No such property:
