Bug 1116819
Summary: | Jenkins build for app reports "InvalidByteSequenceError" | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Brenton Leanhardt <bleanhar> |
Component: | ImageStreams | Assignee: | Luke Meyer <lmeyer> |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 2.1.0 | CC: | adellape, bmeng, bparees, jialiu, jokerman, jolamb, libra-bugs, libra-onpremise-devel, lmeyer, mmccomas |
Target Milestone: | --- | Keywords: | Upstream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openshift-origin-cartridge-jenkins-client-1.19.3.5-1.el6op | Doc Type: | Bug Fix |
Doc Text: |
Previously, the Jenkins client cartridge did not define a character encoding for builds. As a result, builds reported "InvalidByteSequenceError" failures in some cases, although the build was actually successful. This bug fix updates the Jenkins client cartridge to define a default character set of UTF-8, and the error message no longer appears during builds.
|
Story Points: | --- |
Clone Of: | 1114948 | Environment: | |
Last Closed: | 2014-10-02 13:59:35 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1114948 | ||
Bug Blocks: |
Description
Brenton Leanhardt
2014-07-07 11:30:14 UTC
I encontered this issue today twice, could you help merge the PR into ose-2.1.z? Verified this bug with openshift-origin-cartridge-jenkins-client-1.19.3.5-1.el6op.noarch, and PASS. The following line is added into jenkins-client/bin/jenkins_build Encoding.default_external = "utf-8" And when doing jenkins build, the above error is not seen any more. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1353.html |