[
https://issues.jboss.org/browse/JBIDE-23734?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-23734:
------------------------------------
{quote}Would it be possible to trigger integration tests from a PR just like testPR but
using a separate comment{quote}
Yes, I believe we can set the trigger phrase to be specific to the job. For the jobs
Mickael set up, the default trigger phrase "test this please" was changed to
"testPR".
We could use "testPR" and "itestPR" so that itest PR jobs only fire
when requested ... not sure if they'll fire automatically on their own anyway. But we
could schedule itest PR check jobs to check github for changes only *once every 24 hours
at 11pm EST / 5am CET*, or even just *@weekly* rather than *every 5 minutes*, so they
won't fire when we don't need/want them to run.
dedupe vpe unit test jobs / migrate vpe builds to CCI
-----------------------------------------------------
Key: JBIDE-23734
URL:
https://issues.jboss.org/browse/JBIDE-23734
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, integration-tests
Affects Versions: 4.4.3.AM1
Reporter: Nick Boldt
Assignee: Rastislav Wagner
Fix For: 4.4.3.Final
There are four VPE unit test jobs. We probably only need 2 of those.
These both run on multiple OSes:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
These probably run the same unit tests, but against master or 4.4.x branches, and are
called from the VPE build jobs [1], [2] on Boston MW Jenkins (because the tests were
failing to run in Boston):
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
[1]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master/
[2]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_4.4.neon/
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)