Closed Bug 925402 Opened 11 years ago Closed 11 years ago

Invalid options in Jenkins config

Categories

(Socorro :: Infra, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: lonnen, Unassigned)

Details

We may want to clean these up. # run tests with coverage rm -f coverage.xml PYTHONPATH="." /var/lib/jenkins/jobs/socorro-github/workspace/socorro-virtualenv/bin/coverage run /var/lib/jenkins/jobs/socorro-github/workspace/socorro-virtualenv/bin/nosetests socorro -s --with-xunit ......................................................................................................................................................................................................................................................................................................................................................................................S........................................................................................./var/lib/jenkins/jobs/socorro-github/workspace/socorro-virtualenv/lib/python2.6/site-packages/configman/config_manager.py:663: UserWarning: Invalid options: JENKINS_HOME, BUILD_CAUSE, HUDSON_URL, GIT_BASE_REPO, BUILD_URL, GIT_SHA1, BUILD_TAG, GITHUB_URL, HUDSON_SERVER_COOKIE, JENKINS_URL, LOGNAME, USER, WORKSPACE, MAVEN_HOME, PATH, LD_LIBRARY_PATH, MAKEFLAGS, LANG, TERM, SHELL, GIT_HEAD_REPO, SHLVL, HUDSON_HOME, JOB_NAME, NODE_LABELS, elasticSearchHostname, JENKINS_SERVER_COOKIE, JAVA_HOME, MFLAGS, BUILD_ID, BUILD_NUMBER, RABBITMQ_HOST, HUDSON_COOKIE, JOB_URL, PYTHONPATH, HOME, BUILD_CAUSE_USERIDCAUSE, GIT_COMMIT, ANDROID_HOME, NLSPATH, MAKEOVERRIDES, _, RABBITMQ_VHOST, DEFAULT_SOCORRO_CONFIG_PATH, RABBITMQ_USERNAME, EXECUTOR_NUMBER, NODE_NAME, MAKELEVEL, PWD, DB_HOST, XFILESEARCHPATH, RABBITMQ_PASSWORD, ES_HOST, GIT_BRANCH 'Invalid options: %s' % ', '.join(unmatched_keys) ........./var/lib/jenkins/jobs/socorro-github/workspace/socorro-virtualenv/lib/python2.6/site-packages/configman/config_manager.py:663: UserWarning: Invalid options: JENKINS_HOME, database_hostname, BUILD_CAUSE, HUDSON_URL, GIT_BASE_REPO, BUILD_URL, GIT_SHA1, database_superusername, BUILD_TAG, GITHUB_URL, HUDSON_SERVER_COOKIE, JENKINS_URL, LOGNAME, USER, WORKSPACE, MAVEN_HOME, PATH, LD_LIBRARY_PATH, MAKEFLAGS, LANG, TERM, SHELL, GIT_HEAD_REPO, SHLVL, HUDSON_HOME, JOB_NAME, NODE_LABELS, elasticSearchHostname, JENKINS_SERVER_COOKIE, JAVA_HOME, MFLAGS, BUILD_ID, BUILD_NUMBER, RABBITMQ_HOST, HUDSON_COOKIE, JOB_URL, PYTHONPATH, HOME, database_username, database_password, BUILD_CAUSE_USERIDCAUSE, GIT_COMMIT, ANDROID_HOME, NLSPATH, MAKEOVERRIDES, _, RABBITMQ_VHOST, DEFAULT_SOCORRO_CONFIG_PATH, RABBITMQ_USERNAME, database_superuserpassword, EXECUTOR_NUMBER, NODE_NAME, MAKELEVEL, PWD, DB_HOST, database_port, XFILESEARCHPATH, RABBITMQ_PASSWORD, ES_HOST, GIT_BRANCH 'Invalid options: %s' % ', '.join(unmatched_keys) ............................................................................................................................................................................................................................................................................... ----------------------------------------------------------------------
selena, brandon, adrian, peterbe -- any idea whats up here?
Tempted to WONTFIX this because there's little we can do. Or should do. Every configman app will, by default, print a UserWarning if your ini file or environment variables aren't recognized by the program. And because nosetests starts many different apps, individually they'll complain about excess options set. The only time this will have this massive outburst of junk warnings is during nosetests of the directory. What say you Lars?
Flags: needinfo?(lars)
It seems to me that I've addressed this in the latest configman. It doesn't whine about unmatched things from the environment. I'll go look. Even if I didn't already address it, I plan on doing so.
Flags: needinfo?(lars)
Happy to wait for that, then.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.