Gulp 从azure开发运营管道构建gatsbyjs站点

Gulp 从azure开发运营管道构建gatsbyjs站点,gulp,azure-devops,gatsby,Gulp,Azure Devops,Gatsby,我正在尝试从Azure开发人员ops构建定义构建一个gatsby静态网站 AzureDev ops提供了一个gulp任务,所以我尝试创建一个简单的gulpfile来包装gatsby的构建过程 现在我试着: const gatbsyCli = require('gatsby-cli/lib/create-cli'); function gatsbyBuild() { gatbsyCli([ 'build' ]); } exports.gatsbyBuild = gatsbyBuild;

我正在尝试从Azure开发人员ops构建定义构建一个gatsby静态网站

AzureDev ops提供了一个gulp任务,所以我尝试创建一个简单的gulpfile来包装gatsby的构建过程

现在我试着:

const gatbsyCli = require('gatsby-cli/lib/create-cli');

function gatsbyBuild() {
    gatbsyCli([ 'build' ]);
}

exports.gatsbyBuild = gatsbyBuild;
但是,该任务仅显示命令行帮助:

Usage: gulp.js <command> [options]

Commands:
  gulp.js develop                   Start development server. Watches files, rebuilds, and hot reloads if something
                                    changes
  gulp.js build                     Build a Gatsby project.
  gulp.js serve                     Serve previously built Gatsby site.
  gulp.js info                      Get environment information for debugging and issue reporting
  gulp.js repl                      Get a node repl with context of Gatsby environment, see (add docs link here)
  gulp.js new [rootPath] [starter]  Create new Gatsby project.

Options:
  --verbose      Turn on verbose output                                                       [boolean] [default: false]
  --no-color     Turn off the color in output                                                 [boolean] [default: false]
  -h, --help     Show help                                                                                     [boolean]
  -v, --version  Show version number                                                                           [boolean]

Pass --help to see all available commands and options.
[22:28:15] The following tasks did not complete: gatsbyBuild
[22:28:15] Did you forget to signal async completion?
但由于类型错误而失败:无法读取未定义的属性“openTracingConfigFile”

[/Edit]

[编辑2019-02-02]关于答案,这里是关于我进度的更新

首先,我尝试使用NPM操作来构建站点,如下所示

但是,它失败并出现以下错误:

2019-02-02T21:13:22.3306376Z [command]/usr/local/bin/npm run build
2019-02-02T21:13:27.6097839Z error GraphQL Error There was an error while compiling your site's GraphQL queries.
2019-02-02T21:13:27.6098171Z 
2019-02-02T21:13:27.6099612Z   Error: RelayParser: Encountered duplicate defintitions for one or more documents: each document must have a unique name. Duplicated documents:
2019-02-02T21:13:27.6100019Z > gatsby-starter-blog@1.0.0 build /home/vsts/work/1/s
2019-02-02T21:13:27.6100847Z - DefaultSEOQuery
2019-02-02T21:13:27.6100902Z > gatsby build
然而,我不理解这个错误。该网站完美地构建在本地

我的gatbsy-node.js查询是:

            `
{
  allMarkdownRemark(sort: {fields: [frontmatter___date], order: DESC}, limit: 1000) {
    edges {
      node {
        fields {
          slug
        }
        frontmatter {
          title
        }
      }
    }
    cats: group(field: frontmatter___categories, limit:1000) {
      fieldValue
      totalCount
    }
    tags: group(field: frontmatter___tags, limit:1000) {
      fieldValue
      totalCount
    }
  }
}
此外,以下是我对yaml的定义:

resources:  
- repo: self    
queue:    
  name: Hosted Ubuntu 1604    
  demands: npm

steps:    
- task: Npm@1    
  displayName: 'npm install'    
  inputs:    
    verbose: false       

- task: Npm@1    
  displayName: 'npm custom'    
  inputs:    
    command: custom        
    verbose: false  
    customCommand: 'run build'
移动到“托管”代理时,引发另一个错误:

019-02-02T21:52:17.2419822Z [0m
2019-02-02T21:52:17.2419867Z [0m  [0m[97m[41mError[0m[37m[41m:[0m[37m[41m [0m[97m[41m0-0cf4e58448448331aa6c.js from Terser[0m
2019-02-02T21:52:17.2421623Z [0m  [0m[97m[41mTypeError: Cannot read property 'minify' of undefined[0m
2019-02-02T21:52:17.2421678Z [0m  [0m[97m[41m    at minify (D:\a\1\s\node_modules\terser-webpack-plugin\dist\minify.js:175:[0m  [0m[97m[41m22)[0m
2019-02-02T21:52:17.2421746Z [0m  [0m[97m[41m    at TaskRunner.boundWorkers.error [as boundWorkers] (D:\a\1\s\node_modules\[0m  [0m[97m[41mterser-webpack-plugin\dist\TaskRunner.js:68:40)[0m
2019-02-02T21:52:17.2421794Z [0m  [0m[97m[41m    at enqueue (D:\a\1\s\node_modules\terser-webpack-plugin\dist\TaskRunner.js[0m  [0m[97m[41m:89:14)[0m
2019-02-02T21:52:17.2421841Z [0m  [0m[97m[41m    at tryCatcher (D:\a\1\s\node_modules\bluebird\js\release\util.js:16:23)[0m
2019-02-02T21:52:17.2421906Z [0m  [0m[97m[41m    at Promise._settlePromiseFromHandler (D:\a\1\s\node_modules\bluebird\js\re[0m  [0m[97m[41mlease\promise.js:512:31)[0m
2019-02-02T21:52:17.2421954Z [0m  [0m[97m[41m    at Promise._settlePromise (D:\a\1\s\node_modules\bluebird\js\release\promi[0m  [0m[97m[41mse.js:569:18)[0m
2019-02-02T21:52:17.2422390Z [0m  [0m[97m[41m    at Promise._settlePromise0 (D:\a\1\s\node_modules\bluebird\js\release\prom[0m  [0m[97m[41mise.js:614:10)[0m
2019-02-02T21:52:17.2422463Z [0m  [0m[97m[41m    at Promise._settlePromises (D:\a\1\s\node_modules\bluebird\js\release\prom[0m  [0m[97m[41mise.js:690:18)[0m
2019-02-02T21:52:17.2422512Z [0m  [0m[97m[41m    at _drainQueueStep (D:\a\1\s\node_modules\bluebird\js\release\async.js:138[0m  [0m[97m[41m:12)[0m
2019-02-02T21:52:17.2422560Z [0m  [0m[97m[41m    at _drainQueue (D:\a\1\s\node_modules\bluebird\js\release\async.js:131:9)[0m
2019-02-02T21:52:17.2422626Z [0m  [0m[97m[41m    at Async._drainQueues (D:\a\1\s\node_modules\bluebird\js\release\async.js:[0m  [0m[97m[41m147:5)[0m
2019-02-02T21:52:17.2422677Z [0m  [0m[97m[41m    at Immediate.Async.drainQueues (D:\a\1\s\node_modules\bluebird\js\release\[0m  [0m[97m[41masync.js:17:14)[0m
2019-02-02T21:52:17.2422769Z [0m  [0m[97m[41m    at runCallback (timers.js:637:20)[0m
2019-02-02T21:52:17.2422832Z [0m  [0m[97m[41m    at tryOnImmediate (timers.js:610:5)[0m
2019-02-02T21:52:17.2422878Z [0m  [0m[97m[41m    at processImmediate [as _immediateCallback] (timers.js:582:5)[0m

npm ERR! Failed at the gatsby-starter-blog@1.0.0 build script 'gatsby build'.
2019-02-02T21:52:17.2430701Z npm ERR! Make sure you have the latest version of node.js and npm installed.
2019-02-02T21:52:17.2430849Z npm ERR! If you do, this is most likely a problem with the gatsby-starter-blog package,
2019-02-02T21:52:17.2431116Z npm ERR! not with npm itself.

您可以简单地使用npm。对于第一次启动,两个构建步骤就足够了:

  • 安装依赖项

    npm安装

  • 建造

    npm运行构建

  • 在此之前,您的package.json需要以下脚本(在每个可用的gatsbyJS样板文件中):


    您可以简单地使用npm。对于第一次启动,两个构建步骤就足够了:

  • 安装依赖项

    npm安装

  • 建造

    npm运行构建

  • 在此之前,您的package.json需要以下脚本(在每个可用的gatsbyJS样板文件中):


    你能提供你的构建yaml吗?我没有yml文件。我使用门户中的GUI来构建管道。实际上,我试图创建一个yml文件,但没有找到一个好的快速启动程序。您可以将可视化设计器数据导出到yaml-如果您在管道上单击“编辑”,则在设计器的右上角应该有一个“查看yaml”按钮(当您在左侧选择了“管道”选项时,这应该是默认选项)@EdwardThomson:谢谢你的提示。此导出是了解yaml工作原理的良好起点。我已编辑问题以添加此文件内容。1。当gatsby develop在本地计算机上运行良好时,请尝试:在本地计算机上运行“gatsby build”。2.用盖茨比初学者试一试,不做任何改动。你能提供你的构建yaml吗?我没有yml文件。我使用门户中的GUI来构建管道。实际上,我试图创建一个yml文件,但没有找到一个好的快速启动程序。您可以将可视化设计器数据导出到yaml-如果您在管道上单击“编辑”,则在设计器的右上角应该有一个“查看yaml”按钮(当您在左侧选择了“管道”选项时,这应该是默认选项)@EdwardThomson:谢谢你的提示。此导出是了解yaml工作原理的良好起点。我已编辑问题以添加此文件内容。1。当gatsby develop在本地计算机上运行良好时,请尝试:在本地计算机上运行“gatsby build”。2.用盖茨比初学者试一试,不做任何更改。我可以看到构建实际上是被触发的,但是,它失败了,出现了一个神秘的错误。我把这个错误放在问题中。正如建议的那样,我尝试了一个未修改的启动器。在本例中,它按预期工作。我可以看到构建实际上被触发,但是,它失败了,出现了一个神秘的错误。我把这个错误放在问题中。正如建议的那样,我尝试了一个未修改的启动器。在本例中,它按预期工作。
    019-02-02T21:52:17.2419822Z [0m
    2019-02-02T21:52:17.2419867Z [0m  [0m[97m[41mError[0m[37m[41m:[0m[37m[41m [0m[97m[41m0-0cf4e58448448331aa6c.js from Terser[0m
    2019-02-02T21:52:17.2421623Z [0m  [0m[97m[41mTypeError: Cannot read property 'minify' of undefined[0m
    2019-02-02T21:52:17.2421678Z [0m  [0m[97m[41m    at minify (D:\a\1\s\node_modules\terser-webpack-plugin\dist\minify.js:175:[0m  [0m[97m[41m22)[0m
    2019-02-02T21:52:17.2421746Z [0m  [0m[97m[41m    at TaskRunner.boundWorkers.error [as boundWorkers] (D:\a\1\s\node_modules\[0m  [0m[97m[41mterser-webpack-plugin\dist\TaskRunner.js:68:40)[0m
    2019-02-02T21:52:17.2421794Z [0m  [0m[97m[41m    at enqueue (D:\a\1\s\node_modules\terser-webpack-plugin\dist\TaskRunner.js[0m  [0m[97m[41m:89:14)[0m
    2019-02-02T21:52:17.2421841Z [0m  [0m[97m[41m    at tryCatcher (D:\a\1\s\node_modules\bluebird\js\release\util.js:16:23)[0m
    2019-02-02T21:52:17.2421906Z [0m  [0m[97m[41m    at Promise._settlePromiseFromHandler (D:\a\1\s\node_modules\bluebird\js\re[0m  [0m[97m[41mlease\promise.js:512:31)[0m
    2019-02-02T21:52:17.2421954Z [0m  [0m[97m[41m    at Promise._settlePromise (D:\a\1\s\node_modules\bluebird\js\release\promi[0m  [0m[97m[41mse.js:569:18)[0m
    2019-02-02T21:52:17.2422390Z [0m  [0m[97m[41m    at Promise._settlePromise0 (D:\a\1\s\node_modules\bluebird\js\release\prom[0m  [0m[97m[41mise.js:614:10)[0m
    2019-02-02T21:52:17.2422463Z [0m  [0m[97m[41m    at Promise._settlePromises (D:\a\1\s\node_modules\bluebird\js\release\prom[0m  [0m[97m[41mise.js:690:18)[0m
    2019-02-02T21:52:17.2422512Z [0m  [0m[97m[41m    at _drainQueueStep (D:\a\1\s\node_modules\bluebird\js\release\async.js:138[0m  [0m[97m[41m:12)[0m
    2019-02-02T21:52:17.2422560Z [0m  [0m[97m[41m    at _drainQueue (D:\a\1\s\node_modules\bluebird\js\release\async.js:131:9)[0m
    2019-02-02T21:52:17.2422626Z [0m  [0m[97m[41m    at Async._drainQueues (D:\a\1\s\node_modules\bluebird\js\release\async.js:[0m  [0m[97m[41m147:5)[0m
    2019-02-02T21:52:17.2422677Z [0m  [0m[97m[41m    at Immediate.Async.drainQueues (D:\a\1\s\node_modules\bluebird\js\release\[0m  [0m[97m[41masync.js:17:14)[0m
    2019-02-02T21:52:17.2422769Z [0m  [0m[97m[41m    at runCallback (timers.js:637:20)[0m
    2019-02-02T21:52:17.2422832Z [0m  [0m[97m[41m    at tryOnImmediate (timers.js:610:5)[0m
    2019-02-02T21:52:17.2422878Z [0m  [0m[97m[41m    at processImmediate [as _immediateCallback] (timers.js:582:5)[0m
    
    npm ERR! Failed at the gatsby-starter-blog@1.0.0 build script 'gatsby build'.
    2019-02-02T21:52:17.2430701Z npm ERR! Make sure you have the latest version of node.js and npm installed.
    2019-02-02T21:52:17.2430849Z npm ERR! If you do, this is most likely a problem with the gatsby-starter-blog package,
    2019-02-02T21:52:17.2431116Z npm ERR! not with npm itself.