semaphore icon indicating copy to clipboard operation
semaphore copied to clipboard

Problem: Setting task template to run on new commits never automatically runs

Open Lysticity opened this issue 1 year ago • 3 comments

Issue

When a new task template is created and configured to run on new commit to a specific repo, the scheduled task that gets created in the database is defaulting to "active": false causing the task to never be run automatically. There seems to be no switch in the UI to enable or disable task templates that run on new commits, only for scheduled tasks.

Impact

Service (scheduled tasks, alerts)

Installation method

Docker

Database

BoltDB

Browser

Chrome

Semaphore Version

v2.10.22

Ansible Version

No response

Logs & errors

No response

Manual installation - system information

No response

Configuration

No response

Additional information

No response

Lysticity avatar Aug 07 '24 22:08 Lysticity

As a workaround you can do this by hand: In the Semaphore database (PostgreSQL here):

update project__schedule set active=true where id=X;

and restart Semaphore service.

lwandrebeck avatar Aug 08 '24 09:08 lwandrebeck

I'm having the same issue, setting active to true in the database does seem to help.

m-vandeneede avatar Aug 14 '24 09:08 m-vandeneede

Is there an older version where this isn't the issue? I'm having the same problem. Set up repo, just activated to run on commit. Nothing happens.

shackofnoreturn avatar Aug 24 '24 07:08 shackofnoreturn

I as well. Would be very nice if it worked...

omarkb93 avatar Dec 05 '24 02:12 omarkb93

I as well. Would be very nice if it worked...

Not sure what happened. I guess a new version (my compose file uses ":latest" for the version). But I can't help but to notice my task templates were running when I published a commit!

I did not not disable the option "I want to run a task by the cron only for new commits of some repository" when it did not work. Because I simply forgot.

My repository is configured using the ssh method looking at the main branch. And when tinkering with it back in the day I set up a GitHub access key as well. When all didn't work I simply left it as is.

Maybe you could try again as well.

Current version now is v2.10.35-a71a3c5-1730103926

shackofnoreturn avatar Dec 10 '24 21:12 shackofnoreturn