Bump junit

Bumps [junit](https://github.com/junit-team/junit4) from 4.12 to 4.13.1.
- [Release notes](https://github.com/junit-team/junit4/releases)
- [Changelog](https://github.com/junit-team/junit4/blob/main/doc/ReleaseNotes4.12.md)
- [Commits](https://github.com/junit-team/junit4/compare/r4.12...r4.13.1)

---
updated-dependencies:
- dependency-name: junit:junit
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
1 file changed
tree: 9a5f885aef349fe1fc11e86bb38151d4bd0c6c84
  1. actionloop-starter-kit/
  2. docker-compose/
  3. java-action-archetype/
  4. java-local/
  5. knative-build/
  6. maven-java/
  7. node-local/
  8. terraform-wskdeploy-plugin/
  9. tools/
  10. .asf.yaml
  11. .gitignore
  12. .travis.yml
  13. CONTRIBUTING.md
  14. LICENSE.txt
  15. README.md
README.md

Developer tools for OpenWhisk

License Build Status

This repository is part of Apache OpenWhisk and provides developer tools that help with local development, testing and operation of OpenWhisk.

Subprojects

  • docker-compose allows testing OpenWhisk locally, using Docker Compose. This is ideal if you are contributing to core development
  • java-action-archetype This archetype helps to generate the Java Action template project.
  • node-local allows testing individual OpenWhisk functions locally, using only node.js. This is ideal if you are writing node.js functions to run in OpenWhisk, but need to emulate some of OpenWhisk's behavior in creating params and expecting promises.
  • maven-java allows testing OpenWhisk Java Actions. This shows how to package the function dependencies e.g. external jar.
  • knative-build contains Knative Build Templates along with modified versions of their respective OpenWhisk Action Runtimes that can be used to Build and Serve Knative compatible applications on Kubernetes.
  • actionloop-starter-kit contains a starter kit to build a new runtime using the ActionLoop proxy used in Go, Swift, PHP, Python and Rust runtimes.

Travis builds

Each tool in this repository has to provide travis build scripts inside a .travis folder. The folder should define 2 scripts:

  • setup.sh - invoked during before_install phase
  • build.sh - invokes during script phase

For an example check out docker-compose/.travis folder.