Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions systemd/openqa-trigger-from-obs-update.service
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,3 @@ After=network-online.target
Type=oneshot
ExecStart=/usr/bin/git -C /opt/openqa-trigger-from-obs pull --quiet --rebase origin master
User=geekotest

[Install]
WantedBy=default.target
Copy link
Contributor

@Martchus Martchus Jul 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This means one can no longer enable this unit normally, e.g. to run the triggering just once after boot. I guess this makes sense for this timer-triggered unit. We also don't have this for other timer-triggered units in openQA.

2 changes: 1 addition & 1 deletion systemd/openqa-trigger-from-obs-update.timer
Original file line number Diff line number Diff line change
Expand Up @@ -6,4 +6,4 @@ OnCalendar=*:0/3
Unit=openqa-trigger-from-obs-update.service

[Install]
WantedBy=default.target
WantedBy=timers.target
Copy link
Contributor

@Martchus Martchus Jul 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sense according to https://man.archlinux.org/man/systemd.special.7. We also use this in other timer-triggered units in openQA.