Add Jenkins parameterized build config file

[oskarth]

Addresses #2511

reviewers: sanity check (actual code is in Jenkins anyway)

testers: feedback on what you want to toggle, and test parameterized build

status: ready

[oskarth]

Should probably print repo

[oskarth]

Moved to 'ready for testing', possibly prematurely for two reasons:

1. Code that is live is actually live already at Jenkins by necessity - only way to test, ephemeral config and I kind of overwrote it :morty:

2. Want to make sure normal external contributor PRs still work, hence testing stage, this is just a copy of this.

Regardless it'd be good to get a review on this, pinging 9-dev-xp swarm for thoughts. See comments for known downsides #2511 (comment) - if you have solutions shoot. I know it can be shell-fued but didn't have time to make it robust enough, hence this simplistic approach.

[annadanchenko]

@rasom what parameters do we toggle for the production release and with what values? It would be great if we can just build the release candidates on our own using the params in Jenkins. So, if some of the "production" parameters is missing, please tell which one. And of course which values to use :)

[oskarth]

@annadanchenko https://github.com/status-im/status-react/blob/develop/.env.prod

Additionally some certificate stuff, but we can defo do RC this way :)

[oskarth]

Before merge: probably fix this #2553 (review)

[rasom]

@oskarth i also added repo name to slack messages in jenkins configurations, it makes a bit simpler to distinguish parametrized builds from these which are built form branches, like

slackSend color: 'good', message: REPO + ":" + BRANCH_NAME + ' build started. ' + env.BUILD_URL

and

slackSend color: c, message: 'Branch: ' + REPO + ":" + BRANCH_NAME +

[yenda]

I think we should remove this line now, also once react-native will be updated this won't work anymore as the packager is now a separate project

[oskarth]

@yenda Can you raise an issue and we test/do this in a separate PR and for all Jenkinsfiles? This is not in scope of this PR IMO (and also need to update it in Jenkins).

[rasom]

let's just try it on jenkins first

[yenda]

It was already commented out in jenkins until @oskarth updated it with that script

[oskarth]

Thanks @rasom, I'll look at this file in Jenkins and put it in this file, then merge. Soonish.

[oskarth]

FYI, added this to live version (with same default values as env.jenkins):

sh 'echo JSC_ENABLED='               + JSC_ENABLED               + '>>' + '.env'
sh 'echo OFFLINE_INBOX_ENABLED='     + OFFLINE_INBOX_ENABLED     + '>>' + '.env'

Also uncommented back sh 'sed -i "" "s/301000/1201000/g" node_modules/react-native/packager/src/JSTransformer/index.js' since all parameterized builds are failing without it right now.

[yenda]

@oskarth No, it was update-react-native build only that was failing and it is not related to this. Now it will fail because of the sed

[oskarth]

@rasom @yenda updated to reflect current Jenkins config at jenkins.status.im - if you have no objections, can you please approve and lets merge this?