Disroot-Ansible/forgejo
12
1
Fork 0
Code Pull requests 1 Projects Releases 4 Activity

improve upgrade and update to 7.0.5 #49

Merged
meaz merged 6 commits from improve_upgrade into staging 2024-07-15 18:36:24 +02:00
Conversation 1 Commits 6 Files changed 3 +35 -26
meaz commented 2024-07-09 16:51:18 +02:00
Owner
Copy link

See Disroot/Disroot-Project#920

@muppeth I've just have a question about why you restart forgejo with:

- name: '[UPGRADE] - Restart forgejo'
  systemd:
    name: forgejo
    state: restarted
  when:
    - forgejo_is_installed.rc == 0
    - forgejo_health is defined and forgejo_health.rc is defined and forgejo_health.rc == 0

- name: '[UPGRADE] - Wait for forgejo to be back online'
  pause:
    seconds: 10
  when:
    - forgejo_is_installed.rc == 0
    - forgejo_health is defined and forgejo_health.rc is defined and forgejo_health.rc == 0

does forgejo need to be up to run forgejo manager flush-queues ? I'm asking coz we stop forgejo just after flush.

See https://git.disroot.org/Disroot/Disroot-Project/issues/920 @muppeth I've just have a question about why you restart forgejo with: ``` - name: '[UPGRADE] - Restart forgejo' systemd: name: forgejo state: restarted when: - forgejo_is_installed.rc == 0 - forgejo_health is defined and forgejo_health.rc is defined and forgejo_health.rc == 0 - name: '[UPGRADE] - Wait for forgejo to be back online' pause: seconds: 10 when: - forgejo_is_installed.rc == 0 - forgejo_health is defined and forgejo_health.rc is defined and forgejo_health.rc == 0 ``` does forgejo need to be up to run `forgejo manager flush-queues` ? I'm asking coz we stop forgejo just after flush.
muppeth was assigned by meaz 2024-07-09 16:51:18 +02:00
meaz added 6 commits 2024-07-09 16:51:19 +02:00 
- Upgrade to version 7.0.2
- Added extra check tasks to upgrade process

Reviewed-on: #45
Reviewed-by: meaz <meaz@no-reply@disroot.org>
Co-authored-by: muppeth <muppeth@disroot.org>
Co-committed-by: muppeth <muppeth@disroot.org>
Co-authored-by: meaz <meaz@disroot.org>
Reviewed-on: #47
Reviewed-by: meaz <meaz@no-reply@disroot.org>
Co-authored-by: muppeth <muppeth@disroot.org>
Co-committed-by: muppeth <muppeth@disroot.org>
meaz changed target branch from main to staging 2024-07-09 16:51:52 +02:00
meaz added 1 commit 2024-07-10 09:29:01 +02:00
meaz added 1 commit 2024-07-13 09:36:23 +02:00
meaz changed title from improve upgrade to improve upgrade and update to 7.0.5 2024-07-13 09:36:30 +02:00
muppeth commented 2024-07-15 15:27:29 +02:00
Owner
Copy link

Yes it needs to be up. Also needs to be restarted prior as otherwise it was giving me an error. I will look into it now to try and fix the process.

Yes it needs to be up. Also needs to be restarted prior as otherwise it was giving me an error. I will look into it now to try and fix the process.
muppeth approved these changes 2024-07-15 16:08:30 +02:00
muppeth left a comment
Owner
Copy link

Works fine on my test machine. We will see if it works on pulga.

Works fine on my test machine. We will see if it works on pulga.
meaz merged commit 4690ef208e into staging 2024-07-15 18:36:24 +02:00
meaz deleted branch improve_upgrade 2024-07-15 18:36:25 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
muppeth
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
muppeth
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Disroot-Ansible/forgejo#49
No description provided.
Delete branch "improve_upgrade"

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?