[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 edited comment on JBIDE-13411 at 3/30/13 12:08 PM:
--------------------------------------------------------------
[~maxandersen] said: "it is not buildable on its own thus not useful for us for CI builds"
I was able to build them in January and up until we moved to Kepler M6 (junit4 issue).
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--> http://download.jboss.org/jbosstools/updates/nightly/integrationtests/trunk/
Note that the current failure (due to org.jboss.tools.modeshape.jcr.test depending on org.junit4 bundle) has been logged as a JIRA here: MODE-1866.
was (Author: nickboldt):
[~maxandersen] said: "it is not buildable on its own thus not useful for us for CI builds"
I was able to build them in January and up until we moved to Kepler M6 (junit4 issue).
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--> http://download.jboss.org/jbosstools/updates/nightly/integrationtests/trunk/
> 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
12 years, 7 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:
------------------------------------
[~maxandersen] said: "it is not buildable on its own thus not useful for us for CI builds"
I was able to build them in January and up until we moved to Kepler M6 (junit4 issue).
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--> http://download.jboss.org/jbosstools/updates/nightly/integrationtests/trunk/
> 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
12 years, 7 months
[JBoss JIRA] (JBIDE-13812) openshift-java-client: get rid of external class to (de)code base64
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13812?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13812:
-------------------------------------------------
Gerard Ryan <gerard(a)ryan.lt> made a comment on [bug 902017|https://bugzilla.redhat.com/show_bug.cgi?id=902017]
(In reply to comment #14)
> Package Review
> ==============
>
> Key:
> [x] = Pass
> [!] = Fail
> [-] = Not applicable
> [?] = Not evaluated
> [ ] = Manual review needed
>
>
> Issues:
> =======
>
> [!]: Changelog in prescribed format.
> >>>> There must either be a space on both sides of the delimiting dash, or
> >>>> no delimiting dash at all. I. e.
> >>>> ...t.org> - 2.0.3-2
> >>>> or
> >>>> ...t.org> 2.0.3-2
Fixed.
> [!]: Package complies to the Packaging Guidelines
> [!]: If (and only if) the source package includes the text of the license(s)
> in its own file, then that file, containing the text of the license(s)
> for the package is included in %doc.
> >>>> you should include
> >>>> %doc license epl-v10.html
> >>>> in %files and %files javadoc
Oops. I don't know how that got removed, thanks for pointing it out. Fixed.
> Notes:
> ======
>
> [!]: Requires correct, justified where necessary.
> >>>> You don't need to specify Requires when building with %mvn_build
Fixed. I've left in Requires on jsch since it doesn't have a maven POM.
DIFF of specfile since previous uploaded version
===========================================================
@@ -4,7 +4,7 @@
Name: openshift-java-client
Version: 2.0.3
-Release: 2.%{checkout}%{?dist}
+Release: 3.%{checkout}%{?dist}
Summary: OpenShift Java Client
Group: Development/Libraries
@@ -13,7 +13,6 @@ URL: http://openshift.redhat.com
Source0: https://github.com/openshift/%{name}/archive/%{commit}/%{name}-%{version}...
BuildArch: noarch
-BuildRequires: java-devel
BuildRequires: maven-local
BuildRequires: jsch
BuildRequires: mvn(org.easytesting:fest-assert)
@@ -25,11 +24,6 @@ BuildRequires: mvn(log4j:log4j)
BuildRequires: mvn(org.codehaus.mojo:properties-maven-plugin)
BuildRequires: mvn(commons-io:commons-io)
Requires: jsch
-Requires: mvn(org.jboss:jboss-dmr)
-Requires: mvn(org.slf4j:slf4j-log4j12)
-Requires: mvn(commons-io:commons-io)
-Requires: mvn(org.codehaus.mojo:properties-maven-plugin)
-Requires: java
%description
This is a client for OpenShift written in java. It pretty much offers all
@@ -57,13 +51,20 @@ API documentation for %{name}.
%files -f .mfiles
%dir %{_javadir}/%{name}
+%doc license epl-v10.html
%files javadoc -f .mfiles-javadoc
+%doc license epl-v10.html
%changelog
-* Wed Mar 20 2013 Gerard Ryan <galileo(a)fedoraproject.org> -2.0.3-2
+* Fri Mar 29 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.0.3-3
+- Fix changelog.
+- Remove unneeded Requires.
+- Added epl-v10.html as a doc to main and javadoc packages.
+
+* Wed Mar 20 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.0.3-2
- Update to fix licensing and new Base64Coder implementation.
- Use new maven macros.
-* Sun Jan 20 2013 Gerard Ryan <galileo(a)fedoraproject.org> -2.0.3-1
+* Sun Jan 20 2013 Gerard Ryan <galileo(a)fedoraproject.org> - 2.0.3-1
- Initial package.
=========================================================================
Spec URL: http://galileo.fedorapeople.org/openshift-java-client/2.0.3-3/openshift-j...
SRPM URL: http://galileo.fedorapeople.org/openshift-java-client/2.0.3-3/openshift-j...
> openshift-java-client: get rid of external class to (de)code base64
> -------------------------------------------------------------------
>
> Key: JBIDE-13812
> URL: https://issues.jboss.org/browse/JBIDE-13812
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Alpha2
>
>
> We're currently using a class that we copied from a different project to (de)code base64. This contradicts the fedora project which wants to package us into an rpm. They suggested to package the full library instead.
> Since we dont want to agument the numbers of dependencies, I'll switch to JDK means to (de)code base64. This will bind us to >= JDK6 which is IMHO perfectly fine.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-13880) 'Start the server' icon is the same as 'Run as' icon so confusing
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13880?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-13880.
---------------------------------------
Resolution: Rejected
Yes and its limited how many ways "run"/"start" can be drawn.
Like many other things in eclipse it is the context/selection that in the end decides what launches - the green "play" button just means "run what is selected".
> 'Start the server' icon is the same as 'Run as' icon so confusing
> -----------------------------------------------------------------
>
> Key: JBIDE-13880
> URL: https://issues.jboss.org/browse/JBIDE-13880
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Reporter: Michelle Murray
> Assignee: Rob Stryker
> Attachments: Start_server_icon.png
>
>
> In the 'Servers' tab, the icon for 'Start the server' is a green circle with a white arrow.
> In the global toolbar of the JBoss perspective, the icon for 'Run/Run as' is the same.
> This could cause confusion for new users. Can one of the icons be changed?
--
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
12 years, 7 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 Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13411:
---------------------------------------------
[~mickael_istria] you wrote "That shows dependency resolution is the bottleneck of this job.", I assume you meant "is *not* the bottleneck", right ?
Also note that the tests are not taking anywhere near 8 hrs when run locally so its also affected by jenkins environment; using nio solves nothing here IMO.
Talking with tycho guys they pointed out that surefire tests currently resolve TP twice - one at build startup and secondly for calculating TP per test run.
Again a reason to look at being able to run tests against an existing eclipse install to avoid overhead of TP calculation.
> 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
12 years, 7 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 Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13411?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13411:
---------------------------------------------
integration-tets repo is just for QE - it is not buildable on its own thus not useful for us for CI builds. Thus moving them to integration-tests is not a good option.
> 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
12 years, 7 months
[JBoss JIRA] (JBIDE-12976) bump feature/plugin versions in runtime-soa repo
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12976?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-12976.
------------------------------
Resolution: Won't Fix
Since all the contents of this project have been migrated elsewhere, this can be closed WONTFIX.
> bump feature/plugin versions in runtime-soa repo
> ------------------------------------------------
>
> Key: JBIDE-12976
> URL: https://issues.jboss.org/browse/JBIDE-12976
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.0.0.Alpha1-SOA
> Reporter: Nick Boldt
> Assignee: Rob Cernich
> Fix For: 4.0.0.Alpha1-SOA
>
>
> Components in new 4.x master branch in github need to be upversioned so that they're "newer" than the stuff in the 3.3.x branch in SVN. Currently, they are not (in some cases the plugins/features in 3.3.x branch are x.y.2 where the plugins/features in 4.x master are x.y.0).
> Obviously, the stuff in master should be bumped to x.(y+1).0
> You can use this to bump easily:
> {code:title=https://gist.github.com/4548933}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=x.y.z-SNAPSHOT
> {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
12 years, 7 months