Details
-
Type:
Task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE 3.0.0
-
Fix Version/s: EE-3.0.0.GA_P01, 3.2
-
Component/s: Release
-
Labels:None
-
Assignee Priority:P1
-
Affects:Compatibility/Configuration
Description
With the adoption of Jenkins CI systen, the ICEpush internal build# mechanism is no longer required.
The build code that creates, updates, and refers to the ICEpush/core/build/build.number file should be removed on the 2 repositories listed in the environment section. Instead, the ICEpush build can simply use the "build.number" ant property (consistent with other ICEfaces, etc. builds). This property is defined by Jenkins at build time, or can be optionally hard-set in the build.properties file as required.
The build code that creates, updates, and refers to the ICEpush/core/build/build.number file should be removed on the 2 repositories listed in the environment section. Instead, the ICEpush build can simply use the "build.number" ant property (consistent with other ICEfaces, etc. builds). This property is defined by Jenkins at build time, or can be optionally hard-set in the build.properties file as required.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
I removed the <buildnumber /> Ant target from the core build.xml. Marking this one as FIXED.