Skip to content

owncloud/smashbox-testing

Repository files navigation

Smashbox Testing

License ownCloud OSPO

Smashbox Testing defines the Drone CI configuration for running the ownCloud Smashbox end-to-end test suite on a nightly schedule against multiple ownCloud server tarballs. It automates the continuous validation of ownCloud storage operations across different server versions.

Note: This repository is in maintenance/legacy mode and is no longer actively developed.

Part of Infrastructure / Tooling

This repository is part of the ownCloud CI/CD infrastructure, providing automated nightly test execution for the smashbox test framework.

Legacy notice: This repository is archived/legacy. Drone CI pipelines defined here are no longer actively maintained.

Getting Started

This repository contains CI pipeline definitions. There is no software to build or install.

Documentation

Community & Support

Star this repo and Watch for release notifications!

Contributing

We welcome contributions! Please read the Contributing Guidelines and our Code of Conduct before getting started.

Workflow

  • Rebase Early, Rebase Often! We use a rebase workflow. Always rebase on the target branch before submitting a PR.
  • Dependabot: Automated dependency updates are managed via Dependabot. Review and merge dependency PRs promptly.
  • Signed Commits: All commits must be PGP/GPG signed. See GitHub's signing guide.
  • DCO Sign-off: Every commit must carry a Signed-off-by line:
    git commit -s -S -m "your commit message"
    
  • GitHub Actions Policy: Workflows may only use actions that are (a) owned by owncloud, (b) created by GitHub (actions/*), or (c) verified in the GitHub Marketplace.

Security

Do not open a public GitHub issue for security vulnerabilities.

Report vulnerabilities at https://security.owncloud.com -- see SECURITY.md.

Bug bounty: YesWeHack ownCloud Program

License

This project is licensed under the MIT.

About the ownCloud OSPO

The Kiteworks Open Source Program Office, operating under the ownCloud brand, launched on May 5, 2026, to steward the open source ecosystem around ownCloud's products. The OSPO ensures transparent governance, license compliance, community health, and sustainable collaboration between the open source community and Kiteworks, which acquired ownCloud in 2023.

For questions about the OSPO or licensing, contact ospo@kiteworks.com.

License Migration to Apache 2.0

The OSPO is driving a strategic relicensing of ownCloud repositories toward the Apache License 2.0, following the Apache Software Foundation's third-party license policy.

Individual repositories will migrate as their audit is completed. The LICENSE file in each repo reflects its current license status (not the target).

Current license: MIT (Category A per Apache policy -- permissive, compatible with Apache-2.0).

Migration prerequisites for this repository:

  • CLA/DCO coverage: All past contributors must have signed agreements permitting relicensing
  • Header updates: All source file headers must be updated from MIT to Apache-2.0 notice
  • Dependency audit: Verify no incompatible transitive dependencies

About

Smashbox testing running on DroneCI

Topics

Resources

License

Code of conduct

Contributing

Security policy

Stars

2 stars

Watchers

18 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors