github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-16 04:42:51 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Cron started to early ... #5669

New Issue
Closed
opened 2025-11-02 06:32:31 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 06:32:31 -06:00
Owner
Copy Link

Originally created by @somera on GitHub (Jul 1, 2020).

  • Gitea version (or commit ref): 1.12.1
  • Git version: 2.20.1
  • Operating system: Linux
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

In #12083 I got the answer, that I can use the cron configuration in Gitea.

This is set in the config to

; Update mirrors
[cron.update_mirrors]
SCHEDULE = 0 3 * * *

image

But as you can see, the you should start to early.

And after I canceld the running job gitea shows:

image

Screenshots

Originally created by @somera on GitHub (Jul 1, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.12.1 - Git version: 2.20.1 - Operating system: Linux - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant ## Description In #12083 I got the answer, that I can use the cron configuration in Gitea. This is set in the config to ``` ; Update mirrors [cron.update_mirrors] SCHEDULE = 0 3 * * * ``` ![image](https://user-images.githubusercontent.com/8334250/86262925-c9160580-bbc0-11ea-80e1-1b696f409f9b.png) But as you can see, the you should start to early. And after I canceld the running job gitea shows: ![image](https://user-images.githubusercontent.com/8334250/86263273-4772a780-bbc1-11ea-9fc4-90fe964dc843.png) ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror commented 2025-11-02 06:32:31 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Jul 12, 2020):

I'm closing it.

Got in #12083 the info how cron should be configured. Test will follow.

@somera commented on GitHub (Jul 12, 2020): I'm closing it. Got in #12083 the info how cron should be configured. Test will follow.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#5669
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?