[jbosstools-issues] [JBoss JIRA] (JBIDE-20046) find lost patches and check that SHAs have been built before publishing to staging

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-20046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-20046:
-------------------------------
    Summary: find lost patches and check that SHAs have been built before publishing to staging  (was: create jiralint-like notifier that can alert if changes in a branch have not been built after X days)


> find lost patches and check that SHAs have been built before publishing to staging
> ----------------------------------------------------------------------------------
>
>                 Key: JBIDE-20046
>                 URL: https://issues.jboss.org/browse/JBIDE-20046
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.5.0.Final
>
>
> Suggested by [~rob.stryker] to avoid having situations where jobs are disabled because no one is maintaining the code & we end up with something like JBIDE-20041, where last year's Freemarker is included in JBT 4.3.0.Beta1 instead of the latest stuff.
> {quote}
> [10:36:50 AM] Rob Stryker: would it be possible to make a script that runs once a week checking for commits and firing emails indicating the jobs should be re-enabled?
> [10:37:50 AM] Rob Stryker: if job is enabled, dont even bother to check/notify
> [10:37:57 AM] Rob Stryker: if job is disabled, then check for new commits
> {quote}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)