November 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18818) Test timeout in org.jboss.tools.jsf.verification.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18818?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18818: ------------------------------- Assignee: Alexey Kazakov > Test timeout in org.jboss.tools.jsf.verification.test > ----------------------------------------------------- > > Key: JBIDE-18818 > URL: https://issues.jboss.org/browse/JBIDE-18818 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > > Tests that time out due to blocking UI or other thread lock result in builds that are recorded as ABORTED [0]. This isn't a problem in terms of publishing new content because the build runs quickly, publishes the new bits, and THEN starts running tests. > [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.... > But where it IS a problem is where we use a buildflow job to run the whole stack of JBT projects. Buildflows will also abort if they encounter an aborted job [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... > Why is this a problem? Because when we do a weekend spin (or respin) not all the projects in the stack are guaranteed to rebuild to verify all the downstream component tests all still work. > -- > If you cannot fix these tests so they run cleanly in Jenkins, please disable them or move them such that they can still be run LOCALLY using a profile, but will be skipped in Jenkins. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18818) Test timeout in org.jboss.tools.jsf.verification.test

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-18818: ---------------------------------- Summary: Test timeout in org.jboss.tools.jsf.verification.test Key: JBIDE-18818 URL: https://issues.jboss.org/browse/JBIDE-18818 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsf Affects Versions: 4.2.1.CR1 Reporter: Nick Boldt Priority: Blocker Tests that time out due to blocking UI or other thread lock result in builds that are recorded as ABORTED [0]. This isn't a problem in terms of publishing new content because the build runs quickly, publishes the new bits, and THEN starts running tests. [0] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.... But where it IS a problem is where we use a buildflow job to run the whole stack of JBT projects. Buildflows will also abort if they encounter an aborted job [1]. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow... Why is this a problem? Because when we do a weekend spin (or respin) not all the projects in the stack are guaranteed to rebuild to verify all the downstream component tests all still work. -- If you cannot fix these tests so they run cleanly in Jenkins, please disable them or move them such that they can still be run LOCALLY using a profile, but will be skipped in Jenkins. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-560) We should add an illustration of the RESTFUL output

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-560?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-560: ------------------------------------- Issue Type: Enhancement (was: Bug) > We should add an illustration of the RESTFUL output > --------------------------------------------------- > > Key: TOOLSDOC-560 > URL: https://issues.jboss.org/browse/TOOLSDOC-560 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Affects Versions: 4.2.0.Final > Environment: Build Name: 22960, Start Developing-8.0 > Build Date: 22-10-2014 11:29:36 > Topic ID: 13785-717269 [Latest] > Reporter: Len DiMaggio > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0.Final > > > Title: Add a RESTful Web Service > Describe the issue: > The final step in this section reads: > Open a new Web Browser and in the address bar of the Web Browser enter http://localhost:8080/ticket-monster/rest/events. This shows the output of the new RESTful endpoint. > Suggestions for improvement: > We should add test explaining to the reader that the output should look like this: > [{"id":2,"version":1,"name":"Rock concert of the decade","description":"Get ready to rock...","major":true,"picture":null},{"id":1,"version":1,"name":"Shane's Sock Puppets","description":"This critically acclaimed masterpiece...","major":true,"picture":null}] > Additional information: -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-563) Fix statement on how to start installer.jar on OS X

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-563?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-563: ------------------------------------- Component/s: Installation Guide > Fix statement on how to start installer.jar on OS X > --------------------------------------------------- > > Key: TOOLSDOC-563 > URL: https://issues.jboss.org/browse/TOOLSDOC-563 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Affects Versions: 4.2.0.Final > Reporter: Michelle Murray > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-563) Fix statement on how to start installer.jar on OS X

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-563?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-563: ------------------------------------- Sprint: 2014/S20 (27-Oct > 9-Nov), 2014/S22 (24-Nov > 7-Dec) (was: 2014/S20 (27-Oct > 9-Nov)) > Fix statement on how to start installer.jar on OS X > --------------------------------------------------- > > Key: TOOLSDOC-563 > URL: https://issues.jboss.org/browse/TOOLSDOC-563 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Affects Versions: 4.2.0.Final > Reporter: Michelle Murray > Assignee: Michelle Murray > Priority: Minor > Fix For: 4.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-564) Mark Ionic as TP in RNs

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-564?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-564: ------------------------------------- Sprint: 2014/S20 (27-Oct > 9-Nov), 2014/S22 (24-Nov > 7-Dec) (was: 2014/S20 (27-Oct > 9-Nov)) > Mark Ionic as TP in RNs > ----------------------- > > Key: TOOLSDOC-564 > URL: https://issues.jboss.org/browse/TOOLSDOC-564 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Affects Versions: 4.2.0.Final > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-566) OpenShift How To: Customize OpenShift Online App Publishing

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-566?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-566. -------------------------------------- Resolution: Done > OpenShift How To: Customize OpenShift Online App Publishing > ----------------------------------------------------------- > > Key: TOOLSDOC-566 > URL: https://issues.jboss.org/browse/TOOLSDOC-566 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide - OpenShift Tools > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Final > > > Create a an article to: Customize OpenShift Online App Publishing(?) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-566) OpenShift How To: Customize OpenShift Online App Publishing

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-566?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-566: ------------------------------------------ PR made: https://github.com/jbosstools/jbosstools-website/pull/286 > OpenShift How To: Customize OpenShift Online App Publishing > ----------------------------------------------------------- > > Key: TOOLSDOC-566 > URL: https://issues.jboss.org/browse/TOOLSDOC-566 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide - OpenShift Tools > Reporter: Supriya Bharadwaj > Assignee: Supriya Bharadwaj > Fix For: 4.2.0.Final > > > Create a an article to: Customize OpenShift Online App Publishing(?) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3163: ---------------------------------- Yes, the intent here is easier releng & testing. But having to push installers to www.qa (internal) and the update sites to devstudio.redhat.com (public) may make the releng process more confusing since installers are on one server and update sites another. OR, we push everthing BUT the EAP bundles to ds.rh.com, but also keep a folder w/ all the installers (including EAP) on an internal server so that when it's time to stage for CSP, we don't have to tell Christ to get the bits from two different servers. That will only confuse QE when they go looking to test the installers on ds.rh.com and can't find the EAP bundles, only the standalone ones. :( > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.1.GA, 9.0.0.Alpha1 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3163: ------------------------------------------- The devstudio installers with EAP was not intended to be part of this. Only the p2 plugins - at least at first, and that is also only what CAT have been testing until now. Thus I agree with Pete - the installers need to stay behind the 0$ wall and security through obscurity is not an option. Pete - devstudio have been publishing its milestone builds for years so its not new. What we are trying to here is that since we are public anyway we can save several hours if not days of the time spent just moving bits around. Plus it gets much simpler to maintain and avoid having to do expensive workarounds between staging and prod releasing. > change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-3163 > URL: https://issues.jboss.org/browse/JBDS-3163 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 8.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.1.GA, 9.0.0.Alpha1 > > > To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. > See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. > Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2014