We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The idea is to solve the egg-chicken issue when somebody want to add a feature/fix in a component, and activate the test.
@branch(ruby="add-remote-config-or-whatever")
@branch
@released
@bug
It will be used on distant repos, and totally ignored in nightly runs.
The text was updated successfully, but these errors were encountered:
and unfortunately, it solves nothing, as we need to do a Pr on system tests after distant PR is merged :(
Sorry, something went wrong.
Implem idea :
/binaries/repo-name
it'll saves any requirements from weblog container
won't do, in favor of #913 : it's too complicated, solving nothing.
#913 offer a gentle way to declare some arbitraries test to run.
A PR on system tests remain mandatories, version declarations remains the main way to activate tests.
No branches or pull requests
The idea is to solve the egg-chicken issue when somebody want to add a feature/fix in a component, and activate the test.
@branch(ruby="add-remote-config-or-whatever")
@branch
declaration, any@released
,@bug
declaration are ignored, and the test is executedIt will be used on distant repos, and totally ignored in nightly runs.
The text was updated successfully, but these errors were encountered: