[
https://issues.apache.org/jira/browse/BEAM-13666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentyn Tymofieiev updated BEAM-13666:
---------------------------------------
Description:
When we take a jenkins node offline and then back online, sometimes an
inventory job can get stuck, and we need to unblock it manually.
Ideally, Jenkins should cancel the stuck jobs. There is some mechanism where we
can cancel Jenkins Jobs for PRs that had new commits. Perhaps it can be reused
here.
Context: https://lists.apache.org/thread/5pzj6pycw1lo15v66p7c2gzy4xh44bjx
was:
When we take a jenkins node offline and then back online, sometimes an
inventory job can get stuck, and we need to unblock it manually.
Ideally, Jenkins should cancel the stuck jobs. There is some mechanism where we
can cancel Jenkins Jobs for PRs that had new commits. Perhaps it can be reused
here.
Context: https://lists.apache.org/thread/87kjxw384c2pdh953vojsc10jzfs2rzf
> Stuck inventory jobs should be cancelled and rescheduled for next run
> ---------------------------------------------------------------------
>
> Key: BEAM-13666
> URL: https://issues.apache.org/jira/browse/BEAM-13666
> Project: Beam
> Issue Type: Improvement
> Components: testing
> Reporter: Valentyn Tymofieiev
> Priority: P2
>
> When we take a jenkins node offline and then back online, sometimes an
> inventory job can get stuck, and we need to unblock it manually.
> Ideally, Jenkins should cancel the stuck jobs. There is some mechanism where
> we can cancel Jenkins Jobs for PRs that had new commits. Perhaps it can be
> reused here.
> Context: https://lists.apache.org/thread/5pzj6pycw1lo15v66p7c2gzy4xh44bjx
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
