[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master is a spam bomb
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23889:
-------------------------------
Fix Version/s: 4.4.4.AM1
(was: 4.4.3.Final)
> jbosstools-composite-install_master is a spam bomb
> --------------------------------------------------
>
> 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
>
>
> 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)
9 years, 1 month
[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master is a spam bomb
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23889:
-------------------------------
Affects Version/s: 4.4.3.AM2
(was: 4.4.4.AM1)
> jbosstools-composite-install_master is a spam bomb
> --------------------------------------------------
>
> 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
>
>
> 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)
9 years, 1 month
[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23708:
-------------------------------
Affects Version/s: 4.4.4.AM2
(was: 4.4.3.AM1)
> Pod Log: unable to get build log if build failed with error
> -----------------------------------------------------------
>
> Key: JBIDE-23708
> URL: https://issues.jboss.org/browse/JBIDE-23708
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Labels: logs, properties
> Fix For: 4.4.3.Final
>
> Attachments: cannot-get-logs-for-erroring-build.png, webconsole-logs-for-erroring-build.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a build that failed (ex. launch a nodejs build and shut down your vpn. The build will fail because it cannot connect to the registry)
> # EXEC: in Properties view: select "Builds" tab and choose your erroring build. Choose "Build Log..." in it's context menu
> Result:
> You're told that you cannot get the logs for an erroring build. You therefore cannot have insights on why your build failed:
> !cannot-get-logs-for-erroring-build.png!
> The webconsole allows you to inspect those logs:
> !webconsole-logs-for-erroring-build.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month