We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi sfcc-ci team,
sfcc-ci sandbox:create --realm bdtw -s -j
returning 2 almost identical JSON objects (instead of one) and only time in milliseconds is different there. Example:
...finished (314646 ms). Sandbox id is ... ...finished (318858 ms). Sandbox id is ...
Because of this issue, commands (bellow) are not working, as SANDBOX_HOST now is 2 values in different rows with the same value:
SANDBOX=`sfcc-ci sandbox:create <a-realm> -s -j` SANDBOX_HOST=`$SANDBOX | jq '.instance.host' -r` sfcc-ci code:deploy <path/to/code.zip> -i $SANDBOX_HOST sfcc-ci instance:upload <path/to/data.zip> -i $SANDBOX_HOST -s sfcc-ci instance:import <data.zip> -i your-instance.demandware.net
Visual evidence:
Based on the slack discussion steps to reproduce is to use -s parameter.
-s
There is a workaround for me to use in the Docker as following: and to run the jobs after I just read the first row:
but that would be great to have this issue fixed as well :)
Regards, Oleg
The text was updated successfully, but these errors were encountered:
As a workaround @EvilJordan also suggested to use sfcc-ci sandbox:create --sync --json | jq -s -r '.[0]' while fix is not in place as of yet.
sfcc-ci sandbox:create --sync --json | jq -s -r '.[0]'
🌮 for that 🥇
Sorry, something went wrong.
No branches or pull requests
Hi sfcc-ci team,
returning 2 almost identical JSON objects (instead of one) and only time in milliseconds is different there. Example:
Because of this issue, commands (bellow) are not working, as SANDBOX_HOST now is 2 values in different rows with the same value:
Visual evidence:
Based on the slack discussion steps to reproduce is to use
-s
parameter.There is a workaround for me to use in the Docker as following:
and to run the jobs after I just read the first row:
but that would be great to have this issue fixed as well :)
Regards,
Oleg
The text was updated successfully, but these errors were encountered: