CI/CD Project

• 
  Hi Thibault
  
  Sorry to hear you're experience this issue!
  
  I've noticed that the two paths are slightly different and end up cutting off  after "\Octopus\Tentacles\SQL_UAT"
  
  Can you verify if that's the case?

  DanC July 07, 2020 11:14

  - 0 +
• 
  I don't see any cutting off.
  "D:\Octopus\Tentacles\SQL_UAT\Applications\UAT\AccountsDb.Metering\1.0.4"
  this path seems to be the same everywhere.
  Or am I missing one?
  

  Thibault July 07, 2020 11:22

  - 0 +
• 
  Hi @Thibault
  
  Apologies, Ignore my last remark I got confused with the pathing.
  
  So looking at the logs it looks like the following is occurring
  
  - Deploying package:    \Octopus\Tentacles\SQL_UAT\Files\AccountsDb.Metering@S1.0.4@1BD081527BDE4E4699D858E245E52DCC.nupkg
  
  - Extracting package to: \Octopus\Tentacles\SQL_UAT\Applications\UAT\AccountsDb.Metering\1.0.4
  
  - The package has been installed to: \Octopus\Tentacles\SQL_UAT\Applications\UAT\AccountsDb.Metering\1.0.4
  
  - Path: \Octopus\Tentacles\SQL_UAT\Applications\UAT\AccountsDb.Metering\1.0.4
  
  - The file or folder is not a valid build artifact: 'D:\Octopus\Tentacles\SQL_UAT\Applications\UAT\AccountsDb.Metering\1.0.4'
  
  If you go to that folder location does the package exist and is it a ".nupkg"?
  
  
  

  DanC July 07, 2020 11:42

  - 0 +
• 
  The package seems to be there, but I checked the nupgk, and if I check it against similar builds there seems to be a folder 'db' missing from the package.
  I don't know how to fix this.
  
  

  Thibault July 07, 2020 13:41

  - 0 +
• 
  Hi @Thibault
  
  That's very odd and I suspect there's something going on with the package creation. 
  
  Can I ask how you're creating the package?

  DanC July 07, 2020 14:18

  - 0 +
• 
  We are building the package using the TeamCity templates for creating a nuget package.
  

  Thibault July 07, 2020 14:20

  - 0 +
• 
  Hi @Thibault
  
  Thanks for that, could you send me TeamCity logs for the creation of that package?

  DanC July 07, 2020 14:37

  - 0 +
• 
  Hi @DanC
  

  
  

  Certainly!
  

  
  

  Thibault July 08, 2020 07:04

  - 0 +
• 
  Hi @Thibault
  
  Thanks for sharing that with me!
  
  Can I check with you, are you using a SQL Source Control project as the source?

  DanC July 08, 2020 09:28

  - 0 +
• 
  We are using a SQL Change Automation project
  

  Thibault July 08, 2020 09:48

  - 0 +
• 
  Hi @Thibault
  
  Thanks for confirming that for me! so from the logs it looks like you're potentially using the wrong Runner type as it's looking for a SQL Source Control project.
  

  Validating SQL Source Control project 'D:\TeamCity\BuildAgent1\work\98432a360a2ad247'.

  
  Could you check that's the case for me?
  
  The following documentation should help: https://documentation.red-gate.com/sca/deploying-database-changes/add-ons/teamcity/use-the-teamcity-plugin-with-a-sql-change-automation-project

  DanC July 08, 2020 10:14

  - 0 +
• 
  Hi @DanC

  
  

  We have found the problem, it was building the Master branch and not my pull request..

  My bad!
  

  Thank you for all your help!
  
  

  Thibault July 09, 2020 05:40

  - 0 +
• 
  Hi @Thibault
  
  Ah brilliant, glad you managed to find the issue!
  
  You're most welcome and if you have any other issues don't hesitate to contact us at Redgate Support!

  DanC July 09, 2020 09:13

  - 0 +

Add comment

Please sign in to leave a comment.