On 26.11.2015, at 16:35, Fernando Boaglio <
boa...@gmail.com> wrote:
> 1. When I run my plugin, I setup and save it global preferences, the xml is created at Jenkins Home, but when I go back everything is blank. If I run the plugin, it works fine, but the user can never see what the old configuration was.
Try using standard getters and setters (`private String oracleHome` will have the getter `public String getOracleHome()` and the setter `public void setOracleHome(String …)`) rather than what you're doing now.
> 2. This user is trying to run on a slave machine, should I change anything to make my plugin work on slave machines ?
https://wiki.jenkins-ci.org/display/JENKINS/Making+your+plugin+behave+in+distributed+Jenkins should get you started. It's also really easy to set up a slave on the same machine to test this.
> 3. I am aware of the translation process of Jenkins, but I don´t know how can I translate my plugin, if I put all the messages inside a properties file, how can I read this message ?
Everything you need to know about this is documented at
https://wiki.jenkins-ci.org/display/JENKINS/Internationalization
> Can I force a default language or Jenkins will do it for me ?
Jenkins will serve the default translation (in e.g. Messages.properties) if no better matching one is found (e.g. Messages_de.properties).