[
https://issues.jboss.org/browse/JBIDE-23367?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-23367 at 10/16/16 4:57 PM:
--------------------------------------------------------------
Performance baselines:
BEFORE changes above:
* building 4 TPs: ~45-65 mins ::
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
* building devstudio installers: >60 mins ::
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
* publishing CI to staging: 2h45
AFTER changes above:
* building TPs: 40-45 min
* building devstudio installers: 35-40 min
* publishing CI to staging: 40 min
was (Author: nickboldt):
Performance baselines:
BEFORE changes above:
* building 4 TPs: ~45-65 mins ::
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
* building devstudio installers: >60 mins ::
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
* publishing CI to staging: 2h45
AFTER changes above:
* building TPs: __
* building devstudio installers: __
* publishing CI to staging: 40 mins
use internal IP instead of external domain name to speed up
publishing
----------------------------------------------------------------------
Key: JBIDE-23367
URL:
https://issues.jboss.org/browse/JBIDE-23367
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.4.2.AM2
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.2.AM2
Recently found out that we can use the internal IP for the machine that actually contains
the data that sits on
download.jboss.org and
devstudio.redhat.com, which speeds up
publishing a CI build to stating by a factor of 3 -- from 2h45 down to 40 mins!
We should do the same for publishing CI jobs too.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)