Skip to content

Automate onefile build in CI #40

Description

@netanelcyber

Problem

adpentest_onefile.py is currently regenerated by hand via a scratch script. It will drift from the package on any core change.

Proposal

  • Move the assembly logic into scripts/build_onefile.py (checked in)
  • Add a GitHub Actions job on push to main that:
    1. Runs the script
    2. Fails CI if adpentest_onefile.py differs from HEAD
    3. Runs python3 -m py_compile adpentest_onefile.py and a smoke import

Bonus

  • Attach the built onefile as a release asset on tag pushes (v*).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions