status-react/ci
Jakub Sokołowski 58d20967ae
nix: use jsbundle derivation for iOS as well
For some unknown to me reason we are using a different Yarn call to
Shadow-cljs to generate the JSBundle for iOS builds, while the one
created by the Android derivation shoudl be exactly the same.

I'm changing the target to just be `make jsbundle` while keeping aliases
referencing old naming, and moving things around in `nix` folder to
reflect the fact that the derivation is no longer Android-specific.

Also, crucially, I've changed the `import` in `index.js` to use the
`./result/index.js` path, since that's what Nix creates. I'm not sure if
this clashes with any developer workflow that takes place locally, so
I'd appreciate some testing from developers.

Depends on: https://github.com/status-im/status-jenkins-lib/pull/67

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-05-22 10:31:09 +02:00
..
tests nix: use jsbundle derivation for iOS as well 2023-05-22 10:31:09 +02:00
tools nix: use jsbundle derivation for iOS as well 2023-05-22 10:31:09 +02:00
Jenkinsfile remove old jenkisnfiles 2018-09-04 07:39:40 -04:00
Jenkinsfile.android nix: use jsbundle derivation for iOS as well 2023-05-22 10:31:09 +02:00
Jenkinsfile.combined nix: use jsbundle derivation for iOS as well 2023-05-22 10:31:09 +02:00
Jenkinsfile.ios nix: use jsbundle derivation for iOS as well 2023-05-22 10:31:09 +02:00
Jenkinsfile.nix-cache nix: use jsbundle derivation for iOS as well 2023-05-22 10:31:09 +02:00
Jenkinsfile.tests nix: use jsbundle derivation for iOS as well 2023-05-22 10:31:09 +02:00
README.md ci: upgrade jenkins lib to 1.2.12 to generalize GH release 2021-04-19 11:47:34 +02:00

README.md

Description

This folder contains files defininf Jenkins pipelines that run on https://ci.status.im/.

Libraries

All Jenkinsfiles contain the following line:

library 'status-jenkins-lib@master'

Which loads the used methods - like nix.shell() - from a separate private repo:

https://github.com/status-im/status-jenkins-lib

This is done to improve security of our CI setup.