Build #442

Plan branch:

Build: #442 failed Changes by Ian Bacher

Stages & jobs

  1. Default Stage

  2. Release

    Requires a user to start manually

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
40 minutes
Labels
None
Revisions
SDK
04f4befe0e535a414162aede1326ecb82d46f90d 04f4befe0e535a414162aede1326ecb82d46f90d
Release scripts
c4475a9228b197817dce78683d9da8a1e2c4e3a5 c4475a9228b197817dce78683d9da8a1e2c4e3a5
Failing since
#434 (Manual run by Daniel Kayiwa – )
Fixed in
#446 (Manual run from the stage: Release by Ian Bacher)
No failed test found. A possible compilation error occurred.

Responsible

This build has been failing since #434
No one has taken responsibility

Code commits

SDK
Author Commit Message Commit date
Ian Bacher Ian Bacher 04f4befe0e535a414162aede1326ecb82d46f90d 04f4befe0e535a414162aede1326ecb82d46f90d Try using "npm exec -- " directly instead of npx
The idea here is that running npx through the maven-frontend-plugin isn't
one-to-one the same as executing the command from the shell, so that by
using npm exec, we can pass the --cache argument and then run
"npm exec --cache=... -- <command>"

Configuration changes

Plan configuration has changed since the last successful build. See the plan audit log for more details.