October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19933: ------------------------------------ Slip to 4.4.2.Final so I do this in prep for the 4.4.2.x branch > Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it > --------------------------------------------------------------------------------------- > > Key: JBIDE-19933 > URL: https://issues.jboss.org/browse/JBIDE-19933 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master). > Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch. > It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point. > For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22819) wrap staging build process with a jenkins job

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22819?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22819: ------------------------------- Sprint: devex #118 July 2016, devex #119 August 2016, devex #121 October 2016 (was: devex #118 July 2016, devex #119 August 2016, devex #121 September 2016) > wrap staging build process with a jenkins job > --------------------------------------------- > > Key: JBIDE-22819 > URL: https://issues.jboss.org/browse/JBIDE-22819 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > Job requires about 13 params: > {code} > version (JBT and JBDS) > versionWithRespin (JBT and JBDS) > versionWithRespin_PREV (JBT and JBDS) > target platforms (min, max, central) > respin # (- or a, b, c) > devsuite installerExe url > stream_JBT=master # or 4.4.neon > stream_DS=master # or 10.0.neon > {code} > See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... for the steps to convert into a job -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20904) automate publishing latest CI build to staging, then from staging to development (or stable)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20904: ------------------------------- Sprint: devex #115 May 2016, devex #116 June 2016, devex #118 July 2016, devex #119 August 2016, devex #121 October 2016 (was: devex #115 May 2016, devex #116 June 2016, devex #118 July 2016, devex #119 August 2016, devex #121 September 2016) > automate publishing latest CI build to staging, then from staging to development (or stable) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-20904 > URL: https://issues.jboss.org/browse/JBIDE-20904 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > Suggestion: > rather than opening 10 bash terminals to perform the copy-from-one-place-on-disk-to-local, copy-from-local-to-another-place steps required to clone CI bits to Stage or from Stage to release, [~mickael_istria] and I discovered today that we could use `wait` or `parallel` to orchestrate these steps via a bash script so they run in parallel (as quickly as possible), but still return feedback when all parallel steps are completed. > So, where today we run these steps sorta-by-hand (copy script into a console and wait until it's done) [1], in future we could simply kick a job and wait for the job to notify its completion. > [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... > Examples of using a series of commands in parallel w/ a wait at the end: > http://stackoverflow.com/questions/19543139/bash-script-processing-comman... > {code:title=spawns the 3 parallel steps, waits until #3 is done (2 seconds later) and returns the PID of the last one + its return code} > echo "1" & echo 2 & (sleep 2;echo 3) & wait && echo $! $# > {code} > More discussion: > {quote} > [12:44:46 PM] Mickael Istria: I believe some parts would have to be turned into functions > [12:54:41 PM] Mickael Istria: so, to hack the script, it could be just: > * add && after the 1st rsync in each loop > * add & after the last one > * put a wait after the last loop > * give the big piece of code to procede directly to bash > {quote} > After this job is done, releng would still have to "wire up" the new bits by updating composite*.xml and index.html pages, but that's considerably easier to do locally in a terminal, or even to script too. Rather than updating these files w/ sed, we could generate them from a template. > And if we don't care about committing those changes back to github, we could even push them to the dl.jb.o and ds.jb.c servers directly as part of the above job. > Scary, but much faster! -- 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 updated JBIDE-23017: ------------------------------- Sprint: devex #119 August 2016, devex #120 September 2016, devex #121 October 2016 (was: devex #119 August 2016, devex #120 September 2016, devex #121 September 2016) > 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-23317) Create and use Oxygen.M4 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23317?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23317: ------------------------------- Sprint: devex #120 September 2016 (was: devex #120 September 2016, devex #122 October 2016) > Create and use Oxygen.M4 target platform > ---------------------------------------- > > Key: JBIDE-23317 > URL: https://issues.jboss.org/browse/JBIDE-23317 > 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.3.AM1, 4.5.0.AM1 > > > Once available on Dec 14/15, we should create a new 4.70.0.AM1-SNAPSHOT target platform containing Oxygen.0.M4 bits. > https://wiki.eclipse.org/index.php?title=Oxygen/Simultaneous_Release_Plan... > 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-20901) JBDS update site builds produces update site zip TWICE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20901?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20901: ------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.x) > JBDS update site builds produces update site zip TWICE > ------------------------------------------------------ > > Key: JBIDE-20901 > URL: https://issues.jboss.org/browse/JBIDE-20901 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > > JBDS build creates the update site zip TWICE: > {code} > [INFO] --- tycho-p2-repository-plugin:0.23.1:archive-repository (default-archive-repository) @ com.jboss.devstudio.core.site --- > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > [INFO] > [INFO] --- repository-utils:0.23.1:generate-repository-facade (generate-facade) @ com.jboss.devstudio.core.site --- > [WARNING] No /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/repository/web/site.css found; using default. > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4118) JBDS update site builds produces update site zip TWICE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4118?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4118: ----------------------------- Project: Red Hat JBoss Developer Studio (devstudio) (was: Tools (JBoss Tools)) Key: JBDS-4118 (was: JBIDE-20901) Docs QE Status: NEW Component/s: build updatesite (was: build) (was: updatesite) Affects Version/s: 10.2.0.AM2 (was: 4.4.0.Alpha1) Fix Version/s: 10.2.0.AM3 (was: 4.4.2.AM3) > JBDS update site builds produces update site zip TWICE > ------------------------------------------------------ > > Key: JBDS-4118 > URL: https://issues.jboss.org/browse/JBDS-4118 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > > JBDS build creates the update site zip TWICE: > {code} > [INFO] --- tycho-p2-repository-plugin:0.23.1:archive-repository (default-archive-repository) @ com.jboss.devstudio.core.site --- > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > [INFO] > [INFO] --- repository-utils:0.23.1:generate-repository-facade (generate-facade) @ com.jboss.devstudio.core.site --- > [WARNING] No /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/repository/web/site.css found; using default. > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20901) JBDS update site builds produces update site zip TWICE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20901?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-20901 at 10/16/16 3:38 PM: -------------------------------------------------------------- Building devstudio takes over 60 mins in jenkins. But most of that is publishing time. So, a better fix for slow building would be in JBIDE-23367. was (Author: nickboldt): Building devstudio takes between 30 and 60 mins in jenkins. But most of that is publishing time. So, a better fix for slow building would be in JBIDE-23367. > JBDS update site builds produces update site zip TWICE > ------------------------------------------------------ > > Key: JBIDE-20901 > URL: https://issues.jboss.org/browse/JBIDE-20901 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > JBDS build creates the update site zip TWICE: > {code} > [INFO] --- tycho-p2-repository-plugin:0.23.1:archive-repository (default-archive-repository) @ com.jboss.devstudio.core.site --- > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > [INFO] > [INFO] --- repository-utils:0.23.1:generate-repository-facade (generate-facade) @ com.jboss.devstudio.core.site --- > [WARNING] No /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/repository/web/site.css found; using default. > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > {code} -- 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: ------------------------------------ s/filemgmt.jboss.org/10.5.105.197/g when deploying > 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-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: ------------------------------------ s/filemgmt.jboss.org/10.5.105.197/g when deploying devstudio > 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

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