[jbosstools-issues] [JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master sends lots of nag emails when something goes awry (as it should)

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13368441#comment-13368441 ] 

Nick Boldt edited comment on JBIDE-23889 at 2/23/17 1:50 PM:
-------------------------------------------------------------

 !composite.png|thumbnail! 

Yes, that's because this is the job that aggregates all the upstream changes from the jbosstools-* projects to determine if we need to rebuild the JBT and devstudio aggregates/products. 

It's supposed to run frequently. Or as frequently as it sees changes in github upstream repos. 

It will then keep trying again every 30 mins or so until someone notices and fixes the problem.


was (Author: nickboldt):
 !composite.png|thumbnail! 

Yes, that's because this is the job that aggregates all the upstream changes from the jbosstools-* projects to determine if we need to rebuild the JBT and devstudio aggregates/products. 

It's supposed to run frequently. Or as frequently as it sees changes in github upstream repos. 

> jbosstools-composite-install_master sends lots of nag emails when something goes awry (as it should)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-23889
>                 URL: https://issues.jboss.org/browse/JBIDE-23889
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.4.3.AM2
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>            Priority: Critical
>             Fix For: 4.4.4.AM1
>
>         Attachments: composite.png
>
>
> jbosstools-composite-install_master re-runs itself on failure. However, it seems like the SLEEP_TIME parameter is now ignored, resulting on constant re-run of the job and a lot of spam (multiple mails per minutes). Additionally to spam, this adds a relatively big load on Jenkins and slaves queue.
> I've removed the re-run on failure block of the downstream job trigger as a temporary workaround.



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