Skip to main content
Jump to: navigation, search

Difference between revisions of "WTP Smoke Test Results R3100 01252018"

(Merge edit by Stephanie.cao.ibm.com)
 
(One intermediate revision by one other user not shown)
Line 39: Line 39:
 
| DG (Deployment of Java EE 8 modules is not tested)
 
| DG (Deployment of Java EE 8 modules is not tested)
 
|-
 
|-
|JSF
+
|JSF  
 
| align="center" |[[Image:Checkmark.gif]]
 
| align="center" |[[Image:Checkmark.gif]]
 
| IMT
 
| IMT
Line 79: Line 79:
 
|  
 
|  
 
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=530465 - Remediation presented and two versions of server core in WTP update site  
 
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=530465 - Remediation presented and two versions of server core in WTP update site  
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=530464 - WTP update site should include redistribution of Jetty 9.4.7
 
 
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=530467 - compile failed in org/eclipse/wst/xsl/xalan/debugger with Tycho 1.1.0-SNAPSHOT (3.10.0.M5)
 
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=530467 - compile failed in org/eclipse/wst/xsl/xalan/debugger with Tycho 1.1.0-SNAPSHOT (3.10.0.M5)
 +
* https://bugs.eclipse.org/bugs/show_bug.cgi?id=530464 - DONE: WTP update site should include redistribution of Jetty 9.4.7
 
|}
 
|}
  

Latest revision as of 11:06, 6 February 2018

Smoke Test Promotion votes

Instructions:

Use a red X (fail) icon (Fail.gif) to signify that the build should not be promoted, that a respin is required. In that case, please provide bug number and be sure those that need to fix something are aware of it, and can arrange for a respin. Once the issue has been fixed, and confirmed, change the red X to a green check mark with the build Id where is was verified, so those doing the promotion know its ready to go.

If a smoke test does not pass but the build can still be promoted, use a green check mark (ok) icon (Checkmark.gif) but then document in the comments bug numbers, how the smoke test fails, workarounds, or cautions about the build.

If a build can be promoted and no issues were found, simple use the green check mark and include the initials or names of who performed the test.

Remember the significant column for promoting a build is the left-most project column. If some component within a project has not (or can not) be tested, the Project Lead should either make sure someone does the test, or make a judgment call on if the build (from their project's point of view) can be promoted or not. If the smoke test could not be performed, a note should be made in the comments section that it wasn't performed, why, and why that should prevent promotion.

Keep in mind the threshold for promoting a build gets higher as we near a milestone or near a release.

This Week's Results
Project Vote Initials Comments


Java EE Checkmark.gif DG (Deployment of Java EE 8 modules is not tested)
JSF Checkmark.gif IMT
Dali Questionmark.gif
Server Checkmark.gif SC (Stephanie Cao)
Web Services, WSDL Checkmark.gif Checkmark.gifWeb Services (kc) - Caveat: Pass with 201705 Server Tools component installed. See 530465.

Checkmark.gifWSDL (kc)

Checkmark.gifJAXWS (sc)

JSDT,

Node.js tools (bower, npm, grunt, gulp)

Checkmark.gif Checkmark.gifJSDT (vr)

Checkmark.gifNode.js-tools (vr)

Source Editing Checkmark.gif Checkmark.gifXML + JSP (nd)

Checkmark.gifXSD (kc)

Checkmark.gifJSON (vr)

Release Engineering Fail.gif


Smoke Test ok to promote vote = Checkmark.gif
Smoke Test do not promote vote = Fail.gif
Smoke Test Pending = Questionmark.gif
Back to the WTP Smoke Test Results Main Page

Back to the top