-
New Feature
-
Resolution: Unresolved
-
Major
-
None
The "sidecar container" pattern is a popular one for setting up dependent containers for running tests/builds.
It would be nice to have support for this pattern in declarative to avoid the need to drop to script.
To investigate...
In scope:
- Be able to specify sidecar containers, their network/port sharing with main build, in agent section
- Cleanup of containers
- Formalise the patterns shown: https://jenkins.io/doc/book/pipeline/docker/#running-sidecar-containers in declarative, essentially
testing:
- Should be able to be fully automated using ci.jenkins.io
- check sidecar containers are shut down in all scenarios possible
- is duplicated by
-
JENKINS-41581 Declarative: Support for multiple docker agents run in parallel and communicating
-
- Closed
-
- is related to
-
JENKINS-48135 kubernetes-plugin should support multiple containers in declarative templates
-
- Resolved
-
[JENKINS-46336] Sidecar docker containers for declarative
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Description |
Original:
The "sidecar container" pattern is a popular one for setting up dependent containers for running tests/builds. It would be nice to have support for this pattern in declarative to avoid the need to drop to script. To investigate... |
New:
The "sidecar container" pattern is a popular one for setting up dependent containers for running tests/builds. It would be nice to have support for this pattern in declarative to avoid the need to drop to script. To investigate... In scope: Be able to specify sidecar containers, their network/port sharing with main build, in agent section Cleanup of containers testing: Should be able to be fully automated using ci.jenkins.io check sidecar containers are shut down in all scenarios possible |
Description |
Original:
The "sidecar container" pattern is a popular one for setting up dependent containers for running tests/builds. It would be nice to have support for this pattern in declarative to avoid the need to drop to script. To investigate... In scope: Be able to specify sidecar containers, their network/port sharing with main build, in agent section Cleanup of containers testing: Should be able to be fully automated using ci.jenkins.io check sidecar containers are shut down in all scenarios possible |
New:
The "sidecar container" pattern is a popular one for setting up dependent containers for running tests/builds. It would be nice to have support for this pattern in declarative to avoid the need to drop to script. To investigate... In scope: * Be able to specify sidecar containers, their network/port sharing with main build, in agent section * Cleanup of containers * Formalise the patterns shown: [https://jenkins.io/doc/book/pipeline/docker/#running-sidecar-containers] in declarative, essentially testing: * Should be able to be fully automated using ci.jenkins.io * check sidecar containers are shut down in all scenarios possible |
Epic Link |
New:
|
Sprint | New: Pipeline - Candidates [ 381 ] |
Sprint | Original: Pipeline - Candidates [ 381 ] |
Rank | New: Ranked higher |
Sprint | New: Pipeline - Candidates [ 381 ] |
Epic Link |
Original:
|
New: JENKINS-47962 [ 186491 ] |
Link |
New:
This issue is blocking |