Databases
StackOverflow2013
Postsdbo
POGetting RAD builds and Jenkins builds to play nice
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGetting RAD builds and Jenkins builds to play nice
    primarykey
    data
    text
    <p>I have about 50 projects in version control for which I am standardizing the way that they are structured and built.</p> <p>Each has a build.xml in its root folder. We also have a project in which there is a build file that gets imported by the other projects in order to do common tasks. This makes maintenance of these common tasks much easier.</p> <p>SVN Repositories for each project adhere to svn standard root structure of trunk/tags/branches. Our workspaces are built in RAD by checking out from trunk. When rad then builds the project structure there is no actual trunk directory created on the filesystem. Projects simply begin in workspaceRoot/projectName, without the trunk. Although the infomation about where the project was checked out from is in brackets after the project name, so you know what branch of the repository you are working on.</p> <p>We support both File->Export style war creation in RAD and explicit build.xml creation of the war file as well. All of this is working just peachy.</p> <p>Now starting to get these projects building nightly in Jenkins and struggling with some of the file structure differences between the RAD environment and the Jenkins Environment.</p> <p>For instance, if I have a specific project I am working on, say project1, the build.xml location in my workspace will be </p> <pre><code>workspaceRoot/project1/build.xml </code></pre> <p>The common build.xml file similarly will be at </p> <pre><code>workspaceRoot/commonProject/build.xml </code></pre> <p>So project1 will attempt to import that build file with </p> <pre><code> &lt;import file="${basedir}/../commonProject/build.xml"/&gt; </code></pre> <p>In Jenkins however when I specify the repository location and it does its checkout it goes to </p> <pre><code>jenkinsRoot/workspace/jobName/project1/trunk/build.xml </code></pre> <p>and similarly the common project build.xml is at</p> <pre><code>jenkinsRoot/workspace/jobName/commonProject/trunk/build.xml </code></pre> <p>So the syntax in the project1 build file to import the common build file will not work. I have other similar issues, all related to differences in file structure.</p> <p>It seems this must be a fairly common issue, is there an "best practice" approach to addressing problems such as this. I have done a deal of searching around with no luck thus far.</p> <p>Would be nice, for instance, if Jenkins could check out the trunk in the same way as RAD, but it does not seem that it can. This at least would allow me to use an ant "available" tag to look for the two possible trunk locations and use the correct one as appropriate. But one has a trunk and one does not. Jenkins includes the jobName in the workspace path, while obviously RAD has no such concept ... and so on. Would like a clean way of putting together a build process that works seamlessly whether launched from Rad or Jenkins.</p> <p>-Jim</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJames Gawron
    1. USJames Gawron
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COwhat is the svn URL that you use for checkout? Does it end with trunk?
      singulars
      1. POGetting RAD builds and Jenkins builds to play nice
      1. USPeter Schuetze
    2. COIn Jenkins it does not have the trunk ... If I provide trunk on the URL to Jenkins it complains that the given URL doesn't contain a repository ... Jenkins is insisting that only the path to the base of the repository be given. In RAD the repository is also mapped without the trunk, but you can specify the trunk when you do the checkout.
      singulars
      1. POGetting RAD builds and Jenkins builds to play nice
      1. USJames Gawron
    3. COSomething is wrong with your URL. I always supply trunk or branches/<branchname> or tags/<tagname>.
      singulars
      1. POGetting RAD builds and Jenkins builds to play nice
      1. USPeter Schuetze
 

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