From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com> To: linux-trace-devel@vger.kernel.org Cc: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com> Subject: [PATCH v2 9/9] trace-cruncher: Add github workflow for CI testing Date: Fri, 11 Jun 2021 14:39:58 +0300 [thread overview] Message-ID: <20210611113958.38142-10-y.karadz@gmail.com> (raw) In-Reply-To: <20210611113958.38142-1-y.karadz@gmail.com> The CI workflow will run once a week, or on any push to branches "master" and "yordan_devel". Signed-off-by: Yordan Karadzhov (VMware) <y.karadz@gmail.com> --- .github/workflows/main.yml | 58 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+) create mode 100644 .github/workflows/main.yml diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml new file mode 100644 index 0000000..94abf64 --- /dev/null +++ b/.github/workflows/main.yml @@ -0,0 +1,58 @@ +name: trace-cruncher CI + +on: + push: + branches: [master, yordan_devel] + schedule: + - cron: '0 15 * * THU' + +jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Install Dependencies + shell: bash + run: | + sudo apt-get update + sudo apt-get install build-essential git cmake libjson-c-dev -y + sudo apt-get install libpython3-dev cython3 python3-numpy -y + sudo apt install python3-pip + sudo pip3 install --system pkgconfig GitPython + git clone https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/ + cd libtraceevent + make + sudo make install + cd .. + git clone https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/ + cd libtracefs + make + sudo make install + cd .. + git clone https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git + cd trace-cmd + make + sudo make install_libs + cd .. + git clone https://github.com/yordan-karadzhov/kernel-shark-v2.beta.git kernel-shark + cd kernel-shark/build + cmake .. + make + sudo make install + cd ../.. + + - name: Build + working-directory: ${{runner.workspace}}/trace-cruncher + shell: bash + # Build and install. + run: | + make + sudo make install + + - name: Test + working-directory: ${{runner.workspace}}/trace-cruncher/tests + shell: bash + # Execute tests defined by the CMake configuration. + run: sudo python3 -m unittest discover . -- 2.27.0
prev parent reply other threads:[~2021-06-11 11:41 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-11 11:39 [PATCH v2 0/9] Build trace-cruncher as Python pakage Yordan Karadzhov (VMware) 2021-06-11 11:39 ` [PATCH v2 1/9] trace-cruncher: Refactor the part that wraps ftrace Yordan Karadzhov (VMware) 2021-06-11 11:39 ` [PATCH v2 2/9] trace-cruncher: Refactor the part that wraps libkshark Yordan Karadzhov (VMware) 2021-06-11 11:39 ` [PATCH v2 3/9] trace-cruncher: Add "utils" Yordan Karadzhov (VMware) 2021-06-11 11:39 ` [PATCH v2 4/9] trace-cruncher: Refactor the examples Yordan Karadzhov (VMware) 2021-06-11 11:39 ` [PATCH v2 5/9] trace-cruncher: Add Makefile Yordan Karadzhov (VMware) 2021-06-11 11:39 ` [PATCH v2 6/9] trace-cruncher: Update README.md Yordan Karadzhov (VMware) 2021-06-11 11:39 ` [PATCH v2 7/9] trace-cruncher: Remove all leftover files Yordan Karadzhov (VMware) 2021-06-11 11:39 ` [PATCH v2 8/9] trace-cruncher: Add testing Yordan Karadzhov (VMware) 2021-06-11 11:39 ` Yordan Karadzhov (VMware) [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20210611113958.38142-10-y.karadz@gmail.com \ --to=y.karadz@gmail.com \ --cc=linux-trace-devel@vger.kernel.org \ --subject='Re: [PATCH v2 9/9] trace-cruncher: Add github workflow for CI testing' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).