forked from nextcloud/server
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
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
[backport 27]Multiple cron background jobs based on class - Patch - maybe need a new for nc28 #256
Open
sgyuris
wants to merge
1
commit into
stable27
Choose a base branch
from
backport/27/nmc/allow-calling-cron-background-jobs-by-class
base: stable27
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[backport 27]Multiple cron background jobs based on class - Patch - maybe need a new for nc28 #256
sgyuris
wants to merge
1
commit into
stable27
from
backport/27/nmc/allow-calling-cron-background-jobs-by-class
Conversation
This file contains 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
sgyuris
added
custom
MagentaCLOUD customisation
build-ready
Customization to include into build
labels
Feb 14, 2024
github-actions bot
pushed a commit
that referenced
this pull request
Feb 14, 2024
…- Patch - maybe need a new for nc28
github-actions bot
pushed a commit
that referenced
this pull request
Feb 15, 2024
…- Patch - maybe need a new for nc28
github-actions bot
pushed a commit
that referenced
this pull request
Feb 22, 2024
…- Patch - maybe need a new for nc28
github-actions bot
pushed a commit
that referenced
this pull request
Mar 1, 2024
…- Patch - maybe need a new for nc28
github-actions bot
pushed a commit
that referenced
this pull request
Mar 5, 2024
…- Patch - maybe need a new for nc28
github-actions bot
pushed a commit
that referenced
this pull request
Mar 8, 2024
…- Patch - maybe need a new for nc28
github-actions bot
pushed a commit
that referenced
this pull request
Mar 8, 2024
…- Patch - maybe need a new for nc28
github-actions bot
pushed a commit
that referenced
this pull request
Mar 11, 2024
…- Patch - maybe need a new for nc28
github-actions bot
pushed a commit
that referenced
this pull request
Mar 28, 2024
…- Patch - maybe need a new for nc28
github-actions bot
pushed a commit
that referenced
this pull request
Apr 8, 2024
…- Patch - maybe need a new for nc28
github-actions bot
pushed a commit
that referenced
this pull request
Apr 25, 2024
…- Patch - maybe need a new for nc28
github-actions bot
pushed a commit
that referenced
this pull request
May 31, 2024
…- Patch - maybe need a new for nc28
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
…[email protected]>
Summary
Hi,
As discussed in the call earlier this week, I prepared an adjusted version of the patch to run a background job just for a specific class.
This is slightly different from the upstream PR to only include minimal changes as they used to be on your nextcloud 25 deployment. I’ll try to push finishing the actual upstream change forward for the 29 branch, but would recommend to stick to the simple patch variant for now.
I was not sure if I should just push it to the branch in #245, so for now only attached as a single commit patch file.
Let me know if you have any questions.
Best regards,
Julius