The prepared distribution packages are failing autoreconf
due to a missing acsite.m4. Add autoreconf to the centos-7
build which uses the prepared package to test for this
issue.
For example, to use suricata-verify pr #239:
suricata-verify-pr: 239
Also update the pull request template to contain the available
parameters that can be set.
Create a "prep" build that parses libhtp, suricata-update and
suricata-verify repo and branch information from the pull
request message and turn these into artifacts that are
used by the builders
Examples:
libhtp-repo: https://github.com/OISF/libhtp
libhtp-branch: 0.5.x
suricata-verify-repo: http://github.com/OISF/suricata-verify
suricata-verify-branch: master
suricata-update-repo: http://github.com/OISF/suricata-update
suricata-update-branch: master
Other changes:
- checkout@v2 (faster)
- working directory cleanup
0.14.2 breaks builds with Rust 1.34.0, which we still support.
Also build cbdingen in debug mode. It builds much faster
with minimal runtime performance.
On a pull request, attempt to compile all commits from
the base branch to the head of the PR branch.
The job is in a separate workflow file to limit it to
pull-requests only, as the base branch is not available
on push (something to look into).
On the CentOS 7 build, test a make after a make clean. Should
catch the case where bundled generated headers files get deleted
when cbindgen is not available to rebuild them.
If sources are vendored, we get the same effect of using frozen
with a lock file, and the Cargo.lock is generated based
on the vendored sources.
This also removes the need to ship a Cargo.lock.
Fixed out of source builds with vendored sources.
As the action runs natively on 18.04 we were not explicitly
setting a container, but this means we're using what GitHub
provides us as a default state which might be broken. Instead
use the standard Ubuntu 18.04 container.
Jason Ish
Roland Fischer
Shivani Bhardwaj
Philippe Antoine
Victor Julien
Danny Browning