You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by ah...@apache.org on 2019/11/08 17:43:17 UTC
[isis] branch master updated: ISIS-2167: initial CI workflow only
printing mvn version (#157)
This is an automated email from the ASF dual-hosted git repository.
ahuber pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/isis.git
The following commit(s) were added to refs/heads/master by this push:
new d67a3df ISIS-2167: initial CI workflow only printing mvn version (#157)
d67a3df is described below
commit d67a3df61aa356111b5f3993246af8c3082d4517
Author: Andi Huber <ah...@apache.org>
AuthorDate: Fri Nov 8 18:43:09 2019 +0100
ISIS-2167: initial CI workflow only printing mvn version (#157)
* ISIS-2167: initial CI workflow only printing mvn version
* ISIS-2167: github-ci: add step 'Setup Script Environment'
* ISIS-2167: github-ci: testing workflow scoped env vars
* ISIS-2167: github-ci: testing workflow scoped env vars (2)
* ISIS-2167: github-ci: testing workflow scoped env vars (3)
* ISIS-2167: github-ci: testing workflow scoped env vars (4)
* ISIS-2167: github-ci: testing workflow scoped env vars (5)
* ISIS-2167: github-ci: testing workflow scoped env vars (6)
* ISIS-2167: github-ci: testing workflow scoped env vars (7)
* ISIS-2167: github-ci: testing workflow scoped env vars (8)
* ISIS-2167: github-ci: testing workflow scoped env vars (9)
* ISIS-2167: github-ci: testing workflow scoped env vars (10)
* ISIS-2167: github-ci: testing workflow scoped env vars (11)
* ISIS-2167: github-ci: testing workflow scoped env vars (12)
* ISIS-2167: github-ci: testing workflow scoped env vars (13)
* ISIS-2167: github-ci: testing workflow scoped env vars (14)
* ISIS-2167: github-ci: testing workflow scoped env vars (15)
* ISIS-2167: github-ci: testing workflow scoped env vars (16)
* ISIS-2167: github-ci: testing workflow scoped env vars (17)
* ISIS-2167: github-ci: add 'Build Mixins' step
* ISIS-2167: github-ci: testing workflow scoped env vars (18)
* ISIS-2167: github-ci: testing workflow scoped env vars (19)
* ISIS-2167: github-ci: testing workflow scoped env vars (20)
* ISIS-2167: github-ci: adds stage 'Build Core', switches goal to install
no publishing for now
* ISIS-2167: github-ci: trying to fix the core build
* ISIS-2167: github-ci: trying to fix the core build (2)
* ISIS-2167: github-ci: trying to fix the core build (3)
* ISIS-2167: github-ci: seems to work, adding some comments
---
.github/workflows/ci-workflow.yml | 89 +++++++++++++++++++++++++++++++++++++++
scripts/ci/core-gitlab-ci.yml | 2 +-
2 files changed, 90 insertions(+), 1 deletion(-)
diff --git a/.github/workflows/ci-workflow.yml b/.github/workflows/ci-workflow.yml
new file mode 100644
index 0000000..46e0403
--- /dev/null
+++ b/.github/workflows/ci-workflow.yml
@@ -0,0 +1,89 @@
+name: Build Package Push All
+
+on: [push]
+
+jobs:
+ build:
+ name: build
+ runs-on: ubuntu-latest
+ env:
+ # to be shared amoung all steps of this job
+ BASELINE: 2.0.0-M2
+ PROJECT_ROOT_PATH: ${{ github.workspace }}
+ CI_SCRIPTS_PATH: ${{ github.workspace }}/scripts/ci
+
+ # not used, would be nice if we could transform the TIMESTAMP string into the REVISION
+ # variable here, but it seems github not yet has any string expression manipulation
+ # operators other than concatination
+ TIMESTAMP: ${{ github.event.head_commit.timestamp }}
+
+ # set this to 'deploy' when intent is to push the built packages to a repo
+ # requires 'secrets' which we don't have yet
+ MVN_STAGES: install
+
+ # though equivalent, setting SHARED_VARS_FILE to ~/.env breaks the build, not sure why
+ # the tilde character appears to produce strange side-effects when used here
+ SHARED_VARS_FILE: /home/runner/.env
+
+ steps:
+ - uses: actions/checkout@v1
+ - name: Set up JDK 11
+ uses: actions/setup-java@v1
+ with:
+ java-version: 11
+ - name: Print Maven Version
+ run: mvn --version
+ - name: Setup Script Environment
+ shell: bash
+ # we write the more tricky varibles to the $SHARED_VARS_FILE using the full power of bash commands
+ # then we simply print all the (non-secret) variables as used by the build scripts to the console
+ run: |
+ echo REVISION=$BASELINE.$(date +%Y%m%d)-$(date +%H%M)-$(echo $GITHUB_SHA | cut -c1-8) > $SHARED_VARS_FILE
+ echo GCPAPPENGINEREPO_URL=https\://repo.incode.work >> $SHARED_VARS_FILE
+ echo ============== ENV =================
+ echo BASELINE\: $BASELINE
+ echo TIMESTAMP\: $TIMESTAMP
+ echo PROJECT_ROOT_PATH\: $PROJECT_ROOT_PATH
+ echo CI_SCRIPTS_PATH\: $CI_SCRIPTS_PATH
+ echo MVN_STAGES\: $MVN_STAGES
+ cat $SHARED_VARS_FILE
+ echo ======================================
+ - name: Build Mixins
+ shell: bash
+ run: bash $CI_SCRIPTS_PATH/build-mixins.sh
+ - name: Build Core
+ shell: bash
+ run: bash $CI_SCRIPTS_PATH/build-core.sh
+
+
+# FOR DEBUG USE
+# - name: Dump GitHub context
+# env:
+# ENV_CONTEXT: ${{ toJson(env) }}
+# run: echo "$ENV_CONTEXT"
+# - name: Dump GitHub context
+# env:
+# GITHUB_CONTEXT: ${{ toJson(github) }}
+# run: echo "$GITHUB_CONTEXT"
+# - name: Dump job context
+# env:
+# JOB_CONTEXT: ${{ toJson(job) }}
+# run: echo "$JOB_CONTEXT"
+# - name: Dump steps context
+# env:
+# STEPS_CONTEXT: ${{ toJson(steps) }}
+# run: echo "$STEPS_CONTEXT"
+# - name: Dump runner context
+# env:
+# RUNNER_CONTEXT: ${{ toJson(runner) }}
+# run: echo "$RUNNER_CONTEXT"
+# - name: Dump strategy context
+# env:
+# STRATEGY_CONTEXT: ${{ toJson(strategy) }}
+# run: echo "$STRATEGY_CONTEXT"
+# - name: Dump matrix context
+# env:
+# MATRIX_CONTEXT: ${{ toJson(matrix) }}
+# run: echo "$MATRIX_CONTEXT"
+
+
\ No newline at end of file
diff --git a/scripts/ci/core-gitlab-ci.yml b/scripts/ci/core-gitlab-ci.yml
index ab5a6ec..201c8e4 100644
--- a/scripts/ci/core-gitlab-ci.yml
+++ b/scripts/ci/core-gitlab-ci.yml
@@ -20,7 +20,7 @@
build all:
stage: build-package-push
variables:
- SHARED_VARS_FILE: ~/ci-env.txt
+ SHARED_VARS_FILE: /builds/apache-isis-committers/apache-isis/ci-env.txt
MVN_STAGES: deploy
script:
# mixins are built first because core (which includes extensions) depend upon them.