Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>One approach is to use the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Locks+and+Latches+plugin" rel="nofollow">Locks and Latches</a> plugin and give each of the jobs on each pipeline their own Lock eg Pipeline-A and Pipeline-B, then the job that runs the tests is configured to obtain the lock on both Pipeline-A and Pipeline-B. This both prevents the test job running if any part of either pipeline is running, and blocks any changes on the pipeline whilst the tests are running.</p> <p>If you'd only like to lock on the deploy jobs, you can use the same approach but only configure the deploy jobs with the locks; this will allow normal builds to run as normal, but deploy jobs queue up whilst the tests run.</p> <p>Assumptions;</p> <ul> <li>Any Deploy jobs are triggering a test execution</li> </ul> <p>A second approach is to have your job pipelines setup such that before performing a deployment they trigger a single job in the following layout;</p> <pre><code>EndOfPipelineA -&gt; SystemDeploymentController EndOfPipelineB -&gt; SystemDeploymentController SystemDeploymentController -&gt; DeployAppOne SystemDeploymentController -&gt; DeployAppTwo DeployAppTwo -&gt; TestExecution DeployAppOne -&gt; TestExecution </code></pre> <p>Then you use the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Join+Plugin" rel="nofollow" title="join">Join</a> plugin to only run the TestExecution job when both the deployments are complete AND successful.</p> <p>The second approach allows you to:</p> <ol> <li>conditionally control the execution of the test execution depending on the success of deployments, </li> <li>Have a single job that'll let you redeploy your whole system if you make any changes to the system it runs on, AND then run tests automatically.</li> <li>Potentially make use of the Promotions plugin to highlight "good configurations" where both apps worked well together</li> </ol> <p>However it is a bit trickier to manage.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do you tie two different build pipelines together in Jenkins?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USToby Jackson
    1. USToby Jackson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do you tie two different build pipelines together in Jenkins?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThe correct URL for the Locks and Latches plugin is here: https://wiki.jenkins-ci.org/display/JENKINS/Locks+and+Latches+plugin
      singulars
      1. PO
      1. USKevin P.
    2. COThanks, I've updated the description with the correction.
      singulars
      1. PO
      1. USToby Jackson
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload