Sorry I need to change enviroment variables not parameters.

Il giorno martedì 1 marzo 2022 alle 15:38:09 UTC+1 Mario Giammarco ha 
scritto:

> Hi,
> I resurrect this thread.
> I have one pipeline and several agents. I need to run the pipeline 
> multiple times in parallel with different parameters.
> It seems to me a common and easy question. 
> Reading this thread, bug description and other threads it seems it is not 
> possible.
> I am really surprised about it.
> Is it really not possible?
> Is there a workaround?
> Thanks,
> Mario
>
> Il giorno lunedì 3 ottobre 2016 alle 08:00:08 UTC+2 Zabil C M ha scritto:
>
>> There's an issue logged for this here 
>> https://github.com/gocd/gocd/issues/2329
>>
>> In short, you can't do this at the moment but we are willing to help out 
>> with and merge this feature if someone picks it up. 
>>
>> On Wed, Sep 28, 2016 at 3:48 PM, <[email protected]> wrote:
>>
>>> One of the key features that made us decide to migrate to gocd several 
>>> months ago was the idea that pipelines are able to run in parallel and that 
>>> more than one instance of a pipeline can be started.
>>> Only now are we starting to realise that actually the same pipeline 
>>> cannot be executed multiple times in parallel since each stage will always 
>>> run sequentially even if it's the same stage in different pipeline 
>>> instances. I'm stating this only based on this post 
>>> <https://groups.google.com/d/msg/go-cd/E0goLJITLy8/8UN7KrjCCAAJ> which 
>>> is the only mention of this issue that I've been able to find.
>>>
>>> So first off I'd like to verify if this is correct. Is it not possible 
>>> to run several instances of the same pipeline concurrently (in parallel 
>>> )without one instance being constrained by another (i.e. the second 
>>> instance of the same pipeline is able to complete even if a previously 
>>> initiated instance has not done so)?
>>>
>>> If this is the case, I'd really appreciate any help/ideas on overcoming 
>>> this limitation in some way.
>>> The pipeline I'm working on has only one stage which simply runs a 
>>> docker and then deletes the container and image. The docker does some work 
>>> on our machine learning models, there is no problem to run several 
>>> containers of this docker at the same time - and that's exactly what I'd 
>>> like to do - i.e. run another docker each time that the pipeline is 
>>> triggered (we're using the api to trigger it).
>>> I'd like to see the output created by each docker and, of course, see 
>>> whether each pipeline has finished successfully or failed. The order of 
>>> execution and even the material version is not relevant, each instance of 
>>> the pipeline/docker has it's job to do.
>>>
>>> Finally, I'd like to ask if you guys feel that a feature that enables 
>>> the same stage to run concurrently in different pipeline instances  is 
>>> feasible. And that a request for this is something which has a chance of 
>>> being accepted (I will, of course, contribute anything I can within my 
>>> technical skills) .
>>> I'm sure that the are many use cases that will benefit from such a 
>>> feature.
>>>
>>> Thanks
>>>
>>>
>>>
>>>
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "go-cd" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to [email protected].
>>
>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/b9f673a6-01ba-4950-9d0e-9cafc2151014n%40googlegroups.com.

Reply via email to