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:45 AM UTC-6, slide wrote:
>
> 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 <joe.d.cava...@gmail.com
> <javascript:>> wrote:
>
>> 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: 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 {
>>>> \$ErrorActionPreference = 'Stop'
>>>> yarn install
>>>> } catch {
>>>> Write-Output "Install failed : \$PSItem"
>>>> }
>>>> '''
>>>> }
>>>> }
>>>>
>>>> However, when I run the command on the server itself in the directory,
>>>> all i get is
>>>>
>>>>> yarn install v1.5.1
>>>>>
>>>>> yarn : warning package.json: No license field
>>>>>
>>>>> At line:1 char:19
>>>>>
>>>>> + try { yarn install --frozen-lockfile } catch {
>>>>>> ...
>>>>>
>>>>> + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>>>
>>>>> + CategoryInfo : NotSpecified: (warning package.json: No
>>>>>> license field:String) [], RemoteException
>>>>>
>>>>> + FullyQualifiedErrorId : NativeCommandError
>>>>>
>>>>>
>>>>>> warning soe@0.0.0: No license field
>>>>>
>>>>> [1/4] Resolving packages...
>>>>>
>>>>> success Already up-to-date.
>>>>>
>>>>> Done in 2.16s.
>>>>>
>>>>> [blwdsoabuild4]: PS C:\Jenkins\workspace\SOE.POC> echo $LASTEXITCODE
>>>>>
>>>>> 0
>>>>>
>>>>>
>>>> Seems to me that the powershell method is incorrectly interpreting the
>>>> warning as a remote exception... The catch never gets hit, and even if I
>>>> set the $global:LASTEXITCODE to zero after the yarn install line it still
>>>> fails.
>>>>
>>>> Any hints as to what else to try or consider would be greatly
>>>> appreciated. Yarn Version is 1.5.2 and Node is LTS (8.9.4) with Powershell
>>>> version 5.1.
>>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-use...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/6b3b58f6-a870-43d6-800f-6396329ad8b0%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/jenkinsci-users/6b3b58f6-a870-43d6-800f-6396329ad8b0%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/bdb03d61-ee14-4e06-aecd-e6bf3c8aef78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
