Create news entry on sourceforge for releases automatically

Author: adangel

.ci/build.sh

@@ -122,7 +122,7 @@ function release_build() {
         pmd_ci_gh_releases_uploadAsset "$GH_RELEASE" "net.sourceforge.pmd.eclipse.p2updatesite/target/net.sourceforge.pmd.eclipse.p2updatesite-${PMD_CI_MAVEN_PROJECT_VERSION}.zip"
 
         # extract the release notes
-        RELEASE_NAME="PMD For Eclipse ${PMD_CI_MAVEN_PROJECT_VERSION} ($(date -u +%d-%B-%Y))"
+        RELEASE_NAME="PMD For Eclipse ${PMD_CI_MAVEN_PROJECT_VERSION}"
         BEGIN_LINE=$(grep -n "^## " ReleaseNotes.md|head -1|cut -d ":" -f 1)
         END_LINE=$(grep -n "^## " ReleaseNotes.md|head -2|tail -1|cut -d ":" -f 1)
         END_LINE=$((END_LINE - 1))
@@ -137,6 +137,10 @@ $(head -$END_LINE ReleaseNotes.md | tail -$((END_LINE - BEGIN_LINE)))
 
         # Upload it to sourceforge
         pmd_ci_sourceforge_uploadFile "pmd-eclipse/zipped" "net.sourceforge.pmd.eclipse.p2updatesite/target/net.sourceforge.pmd.eclipse.p2updatesite-${PMD_CI_MAVEN_PROJECT_VERSION}.zip"
+
+        # Create sourceforge blog entry
+        pmd_ci_sourceforge_createDraftBlogPost "$RELEASE_NAME released" "$RELEASE_BODY" "pmd-eclipse-plugin,release"
+        local sf_blog_url="${RESULT}"
     pmd_ci_log_group_end
 
     pmd_ci_log_group_start "Add new release to update site"
@@ -159,6 +163,8 @@ $(head -$END_LINE ReleaseNotes.md | tail -$((END_LINE - BEGIN_LINE)))
 
     # Publish release - this sends out notifications on github
     pmd_ci_gh_releases_publishRelease "$GH_RELEASE"
+    # Publish sourceforge blog entry
+    pmd_ci_sourceforge_publishBlogPost "${sf_blog_url}"
 }
 
 

README.md

@@ -86,7 +86,9 @@ The release happens in two phases:
     *   Update the versions
 2.  Push the changes and the tag. The [Github Actions build](https://github.com/pmd/pmd-eclipse-plugin/actions) will
     then publish the new version on [update site](https://github.com/pmd/pmd-eclipse-plugin-p2-site/) and
-    [github releases](https://github.com/pmd/pmd-eclipse-plugin/releases)
+    [github releases](https://github.com/pmd/pmd-eclipse-plugin/releases). It will also upload the update site
+    to [sourceforge](https://sourceforge.net/projects/pmd/files/pmd-eclipse/zipped/) and create a sourceforge
+    [blog entry](https://sourceforge.net/p/pmd/news/).
 
 
 #### Script
@@ -153,20 +155,9 @@ The release happens in two phases:
 
     echo Done.
 
-Also, don't forget to create a [News](https://sourceforge.net/p/pmd/news/) and
-verify, that the zipped update site has been uploaded to
-[GitHub Releases](https://github.com/pmd/pmd-eclipse-plugin/releases).
-
-You can use the following template:
-
-    PMD for Eclipse $VERSION.$BUILDQUALIFIER released
-    
-    A new PMD for Eclipse plugin version has been released.
-    It is available via the update site: <https://pmd.github.io/pmd-eclipse-plugin-p2-site/>
-    
-    * Release Notes: <https://github.com/pmd/pmd-eclipse-plugin/blob/$VERSION.$BUILDQUALIFIER/ReleaseNotes.md>
-
-
+Verify, that the zipped update site has been uploaded to
+[GitHub Releases](https://github.com/pmd/pmd-eclipse-plugin/releases) and [sourceforge](https://pmd.github.io/pmd-eclipse-plugin-p2-site/)
+and that a [news blog entry](https://sourceforge.net/p/pmd/news/) has been created on sourceforge.
 
 ### Updating the used PMD version
 The parent pom contains the property `pmd.version`. This is used inside the plugin module, to resolve the dependencies.