This project is not covered by Drupal’s security advisory policy.
This project is designed to be used by security team members.
Instructions
- Clone this sandbox project locally.
- Put the email address you wish to use to receive test results in a file called
.emailin the root of the cloned repository:
kick_drupalCI $ echo "you@example.com" > .email - Contact a security team member for the secret token. Place it in a secure
.tokenfile in the root of the cloned repository:
kick_drupalCI $ echo "SECRET_TOKEN_HERE" > .token kick_drupalCI $ chmod 600 .token - Generate a one-time download link for the patch you wish to test on the security.drupal.org issue.
- On the issue, click the "One-time downloads" tab.
- Check the file you wish to test and click submit.
- Copy the one-time download link displayed on the page.
- On the issue, click the "One-time downloads" tab.
- Run the
kick.shshell script to start the test run. Follow the prompts.
kick_drupalCI $ ./kick.sh - Ignore the links output by the script; they will not work. The results will be emailed to you as a file attachment called
build.logwithin 30-60 mins. - To look for test failures in the results:
Drupal 7
grep fail build.log | grep -v \ 0\ fail grep exception build.log | grep -v \ 0\ exceptionDrupal 8
grep \ fail build.log grep \ exception build.log - Upload the full test results to the issue by renaming the
build.logto something liked8_issue_number_results_log.txtand adding it as a file attachment to the issue. This will allow others to check the test results.
Project information
Minimally maintained
Maintainers monitor issues, but fast responses are not guaranteed.Maintenance fixes only
Considered feature-complete by its maintainers.- Created by mlhess on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.




