Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I do not understand exactly what your requirements are, but let's give it a shot:</p> <p>Start your three jobs from a single job (lets call it <em>TriggerJob</em>) using <a href="https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin" rel="nofollow">Parameterized Trigger Plugin</a> as a build step. Give them <em>TriggerJob</em>'s <code>BUILD_ID</code> as a parameter, which they'll use to store the results (instead of using their own BUILD_ID's; if you still need to build them separately sometimes - without being triggered from <em>TriggerJob</em> - you can specify some default value for the parameter, and check for it with <a href="https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin" rel="nofollow">Conditional BuildStep Plugin</a>, when it has the default value - use own BUILD_ID, otherwise use the parameter passed in).</p> <p>Make <em>TriggerJob</em> wait for the three jobs to finish, then collect your jar's (<em>TriggerJob</em> knows where they are), and proceed with the fourth job that will call your last ANT to archive them together (or make it into an ANT build step in <em>TriggerJob</em>, whatever fits better).</p> <p>Just in case the following observation may prove useful for you: every ANT build step can use its own build file (it's under ADVANCED button). You can use environment variables to specify its path.</p> <p>Multiple checkouts: I'm not familiar with CVS plugin, but with Subversion plugin I prefer to do things by hand: I have trigger jobs that poll SVN via Subversion Plugin and pass revision numbers as parameters to jobs that do actual work. Those jobs then use explicit SVN calls (from shell build steps) to update to revisions passed as parameters. Maybe you can do the same thing with CVS plugin.</p>
    singulars
    1. This table or related slice is empty.
    1. POBuilding dependent projects using Jenkins
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmalenkiy_scot
    1. USmalenkiy_scot
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBuilding dependent projects using 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. COI have clarified the requirement a bit more so hopefully it is clear now. See the Edit. How exactly will the TriggerJob know where the jar files are?
      singulars
      1. PO
      1. USziggy
    2. CO_but each jar file ends up in an unrelated folder_ - what do you mean? It ends up in some place other than what your specify on top (/output/... etc.)? Which place?
      singulars
      1. PO
      1. USmalenkiy_scot
    3. COWhen jenkins runs every project, it checks out the files from CVS and puts them in a workspace folder for that project. When the ANT script is run the JAR file ends up in the workspace folder. For example proj1's jar file will be in workspace/proj1/distribution/proj1.jar and proj2's jar file will be in workspace/proj2/distribution/proj2.jar - Proj4 can not build the war file with the jar files in these folder. (unless i manually copy them to the proj4 workspace)
      singulars
      1. PO
      1. USziggy
 

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