Hi,
I'm not sure if you've received any response, but I see two possible solutions:
* create a separate job in Jenkins for these merges, subscribe to the "code
review approved" events from Github and work from that
* in the pipeline, create an "infinite loop" with some sensible upper limit
(lik
Feb 2019, at 14:48, Adrien Lecharpentier
mailto:adrien.lecharpent...@gmail.com>> wrote:
as a workaround, you could try to `stash` the binaries and `unstash` them all
in the same node and archive them then.
But for your problem, it's the first time I see this. Sorry.
Le ven. 15 févr.
Anyone with a similar issue? I'd really appreciate any tip.
Thanks!
Laci
> On 13 Feb 2019, at 10:37, László Boros wrote:
>
> Hi everyone!
>
> We are facing some issues with our main Jenkins pipeline. It consists of
> multiple stages which are executed on different m
Hi everyone!
We are facing some issues with our main Jenkins pipeline. It consists of
multiple stages which are executed on different machines, and each stage can
produce artifacts. We are trying to archive these all by calling the
`archiveArtifacts` pipeline command after each stage, but it se
