November 2014 - jbosstools-issues

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

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18818?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18818: ---------------------------------------- {code}Might also be cool to be able to collect up any .log or other Eclipse/Surefire metadata files; however, I'm not sure you can have a script run if the build times out / aborts{code} The Jenkins archive plugin does that and has been configured to store logs for a while. Cf https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.... , click on "Build Artifacts". > 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 > Fix For: 4.2.1.Final > > > 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, 4 months

1
0
0 / 0

[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 commented on JBIDE-18818: ------------------------------------ That might be possible. We run the builds with -e, but could use -X if you need even more verbose output from Maven. You can always look in the console log for the latest build by going to the job in Jenkins: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-javaee_4.... Might also be cool to be able to collect up any .log or other Eclipse/Surefire metadata files; however, I'm not sure you can have a script run if the build times out / aborts. [~mickael_istria] do you have any ideas here? > 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 > Fix For: 4.2.1.Final > > > 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, 4 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 updated JBDS-3163: ----------------------------- Description: 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. --- After much discussion it's been decided that: * we can push only the nightly/staging update sites automatically onto devstudio.redhat.com. * Installers will remain internal-only until they're released and available on CSP and www.jboss.org was: 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. > 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. > --- > After much discussion it's been decided that: > * we can push only the nightly/staging update sites automatically onto devstudio.redhat.com. > * Installers will remain internal-only until they're released and available on CSP and www.jboss.org -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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 act of pre-pushing staging bits to ds.jh.com would save a step at QE-staging time. [0] https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... No, installers don't need to be crosslinked to where update sites are; the installer's build folder [1] contains update site ZIPs (not the unpacked ones) so we could simply continue to link to that folder [2] when it's for CSP staging. [1] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... [2] http://www.qa.jboss.com/binaries/RHDS/builds/development/8.0.0.GA-build-c... > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18846?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18846: ------------------------------- Description: Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as: builds (nightly, staging, dev, stable) updates (nightly, staging, dev, stable) Jenkins jobs discovery sites (nightly, staging, dev, stable) target platforms etc. And for each component, we can list: build update Jenkins job etc. The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html Unsure whether generated HTML (via script) or simple .adoc is better for this. was: Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as: builds (nightly, staging, dev, stable) updates (nightly, staging, dev, stable) Jenkins jobs discovery sites (nightly, staging, dev, stable) target platforms etc. And for each component, we can list: build update Jenkins job etc. > create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18846 > URL: https://issues.jboss.org/browse/JBIDE-18846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Nick Boldt > > Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as: > builds (nightly, staging, dev, stable) > updates (nightly, staging, dev, stable) > Jenkins jobs > discovery sites (nightly, staging, dev, stable) > target platforms > etc. > And for each component, we can list: > build > update > Jenkins job > etc. > The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html > Unsure whether generated HTML (via script) or simple .adoc is better for this. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18846?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18846: ---------------------------------- Assignee: Nick Boldt > create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18846 > URL: https://issues.jboss.org/browse/JBIDE-18846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Nick Boldt > Assignee: Nick Boldt > > Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as: > builds (nightly, staging, dev, stable) > updates (nightly, staging, dev, stable) > Jenkins jobs > discovery sites (nightly, staging, dev, stable) > target platforms > etc. > And for each component, we can list: > build > update > Jenkins job > etc. > The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html > Unsure whether generated HTML (via script) or simple .adoc is better for this. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18833) luna nightly are not being updated preventing QE to do easy testing of committed code

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18833?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18833 at 11/27/14 12:43 PM: --------------------------------------------------------------- Long blarg short: Max wants an URL with *updates* in it, /updates/nightly/luna/ [1] to point to a composite of the latest nightly *builds* for the luna stream, because the stable URL [2] we've had for ages is too much effort to type or remember. And sees no problem mixing the concept of builds and updates in the same URL. So I've recreated a /luna/ one that points to the correct nightly builds folder. Hooray! [1] http://download.jboss.org/jbosstools/updates/nightly/luna/ [2] http://download.jboss.org/jbosstools/builds/nightly/core/4.2.luna/ And we need a more detailed list of process/steps to perform when moving the new master branch to a new Eclipse baseline. We forgot this step, as well as the step of updating composite install and p2.director jobs to use Mars.M3 instead of Luna.SR1/Luna.R. Probably missed more stuff too. I personally feel that the creation of these symlinks is pointless, because they're just redirects for the lazy. What we really need is a page listing all the URLs for target platforms, builds, update sites, etc. in a single place, a la https://projects.eclipse.org/list-of-projects. I believe this was raised at the F2F. Here's a JIRA for that: JBIDE-18846 was (Author: nickboldt): Long blarg short: Max wants an URL with *updates* in it, /updates/nightly/luna/ [1] to point to a composite of the latest nightly *builds* for the luna stream, because the stable URL [2] we've had for ages is too much effort to type or remember. And sees no problem mixing the concept of builds and updates in the same URL. So I've recreated a /luna/ one that points to the correct nightly builds folder. Hooray! [1] http://download.jboss.org/jbosstools/updates/nightly/luna/ [2] http://download.jboss.org/jbosstools/builds/nightly/core/4.2.luna/ And we need a more detailed list of process/steps to perform when moving the new master branch to a new Eclipse baseline. We forgot this step, as well as the step of updating composite install and p2.director jobs to use Mars.M3 instead of Luna.SR1/Luna.R. Probably missed more stuff too. I personally feel that the creation of these symlinks is pointless, because they're just redirects for the lazy. What we really need is a page listing all the URLs for target platforms, builds, update sites, etc. in a single place, a la https://projects.eclipse.org/list-of-projects. I believe this was raised at the F2F but I can't recall if there's a JIRA opened for this. [~maxandersen] do you know if there's a JIRA for that? Can you link it from here? > luna nightly are not being updated preventing QE to do easy testing of committed code > ------------------------------------------------------------------------------------- > > Key: JBIDE-18833 > URL: https://issues.jboss.org/browse/JBIDE-18833 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.1.Final > > > http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated 26-nov but latest build there is from 28-oct-2014 (29 days ago) > I could not spot updates in https://github.com/jbdevstudio/jbdevstudio-ci related to this. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-18846: ---------------------------------- Summary: create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs Key: JBIDE-18846 URL: https://issues.jboss.org/browse/JBIDE-18846 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Nick Boldt Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as: builds (nightly, staging, dev, stable) updates (nightly, staging, dev, stable) Jenkins jobs discovery sites (nightly, staging, dev, stable) target platforms etc. And for each component, we can list: build update Jenkins job etc. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3239) JBDS 8.0.1 - requires a respin to pull in latest build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3239?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3239: ---------------------------------- I can't fix this without doing a full respin to move to B335. However, it'll be irrelevant when the respin-a for CR1 runs on Dec 7. So... I could close this as won't fix, or you can close it then. > JBDS 8.0.1 - requires a respin to pull in latest build > ------------------------------------------------------ > > Key: JBDS-3239 > URL: https://issues.jboss.org/browse/JBDS-3239 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build > Affects Versions: 8.0.1.CR1 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Labels: respin-a > Fix For: 8.0.1.CR1, 8.0.1.GA > > > When I installed the 8.0.1 build on Monday: > Version: 8.0.1.CR1 > Build id: CR1-v20141124-0512-B333 > Build date: 20141124-0512 > I quickly discovered that new updates were available here: > JBoss Developer Studio (Branded Product) > 8.0.1.CR1-v20141124-0632-B334 > We will need a respin to pull in this build. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3239) JBDS 8.0.1 - requires a respin to pull in latest build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3239?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3239: ----------------------------- Fix Version/s: 8.0.1.CR1 > JBDS 8.0.1 - requires a respin to pull in latest build > ------------------------------------------------------ > > Key: JBDS-3239 > URL: https://issues.jboss.org/browse/JBDS-3239 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build > Affects Versions: 8.0.1.CR1 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Labels: respin-a > Fix For: 8.0.1.CR1, 8.0.1.GA > > > When I installed the 8.0.1 build on Monday: > Version: 8.0.1.CR1 > Build id: CR1-v20141124-0512-B333 > Build date: 20141124-0512 > I quickly discovered that new updates were available here: > JBoss Developer Studio (Branded Product) > 8.0.1.CR1-v20141124-0632-B334 > We will need a respin to pull in this build. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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