apache/openwhisk

Build binary test actions from source

Open

#4630 opened on Sep 17, 2019

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Scala (6,777 stars) (1,177 forks)batch import
good first issuehelp wantedreleasetesting

Description

Apache source releases should not include compiled files or other binary artifacts.

Our git repo includes binary artifacts as listed below that are used as input to our test suite. We should add support for building these artifacts from source so that it is possible to run the full openwhisk test suite from a pure source release.

tests/dat/actions/helloSwift311.zip: application/zip; charset=binary
tests/dat/actions/sleep.jar: application/java-archive; charset=binary
tests/dat/actions/helloJavaDefaultPackage.jar: application/java-archive; charset=binary
tests/dat/actions/python_virtualenv_name.zip: application/zip; charset=binary
tests/dat/actions/zippedaction.zip: application/zip; charset=binary
tests/dat/actions/helloJava.jar: application/zip; charset=binary
tests/dat/actions/python37_virtualenv.zip: application/zip; charset=binary
tests/dat/actions/python_virtualenv_dir.zip: application/zip; charset=binary
tests/dat/actions/multiSwift.zip: application/zip; charset=binary
tests/dat/actions/python3_virtualenv.zip: application/zip; charset=binary
tests/dat/actions/unicode.tests/ballerina-0.990.bin: application/octet-stream; charset=binary
tests/dat/actions/unicode.tests/dotnet-2.2.bin: application/zip; charset=binary
tests/dat/actions/unicode.tests/java-8.bin: application/zip; charset=binary
tests/dat/actions/python.zip: application/zip; charset=binary
tests/dat/actions/blackbox.zip: application/zip; charset=binary
tests/dat/actions/python2_virtualenv.zip: application/zip; charset=binary
tests/performance/gatling_tests/src/gatling/resources/data/javaAction.jar: application/java-archive; charset=binary)

Contributor guide

Tech stack
javapythonswiftshell
Domain
build systemtesting
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Java build toolsPython packagingSwift compilationApache OpenWhisk project structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue requires replacing binary test artifacts (listed in `tests/dat/actions/`) with source built versions. Start by examining the current build system (likely Gradle or SBT) and how existing action types are compiled. For each artifact, identify the source language (Java, Python, Swift, etc.) and determine the appropriate build commands (e.g., `jar` for Java, `zip` for Python, `swiftc` for Swift). Proposed approach: create a script (e.g., `tools/build/compile test actions.sh`) that generates each artifact from its source, and update the test suite to build these before running tests. Check the repository's `tests` and `tools` directories for existing build scripts and configuration files.