Files
atom/script
Rafael Oleza 6fcfaffa04 Do not depend on CONFIG.executableName on the windows tests
CONFIG.executableName depends on the ATOM_RELEASE_VERSION env variable
to work correctly on nightly releases.

Since this env variable is not being set for the testing steps, the
nightly release builds contain a wrong executableName on the testing
step, which causes a failure when trying to find the Atom executable.

This commit fixes that by stop using the executableName from the test
step, like it's done on other platforms.
2019-07-17 11:40:39 +02:00
..
2019-04-17 11:48:28 -04:00
2016-08-02 14:04:45 +02:00
2016-08-02 14:04:45 +02:00
2016-08-02 15:31:05 +02:00
2016-08-08 14:47:17 -07:00
2019-06-26 16:32:07 +02:00
2016-08-29 10:37:12 +02:00
2016-08-29 10:37:12 +02:00
2019-06-19 17:06:44 +02:00
2019-06-19 17:06:44 +02:00
2016-09-09 17:58:23 +02:00