Bug 1056666
Summary: | Jenkins cartridge InvalidPathException with é or ' | |||
---|---|---|---|---|
Product: | OpenShift Online | Reporter: | Aidan Delaney <a.j.delaney> | |
Component: | Image | Assignee: | Ben Parees <bparees> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> | |
Severity: | low | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 2.x | CC: | bmeng, chunchen, libra-bugs | |
Target Milestone: | --- | Flags: | bparees:
needinfo+
|
|
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1091191 (view as bug list) | Environment: | ||
Last Closed: | 2014-03-12 03:06:20 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: | ||||
Bug Blocks: | 1091191 |
Description
Aidan Delaney
2014-01-22 16:40:17 UTC
This appears to be a limitation of jenkins itself: http://jenkins-ci.361315.n4.nabble.com/Re-What-characters-are-illegal-to-include-in-job-names-td4678893.html Have you seen this behavior work in a standalone jenkins environment? If so, what version? OpenShift currently uses Jenkins v1.509, but I don't see anything in the current code that would have changed this codepath. Oh, sorry for the dodgy report then. I've generally used the GitHub plugin in the past, example here: http://54.194.213.207/job/Eric%27s%20WebProt%C3%A9g%C3%A9/ which seems to cope with these characters. On further analysis this does seem to work in a standalone jenkins install, so there may be something different about our gear environment that doesn't tolerate those characters. I'll dig further. Interestingly this problem appears togo away if you do a restart of the jenkins cartridge. I'm still investigating, but perhaps you can use that as a workaround for now. fyi I determined the cause here is a missing LANG=en_US.UTF.8 environment variable, which i'll be adding shortly. In the meantime, if you ssh into the gear and issue a "jenkins/bin/control restart" then you'll restart the process w/ the environment variable, as it exists correctly in the ssh shell. if you do "rhc app restart jenkins" it will still not have it, so the actual workaround requires ssh'ing into the gear. (unless you explicitly add the LANG env variable to your jenkins app) Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/718326d5835969eefc043ad63929b53e3edf443b Bug 1056666 - Jenkins cartridge InvalidPathException with é or ' It's fixed, verified on devenv_4270, please refer to the following results: 1. Create an app with jenkins-client-1 app rhc app create cphp4 php-5.4 --enable-jenkins 2. Log into the jenkins admin console from https://jenkins-cdm.dev.rhcloud.com/me/configure 3. Create job named "ccy'testé2" 4. Trigger this job build the log messages like below: <-------snip------> FATAL: Could not apply tag jenkins-ccy'test?2-1 hudson.plugins.git.GitException: Could not apply tag jenkins-ccy'test?2-1 at hudson.plugins.git.GitAPI.tag(GitAPI.java:718) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1230) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1178) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: hudson.plugins.git.GitException: Error performing command: git tag -a -f -m Jenkins Build #1 jenkins-ccy'test?2-1 Command "git tag -a -f -m Jenkins Build #1 jenkins-ccy'test?2-1" returned status code 128: fatal: 'jenkins-ccy'test?2-1' is not a valid tag name. at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:764) at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:729) at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:739) at hudson.plugins.git.GitAPI.tag(GitAPI.java:716) ... 11 more Caused by: hudson.plugins.git.GitException: Command "git tag -a -f -m Jenkins Build #1 jenkins-ccy'test?2-1" returned status code 128: fatal: 'jenkins-ccy'test?2-1' is not a valid tag name. at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:759) ... 14 more |