Should only display "result" message when creating jenkins apps or embedding cartridges --------------------------------------------------------------------------------------- Key: JBIDE-14509 URL: https://issues.jboss.org/browse/JBIDE-14509 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.1.0.Alpha2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.0.Beta2 Attachments: jenkins.png When creating jenkins applications or embedding cartridges we show in a dialog what OpenShift reports back to us: * creating jenkins: {code} "messages":[ { "exit_code":null, "field":null, "severity":"info", "text":"Application jekyll was created." }, { "exit_code":0, "field":"current_ip", "severity":"info", "text":"107.21.169.102" }, { "exit_code":0, "field":"result", "severity":"info", "text":"\nJenkins created successfully. Please make note of these credentials:\n\n User: admin\n Password: edWlFXhq-BqY\n\nNote: You can change your password at: https://jekyll-foobarz.rhcloud.com/me/configure\n\n" } ], {code} * embedding mysql: {code} "messages":[ { "exit_code":null, "field":null, "severity":"info", "text":"Added mysql-5.1 to application springeap6" }, { "exit_code":0, "field":"result", "severity":"info", "text":"\nMySQL 5.1 database added. Please make note of these credentials:\n\n Root User: adminnFC22YQ\n Root Password: U1IX8AIlrEcl\n Database Name: springeap6\n\nConnection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/\n\nYou can manage your new MySQL database by also embedding phpmyadmin-3.4.\nThe phpmyadmin username and password will be the same as the MySQL credentials above.\n" }, { "exit_code":0, "field":"appinfo", "severity":"info", "text":"Connection URL: mysql://127.13.125.1:3306/\n" } {code} Whe show all message blocks we get back. In case of OpenShift Enterprise this results in us showing non-routeable internal IPs: !jenkins.png! Talking to Dan McPherson and Brenton LeanHardt we decided to only show the *result* filed and thus not show those internal IPs any more. {quote} Personally I think "result" is the only thing that's useful. It's not like users can connect to mysql://127.13.125.1:3306 in the MySQL case without port forwarding. And we don't want them hardcoding IP addresses either. It's much better to use the ENV vars that are printed in the "result" field. {quote}