On Wed, 19 Apr 2017, 'J Hawkesworth' via Ansible Project wrote:
I would recommend using win_package - that's what I use to maintain java
versions in our playbooks.
For info, recent java versions like to upgrade themselves. While this is
laudable it may cause unexpected behaviours as clusters start running
different java versions. So I would strongly recommend checking the
command line options for the java installer you are using. Below are the
command line arguments that we use on some systems:
arguments: INSTALL_SILENT=1 AUTO_UPDATE=0 WEB_JAVA=0 WEB_ANALYTICS=0 /s
/L C:\ansible\log\java-installation.log
# added install options based on options here:
http://docs.oracle.com/javase/8/docs/technotes/guides/install/config.html#table_config_file_options
Jon,
I think that example deserves to be part of the win_package documentation.
To draw the attention to a common issue, and to showcase using win_package
for Java installation, a common thing people tend to do :-)
Examples like this greatly improves the user-experience of the
documentation, and to a greater extent, Ansible.
Everyone else,
We do accept improvements to the documentation, so if you come across a
nice solution with the potential of being a great example to others, feel
free to edit the documentation (through the website, or GitHub). No prior
knowledge of git or internal processes required.
--
Dag
--
You received this message because you are subscribed to the Google Groups "Ansible
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/alpine.LRH.2.20.1705091453460.19483%40pikachu.3ti.be.
For more options, visit https://groups.google.com/d/optout.
