[JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13411:
---------------------------------------------
btw. [~mickael_istria] -Dmaven.test.skip means you are also skipping tycho surefire's target platform resolution.
Yes, platform resolution is not the full picture here - but it surely is what majority of the build is doing locally.
> JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13411
> URL: https://issues.jboss.org/browse/JBIDE-13411
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, Visual Page Editor Templates
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.1.x
>
> Attachments: tests-vs-tycho-build-time.png
>
>
> On a good day, tests will run and all pass in under 4hrs.
> On a grey day, tests will have failures but complete in under 6hrs.
> On a bad day, tests will stall out and the job will fail when it hits its duration upper limit of 8hrs.
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> Surely some of these tests are:
> a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... ?
> b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13914) Have a test run that runs test plugins for each component in a fully installed JBT
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13914?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-13914:
-----------------------------------
Fix Version/s: 4.1.0.Alpha2
Affects Version/s: 4.1.0.Alpha2
Component/s: Build/Releng
This will require to create a new CI job for each scenario. A scenario is basically {Eclipse verion, test suite}.
Which scenario would you like me to start with?
> Have a test run that runs test plugins for each component in a fully installed JBT
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-13914
> URL: https://issues.jboss.org/browse/JBIDE-13914
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha2
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha2
>
>
> You said you had a way to run tests against existing install.
> Thus lets get this rolling by having a way to run a components test plugins and its included Test classes in a fully loaded JBoss Tools installation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13411) JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13411:
---------------------------------------------
Okey [~mickael_istria] jira for having a way to run this is at https://issues.jboss.org/browse/JBIDE-13914
> JavaEE component job can take over 8hrs to run w/ tests - move out integration tests and rewrite them to avoid UI blocking
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13411
> URL: https://issues.jboss.org/browse/JBIDE-13411
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng, Visual Page Editor Templates
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.1.x
>
> Attachments: tests-vs-tycho-build-time.png
>
>
> On a good day, tests will run and all pass in under 4hrs.
> On a grey day, tests will have failures but complete in under 6hrs.
> On a bad day, tests will stall out and the job will fail when it hits its duration upper limit of 8hrs.
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> Surely some of these tests are:
> a) integration, not unit test, and should be relocated to https://github.com/jbosstools/jbosstools-integration-tests/ and run as part of a new job like https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... ?
> b) reliant on UI which is blocking, and should therefore be rewritten so as to not block test execution?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13915) Support LiveReload for diretory content
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-13915:
-------------------------------------
Summary: Support LiveReload for diretory content
Key: JBIDE-13915
URL: https://issues.jboss.org/browse/JBIDE-13915
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: livereload
Affects Versions: 4.1.0.Alpha2
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.1.0.Alpha2
Provide an embedded websocket server that provides LiveReload support for Browser which have the LiveReload extension installed.
Browsers should be refreshed when relevant files are saved.
Browsers would access those files using the file:// scheme
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBIDE-13914) Have a test run that runs test plugins for each component in a fully installed JBT
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13914?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13914:
---------------------------------------------
Usecase is to be able to run the tests without having to rebuild them - checking if other components are affecting them.
Over time we might find some tests are not built for that but then we should filter them out or adjust the tests.
> Have a test run that runs test plugins for each component in a fully installed JBT
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-13914
> URL: https://issues.jboss.org/browse/JBIDE-13914
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
>
> You said you had a way to run tests against existing install.
> Thus lets get this rolling by having a way to run a components test plugins and its included Test classes in a fully loaded JBoss Tools installation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years