[
https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-23733:
------------------------------------
I would say since the Nightly and Weekly are the same tests (but on different OS
combinations) that you don't have to do nightly AND weekly. Instead, just run the
weekly job (Sat or Sunday night between 3 and 8am Brno time), on all OSes. That frees up
RHEL7 slaves for CI builds and PRs. And if anything is built through the week which breaks
an ITest, dev and QE will find out first-thing on a Monday morning.
Please clarify how the smoke tests relate to the tests in the Nightly or Weekly set. Is it
a smaller set? Are they special tests? Do they take longer? When do you run them, and why
can't they be merged with the Weekly jobs to run every week?
Merge .smoke and .nightly integration jobs into a single job and run
them weekly
--------------------------------------------------------------------------------
Key: JBIDE-23733
URL:
https://issues.jboss.org/browse/JBIDE-23733
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
Purpose:
a) easier maintenance of jobs / tests
b) run fewer nightly jobs so that we don't block slaves from being available for
other builds / tests
c) more frequent full integration runs (rather than once per sprint, once per week)
Tests to merge are in this view:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)