[OpenStack-Infra] Request to add project to openstack/ namespace
Greetings, infra team I would like to ask for review of the following change: https://review.openstack.org/#/c/286137/ It adds project called 'fuel-tuning-box'. This is the Fuel Configuration Store service, a component of Fuel architecture facilitating the flow of the configuration data between other components. Please, consider adding this repository to the openstack/ namespace. -- Best regards, Oleg Gelbukh Principal Engineer Mirantis Inc ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] JJB nested template variables
Hi Everyone,
I'm trying to nest template variables and discovered that JJB behaves in a
way I didn't expect when a template variable is nested. For example:
- project:
name: test
jobs:
- '{name}-verify-{value}-{jdk}'
value:
- a:
jdk:
- openjdk8
- job-template:
name: '{name}-verify-{value}-{jdk}'
When jdk is nested under the value a. It generates a job with the name:
*'test-verify-a-['\''openjdk8'\'']'*
You'll notice the name also includes extra single quotes at the beginning
and end of the job name itself in addition to a python list being passed
out in place of the jdk variable. However if you don't nest JDK and put it
by itself you get the expected name of *test-verify-a-openjdk8 *without the
extra single quotes and python list.
I'd be interested in attempting to fix this since I have a use case for
having job templates with nested variables. Would this be something that's
easy to fix or would this have some larger affect on the code base?
Can someone point me to the code files related to the template name scheme.
I can have a poke at it and see if it's something that can be fixed.
Thanks,
Thanh
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
