-
Notifications
You must be signed in to change notification settings - Fork 47
43 lines (35 loc) · 1.41 KB
/
command-line.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
# This is a basic workflow to help you get started with Actions
# based on https://github.com/JGCRI/hector/new/main?filename=.github%2Fworkflows%2Fmain.yml&workflow_template=blank
name: Command Line Hector
# Controls when the action will run.
on:
push:
branches:
- main
pull_request:
branches:
- '**' # matches every branch
schedule:
# * is a special character in YAML so you have to quote this string
# Launch run at 6am the 1st of every month.
- cron: '0 6 1 * *'
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
jobs:
# This workflow contains two jobs, one that builds hector on ubuntu and the second
# builds and tests Hector on macos. The purpose of this work for is to make sure that Hector
# can be built from the command line.
ubuntu:
# Don't run scheduled job on forks, only in main repository.
if: (github.event_name == 'schedule' && github.repository == 'JGCRI/hector') || (github.event_name != 'schedule')
runs-on: ubuntu-latest
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
- name: build and run
run: |
sudo apt-get update
sudo apt install libboost-dev
make hector
bash ./test_hector.sh ./src/hector