Skip to content

Commit 54549ae

Browse files
committed
pass the project name
1 parent 257481c commit 54549ae

File tree

3 files changed

+22
-4
lines changed

3 files changed

+22
-4
lines changed

.github/projects/morphia/build.sh

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,8 @@ export MVN="$(pwd)/mvnw"
88
rm -rf core/src/main/java
99
cp -v ../.github/projects/morphia/core-pom.xml core/pom.xml
1010
rewrite.sh
11-
echo hit enter
1211
read
1312

1413
echo -ne "\033]30;Compiling\007"
15-
pwd | tee target/tree.out
1614
$MVN -e -f core/pom.xml dependency:tree 2>&1 | tee -a target/tree.out
1715
$MVN -e -f core/pom.xml test-compile 2>&1 | tee target/build.out

.github/workflows/build.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ jobs:
1313
strategy:
1414
fail-fast: false
1515
matrix:
16-
git-url: [ morphia, javabot ]
16+
project: [ morphia, javabot ]
1717
steps:
1818
- name: Checkout
1919
uses: actions/checkout@v4
@@ -25,4 +25,4 @@ jobs:
2525
server-id: central
2626
cache: maven
2727
- name: Perform Upgrade and Test
28-
run: .github/test-upgrade.sh
28+
run: .github/test-upgrade.sh ${ matrix.project }

README.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
Morphia Upgrade Testing
2+
===
3+
4+
This project exists to automatically run the [openrewrite](https://docs.openrewrite.org/) recipe to assist when upgrading from 2.x to
5+
the upcoming 3.0 release. Failures in the actions are likely and most likely indicate areas that need to have a recipe written to
6+
migrate. Not every change can be automated so failures are likely a permanent issue.
7+
8+
Contributing
9+
---
10+
11+
The initial two projects supported here are the tests from the morphia 2.x branch and a personal project that also uses morphia. If you
12+
have a project that you would like to include in these runs to see how far off the upgrade process is, please file a pull request with
13+
the information listed below.
14+
15+
Each project needs a folder in .github/projects. The bare minimum require is a file called `git` that contains the git repository url
16+
for your project. The git url should include the hash of the branch/version you want to test against. When you have that in place,
17+
you'll need to update the [build workflow](.github/workflows/build.yml) to include your named project in the matrix definition.
18+
19+
Typically, the [build.sh](.github/projects/build.sh) script include should be sufficient to test against your project. If your project
20+
needs a little tweaking, like morphia's does, you can copy build.sh in to your project's folder and customize however you need.

0 commit comments

Comments
 (0)