Hello,
I'm following the documentation at https://success.outsystems.com/Documentation/Development_FAQs/How_to_automate_OutSystems_Deployments_with_Jenkins
When running the FetchLifeTimeData step I get the following error :
12:31:25 Started by user Jenkins 12:31:25 [EnvInject] - Loading node environment variables. 12:31:25 Building in workspace C:\Program Files (x86)\Jenkins\workspace\Outsystems\FetchLifeTimeData 12:31:25 [EnvInject] - Executing scripts and injecting environment variables after the SCM step. 12:31:25 [EnvInject] - Injecting as environment variables the properties content 12:31:25 LifeTimeUrl=<my Lifetime server> 12:31:25 AuthorizationToken=<my Token> 12:31:25 12:31:25 [EnvInject] - Variables injected successfully. 12:31:25 [FetchLifeTimeData] $ powershell.exe -NonInteractive -ExecutionPolicy ByPass "& 'C:\WINDOWS\TEMP\jenkins6756333568374154746.ps1'" 12:31:26 https://github.com/OutSystems/jenkins/blob/master/scripts/powershell/FetchLifeTimeData.ps1 : The term 12:31:26 'https://github.com/OutSystems/jenkins/blob/master/scripts/powershell/FetchLifeTimeData.ps1' is not recognized as the 12:31:26 name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was 12:31:26 included, verify that the path is correct and try again. 12:31:26 At C:\WINDOWS\TEMP\jenkins6756333568374154746.ps1:1 char:1 12:31:26 + https://github.com/OutSystems/jenkins/blob/master/scripts/powershell/ ... 12:31:26 + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 12:31:26 + CategoryInfo : ObjectNotFound: (https://github....ifeTimeData.ps1:String) [], CommandNotFoundException 12:31:26 + FullyQualifiedErrorId : CommandNotFoundException
Anyone had this error?
Hi Nelson,
I think you have a misconfiguration in the step "WindowsPowershell". I guess it is pointing to github but what you need to to is "Next, copy/paste the contents of the PowerShell script to the Command field".
Please check the documentation and just share if you were able to progress.
Cheers
António
Not familiar with that error, but I'm checking internally to see what I can find out.
After some checking internally, the likely culprit is an error in your configuration. Can you run through the instructions again and double-check and make sure that you've configured things correctly?
I'll follow up if I get any additional info.
G. Andrew Duthie wrote:
I've done it several times already, but I'll do it again.