M5 spin status :: no aggregate or JBDS installers available yet; many bot and non-UI test failures, plus one inter-build compilation failure
by Nick Boldt
Since turning on the stable branch jobs, here's what's borked...
https://issues.jboss.org/browse/JBIDE-10349
Still trying to get a clean stable_branch aggregate build (and then JBT
builds too) - last time the aggregate failed due to missing Central,
OTDT, and OpenShift (hadn't spun clean yet).
---
Details:
- hibernate : test failure in org.hibernate.eclipse.console.test
- jbpm : test failure in org.jboss.tools.jbpm.convert.test
- jsf : test failure in org.jboss.tools.jsf.vpe.jsf.test
- maven : 15 bot test failures (same failures in trunk) ... should these
just be turned off and only run locally / manually?
- struts : COMPILE FAILED - upstream bits missing? "The import
org.jboss.tools.jst.web.validation cannot be resolved."
---
There are also a few jobs for which the latest build failed, but at
least we have one good build since branching. This suggests we're having
some stability issues w/ a few Jenkins slaves, but at least we're
getting clean spins when the server is quiet(er).
= archives : aborted build? [Dec 4 ok]
= birt : failed to find usage bits (poor timing between builds) [Dec 4 ok]
= seam : no more locks failure [Dec 4 ok]
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
2 weeks, 2 days
ACTION REQUIRED: JBoss Tools + Developer Studio triage time
by jmaury＠redhat.com
As the current sprint 'devex #180 Feb/Mar 2020' draws to a close, it is time
to review your unresolved issues!
Some may be done (or will be done soon), but the JIRA(s) need resolution.
Others may need to be pushed to the next milestone (4.15.0.AM1 + 12.15.0.AM1),
to a future .x release, or LATER.
All unresolved issues for 4.14.0.Final + 12.14.0.GA:
https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVe...
All *YOUR* unresolved issues for 4.14.0.Final + 12.14.0.GA:
https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVe...
Once created, you can also begin scheduling your work for the upcoming
sprint, 'devex #181 Mar 2020'.
Triage tips:
* blocker/critical issues: make these your priority work for the next sprint:
move to next version & assign to the next sprint
* other issues that WILL be done in the next sprint:
move to next version & assign to the forthcoming sprint, but lower down
* non-blocker & non-critical issues not for the next sprint:
move to .x (or LATER)
6 years
Proposed 4.14.0.Final-SNAPSHOT target platform change(s): Docker 4.5.1 WildWebDeveloper 0.8.2
by sbouchet＠redhat.com
Here is a proposal for change(s) to the JBoss Tools / Red Hat CodeReady Studio / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.14.0.Final
devstudio 12.14.0.GA
jbt/ds TPs 4.14.0.Final-SNAPSHOT
central TPs 4.14.0.Final-SNAPSHOT
Detail / Summary:
Docker 4.5.1
WildWebDeveloper 0.8.2
Related JIRA(s):
(already merged - see related JIRA(s))
https://issues.redhat.com/browse/JBIDE-26973
Pull Request(s):
https://github.com/jbosstools/jbosstools-target-platforms/pull/348
https://github.com/jbosstools/jbosstools-target-platforms/pull/346
p2diff Report(s):
see related JIRA(s)
----------
Please review the above changes, as they have been applied and are building today.
Once the target platform is built, jobs and parent pom will be updated to point
TARGET_PLATFORM_VERSION_MAX at the new version, 4.14.0.Final-SNAPSHOT.
You can use the following to build & test the target platforms locally against
your component(s).
Build target-platform:
cd /path/to/jbosstools-target-platforms
git fetch origin pull/<pull-request-number>/head && git checkout FETCH_HEAD
# or, using hub for git
git checkout <pull-request-URL>
mvn clean install -f jbosstools/multiple/pom.xml
Then, to test the new multiple target platform against your component's build:
cd /path/to/your/jbosstools-component
mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------
6 years
Proposed 4.14.0.Final-SNAPSHOT target platform change(s): Docker 4.5.1 WildWebDeveloper 0.8.2
by sbouchet＠redhat.com
Here is a proposal for change(s) to the JBoss Tools / Red Hat CodeReady Studio / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.14.0.Final
devstudio 12.14.0.GA
jbt/ds TPs 4.14.0.Final-SNAPSHOT
central TPs 4.14.0.Final-SNAPSHOT
Detail / Summary:
Docker 4.5.1
WildWebDeveloper 0.8.2
Related JIRA(s):
https://issues.redhat.com/browse/JBIDE-26973
Pull Request(s):
https://github.com/jbosstools/jbosstools-target-platforms/pull/348
https://github.com/jbosstools/jbosstools-target-platforms/pull/346
p2diff Report(s):
(will attach to JIRA when available)
----------
Please review the above changes, as they have been applied and are building today.
Once the target platform is built, jobs and parent pom will be updated to point
TARGET_PLATFORM_VERSION_MAX at the new version, 4.14.0.Final-SNAPSHOT.
You can use the following to build & test the target platforms locally against
your component(s).
Build target-platform:
cd /path/to/jbosstools-target-platforms
git fetch origin pull/<pull-request-number>/head && git checkout FETCH_HEAD
# or, using hub for git
git checkout <pull-request-URL>
mvn clean install -f jbosstools/multiple/pom.xml
Then, to test the new multiple target platform against your component's build:
cd /path/to/your/jbosstools-component
mvn clean verify -Dtpc.version=4.14.0.Final-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------
6 years
Introduction | JBoss | GSoC 2020 | Project Starfish | Overview
by Saurav Kumar
Hello Community,
I am Saurav Kumar, a fourth-year computer engineering undergraduate from
the Army Institute of Technology, India looking forward to participating in
GSoC 2020 on the Project Starfish.
I went through the Project Starfish idea summary
<https://docs.jboss.org/display/GSOC/Google+Summer+of+Code+2020+ideas#Goog...>
and
explored the details mentioned. A rough idea which I figured out is, the
overall development consists of two client-side applications that are
compatible with the various platforms.
- A browser extension (which will act as producer of URL).
- A plug-in for IDE's (which will act as a consumer of URL, supports
urlhandlers, serve the purpose of open, edit, debug according to URL passed)
Learning about IDE's and adding urlhandler features is something
interesting and requires a lot of exploring. Furthermore, the extension
development for browsers is something I have worked on but only for chrome
browser and building of cross-browser extension is almost similar with some
differences in tackling API namespace and asynchronous event.
Please let me know further technicalities of the project, correct me if I
am/was wrong at some point and meanwhile I will research more into the
design of the project.
Language: Java, Python, C++, Javascript.
GitHub profile : https://github.com/svkrclg
Saurav Kumar | +918698588414
6 years