[13.0][ADD] queue_job: innocuous test job for debugging/monitoring purposes#265
Merged
OCA-git-bot merged 1 commit intoOCA:13.0from Oct 27, 2020
Merged
Conversation
Contributor
|
Hi @guewen, |
guewen
approved these changes
Oct 22, 2020
Member
guewen
left a comment
There was a problem hiding this comment.
Hey that's great! I wanted to add a kind of way to create test jobs easily, and didn't think about using a simple controller endpoint. ❤️
guewen
reviewed
Oct 22, 2020
f65c3fb to
2cdd75e
Compare
simahawk
approved these changes
Oct 27, 2020
Member
|
/ocabot merge patch |
Contributor
|
Hey, thanks for contributing! Proceeding to merge this for you. |
Contributor
|
Congratulations, your PR was merged at 3365bff. Thanks a lot for contributing to OCA. ❤️ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The goal of this PR is to introduce an easy and innocuous way to confirm that jobs are running fine in a production environment, by triggering the creation of a test job through an http route.
Of course, only accessible to admin users to avoid any abuse :)