8b982ed886
JJB didn't actually handle unicode data very well for a couple reasons. First the local yaml loader was loading files into yaml as strings instead of unicode which we should just go ahead and do because yaml's built int loader loads utf-8 by default (and we don't override the default). Second we need to do parameter substitution on unicode and regular strings so change the substitution typecheck to use basestring instead of str. Finally we need to use UTF-8 as the encoding when emitting XML so do that. Add tests to actually test this in the yamlparser tests. The addition of these new tests comes with a little bit of cleanup in the test classes to make sure we load unicode files as utf8 more consistently. Change-Id: I2169e19aae2cdc7ddbd1e7217ef7584c786a039a Fixes-bug: 1361090
13 lines
238 B
YAML
13 lines
238 B
YAML
- wrapper:
|
|
name: unicode-wrapper
|
|
wrappers:
|
|
- pre-scm-buildstep:
|
|
- shell: |
|
|
#!/bin/bash
|
|
echo "Unicode! ☃"
|
|
|
|
- job:
|
|
name: test-unicode-wrapper
|
|
wrappers:
|
|
- unicode-wrapper
|