Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add compilation.yml to enable CI #7

Closed
wants to merge 1 commit into from
Closed

add compilation.yml to enable CI #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions .github/workflows/compilation.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
name: CI-compile

on:
push:
pull_request:

jobs:
build:
runs-on: ubuntu-latest
container: tobix/mipsr5900el-toolchain:latest
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we’d have a dependency on @TobiX repo, then.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is why I didnt made this pr earlier, caus eit is based on 3rd party docker container that can be removed in any moment.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As about describing in Readme where files can be found, @frno7 do you mean just point to the the github official documentation? This is GitHub basic features I dont think that such features should be covered by repo.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AKuHAK, a couple of sentences about why and where (a URL) one might find the produced IRX files would be good, in the README.md especially. Maybe we ought to have a build pass/fail badge there too? :-)

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AKuHAK, are you proposing frno7/linux#69 as a replacement for this pull request?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AKuHAK, are you proposing frno7/linux#69 as a replacement for this pull request?

Not a replacement but more an addition. CI (Continuous Integration) is meant to be involved in each repository as a part of repository's internal check and as an easy way for generating precompiled binaries. This PR can be revisited when the necessary preparations will be made (as described in that PR).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@frno7 frno7/linux#69 is only the next step after you create one more repository for holding the main Docker image

steps:
- uses: actions/checkout@v2
- run: git fetch --prune --unshallow

- name: Compile project
run: make

- name: Get short SHA
id: version
run: echo "::set-output name=version::$(git rev-parse --short HEAD)"

- name: Prepare artifacts for release
run: |
tar -czvf iopmod-modules-${{ steps.version.outputs.version }}.tar.gz module/*.irx

- name: Create release
if: github.ref == 'refs/heads/master'
uses: marvinpinto/action-automatic-releases@latest
with:
repo_token: "${{ secrets.GITHUB_TOKEN }}"
prerelease: true
automatic_release_tag: "latest"
title: "${{ steps.version.outputs.version }}"
files: iopmod-modules-${{ steps.version.outputs.version }}.tar.gz