When compiling on the server side, pass my keystore password in the form of parameters. Is there a good way?

[asking1233]

When compiling locally, my keystore password will be exposed. I want to use mirakle to compile on the server. When compiling on the server side, pass my keystore password in the form of parameters. Is there a good way?

[asking1233]

The keystore password is stored on the server and only I know it

[LuigiVampa92]

When compiling locally, my keystore password will be exposed. I want to use mirakle to compile on the server. When compiling on the server side, pass my keystore password in the form of parameters. Is there a good way?

It really depends how you implement it in build.gradle script. I believe you must first make a logic that will accept keystore password, key alias and key password values as gradle call parameters locally on your computer, and then by calling this command with mirakle enabled, it will be executed the same way with the same parameters on the remote machine.

I think the most correct way is to make mirakle break remote execution on task "signRelease", pull the intermediate results, and then continue to do the signing locally. There is "breakOnTasks" config that mirakle plugin accepts, it is made specifically for such cases, however I hadn't managed to get them working. I personally pass the keystore file and its passwords in the properties file to the server, but that's ok in my case, because I use my own desktop PC as a server