October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22581) Create and use Neon.1 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22581?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22581: ------------------------------- Sprint: devex #120 September 2016, devex #121 October 2016 (was: devex #120 September 2016, devex #122 October 2016) > Create and use Neon.1 target platform > ------------------------------------- > > Key: JBIDE-22581 > URL: https://issues.jboss.org/browse/JBIDE-22581 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.2.AM2 > > Attachments: jbosstools.p2diff.summary.txt, jbosstools.p2diff.txt, jbtcentral.p2diff.txt > > > Once available in late August or early September, we should move up to Neon.1. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > jbds tp, > central tp; > jbt-build-sites, > jbds site build; > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23017) use sshfs to speed up publishing process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23017?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23017: ------------------------------------ More perf tuning and I've got the CI -> staging job down to: {code} devstudio.product_master INT - 13m devstudio.product_master EXT - 35m (24 if copy from www.qa) core + coretests 41m (or 26 min each) bsim 30s ds central+ea 3m45 jbt central+ea 3m18 ds tp zips 2m30 {code} So the overall time to do a push is about 30-45min. Can't get it much faster, as when I moved to using a local upload from www.qa -> ds.rh.c, I started getting ssh timeouts & drops again. -- Only thing I can still try is to implement sshfs for copying files, either still using the tmpdir intermediate, or skipping that entirely. > use sshfs to speed up publishing process > ----------------------------------------- > > Key: JBIDE-23017 > URL: https://issues.jboss.org/browse/JBIDE-23017 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Currently, publishing from /snapshots to /staging and from /staging to /development requires that we fetch several GBs of data from filemgmt.jboss.org to a temp folder, then push those bits to a new folder on filemgmt.jboss.org. > If we could simply copy bits over sshfs, the process might be a lot faster than these times: > {code} > JBT coretests 1.1G: 59m20 > JBT core 1.2G: 64m23 > devstudio (copy from filemgmt to filemgmt) 2.4G: 2h13 > devstudio (copy from local to www.qa) 3.1G: 6mins(?) > {code} > To make this work, however, we need more slaves to have sshfs installed. Currently, it appears that only dev01 [1] is so equipped. And that slave, currently, has a build queue more than 170 jobs long, making it impractical to even TEST publishing over sshfs. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev01-rhel5-x86/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20034) Should repository-utils:generate-repository-facade generate files and then use additionalFileSets configuration?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20034?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20034: ------------------------------------ So, this is a fix for JBDS-4118 ? > Should repository-utils:generate-repository-facade generate files and then use additionalFileSets configuration? > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20034 > URL: https://issues.jboss.org/browse/JBIDE-20034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Denis Golovin > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.x > > > Explanation how to use is here https://bugs.eclipse.org/bugs/show_bug.cgi?id=424691. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20034) Should repository-utils:generate-repository-facade generate files and then use additionalFileSets configuration?

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20034?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-20034: --------------------------------------- This would improve performance. Instead of zipping p2 repo first and then add resources to it, which takes time, we would provide files for repository fasade before tycho packages p2 repository first time. > Should repository-utils:generate-repository-facade generate files and then use additionalFileSets configuration? > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20034 > URL: https://issues.jboss.org/browse/JBIDE-20034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Denis Golovin > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.x > > > Explanation how to use is here https://bugs.eclipse.org/bugs/show_bug.cgi?id=424691. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23367) use internal IP instead of external domain name to speed up publishing

by Nick Boldt (JIRA)

[ 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)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23017) use sshfs to speed up publishing process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23017?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23017: ------------------------------------ looks like sshfs is available on all these slaves: * dev01 * vmg100 - 132 So, a slave label could be: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/dev01-rhel5-x86%7C... > use sshfs to speed up publishing process > ----------------------------------------- > > Key: JBIDE-23017 > URL: https://issues.jboss.org/browse/JBIDE-23017 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Currently, publishing from /snapshots to /staging and from /staging to /development requires that we fetch several GBs of data from filemgmt.jboss.org to a temp folder, then push those bits to a new folder on filemgmt.jboss.org. > If we could simply copy bits over sshfs, the process might be a lot faster than these times: > {code} > JBT coretests 1.1G: 59m20 > JBT core 1.2G: 64m23 > devstudio (copy from filemgmt to filemgmt) 2.4G: 2h13 > devstudio (copy from local to www.qa) 3.1G: 6mins(?) > {code} > To make this work, however, we need more slaves to have sshfs installed. Currently, it appears that only dev01 [1] is so equipped. And that slave, currently, has a build queue more than 170 jobs long, making it impractical to even TEST publishing over sshfs. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev01-rhel5-x86/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23367) use internal IP instead of external domain name to speed up publishing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23367?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23367: ------------------------------------ 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)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18848) setup tests for ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18848?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18848: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.x) > setup tests for ide-config.properties > ------------------------------------- > > Key: JBIDE-18848 > URL: https://issues.jboss.org/browse/JBIDE-18848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.4.2.AM3 > > > JBIDE-18837 and other jiras showed that ide-config.properties risk having errors introduced into it. > we should have a test that runs every day to check if it is still consistent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18848) setup tests for ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18848?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18848: ---------------------------------- Assignee: Nick Boldt (was: Fred Bricon) > setup tests for ide-config.properties > ------------------------------------- > > Key: JBIDE-18848 > URL: https://issues.jboss.org/browse/JBIDE-18848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > JBIDE-18837 and other jiras showed that ide-config.properties risk having errors introduced into it. > we should have a test that runs every day to check if it is still consistent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18848) setup tests for ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18848?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18848: ------------------------------- Sprint: devex #122 October 2016 > setup tests for ide-config.properties > ------------------------------------- > > Key: JBIDE-18848 > URL: https://issues.jboss.org/browse/JBIDE-18848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.4.2.AM3 > > > JBIDE-18837 and other jiras showed that ide-config.properties risk having errors introduced into it. > we should have a test that runs every day to check if it is still consistent. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2016