-
To facilitate integration with job schedulers such as jenkins it would help if the `sasjs job execute` command would provide a return code indicating the success (or failure) of a job.
such return …
-
for some reason the `sasjs job execute` command is adding a _local_ filepath to the provided path.
SAS jobs _always_ execute on the server, so wouldn't expect this.
Also, the message says it has…
-
currently the page is empty:
https://cli.sasjs.io/job/
-
Flag `--log` has to be changed to `--logFile` with aliases `--log` and `-l`
Flag `--output` should be changed so that it outputs to a FILE (not folder)
Flag `--status` should be added, to contai…
-
Problem:
Log is being truncated
Cause:
We are fetching the lineCount from logStatistics before the job has completed
![image](https://user-images.githubusercontent.com/4420615/101469848-87…
-
Problem:
The `sasjs create someProject -t jobs` command fails with an exception
Cause:
When running portable git bash on a locked down windows machine the underlying `curl` command fails with…
-
when running `sasjs deploy`, the expectation is always that the `appLoc` will be deleted and rebuilt, so the `-f` flag should be applied by default
![image](https://user-images.githubusercontent.…
-
We should have a max line-length of 80, and each command should be in alphabetical order
![image](https://user-images.githubusercontent.com/4420615/99005258-c64cf900-2540-11eb-8c9d-4fd58a1af694.png…
-
it's ok for output to be json, but the log should be plain text (just the `line` values)
Definition of done:
* log output for `sasjs job` is a plain text file, eg `sasjs job -l ./my/folder/myc…
-