Skip to content

Actions: umts/jobapps

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
10 workflow runs
10 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Update Ruby to 3.2.5
ci #10: Pull request #657 opened by werebus
October 16, 2024 18:48 2m 22s werebus/ruby-32
October 16, 2024 18:48 2m 22s
Add actions setup (#656)
ci #9: Commit 178c723 pushed by werebus
October 16, 2024 18:34 2m 32s main
October 16, 2024 18:34 2m 32s
Add actions setup
ci #8: Pull request #656 synchronize by werebus
October 16, 2024 18:33 1m 13s werebus/actions
October 16, 2024 18:33 1m 13s
Add actions setup
ci #7: Pull request #656 synchronize by werebus
October 16, 2024 16:26 1m 13s werebus/actions
October 16, 2024 16:26 1m 13s
Add actions setup
ci #6: Pull request #656 opened by werebus
October 16, 2024 16:24 2m 32s werebus/actions
October 16, 2024 16:24 2m 32s
Eh, let's just stick to the setup script, I guess
ci #5: Commit e6a98ef pushed by werebus
October 16, 2024 16:16 1m 11s actions-test
October 16, 2024 16:16 1m 11s
Is it the cache key?
ci #4: Commit 1afc144 pushed by werebus
October 16, 2024 16:05 50s actions-test
October 16, 2024 16:05 50s
Do we need to specify the package manager?
ci #3: Commit 3db64c7 pushed by werebus
October 16, 2024 16:00 1m 8s actions-test
October 16, 2024 16:00 1m 8s
Skip setup script
ci #2: Commit d5e4c8f pushed by werebus
October 16, 2024 15:35 58s actions-test
October 16, 2024 15:35 58s
Add actions setup
ci #1: Commit 4e67aaa pushed by werebus
October 16, 2024 15:28 2m 24s actions-test
October 16, 2024 15:28 2m 24s