This fixes issues like :
11:16:59 + s3cmd --stats --acl-public --no-preserve --host=ams3.digitaloceanspaces.com '--host-bucket=%(bucket)s.ams3.digitaloceanspaces.com' put pkg/StatusIm-Desktop-250205-101034-e6dfac-pr17210-aarch64.dmg s3://status-im-desktop-prs/
11:16:59 /opt/homebrew/Cellar/s3cmd/2.4.0_1/libexec/lib/python3.13/site-packages/S3/S3Uri.py:122: SyntaxWarning: invalid escape sequence '\.'
11:16:59 m = re.match("(.*\.)?s3(?:\-[^\.]*)?(?:\.dualstack)?(?:\.[^\.]*)?\.amazonaws\.com(?:\.cn)?$",
11:16:59 /opt/homebrew/Cellar/s3cmd/2.4.0_1/libexec/lib/python3.13/site-packages/S3/S3Uri.py:170: SyntaxWarning: invalid escape sequence '\w'
11:16:59 _re = re.compile("^(\w+://)?(.*)", re.UNICODE)
11:16:59 /opt/homebrew/Cellar/s3cmd/2.4.0_1/libexec/lib/python3.13/site-packages/S3/FileLists.py:525: SyntaxWarning: invalid escape sequence '\*'
11:16:59 wildcard_split_result = re.split("\*|\?", uri_str, maxsplit=1)
11:17:00 ERROR: SSL certificate verification failure: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1018)
- we also bump nix interpreter version to 2.24.11
- we also use a newer image which has support for nix-shell since sc5cmd needs a nix-shell
* chore: identify version numbers using a git tag
- remove VERSION file
- expose the `GIT_COMMIT`so that we can properly construct the web links
when the user clicks the version number in Settings/About
- some smaller cleanups and warning fixes
Fixes#12349
* fix_: ci artifact version and use version scripts
---------
Co-authored-by: Igor Sirotin <sirotin@status.im>
An error has shown that Nim compilation uses cache folder in `jenkins` home:
```
clang: error: no such file or directory:
'/Users/jenkins/.cache/nim/nimsuggest_r/@m..@slib@swrappers@slinenoise@slinenoise.c.o'
```
This is a bad idea as parallel CI builds can result in very bizzarre bugs.
Signed-off-by: Jakub Sokołowski <jakub@status.im>
This commit points to `status-jenkins-lib` version where we provide api-proxy credentials to Jenkins in CI and the desktop build would then get these env vars
- `STATUS_BUILD_PROXY_USER`
- `STATUS_BUILD_PROXY_PASSWORD`
