Jenkins dockerized testing - my architecture makes sense?

<p>Hi, I&#39;d be glad to get your validation and advice regarding the following Jenkins + scripted pipeline + docker + AWS ECS architecture:</p> <ol> <li>Pipeline runs testing step in a dockerized agent (delegated to ECS, see next) + </li> <li>Jenkins cloud plugin instantiate a new ECS task (slave image with Docker inside, mounted to /var/run/docker.sock) + </li> <li>The test/step invokes &#34;ssh &#39;docker-compose --exit-code-from my testing container&#39; (need to isolate the network here so two compose can run at once, not sure how) + </li> <li>I copy back all the test artifacts XML to the workspace (how?) + </li> <li>Jenkins kills the cloud task +</li> <li>Pipeline is back to non-dockerized agent, using plugins it evaluates the test results and set the build status (if I perform the evaluation within docker than I need to install Jenkins there, not sure if this holds true)</li> </ol> <hr/>**评论：**<br/><br/>whizack: <pre><p>for #4 you&#39;ll need to volume mount the results outputs to folders then aggregate/upload the results to something like s3 (or some generic object storage like minio) after the run completes</p> <p>i don&#39;t know of a clean way to isolate #3 at the network level</p></pre>loafoe: <pre><p>Have a look at <a href="https://concourse.ci" rel="nofollow">https://concourse.ci</a></p></pre>