Skip to content

Commit

Permalink
fix: always run benchmarks after build + some inputs to the benchmark…
Browse files Browse the repository at this point in the history
…er and secrets.
  • Loading branch information
maxemiliang committed Apr 20, 2024
1 parent a49fd1e commit ed3d84e
Show file tree
Hide file tree
Showing 2 changed files with 19 additions and 0 deletions.
6 changes: 6 additions & 0 deletions .github/workflows/build-push.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,10 @@ jobs:
build_type: Release
retention: 30
upload_artifacts: true
run_benchmarks: true
secrets:
OS_USERNAME: ${{ secrets.OS_USERNAME }}
OS_PASSWORD: ${{ secrets.OS_PASSWORD }}

# Then, we build and test using all licenses included proprietary ones
build-proprietary:
Expand All @@ -33,6 +37,8 @@ jobs:
secrets:
gurobi_license: ${{ secrets.GUROBI_LICENSE_FILE }}
gams_license: ${{ secrets.GAMS_LICENSE_FILE }}
OS_USERNAME: ${{ secrets.OS_USERNAME }}
OS_PASSWORD: ${{ secrets.OS_PASSWORD }}


# Publish the test results as an output
Expand Down
13 changes: 13 additions & 0 deletions .github/workflows/build-workflow.yml
Original file line number Diff line number Diff line change
Expand Up @@ -59,13 +59,24 @@ on:
default: '42.3.0'
required: false
type: string
run_benchmarks:
description: 'Should the benchmarks be run'
default: false
required: false
type: boolean
secrets:
gurobi_license:
description: 'Gurobi license file secret'
required: false
gams_license:
description: 'GAMS license file secret'
required: false
OS_USERNAME:
description: 'OpenStack username'
required: false
OS_PASSWORD:
description: 'OpenStack password'
required: false

outputs:
test-artifact:
Expand Down Expand Up @@ -350,8 +361,10 @@ jobs:
# Finally, we run some simple benchmarks
benchmark:
if: ${{ inputs.run_benchmarks }}
name: Benchmark
uses: ./.github/workflows/benchmarker.yml
needs: [ build ]
with:
shot_executable_path: "${{ github.workspace }}/build"
benchmark_folder: "MINLP-convex-small"
Expand Down

0 comments on commit ed3d84e

Please sign in to comment.