Before, it was not possible to use the stateName parameter to place the state file outside of the deploy directory, because the entire stateName parameter was also used to determine where to store the local state file.
This serves no purpose, as the local state file is never uploaded and thrown away when the job finishes.
This issue changes the location of the local state file to always be ./local_state.json, meaning that you can now use stateName to place the state file outside the deploy directory by using parameters such as:
serverDir: somefolder/deployfolderstateName: ../statefile.json
Before, it was not possible to use the stateName parameter to place the state file outside of the deploy directory, because the entire stateName parameter was also used to determine where to store the local state file.
This serves no purpose, as the local state file is never uploaded and thrown away when the job finishes.
This issue changes the location of the local state file to always be
./local_state.json, meaning that you can now use stateName to place the state file outside the deploy directory by using parameters such as:serverDir:somefolder/deployfolderstateName:../statefile.json