blog/azure-devops-gatsbyjs-build-pipeline/

[utterances-bot]

Azure DevOps - GatsbyJs Build Pipeline | Abhith Rajan

Continuous Integration & Continuous Deployment for your GatsbyJS website using Azure Pipelines.

https://www.abhith.net/blog/azure-devops-gatsbyjs-build-pipeline/

[Bartosz-L]

Can you provide explanation for this line:
rootDirectory: '$(System.DefaultWorkingDirectory)/_Abhith.abhith.net/drop' ?
How do I get proper path?

[abhith]

@Bartosz-L You can select the path using the "..." button near to the Root folder textbox with the title (on hover) Browse Root Folder, in the FTP upload task.

And that will open the folder browser,

Choose the parent folder which basically contains the build artifacts.

[Bartosz-L]

I just used plain yaml based pipline without any creator. There is no such option as yours. I'm uploading files with regular FtpUpload@2 task. Any further suggestions? Thanks for the response anyway!

trigger:
- master

pool:
  vmImage: 'ubuntu-latest'

jobs:
  - job : BuildProject
    steps:
    - task: NodeTool@0
      inputs:
        versionSpec: '10.x'
      displayName: 'Install Node.js'

    - script: |
        npm install -g gatsby-cli
      displayName: 'Install gatsby-cli'

    - script: |
        yarn install
      displayName: 'Install dependencies'

    - script: |
        gatsby build
      displayName: 'Gatsby build'

    - task: CopyFiles@2
      inputs:
        sourceFolder: 'public'
        contents: '**' 
        targetFolder: '$(Build.ArtifactStagingDirectory)'
        cleanTargetFolder: true 
      displayName: 'Copy built site'
      condition: and(succeeded(), ne(variables['Build.Reason'], 'PullRequest'))

    - task: PublishBuildArtifacts@1
      inputs:
        PathtoPublish: '$(Build.ArtifactStagingDirectory)'
        ArtifactName: 'deploy'
        publishLocation: 'Container'
      condition: and(succeeded(), ne(variables['Build.Reason'], 'PullRequest'))
      displayName: 'Publish Build Artifacts'
  - job : SendToFTP
    dependsOn: BuildProject
    steps:
    - task: FtpUpload@2
      displayName: 'FTP Upload to remote'
      inputs:
        credentialsOption: inputs
        serverUrl: blahblahblah
        username: blahblahblah
        password: blahblahblah
        rootDirectory: '$(System.DefaultWorkingDirectory)/drop'
        remoteDirectory: blahblahblah
        preservePaths: true
        trustSSL: true
      condition: and(succeeded(), ne(variables['Build.Reason'], 'PullRequest'))

my file looks like this and I just cant get proper rootDirectory in ftp

[abhith]

@Bartosz-L The FTP upload task is in Release pipeline not in the Build Pipeline.
Under the pipelines menu, there is "Releases". Create a release pipeline there, and you will see the GUI as shown above, I skipped the Release Pipeline part in this post. But will update the post to include that part too.

[Bartosz-L]

@Bartosz-L The FTP upload task is in Release pipeline not in the Build Pipeline.
Under the pipelines menu, there is "Releases". Create a release pipeline there, and you will see the GUI as shown above, I skipped the Release Pipeline part in this post. But will update the post to include that part too.

Thank You. My mistake. All done and working well. Great job with the article!