Description of problem: Given a Jenkins server app, the description of the env vars, JENKINS_USERNAME and JENKINS_PASSWORD, references the "Admin user on jenkins server" and "Admin user's password for jenkins server", but the values of these credentials are the system_builders. We could either change the description about the env, or change the value of the env if jenkins build will not use this env to locate username ,password Version-Release number of selected component (if applicable): INT(devenv_3479) How reproducible: always Steps to Reproduce: 1. create a Jenkins server 2. check the REST API of the app's Jenkins-1 cartridge 3. ssh into this app, and check the values of JENKINS_USERNAME, and JENKINS_PASSWORD Actual results: In step 2, the REST API describes the two env vars as "Admin user": { "description": "Admin user on jenkins server", "name": "JENKINS_USERNAME", "type": "environment" }, { "description": "Admin user's password for jenkins server", "name": "JENKINS_PASSWORD", "type": "environment" } But the values of these two env vars refers to system_builder, instead of admin: JENKINS_PASSWORD=lX-VEXHMrXjI JENKINS_USERNAME=system_builder Expected results: The description and values of the Jenkins env vars should match. Additional info:
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/ac697c2beedb5e87aa51cdf0eabe6b1b14fbc0ef Bug 1005119 - Updated manifest.yml text
Verified in devenv_3762 { "description": "User on jenkins server for automated builds", "name": "JENKINS_USERNAME", "type": "environment" }, { "description": "Automated build user's password for jenkins server", "name": "JENKINS_PASSWORD", "type": "environment" }