[SOE.POC] Running batch script
> C:\Jenkins\workspace\SOE.POC\SOE.POC>yarn install --frozen-lockfile
> yarn install v1.5.1
> warning package.json: No license field
> warning soe@0.0.0: No license field
> [1/4] Resolving packages...
> success Already up-to-date.
> Done in 1.33s.
> [Pipeline] }
>
Yep - the middle section of the first post is when I ran directly as the
user on the server. The error codes are fine and the build worked just
great. It appears to only be an issue when transferring back information to
Jenkins to continue doing the pipeline.
On Thursday, March 8, 2018 at 9:31
Have you tried running the same command in powershell directly to see if
the behavior is just powershell itself?
On Thu, Mar 8, 2018 at 8:20 AM Joe Cavanaugh
wrote:
> bat 'yarn install' works fine. It seems that the powershell key word does
> not work correctly in declarative pipelines consisten
bat 'yarn install' works fine. It seems that the powershell key word does
not work correctly in declarative pipelines consistently.
On Thursday, March 8, 2018 at 9:02:38 AM UTC-6, Joe Cavanaugh wrote:
>
> I didn't post the error message :
>
> ERROR: script returned exit code 1
> Finished: FAILU
I didn't post the error message :
ERROR: script returned exit code 1
Finished: FAILURE
On Wednesday, March 7, 2018 at 4:51:41 PM UTC-6, Joe Cavanaugh wrote:
>
> stage('Build') {
> steps {
> powershell '''
> Write-Output "Starting Yarn Install"
> try
stage('Build') {
steps {
powershell '''
Write-Output "Starting Yarn Install"
try {
\$ErrorActionPreference = 'Stop'
yarn install
} catch {
Write-Output "Install failed : \$PSItem"
}
