Compile Path Issue

16 views
Skip to first unread message

Eric Fetzer

unread,
Sep 23, 2016, 10:21:25 AM9/23/16
to Jenkins Users
I've migrated my build to a new server and am having some strange issues.  I've narrowed it down to a path difference when it performs a compile.  On the machine where it works, the build output is:

[compc] Loading configuration file /opt/jenkins/jobs/NAP-Client/workspace/build/configs/production-dto-config.xml
    [compc] /opt/jenkins/jobs/NAP-Client/workspace/libs/library/dtoLibrary-1.3.4.5.swc (62716 bytes)
     [echo] Succesfully compiled dtoLibrary

On the new build machine where it fails, the output is:

[compc] Loading configuration file /opt/jenkins/workspace/NAP-Client/build/configs/production-dto-config.xml
    [compc] /opt/jenkins/workspace/NAP-Client/src/gov/nwcg/server/domain/client/SessionProperties.as: Error: A file found in a source-path must have the same package structure 'gov', as the definition's package, 'gov.nwcg.server.domain.client'.

I notice that the one is building from /opt/Jenkins/workspace/NAP-Client and the other is building from /opt/Jenkins/jobs/NAP-Client/workspace.  The compile task is:

            <compc output="${source.libs}/library/@{swc-name}${version}.swc"
                maxmemory="768m"
                fork="true">
                <!-- set argument to be used in config file -->
                <arg value="+flexLib-dir=${source.libs.flex}" />
                <arg value="+dtoLib-dir=${source.libs.dto}" />
                <arg value="+flex-dir=${FLEX_HOME}" />
                <arg value="-define=COMPILETIME::version,'${version}'"/>
                <load-config filename="build/configs/@{build.config}-dto-config.xml" />
                <source-path path-element="${source.flex.dir}" />
                <source-path path-element="${FLEX_HOME}/frameworks" />
            </compc>

Does anyone have any clue based off of this information what the issue is?  The build file being run in both cases is in:  /opt/Jenkins/jobs/NAP-Client/workspace/build.xml.

Thanks,
Eric

Eric Fetzer

unread,
Sep 23, 2016, 10:44:40 AM9/23/16
to Jenkins Users
OK, I see what is likely causing this.  The old build machine had version 1.637 of Jenkins on it and the new build machine has version 2.7.2.  I'm guessing there are differences in how these 2 handle things.  Can anyone give me any direction in trouble-shooting this issue?

Thanks,
Eric

Eric Fetzer

unread,
Sep 23, 2016, 12:41:50 PM9/23/16
to Jenkins Users
I set a custom workspace to match the old workspace and that doesn't change a thing.  It has to be something else.  The issue shows up in the line below the error I'm posting though:


    [compc] Loading configuration file /opt/jenkins/jobs/NAP-Client/workspace/build/configs/production-dto-config.xml
    [compc] /opt/jenkins/jobs/NAP-Client/workspace/src/gov/nwcg/server/domain/client/ISessionInformation.as: Error: A file found in a source-path must have the same package structure 'gov', as the definition's package, 'gov.nwcg.server.domain.client'.
    [compc]
    [compc] /opt/jenkins/jobs/NAP-Client/workspace/src/gov/nwcg/server/domain/client/ISessionInformation.as: Error: A file found in a source-path 'nwcg/server/domain/client/ISessionInformation' must have the same name as the class definition inside the file 'ISessionInformation'.

Something is causing it to lop off the gov at the beginning of the source-path.


On Friday, September 23, 2016 at 8:21:25 AM UTC-6, Eric Fetzer wrote:
Reply all
Reply to author
Forward
0 new messages