8000 build using Py3.8 and test across more OSs by mr-tz · Pull Request #506 · mandiant/capa · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

build using Py3.8 and test across more OSs #506

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.

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

Merged
merged 3 commits into from
Apr 13, 2021
Merged

build using Py3.8 and test across more OSs #506

merged 3 commits into from
Apr 13, 2021

Conversation

mr-tz
Copy link
Collaborator
@mr-tz mr-tz commented Mar 29, 2021

closes #505
also further discussion is warranted

@mr-tz mr-tz force-pushed the ci/build-update branch 3 times, most recently from d97d7ac to 0bca626 Compare March 29, 2021 12:19
@mr-tz
Copy link
Collaborator Author
mr-tz commented Mar 29, 2021

now this also runs on Windows 7

2021-03-29_14-35-30

capa.exe 478040c

@@ -26,10 +29,11 @@ jobs:
uses: actions/checkout@v2
with:
submodules: true
- name: Set up Python 3.9
# using Python 3.8 to support running across multiple operating systems including Windows 7
Copy link
Contributor

Choose a reason for hiding this comment

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

good comment

@williballenthin williballenthin marked this pull request as draft March 29, 2021 14:00
@mr-tz mr-tz added CI Continuous Integration configuration dont merge Indicate a PR that is still being worked on labels Mar 29, 2021
@williballenthin
Copy link
Contributor

whats our status here?

@mr-tz
Copy link
Collaborator Author
mr-tz commented Apr 6, 2021

If we're fine with Python 3.8 I can remove the testing code and get this set up before the next release.

@mr-tz
Copy link
Collaborator Author
mr-tz commented Apr 9, 2021

bump @Ana06 and @williballenthin
can I enable this / remove the comments for a merge?

@mr-tz mr-tz force-pushed the ci/build-update branch from 0bca626 to 3afd445 Compare April 12, 2021 15:57
@mr-tz mr-tz marked this pull request as ready for review April 12, 2021 15:59
Copy link
Member
@Ana06 Ana06 left a comment

Choose a reason for hiding this comment

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

This fixes a bug, so it should be mentioned in the changelog 😉

@@ -45,10 +46,38 @@ jobs:
name: ${{ matrix.asset_name }}
path: dist/${{ matrix.artifact_name }}

test_run:
Copy link
Member

Choose a reason for hiding this comment

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

I do not really like to test this in the build workflow. I mean, we release and if any OS fails we don't upload any binary. It would be better to test this before releasing. What about adding a test build workflow which is run in master (which should be green before releasing) and removing it from here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

hm, how can we do this on a per-case basis? maybe via a specific activity type https://docs.github.com/en/actions/reference/events-that-trigger-workflows#release?

Copy link
Member
@Ana06 Ana06 Apr 12, 2021

Choose a reason for hiding this comment

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

What do you mean? running it only on a release PR?

My proposal was to create a build_test.yml which is run on master:

on:
  push:
    branches:
      - master

alternatively we could test it on every PR

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Instead of duplicating steps in a new workflow file my new proposal uses if checks to test_run on push to master or to zip on release.

@Ana06 Ana06 added bug Something isn't working and removed dont merge Indicate a PR that is still being worked on labels Apr 12, 2021
@mr-tz mr-tz force-pushed the ci/build-update branch from 3afd445 to b0fde86 Compare April 13, 2021 08:59
@@ -45,10 +48,40 @@ jobs:
name: ${{ matrix.asset_name }}
path: dist/${{ matrix.artifact_name }}

test_run:
if: github.event_name == 'push' && github.ref == 'refs/heads/master'
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

do this step on push to master

Copy link
Member
@Ana06 Ana06 Apr 13, 2021

Choose a reason for hiding this comment

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

I think github.event_name == 'push' should be enough because this only runs in master

zip:
if: github.event_name == 'release'
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

do this only for release events

@Ana06 Ana06 mentioned this pull request Apr 13, 2021
16 tasks
Copy link
Member
@Ana06 Ana06 left a comment

Choose a reason for hiding this comment

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

👍

@@ -45,10 +48,40 @@ jobs:
name: ${{ matrix.asset_name }}
path: dist/${{ matrix.artifact_name }}

test_run:
if: github.event_name == 'push' && github.ref == 'refs/heads/master'
Copy link
Member
@Ana06 Ana06 Apr 13, 2021

Choose a reason for hiding this comment

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

I think github.event_name == 'push' should be enough because this only runs in master

@@ -75,9 +78,10 @@ jobs:
run: ./${{ matrix.artifact_name }} -h

zip:
Copy link
Member

Choose a reason for hiding this comment

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

zip_and_upload may be a better name for this (although this was not modified in this PR)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

updated this and the 'push' check, thanks!

@mr-tz mr-tz force-pushed the ci/build-update branch from 0dd00ab to 3e5135d Compare April 13, 2021 13:21
Copy link
Member
@Ana06 Ana06 left a comment

Choose a reason for hiding this comment

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

Looks ready to merge! 🎉 (nitpick: squashing the commit would be great 👀 )

@mr-tz mr-tz merged commit 3023634 into master Apr 13, 2021
@mr-tz mr-tz deleted the ci/build-update branch April 13, 2021 13:42
@mr-tz
Copy link
Collaborator Author
mr-tz commented Apr 13, 2021

Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CI Continuous Integration configuration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Build releases using older Python version - Windows compatibility
3 participants
0