Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNiraj Modi2019-12-04 16:44:29 +0000
committerNiraj Modi2019-12-04 16:46:50 +0000
commit11ee2ac497c24ea218f2edcd474da570351ba7be (patch)
treedb09c80ff25c79f66ee431330a1d06fa262393ed /scripts/updateProductVersion.sh
parentfb9d16673b181cb4c07ca1f3ca6f77ddb1758f83 (diff)
downloadeclipse.platform.releng.aggregator-11ee2ac497c24ea218f2edcd474da570351ba7be.tar.gz
eclipse.platform.releng.aggregator-11ee2ac497c24ea218f2edcd474da570351ba7be.tar.xz
eclipse.platform.releng.aggregator-11ee2ac497c24ea218f2edcd474da570351ba7be.zip
Bug 545208 - Script for product version update in complete Eclipse code
base. - Added Readme section. - Updated versions changes for 4.14 to 4.15 branching. Change-Id: I63abaebb62363f2badc9e03bc9cbb802928b7a6e Signed-off-by: Niraj Modi <niraj.modi@in.ibm.com>
Diffstat (limited to 'scripts/updateProductVersion.sh')
-rwxr-xr-xscripts/updateProductVersion.sh23
1 files changed, 18 insertions, 5 deletions
diff --git a/scripts/updateProductVersion.sh b/scripts/updateProductVersion.sh
index d2b55c832..62f89c469 100755
--- a/scripts/updateProductVersion.sh
+++ b/scripts/updateProductVersion.sh
@@ -1,6 +1,19 @@
-#Before running this script configure the source and target POM versions correctly
+#############################README##################################################################################
+#Before running this script configure the source and target POM versions correctly, follow detailed steps below:
+#1. Update "updateProductVersion.sh" script with proper source and target version properly for all 4 mentioned files.
+#2. From Shell command prompt go to "eclipse.platform.releng.aggregator" directory
+#3. Then we should run the script using command: ./scripts/updateProductVersion.sh
+#4. Above script will take around less than a minute max to update the complete Eclipse sources.
+#5. Make sure to create the gerrit for for "eclipse.platform.releng.aggregator" in first place:
+#6. gerrit build will fail for this change, you can commit without gerrit validation
+#7. After committing above change, you need to deploy the POM for the new Eclipse version 4.14
+#8. e.g. For new Eclipse release 4.14 [Note: version value will change depending on the release] rub below jobs:
+# https://ci.eclipse.org/releng/job/deploy-eclipse-platform-parent-pom-4.14/
+# https://ci.eclipse.org/releng/job/deploy-eclipse-sdk-target-pom-4.14/
+#9. Now create the gerrit patches for all sub-modules which should pass.
+#10. Finally commit all the modified files in each of the individual submodules of Releng.
cd ..
-find `pwd` -name pom.xml -exec sed -i 's/4.13.0/4.14.0/g' {} \;
-find `pwd` -name MANIFEST.MF -exec sed -i 's/4.13.0/4.14.0/g' {} \;
-find `pwd` -name *.product -exec sed -i 's/4.13.0/4.14.0/g' {} \;
-find `pwd` -name feature.xml -exec sed -i 's/4.13.0/4.14.0/g' {} \;
+find `pwd` -name pom.xml -exec sed -i 's/4.14.0/4.15.0/g' {} \;
+find `pwd` -name MANIFEST.MF -exec sed -i 's/4.14.0/4.15.0/g' {} \;
+find `pwd` -name *.product -exec sed -i 's/4.14.0/4.15.0/g' {} \;
+find `pwd` -name feature.xml -exec sed -i 's/4.14.0/4.15.0/g' {} \;

Back to the top