October 2016 - jbosstools-issues - Jboss List Archives

[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 publishing aggregate sites > 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: ------------------------------------ update jobs to s/filemgmt.jboss.org/10.5.105.197/g > 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 updated JBIDE-23367: ------------------------------- Fix Version/s: 4.4.2.AM2 > 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 > 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 reassigned JBIDE-23367: ---------------------------------- Assignee: Nick Boldt > 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-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 commented on JBIDE-20901: ------------------------------------ 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)

Nick Boldt created JBIDE-23367: ---------------------------------- Summary: 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 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-18067) Consider using Naginator Jenkins plugin to retry builds that fail due to transient issues

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18067?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-18067. ------------------------------ Fix Version/s: 4.4.1.Final (was: 4.4.x) Resolution: Done We're using this for transient failures (eg., in install grinder tests). Closing. > Consider using Naginator Jenkins plugin to retry builds that fail due to transient issues > ----------------------------------------------------------------------------------------- > > Key: JBIDE-18067 > URL: https://issues.jboss.org/browse/JBIDE-18067 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.1.Final > > Attachments: naginator-retry-failed-builds.png > > > The Naginator plugin [1] is now available in the JBoss Jenkins. > [1] https://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin > How should we use it? Hourly retries? Progressive retries? Regex-based retries (eg., for github or nexus failures) ? > Here's one option: up to 3 hourly retries: > !naginator-retry-failed-builds.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3518) Eclipse-cs update to 6.9 or 6.14 on Red Hat Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3518?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3518: ----------------------------- Fix Version/s: LATER (was: 10.x) > Eclipse-cs update to 6.9 or 6.14 on Red Hat Central > --------------------------------------------------- > > Key: JBDS-3518 > URL: https://issues.jboss.org/browse/JBDS-3518 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: 3rd-party-certification, build, central-update > Affects Versions: 9.0.0.CR1 > Reporter: Jiri Peterka > Assignee: Nick Boldt > Priority: Optional > Fix For: LATER > > Attachments: checkstyle.png > > > I've checked Release 6.9.0 with JBDS 9.0.0.CR1 and experienced no issues. > Changes since last version: http://eclipse-cs.sourceforge.net/#!/releasenotes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) move to tycho 0.27.0 (mvn clean verify checks old features versions against baseline)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23212: ------------------------------- Labels: build tycho (was: build tycho,) > move to tycho 0.27.0 (mvn clean verify checks old features versions against baseline) > ------------------------------------------------------------------------------------- > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho > Fix For: 4.4.3.AM1, 4.5.0.AM1 > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) move to tycho 0.27.0 (mvn clean verify checks old features versions against baseline)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23212: ------------------------------- Summary: move to tycho 0.27.0 (mvn clean verify checks old features versions against baseline) (was: when using mvn clean verify, baseline check tries to use old version of IUs in testing feature baselines) > move to tycho 0.27.0 (mvn clean verify checks old features versions against baseline) > ------------------------------------------------------------------------------------- > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho > Fix For: 4.4.3.AM1, 4.5.0.AM1 > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- 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