Nice. That’s a good tip. Thanks
On Mon, Oct 19, 2020 at 4:36 PM Jan Monterrubio
wrote:
> Yep, if docker tags can return you json, you can just slurp stuff and
> transform it.
>
> On Mon, Oct 19, 2020 at 09:27 Kari Cowan wrote:
>
>> This is clever - thanks.
>>
>> I don't have a directory of
Yep, if docker tags can return you json, you can just slurp stuff and
transform it.
On Mon, Oct 19, 2020 at 09:27 Kari Cowan wrote:
> This is clever - thanks.
>
> I don't have a directory of files in my git project- but I am guessing I
> could write something to add - like a deployment tag list
This is clever - thanks.
I don't have a directory of files in my git project- but I am guessing I
could write something to add - like a deployment tag list that matches the
docker registry?
Ideally I would pull the docker register tag list and use that.
On Fri, Oct 16, 2020 at 1:15 PM
You mean something like a dynamic axis created by a piece of script? I had
a similar issue in the past and did not find a way.
There might be something with script blocks in a pipeline and dynamic
stage-creation with a for-loop.
When I remember right I found some examples with google when I
Hi,
Thanks for that. I see I forgot to mention something in my original
post: The nodes I want to run my job on should come from a label. So I
would need to get the 'values' in the matrix-part by figuring out which
nodes have this label set...
Can I add a simple 1-, maybe 2-line script
Hi,
I don't exactly understand your problem. Please have a look here:
https://www.jenkins.io/blog/2019/11/22/welcome-to-the-matrix/
you very easily can integrate matrix in a declarative pipeline. Insert your
nodes as an axis of the matrix and add an 'agent' in the stage doing your
job.
But
