You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Christophe Herreman <ch...@gmail.com> on 2012/05/18 10:43:19 UTC

Failing build

Hi,

I'm getting some messages about the build that is failing. Is anyone
currently configuring the CI system?

regards,
Christophe

-- 
Christophe Herreman
http://www.herrodius.com
http://www.springactionscript.org
http://www.as3commons.org

Re: Failing build

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi Oleg,

> Not sure, you might've tried it already, but saying it just in case, there
> are two useful tasks if you want to canonicalize the path.

Thanks that's useful to know. In this case the paths are being set up in Jenkins, although it possible to set them up in ANT.

Justin


Re: Failing build

Posted by Left Right <ol...@gmail.com>.
Not sure, you might've tried it already, but saying it just in case, there
are two useful tasks if you want to canonicalize the path:

<pathconvert targetos="win" property="FLASHPLAYER_DEBUGGER.win">
  <path location="${FLASHPLAYER_DEBUGGER}/../lib/player/
11.1/FlashPlayerDebugger.exe"/>
</pathconvert>

Or

<dirname property="FLASHPLAYER_DEBUGGER.dir" file="${FLASHPLAYER_DEBUGGER}
/../lib/player/11.1/FlashPlayerDebugger.exe">

I also think that the first one would reverse the slashes into "Windows
mode"... actually, from the time I built on Windows I can remember that
Windows will not handle a situation when there are both kinds of slashes -
which you might be seeing. So it would be better to use <pathconvert/>
because it would canonicalize the pathnames for every system.

Best.

Oleg

Re: Failing build

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

> what is the configuration of env.properties?
env.properties not the issue as far as I can tell, as the build script does a check out from SVN I've set the environment variables in the Jenkins config. 

However as the build script can't currently handle spaces in path or relative paths I'm a bit stuck.

This almost works:
AIR_HOME=${PROJECT_NAME}/../lib/air
FLASHPLAYER_DEBUGGER=${PROJECT_NAME}/../lib/player/11.1/FlashPlayerDebugger.exe
PLAYERGLOBAL_HOME=${PROJECT_NAME}/../lib/player/11.1/

With this the player global check passes but the compile fails. It looks like it using it as a relative path.

I've tried ${WORKSPACE} and %WORKSPACE% as well (it's running on windows) and I've fried full hard coded paths (which contain spaces).

I guess we could extend the Jenkins build script to create env.properties but seems amore complex way of doing it and we'd probably run into the same issue.

Thanks,
Justin


Re: Failing build

Posted by Christophe Herreman <ch...@gmail.com>.
Hi Justin,

what is the configuration of env.properties? I'll see if I can reproduce
the problem locally.

regards,
Christophe

2012/5/18 Justin Mclean <ju...@classsoftware.com>

> Hi Chris,
>
> > I'm getting some messages about the build that is failing. Is anyone
> > currently configuring the CI system?
>
> Yep that would be me. I've given up for now.
>
> It's mostly working but having an issue with the environment variables
> an/or spaces in the path.
>
> Thanks,
> Justin




-- 
Christophe Herreman
http://www.herrodius.com
http://www.springactionscript.org
http://www.as3commons.org

Re: Failing build

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi Chris,

> I'm getting some messages about the build that is failing. Is anyone
> currently configuring the CI system?

Yep that would be me. I've given up for now. 

It's mostly working but having an issue with the environment variables an/or spaces in the path.

Thanks,
Justin