Target directory created from config value

The target directory was being created based on a hardcoded string rather from the target directory configuration value. Backport f6196cf
elastic · Jun 16, 2016 · a61e91f · a61e91f
1 parent 2fd18ad
commit a61e91f
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/tasks/build/archives.js b/tasks/build/archives.js
@@ -4,6 +4,7 @@ module.exports = function createPackages(grunt) {
   let { execFile } = require('child_process');
   let { all, fromNode } = require('bluebird');
 
+  const targetDir = config.get('target');
   let buildPath = resolve(config.get('root'), 'build');
   let exec = async (cmd, args) => {
     grunt.log.writeln(` > ${cmd} ${args.join(' ')}`);
@@ -29,7 +30,7 @@ module.exports = function createPackages(grunt) {
       grunt.config.get('platforms')
       .map(async platform => {
 
-        grunt.file.mkdir('target');
+        grunt.file.mkdir(targetDir);
         await archives(platform);
       })
     )

diff --git a/tasks/build/osPackages.js b/tasks/build/osPackages.js
@@ -10,7 +10,7 @@ export default (grunt) => {
   const fpm = args => exec('fpm', args);
 
   grunt.registerTask('_build:osPackages', function () {
-    grunt.file.mkdir('target');
+    grunt.file.mkdir(targetDir);
 
     grunt.config.get('platforms')
     .filter(({ name }) => /linux-x(86|64)$/.test(name))