Bug 1032901

Description of problem:
Given a Perl-5.10 app with a Jenkins-client added, when trying to install a package to this app, the package fails to take effect with Jenkins build even though no error is reported during the installation. Moreover, a page referencing this package shows 500 error when accessing it. On the other hand, there is no such problem without Jenkins builds.

Version-Release number of selected component (if applicable):
devenv_4057
INT(devenv_4052)
devenv-stage_582

How reproducible:
always

Steps to Reproduce:
1. create a Perl-5.10 app with a Jenkins-client added
rhc app create prl perl-5.10 --enable-jenkins

2. add a package to deplist.txt, for example, 
echo "Plack" > deplist.txt

3. create a new page with the following code under $APP_REPO/perl/:

<--------test.pl-------->
use Plack;

print "Succeed to install Plack!"

<----------------------->

4. push the change and trigger a Jenkins build

5. access the $APP_DNS/test.pl

6. create another Perl-5.10 app WITHOUT adding a Jenkins-client

7. repeat step 2 ~ 5

Actual results:
In Step 5, the test.pl page returns "Internal Server Error", while the page returns the expected string without Jenkins build.

Expected results:
The Perl package should take effect after a Jenkins build.

Additional info: