Develop

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,21 @@
+---
+name: Bug report
+about: Tell us about a bug you found
+title: ''
+labels: bug
+
+---
+
+<!-- Please answer these questions before submitting your issue. Thanks! -->
+
+### What version are you using?
+
+
+### What did you do?
+
+
+### What happened?
+
+
+### What did you expect to see instead?
+

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Stellar Ecosystem Proposals (SEPs)
+    url: https://github.com/stellar/stellar-protocol
+    about: The SEPs implemented in this project are defined here.
+  - name: Stellar Laboratory
+    url: https://laboratory.stellar.org/#?network=test
+    about: The best place to experiment with the Stellar network.
+  - name: Docker Images
+    url: https://hub.docker.com/r/stellar/anchor-platform
+    about: Where to check the available Docker images that have been published.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,18 @@
+---
+name: Feature request
+about: Tell us what you'd like to see
+title: 'Feature Request: '
+labels: 'feature request'
+
+---
+
+<!-- Please answer these questions before submitting your issue. Thanks! -->
+
+### What problem does your feature solve?
+
+
+### What would you like to see?
+
+
+### What alternatives are there?
+

.github/ISSUE_TEMPLATE/release_a_new_version.md

@@ -0,0 +1,32 @@
+---
+name: Release a New Version!
+about: Prepare a release to be launched
+title: ''
+labels: release
+---
+
+<!-- Please Follow this checklist before making your release. Thanks! -->
+
+### Release Checklist
+
+> Attention: the examples below use the version `0.1.0` but you should update them to use the version you're releasing.
+
+- [ ] Decide on a version number based on the current version number and the common rules defined in [Semantic Versioning](https://semver.org). E.g. `0.1.0`.
+- [ ] Update this ticket name to reflect the new version number, following the pattern "Release `0.1.0`".
+- [ ] Cut a branch for the new release out of the `develop` branch, following the gitflow naming pattern `release/0.1.0`.
+- [ ] Update the code to use this version number.
+- [ ] Update the [CHANGELOG.md] file with the new version number and release notes.
+- [ ] Update the badges versions in [docs/00 - Stellar Anchor Platform.md].
+- [ ] Run tests and linting. **Not only CI/CD tests, but also manual tests to make sure the release is up and running, and that it's stable!**
+- [ ] Make all changes necessary to make sure the release is ready to be published. If new issues are found during the manual tests, create new tickets aiming at improving the automated tests so these issues can be automatically detected next time.
+- [ ] DO NOT RELEASE before holidays or weekends! Mondays and Tuesdays are preferred.
+- [ ] When the team is confident the release is stable, you'll need to create two pull requests:
+  - [ ] `release/0.1.0 -> main`: this should require two approvals.
+  - [ ] `release/0.1.0 -> develop`: ideally, this should be merged after the `main` branch is merged.
+- [ ] After the release(e.g. `0.1.0`) branch is merged to `main`, create a new release on GitHub with the name `0.1.0` and the changes from the [CHANGELOG.md] file.
+  - [ ] The release will automatically publish a new version of the docker image to Docker Hub.
+  - You'll need to manually publish a new version of the SDK to [Maven Central](https://search.maven.org/search?q=g:org.stellar.anchor-sdk).
+  - [ ] You'll need to manually upload the jar file from [Maven Central](https://search.maven.org/search?q=g:org.stellar.anchor-sdk) to the GH release.
+
+[CHANGELOG.md]: ../../CHANGELOG.md
+[docs/00 - Stellar Anchor Platform.md]: ../../docs/00%20-%20Stellar%20Anchor%20Platform.md

.github/workflows/build_and_test.yml → .github/workflows/basic_tests.yml

@@ -1,12 +1,19 @@
-# This workflow will build a Java project with Maven, and cache/restore any dependencies to improve the workflow execution time
-# For more information see: https://help.github.com/actions/language-and-framework-guides/building-and-testing-java-with-maven
+# This workflow will build a Java project with Gradle.
+# This workflow is triggered:
+#   1. Called from other workflows.
+#   2. On every pull request
+#   3. When commits are pushed or merged onto `main` branch
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-java-with-maven
 
-name: Java CI with Gradle
+name: Basic Tests
 
 on:
-  push:
-    branches: [ main ]
-  pull_request:
+  workflow_dispatch: 
+  workflow_call: # allows this workflow to be called from another workflow
+  pull_request:  # when a pull request is created.
+  push:          # when commits are pushed or merged onto `main` branch
+    branches: 
+      - main
 
 jobs:
   build_and_test:
@@ -18,52 +25,34 @@ jobs:
       with:
         java-version: '11'
         distribution: 'adopt'
+
     - name: Check code formatting
       run: ./gradlew spotlessCheck || echo "❌ Your code is not properly formatted. You can run './gradlew spotlessApply' to format it. 👀"
+
     - name: Clean, Build and Test
+      run: ./gradlew clean build
+
+    - name: Print Test Results
+      if: success() || failure()
       run: |
-        ./gradlew clean build
-        echo *** SEP test report ***
+        echo "\n\n*** API Schema test report ***\n"
+        cat /home/runner/work/java-stellar-anchor-sdk/java-stellar-anchor-sdk/api-schema/build/reports/tests/test/index.html
+        echo "\n\n*** SEP test report ***\n"
         cat /home/runner/work/java-stellar-anchor-sdk/java-stellar-anchor-sdk/core/build/reports/tests/test/index.html
-        echo *** Payment test report ***
-        cat /home/runner/work/java-stellar-anchor-sdk/java-stellar-anchor-sdk/payment/build/reports/tests/test/index.html
-        echo *** Platform test report ***
+        echo "\n\n*** Platform test report ***\n"
         cat /home/runner/work/java-stellar-anchor-sdk/java-stellar-anchor-sdk/platform/build/reports/tests/test/index.html
-        echo *** Anchor reference server test report ***
+        echo "\n\n*** Integration tests report ***\n"
+        cat /home/runner/work/java-stellar-anchor-sdk/java-stellar-anchor-sdk/integration-tests/build/reports/tests/test/index.html
+        echo "\n\n*** Anchor reference server test report ***\n"
         cat /home/runner/work/java-stellar-anchor-sdk/java-stellar-anchor-sdk/anchor-reference-server/build/reports/tests/test/index.html
 
-  build_and_push_anchor_platform:
-    if: github.event.pull_request == null
-    needs: [build_and_test]
-    runs-on: ubuntu-latest
-    name: Push stellar/anchor-platform:sha to DockerHub
-    steps:
-    - uses: actions/checkout@v3
-
-    - name: Get image tag (short sha)
-      shell: bash
-      id: get_tag
-      run: echo ::set-output name=TAG::$(git rev-parse --short ${{ github.sha }} )
-
-    - name: Login to DockerHub
-      uses: docker/login-action@bb984efc561711aaa26e433c32c3521176eae55b
-      with:
-        username: ${{ secrets.DOCKERHUB_USERNAME }}
-        password: ${{ secrets.DOCKERHUB_TOKEN }}
-
-    - name: Build and push to DockerHub
-      uses: docker/build-push-action@7f9d37fa544684fb73bfe4835ed7214c255ce02b
-      with:
-        push: true
-        tags: stellar/anchor-platform:${{ steps.get_tag.outputs.TAG }},stellar/anchor-platform:latest
-        file: Dockerfile
-
   sep_validation_suite:
     needs: [build_and_test]
     runs-on: ubuntu-latest
     name: Validate SEPs (1, 10, 12, 31, 38)
     env:
       PR_NUMBER: ${{github.event.pull_request.number}}
+      BRANCH_NAME: ${{github.ref}} # e.g. refs/heads/main
     steps:
       - uses: actions/checkout@v3
 
@@ -72,10 +61,13 @@ jobs:
         id: endpoint-finder
         run: |
           export HOME_DOMAIN=https://anchor-sep-server-dev.stellar.org
-          if [ ! -z "$PR_NUMBER" ]
-          then
-            export HOME_DOMAIN=https://anchor-sep-pr$PR_NUMBER.previews.kube001.services.stellar-ops.com
+
+          if [[ ! -z "$PR_NUMBER" ]]; then
+              export HOME_DOMAIN=https://anchor-sep-pr$PR_NUMBER.previews.kube001.services.stellar-ops.com
+          elif [[ $BRANCH_NAME = refs/heads/main ]]; then
+              export HOME_DOMAIN=https://anchor-sep-server-prd.stellar.org
           fi
+
           echo HOME_DOMAIN=$HOME_DOMAIN
           echo "::set-output name=HOME_DOMAIN::$HOME_DOMAIN"
 
@@ -92,8 +84,9 @@ jobs:
           stellar-anchor-tests --home-domain $HOME_DOMAIN --seps 1 10 12 31 38 --sep-config platform/src/test/resources/stellar-anchor-tests-sep-config.json
 
   complete:
+    if: always()
     needs: [build_and_test, sep_validation_suite]
     runs-on: ubuntu-latest
     steps:
-      - if: contains(needs.*.result, 'failure')
-        run: exit 1
+    - if: contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled')
+      run: exit 1

.github/workflows/branch_develop.yml

@@ -0,0 +1,51 @@
+# This workflow will build a docker image and push to docker hub
+# This workflow is triggered:
+#   1. When commits are pushed or merged onto `develop` branch
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-java-with-maven
+
+
+name: Push/Merge to `develop` Branch
+
+on:
+  workflow_dispatch:
+  push:
+    branches: 
+      - develop # when commits are pushed or merged onto `develop` branch
+
+jobs:
+  tests:
+    uses: ./.github/workflows/basic_tests.yml  # use the callable tests job to run tests
+    secrets: inherit # pass all secrets
+
+  build_and_push_docker_image:
+    name: Push to DockerHub # stellar/anchor-platform:{sha} and stellar/anchor-platform:edge
+    needs: [tests]
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v3
+
+    - name: Get image SHA
+      shell: bash
+      id: get_sha
+      run: echo ::set-output name=SHA::$(git rev-parse --short ${{ github.sha }} )
+
+    - name: Login to DockerHub
+      uses: docker/login-action@bb984efc561711aaa26e433c32c3521176eae55b
+      with:
+        username: ${{ secrets.DOCKERHUB_USERNAME }}
+        password: ${{ secrets.DOCKERHUB_TOKEN }}
+
+    - name: Build and push to DockerHub
+      uses: docker/build-push-action@7f9d37fa544684fb73bfe4835ed7214c255ce02b
+      with:
+        push: true
+        tags: stellar/anchor-platform:${{ steps.get_sha.outputs.SHA }},stellar/anchor-platform:edge
+        file: Dockerfile
+
+  complete:
+    if: always()
+    needs: [tests, build_and_push_docker_image]
+    runs-on: ubuntu-latest
+    steps:
+    - if: contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled')
+      run: exit 1

.github/workflows/branch_release.yml

@@ -0,0 +1,46 @@
+name: Push/Merge to any `release` Branches
+
+on:
+  workflow_dispatch:
+  push:
+    branches: 
+      - 'release/**'
+      - 'releases/**'
+
+jobs:
+  tests:
+    uses: ./.github/workflows/basic_tests.yml  # use the callable tests job to run tests
+    secrets: inherit # pass all secrets
+
+  build_and_push_docker_image:
+    name: Push to DockerHub # stellar/anchor-platform:sha
+    needs: [tests]
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v3
+
+    - name : Get Project Version
+      shell: bash
+      id: get_version
+      run: echo ::set-output name=VERSION::$(${{github.workspace}}/gradlew -q printVersionName)
+
+    - name: Login to DockerHub
+      uses: docker/login-action@bb984efc561711aaa26e433c32c3521176eae55b
+      with:
+        username: ${{ secrets.DOCKERHUB_USERNAME }}
+        password: ${{ secrets.DOCKERHUB_TOKEN }}
+
+    - name: Build and push to DockerHub
+      uses: docker/build-push-action@7f9d37fa544684fb73bfe4835ed7214c255ce02b
+      with:
+        push: true
+        tags: stellar/anchor-platform:${{ steps.get_version.outputs.VERSION }}-rc
+        file: Dockerfile
+
+  complete:
+    if: always()
+    needs: [tests, build_and_push_docker_image]
+    runs-on: ubuntu-latest
+    steps:
+    - if: contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled')
+      run: exit 1

.github/workflows/codeql_analysis.yml

@@ -0,0 +1,81 @@
+# For most projects, this workflow file will not need changing; you simply need
+# to commit it to your repository.
+#
+# You may wish to alter this file to override the set of languages analyzed,
+# or to provide custom queries or build logic.
+#
+# ******** NOTE ********
+# We have attempted to detect the languages in your repository. Please check
+# the `language` matrix defined below to confirm you have the correct set of
+# supported CodeQL languages.
+#
+name: CodeQL
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - develop
+      - main
+      - 'release/**'
+      - 'releases/**'
+  pull_request:
+    # The branches below must be a subset of the branches above
+    branches:
+      - develop
+      - main
+  schedule:
+    - cron: '30 9 * * 4'
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [ 'java', 'python' ]
+        # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python', 'ruby' ]
+        # Learn more about CodeQL language support at https://aka.ms/codeql-docs/language-support
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v3
+
+    # Initializes the CodeQL tools for scanning.
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v2
+      with:
+        languages: ${{ matrix.language }}
+        # If you wish to specify custom queries, you can do so here or in a config file.
+        # By default, queries listed here will override any specified in a config file.
+        # Prefix the list here with "+" to use these queries and those in the config file.
+
+        # Details on CodeQL's query packs refer to : https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
+        # queries: security-extended,security-and-quality
+
+
+    # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
+    # If this step fails, then you should remove it and run the build manually (see below)
+    - name: Autobuild
+      uses: github/codeql-action/autobuild@v2
+
+    # ℹ️ Command-line programs to run using the OS shell.
+    # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
+
+    #   If the Autobuild fails above, remove it and uncomment the following three lines. 
+    #   modify them (or add more) to build your code if your project, please refer to the EXAMPLE below for guidance.
+
+    # - run: |
+    #   echo "Run, Build Application using script"
+    #   ./location_of_script_within_repo/buildscript.sh
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v2
+      with:
+        category: "/language:${{matrix.language}}"