[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13599 at 3/18/13 12:32 PM:
--------------------------------------------------------------
PR 81 worked!
!http://snag.gy/2buBl.jpg!
[~dgolovin] or [~maxandersen] can you apply https://github.com/jbosstools/jbosstools-central/pull/81 ?
was (Author: nickboldt):
PR 81 worked!
!http://snag.gy/2buBl.jpg!
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
> Attachments: JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png, JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt, JBTalpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13599:
------------------------------------
PR 81 worked!
!http://snag.gy/2buBl.jpg!
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
> Attachments: JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png, JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt, JBTalpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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-13790) Prepare fast-filter script for integration-stack-tests split
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13790?page=com.atlassian.jira.plugi... ]
Martin Malina reassigned JBIDE-13790:
-------------------------------------
Assignee: Max Rydahl Andersen (was: Martin Malina)
Max, can you take a look at the filter, please?
There shouldn't be really much to worry about I think - we already have a git repo, so unlike in the initial migration, we don't need any global excludes since those pieces are already gone.
At first we would create the new integration-stack-tests repo and all involved would start using it. When everybody's happy and all the dust settles down, we would then remove the plugins from the current repo - either just git rm, or using the inverted fast filter.
> Prepare fast-filter script for integration-stack-tests split
> ------------------------------------------------------------
>
> Key: JBIDE-13790
> URL: https://issues.jboss.org/browse/JBIDE-13790
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Martin Malina
> Assignee: Max Rydahl Andersen
> Fix For: 4.0.2.Final, 4.1.0.Alpha2
>
>
> As discussed in JBIDE-12974 and elsewhere, we need to split https://github.com/jbosstools/jbosstools-integration-tests in two:
> - the current repo will contain tests for all features of JBT core
> - the new repo - integration-stack-tests - will contain all soa/drools/teiid related tests
> We need a fast-filter script to do the split while preserving history
--
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-13808) Test failures and timeouts in JSF tests
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13808:
----------------------------------
Summary: Test failures and timeouts in JSF tests
Key: JBIDE-13808
URL: https://issues.jboss.org/browse/JBIDE-13808
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 4.0.1.Final
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Priority: Blocker
Fix For: 4.0.1.Final
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--javaee/146/console}
[INFO] org.jboss.tools.jsf.text.ext.test ................. FAILURE [1:20.290s]
[INFO] org.jboss.tools.jsf.vpe.facelets.test ............. FAILURE [1:00:28.012s]
[INFO] org.jboss.tools.jsf.vpe.jbpm.test ................. FAILURE [1:00:24.806s]
[INFO] org.jboss.tools.jsf.vpe.jstl.test ................. FAILURE [1:00:25.978s]
[INFO] org.jboss.tools.jsf.vpe.seam.test ................. FAILURE [1:00:28.143s]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.text.ext.test: An unexpected error occured (return code 134). See log for details. -> [Help 1]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.facelets.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.jbpm.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.jstl.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.seam.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
--
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-13807) yet more timeouts running vpe tests
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13807:
----------------------------------
Summary: yet more timeouts running vpe tests
Key: JBIDE-13807
URL: https://issues.jboss.org/browse/JBIDE-13807
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 4.0.1.Final
Reporter: Nick Boldt
Assignee: Yahor Radtsevich
Priority: Blocker
Fix For: 4.0.1.Final
Another series of slow-running tests that take longer than their allotted time limit of 1hr each:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--vpe/108/console}
[INFO] vpe.tests ......................................... SUCCESS [1.023s]
[INFO] org.jboss.tools.vpe.base.test ..................... SUCCESS [1.898s]
[INFO] org.jboss.tools.vpe.docbook.test .................. FAILURE [1:00:27.929s]
[INFO] org.jboss.tools.vpe.ui.test ....................... SUCCESS [51.907s]
[INFO] org.jboss.tools.vpe.html.test ..................... FAILURE [1:00:19.956s]
[INFO] org.jboss.tools.vpe.spring.test ................... FAILURE [1:00:20.025s]
[INFO] org.jboss.tools.vpe.jsp.test ...................... SUCCESS [1:04.495s]
[INFO] org.jboss.tools.vpe.test .......................... SUCCESS [31.253s]
[INFO] org.jboss.tools.vpe.xulrunner.test ................ SUCCESS [22.797s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.vpe.docbook.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 1]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.vpe.html.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 1]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.vpe.spring.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 1]
{code}
--
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-13803) BrowserSim: browsersim doesn't update skin when it is changed via preferences
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13803?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-13803:
-------------------------------------------
Fix Version/s: 4.1.0.Alpha2
Priority: Critical (was: Major)
Affects Version/s: 4.1.0.Alpha2
Component/s: Visual Page Editor core
> BrowserSim: browsersim doesn't update skin when it is changed via preferences
> -----------------------------------------------------------------------------
>
> Key: JBIDE-13803
> URL: https://issues.jboss.org/browse/JBIDE-13803
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.1.0.Alpha2
> Reporter: Konstantin Marmalyukov
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.1.0.Alpha2
>
>
> Steps:
> 1. Open browserSim, open preferences.
> 2. Open edit device dialog for selected device.
> 3. Change skin, save preferences.
> Expected: skin is changed.
> Actual: Old skin is displayed.
--
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