Re: aeb/aet vs. scripting languages
Walter Franzini <[email protected]>
| Newsgroups | gmane.comp.version-control.aegis.user |
|---|---|
| Message-ID | <[email protected]> |
Aryeh Friedman <[email protected]> writes: > Some of our jobs are PHP and python and after some experimentation we > have found that the aeb/aed/aet cycle is very well suited for compiled > langs but not so much for scripted ones because (for example in PHP) > there is no actual building that needs to be performed... I know and > support the idea of build_command="exit 0"; but I would want to find > some way of get the same kind of output that a compiler gives on > errors... ideas? PHP has a --syntax-check option, for javascript you may try jslint and probably something exists also for python. For tests you may want to define test_command as follow: test_command = "${project_specific PYTHON} ${filename} ${arch} ${version}"; Ciao -- Walter Franzini http://aegis.stepbuild.org/ _______________________________________________ Aegis-users mailing list [email protected] http://lists.auug.org.au/listinfo/aegis-users
signature.asc
(application/pgp-signature, 196 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkzZI+oACgkQlqotV8s/60ODHQCgjjtI3eZo6Dz7kO9KlUgLWIjs 7IQAoJuZkApMcL+fmOcAKaSuenssdTeH =RUGr -----END PGP SIGNATURE-----