[JBoss JIRA] (JBIDE-23017) use sshfs to speed up publishing process
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23017?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23017:
-------------------------------
Sprint: devex #119 August 2016, devex #120 September 2016, devex #121 October 2016, devex #128 February 2017, devex #129 March 2017 (was: devex #119 August 2016, devex #120 September 2016, devex #121 October 2016, devex #128 February 2017, devex #129 March 2017, devex #131 May 2017 (JBIDE))
> 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
> Labels: releasework
> Fix For: 4.4.4.Final
>
> Attachments: staging-times.png
>
>
> 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
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-19715) Get rid of "fullSite", stick with "repository"
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19715?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-19715:
-------------------------------
Sprint: devex #116 June 2016, devex #128 February 2017 (was: devex #116 June 2016, devex #128 February 2017, devex #131 May 2017 (JBIDE))
> Get rid of "fullSite", stick with "repository"
> ----------------------------------------------
>
> Key: JBIDE-19715
> URL: https://issues.jboss.org/browse/JBIDE-19715
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.5.0.AM1
>
>
> Currently, some builds such as aggregate create a "site/target/fullSite" folder, which is aimed at being deployed. However, it would be simpler to populate the site/target/repository folder, so it would be only one directory to move, and the same one for all builds.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24121) Update versionwatch for devstudio 11 - document/update known multiples & report upstream problems to Eclipse CVS, Help, WST
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24121?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24121:
-------------------------------
Sprint: (was: devex #131 May 2017 (JBIDE))
> Update versionwatch for devstudio 11 - document/update known multiples & report upstream problems to Eclipse CVS, Help, WST
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24121
> URL: https://issues.jboss.org/browse/JBIDE-24121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa, versionwatch
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.AM1
>
> Attachments: Screenshot_2017-03-21_12-37-07.png, version-decreased.png
>
>
> {code}
> Version Watch - Summary Report: devstudio-11.0.0.AM1
> Multiple version issues
> Feature Problem Reference Version(s)
> Plugin Problem Reference Version(s)
> org.slf4j.api Multiple versions of same bundle found! 1.7.2.v20121108-1250 1.7.10.v20160921-1923
> org.apache.httpcomponents.httpcore Multiple versions of same bundle found! 4.3.3.v201411290715 4.4.4.v20161115-1643
> org.apache.httpcomponents.httpclient Multiple versions of same bundle found! 4.3.6.v201511171540 4.5.2.v20161115-1643
> Ignored (known issue)
> org.apache.lucene.core Multiple versions of bundle are expected and ignored - {3.5.0,5.4.1} 3.5.0.v20120725-1805 6.1.0.v20161115-1612
> javax.wsdl Multiple versions of bundle are expected and ignored - {1.5.1,1.6.2} 1.5.1.v201012040544 1.6.2.v201012040545
> com.jcraft.jsch Multiple versions of bundle are expected and ignored - {0.1.50,0.1.51} 0.1.53.v201508180515 0.1.54.v20170116-1932
> org.eclipse.jdt.annotation Multiple versions of bundle are expected and ignored - {1.1.0,2.1.0} 1.1.100.v20160418-1457 2.1.0.v20170119-1701
> org.objectweb.asm Multiple versions of bundle are expected and ignored - {4.0.0,5.0.1} 4.0.0.v201302062210 5.0.1.v201404251740
> org.apache.commons.logging Multiple versions of bundle are expected and ignored - {1.0.4,1.1.1} 1.0.4.v201101211617 1.1.1.v201101211721
> com.google.guava Multiple versions of bundle are expected and ignored - 13.0.0,15.0.0 15.0.0.v201403281430 18.0.0.v20161115-1643
> Version decreased issues
> Feature Problem Reference Version(s)
> org.eclipse.cvs Version 1.4.300.v20170126-1030 must be higher than 1.4.301.v20161124-1400 1.4.301.v20161124-1400
> org.eclipse.help Version 2.2.0.v20170126-1030 must be higher than 2.2.1.v20161124-1400 2.2.1.v20161124-1400
> Plugin Problem Reference Version(s)
> org.eclipse.cvs Version 1.4.300.v20170126-1030 must be higher than 1.4.301.v20161124-1400 1.4.301.v20161124-1400
> org.eclipse.wst.server.ui Version 1.5.306.v201610202117 must be higher than 1.5.307.v201611072017 1.5.307.v201611072017
>
> 7 issues found.{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4362:
-----------------------------
Sprint: devex #131 April 2017
> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
> Attachments: devstudio-install-add-servers-01.png, devstudio-install-add-servers-02.png, devstudio-install-add-servers-03.png, devstudio-install-add-servers-04.png, devstudio-install-add-servers-05.png
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4362:
-----------------------------
Sprint: (was: devex #131 May 2017 (JBIDE))
> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
> Attachments: devstudio-install-add-servers-01.png, devstudio-install-add-servers-02.png, devstudio-install-add-servers-03.png, devstudio-install-add-servers-04.png, devstudio-install-add-servers-05.png
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months