gradle: create ci_release release strategy

Based on the final release strategy, but allows the repository to be dirty due to incompatibility with how sub-modules are handled in the Travis continuous integration setup.
lnls-dig · Jan 17, 2017 · b644a60 · b644a60
1 parent 489d4bc
commit b644a60
Show file tree

Hide file tree

Showing 2 changed files with 20 additions and 0 deletions.
diff --git a/core/revision/build.gradle b/core/revision/build.gradle
@@ -1,3 +1,5 @@
+import org.ajoberstar.gradle.git.release.opinion.Strategies
+
 plugins {
     id 'org.ajoberstar.grgit' version '1.6.0'
     id 'org.ajoberstar.release-opinion' version '1.6.0'
@@ -24,3 +26,11 @@ model {
         }
     }
 }
+
+release {
+    versionStrategy Strategies.FINAL.copyWith(
+        name: 'ci_release',
+        stages: ['ci_release'] as SortedSet,
+        allowDirtyRepo: true
+    )
+}
diff --git a/libs/halcsclient/build.gradle b/libs/halcsclient/build.gradle
@@ -1,3 +1,5 @@
+import org.ajoberstar.gradle.git.release.opinion.Strategies
+
 plugins {
     id 'org.ajoberstar.grgit' version '1.6.0'
     id 'org.ajoberstar.release-opinion' version '1.6.0'
@@ -34,3 +36,11 @@ model {
         }
     }
 }
+
+release {
+    versionStrategy Strategies.FINAL.copyWith(
+        name: 'ci_release',
+        stages: ['ci_release'] as SortedSet,
+        allowDirtyRepo: true
+    )
+}