[
https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-23733:
------------------------------------
If the jobs are to be run every week, it doesn't really matter if they're run in a
matrix (multi-configuration job) or in several jobs -- the tests will get run.
I just figured it'd be easier to MANAGE the jobs when it's time to move them to a
new version of target platform or maven version if you have 1 job per github repo than 1
job per subproject within the github repos. Thus javaee == 1 job, not 4, for example.
But as long as you guys know what's being tested and devs can run those jobs
themselves if they want to, your set up is fine with me. cc:[~rob.stryker] [~jeffmaury]
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)