Add missing clean line after https://github.com/joomla/joomla-cms/pull/9277

[zero-24]

Pull Request for Issue #9277

Summary of Changes

CodeStyle

Testing Instructions

none. On request by @rdeutz after #9277

Documentation Changes Required

none

[andrepereiradasilva]

I have tested this item ✅ successfully on

code review

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11605.}

[jeckodevelopment]

I have tested this item ✅ successfully on

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11605.}

[jeckodevelopment]

RTC please

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11605.}

[rdeutz]

Travis is still falling on this, I have no idea why. Expecting jenkins failure in a few moments :-)

[rdeutz]

ah I know why the script was moved in-between

[rdeutz]

Here we are: http://build.joomla.org/job/cms/5853/

[zero-24]

**Pushing HEAD to branch master at repo projects
 > git --version # timeout=10
 > git -c core.askpass=true push ssh://[email protected]/joomla-projects/joomla-cms.git HEAD:master
Pushing HEAD to branch master at repo origin
 > git -c core.askpass=true push ssh://[email protected]/joomla/joomla-cms.git HEAD:master
ERROR: Failed to push branch master to origin
hudson.plugins.git.GitException: Command "git -c core.askpass=true push ssh://[email protected]/joomla/joomla-cms.git HEAD:master" returned status code 1:
stdout: 
stderr: remote: error: GH006: Protected branch update failed for refs/heads/master.        
remote: error: Required status check "continuous-integration/travis-ci/push" is pending        
To ssh://[email protected]/joomla/joomla-cms.git
 ! [remote rejected] HEAD -> master (protected branch hook declined)
error: failed to push some refs to 'ssh://[email protected]/joomla/joomla-cms.git'

    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1723)
    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1459)
    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63)
    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1799)
    at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:331)
    at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
    at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
    at hudson.model.Build$BuildExecution.post2(Build.java:185)
    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)
    at hudson.model.Run.execute(Run.java:1745)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:404)
Build step 'Git Publisher' marked build as failure
Notifying endpoint 'HTTP:https://developer.joomla.org/glip/jenkins.php'
Finished: FAILURE**

This has nothing to do with this change. The build itself is successful.

[rdeutz]

You are right it is not the change but the circumstances: After you created the PR another got merged and this one moved a script to another place, if I merge your change the move of the file has happened but the code change in the travis.yml not (don't asked me why). So the travis is failing on this PR. The master branch is protected so our jenkins server can only merge PR's into the master branch when travis is on green. To keep a long story short, never ever merge a PR when travis is not on green.