Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-ui-dev] Failing Gerrit trigger for R4_4_maintenance builds - Create a new build job

On 01/21/2015 10:13 AM, Lars Vogel wrote:
Can you try you suggestion

On Wed, Jan 21, 2015 at 10:10 AM, Mickael Istria <mistria@xxxxxxxxxx> wrote:
Is this really something necessary?

Can you adjust the current job with your suggestion? As long as the issue is fixed that the job is failing for master, I'm fine. And if build time becomes an issue for maintenance and master we can still create the new job.
I just set it up. This requires a few more things than what we identified initially, but it's able to give a green ball and a +1 for Gerrit patches against maintenance branch (see https://git.eclipse.org/r/#/c/39604/ )


Script is:
# Useful for archive plugin on R4_4_maintenance, where no tests are run
logFilesCount=$(ls tests/*/target/work/data/.metadata/.log | wc -l)
if [ "$logFilesCount" -eq "0" ]; then
  mkdir -p tests/mock/target/work/data/.metadata/
  echo 'This is a mock .log file because no test run on R4_4_maintenance' > tests/mock/target/work/data/.metadata/.log
fi

junitReportsCount=$(ls tests/*/target/surefire-reports/TEST-*.xml | wc -l)
if [ "$junitReportsCount" -eq "0" ]; then
  mkdir -p tests/mock/target/surefire-reports/
  echo '<!-- This is a mock JUnit repo file because no test run on R4_4_maintenance-->
<testsuite tests="1">
  <testcase classname="dummyMock" name="ASuccessfulTest"/>
</testsuite>' > tests/mock/target/surefire-reports/TEST-dummy.xml
fi


--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

Back to the top