[
https://issues.apache.org/jira/browse/BEAM-7384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174719#comment-17174719
]
Beam JIRA Bot commented on BEAM-7384:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Cleanup stale Jenkins jobs on UI
> --------------------------------
>
> Key: BEAM-7384
> URL: https://issues.apache.org/jira/browse/BEAM-7384
> Project: Beam
> Issue Type: Task
> Components: build-system
> Reporter: Mark Liu
> Priority: P2
> Labels: stale-P2
>
> Some Jenkins jobs are stale (in disable status) for a while due to many
> reasons (rename, one-time-testing, manually created). We can still see them
> on Jenkins UI (https://builds.apache.org/view/A-D/view/Beam/). Can anyone
> with permission make a cleanup?
> According to [Apache Jenkins
> doc|https://cwiki.apache.org/confluence/display/INFRA/Jenkins#Jenkins-HowdoIgetanaccount],
> only people in hudson-jobadmin group can have account and do such things,
> and seems Kenn (as a PMC member) is already in the group. [~kenn] Can you
> help on this. Or if you add me ([~markflyhigh]) to the group, I'm happy to do
> the cleanup.
> Few stale jobs that known to me:
> beam_PerformanceTests_Python
> beam_PerformanceTests_Python35
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
