| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Because of historical reason, set -e is ignored inside function bodies
[1], which caused the script to attempt to share a file even if the
upload had failed.
[1]: https://lists.gnu.org/archive/html/bug-bash/2012-12/msg00094.html
|
| |
|
|
|
|
|
| |
The former might not be available on older versions of cURL, such as
that distributed by Ubuntu focal. Also, upload-artifact is not
interested in the HTTP body returned on 4xx errors, so the latter is
more appropriate.
|
| |
|
|
|
| |
Otherwise, uploads without the `-d` flag are broken because the first
file is considered the directory to upload to.
|
| | |
|
| |
|
|
|
| |
So far, the root directory (i.e., /) was assumed as the directory to
upload artifacts to. This might be too limiting for some users.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Under some circumstances, curl(1) sends 100-continue to the HTTP server.
[1] While this is handled correctly by slcl, when used together with
Apache as a reverse proxy, for some unknown reason the Content-Length is
not sent to slcl by Apache, and therefore returns a 502 Proxy Error.
Setting the proxy-sendcl environment variable [2] to Apache did not help,
either.
[1]: https://gms.tf/when-curl-sends-100-continue.html
[2]: https://httpd.apache.org/docs/current/mod/mod_proxy.html#request-bodies
|
| |
|
|
|
| |
USER is an environment variable that might be already defined by the
shell.
|
|
|
As its name suggests, this simple shell script allows to upload one or
more artifacts to a slcl instance.
|
