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: 

      testing: 

      • Should be able to be fully automated using ci.jenkins.io 
      • check sidecar containers are shut down in all scenarios possible

          [JENKINS-46336] Sidecar docker containers for declarative

          Michael Neale created issue -
          Michael Neale made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Michael Neale made changes -
          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
          Michael Neale made changes -
          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
          James Dumay made changes -
          Epic Link New: JENKINS-45381 [ 183541 ]
          James Dumay made changes -
          Sprint New: Pipeline - Candidates [ 381 ]
          James Dumay made changes -
          Sprint Original: Pipeline - Candidates [ 381 ]
          James Dumay made changes -
          Rank New: Ranked higher
          James Dumay made changes -
          Sprint New: Pipeline - Candidates [ 381 ]
          James Dumay made changes -
          Epic Link Original: JENKINS-45381 [ 183541 ] New: JENKINS-47962 [ 186491 ]
          Carlos Sanchez made changes -
          Link New: This issue is blocking JENKINS-48135 [ JENKINS-48135 ]

            Unassigned Unassigned
            michaelneale Michael Neale
            Votes:
            32 Vote for this issue
            Watchers:
            48 Start watching this issue

              Created:
              Updated: