[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-12974:
------------------------------------
1. One site would be less to maintain, fewer URLs to hand out. coretests and soatests are simply aggregating from upstream builds which publish their test features/plugins into /staging/{JOB_NAME}/; integrationtests is aggregrating from the same upstream projects (including RedDeer) but also includes its own unique test feature, org.jboss.tools.itests.feature.
https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si...
https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si...
So I would argue that unless you need the core and soa sites to be able to change (that is, be rebuilt and updated) on different cycles, or more frequently/separately from the integrationtests site, there's no longer a need to build them. My understanding was that the reason we produced them in the first place was to make it easier for downstream QE to install/run the tests and develop new ones based on those. For that all you need is an update site... not necessarily 3 sites. If you feel you need 3, then by all means we can maintain 'em. I'm just looking for ways to simplify the infrastructure w/o your losing functionality / ability to do your jobs.
> add missing IUs to coretests and soatests sites
> -----------------------------------------------
>
> Key: JBIDE-12974
> URL: https://issues.jboss.org/browse/JBIDE-12974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing, updatesite
> Affects Versions: 4.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Fix For: 4.1.0.Alpha1
>
>
> The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content.
> [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/
> [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/
> Are there any other missing IUs you need on those sites?
--
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, 2 months
[JBoss JIRA] (JBDS-2038) JBDS installer should open JBDS upon completion
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBDS-2038?page=com.atlassian.jira.plugin.... ]
Daniel Azarov updated JBDS-2038:
--------------------------------
Attachment: JBDS-2038.patch
> JBDS installer should open JBDS upon completion
> -----------------------------------------------
>
> Key: JBDS-2038
> URL: https://issues.jboss.org/browse/JBDS-2038
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.Beta1
> Environment: jbdevstudio-product-win32-x86_64-5.0.0.v201202250031M-H77-Beta1.jar
> Reporter: Fred Bricon
> Assignee: Daniel Azarov
> Fix For: 7.0.x
>
> Attachments: JBDS-2038.patch, RunJBDSAfterInstallation.png
>
>
> As a user, once the JBDS installer completes, I expect it to open the newly installed JBDS.
> On the last page of the installer, there should be a checkbox asking the user if he wants to open JBDS immediately.
--
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, 2 months
[JBoss JIRA] (JBDS-2038) JBDS installer should open JBDS upon completion
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBDS-2038?page=com.atlassian.jira.plugin.... ]
Daniel Azarov reassigned JBDS-2038:
-----------------------------------
Assignee: Denis Golovin (was: Daniel Azarov)
Please, review the patch
> JBDS installer should open JBDS upon completion
> -----------------------------------------------
>
> Key: JBDS-2038
> URL: https://issues.jboss.org/browse/JBDS-2038
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.Beta1
> Environment: jbdevstudio-product-win32-x86_64-5.0.0.v201202250031M-H77-Beta1.jar
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Fix For: 7.0.x
>
> Attachments: JBDS-2038.patch, RunJBDSAfterInstallation.png
>
>
> As a user, once the JBDS installer completes, I expect it to open the newly installed JBDS.
> On the last page of the installer, there should be a checkbox asking the user if he wants to open JBDS immediately.
--
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, 2 months
[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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13411:
------------------------------------
Recent failures:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.1_trunk.component--javaee/253/console}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.tools.jsf.vpe.seam.test.SeamAllTests
Build timed out (after 480 minutes). Marking the build as aborted.
{code}
{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/83/console}
[INFO] --- maven-download-plugin:0.2-SNAPSHOT:wget (install-seam-2.2.0) @ org.jboss.tools.runtime.seam.detector.test ---
[INFO] Got from cache: /home/hudson/static_build_env/jbds/download-cache/jboss-seam-2.2.0.GA.zip
---------------------------------------------------
constituent[0]: file:/qa/tools/opt/apache-maven-3.0.4/lib/maven-embedder-3.0.4.jar
constituent[1]: file:/qa/tools/opt/apache-maven-3.0.4/lib/maven-settings-3.0.4.jar
...
constituent[28]: file:/qa/tools/opt/apache-maven-3.0.4/lib/aether-connector-wagon-1.13.1.jar
---------------------------------------------------
Exception in thread "main" java.lang.OutOfMemoryError
at java.util.zip.Inflater.init(Native Method)
at java.util.zip.Inflater.<init>(Inflater.java:83)
at java.util.zip.ZipFile.getInflater(ZipFile.java:278)
at java.util.zip.ZipFile.getInputStream(ZipFile.java:224)
at java.util.zip.ZipFile.getInputStream(ZipFile.java:192)
at java.util.jar.JarFile.getInputStream(JarFile.java:385)
at sun.misc.URLClassPath$JarLoader$2.getInputStream(URLClassPath.java:692)
...
Build timed out (after 480 minutes). Marking the build as aborted.
{code}
> 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: CDI, JSF, Seam 2, struts/shale
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
>
> 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, 2 months
[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 Nick Boldt (JIRA)
Nick Boldt created JBIDE-13411:
----------------------------------
Summary: 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: CDI, JSF, Seam 2, struts/shale
Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Priority: Blocker
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, 2 months
[JBoss JIRA] (JBTIS-4) Verify the component configuration of the initial Integration Stack tooling release.
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-4?page=com.atlassian.jira.plugin.sy... ]
Paul Leacu updated JBTIS-4:
---------------------------
Description:
Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target.
ref:
https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/...
https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml
https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/...
I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component.
was:
Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target.
ref:
https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/...
https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml
I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component.
> Verify the component configuration of the initial Integration Stack tooling release.
> ------------------------------------------------------------------------------------
>
> Key: JBTIS-4
> URL: https://issues.jboss.org/browse/JBTIS-4
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: BPEL, BPMN2, ESB, JBPM, modeshape, runtime-soa, savara, switchyard, teiid
> Environment: JBT 4.0
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target.
> ref:
> https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/...
> https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml
> https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/...
> I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component.
--
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, 2 months
[JBoss JIRA] (JBIDE-13405) Deploying a RAR with JAR inside fails using remote systems via SSH
by Chris Roberts (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13405?page=com.atlassian.jira.plugi... ]
Chris Roberts commented on JBIDE-13405:
---------------------------------------
Done. I haven't been able to fully test this on a broken eclipse but looking at the source yesterday I'm 99.9% certain it will recreate the issue and I just don't have time right now to go back and break my eclipse again to prove it, I already lost quite a bit of time on this one... Hope you understand.
If it doesn't error on publish for you then let me know.
> Deploying a RAR with JAR inside fails using remote systems via SSH
> ------------------------------------------------------------------
>
> Key: JBIDE-13405
> URL: https://issues.jboss.org/browse/JBIDE-13405
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: JBoss AS 7.1.1 Final, Eclipse Juno SR1, JBoss Tools 4.0.0 Final
> Reporter: Chris Roberts
> Assignee: Fred Bricon
> Attachments: maven-broken.tar.gz
>
>
> Exploding dependant jars seems to have issues for rars. I didn't work out if this is a problem in JBoss Tools or RSE. I suspect a little of both. It seems looking at the source that only the 'Local' RSE adapter correctly explodes deployments?
> 1) Create a maven project, set the packaging to rar
> 2) Create a second maven project, set the packaging to jar
> 3) Include the jar as a maven compile dependency of the rar
> 4) Import both into eclipse
> 5) Deploy to a remote (JBoss AS) server via RSE SSH/dstore/FTP fails
> It seems the JBoss Server Adapter (I think) creates the directory:
> xxxxx-1.0.rar/xxxxx-1.0.jar/
> on deployment. It then requests upload for the jar over the top of the directory which fails. With FTP this looks like:
> CD xxxxx-1.0.rar/
> MKD xxxxx-1.0.jar
> STOR xxxxx-1.0.jar <fails because directory exists>
> This is my first bug opened on JBoss/eclipse, so please point me on if you think this should be opened on RSE, but I think looking at the source it belongs here.
--
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, 2 months
[JBoss JIRA] (JBIDE-13405) Deploying a RAR with JAR inside fails using remote systems via SSH
by Chris Roberts (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13405?page=com.atlassian.jira.plugi... ]
Chris Roberts updated JBIDE-13405:
----------------------------------
Attachment: maven-broken.tar.gz
1) Import maven project
2) Add a new JBoss 7.1 Server, as an RSE server using SSH, FTP or dstore as the publish mechanism
3) Add maven-rar to the server
4) Hit full publish
> Deploying a RAR with JAR inside fails using remote systems via SSH
> ------------------------------------------------------------------
>
> Key: JBIDE-13405
> URL: https://issues.jboss.org/browse/JBIDE-13405
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: JBoss AS 7.1.1 Final, Eclipse Juno SR1, JBoss Tools 4.0.0 Final
> Reporter: Chris Roberts
> Assignee: Fred Bricon
> Attachments: maven-broken.tar.gz
>
>
> Exploding dependant jars seems to have issues for rars. I didn't work out if this is a problem in JBoss Tools or RSE. I suspect a little of both. It seems looking at the source that only the 'Local' RSE adapter correctly explodes deployments?
> 1) Create a maven project, set the packaging to rar
> 2) Create a second maven project, set the packaging to jar
> 3) Include the jar as a maven compile dependency of the rar
> 4) Import both into eclipse
> 5) Deploy to a remote (JBoss AS) server via RSE SSH/dstore/FTP fails
> It seems the JBoss Server Adapter (I think) creates the directory:
> xxxxx-1.0.rar/xxxxx-1.0.jar/
> on deployment. It then requests upload for the jar over the top of the directory which fails. With FTP this looks like:
> CD xxxxx-1.0.rar/
> MKD xxxxx-1.0.jar
> STOR xxxxx-1.0.jar <fails because directory exists>
> This is my first bug opened on JBoss/eclipse, so please point me on if you think this should be opened on RSE, but I think looking at the source it belongs here.
--
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, 2 months