April 2017 - jbosstools-issues - Jboss List Archives

[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, devex #131 April 2017 (was: devex #116 June 2016, devex #128 February 2017) > 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

1
0
0 / 0

[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, devex #131 April 2017 (was: devex #119 August 2016, devex #120 September 2016, devex #121 October 2016, devex #128 February 2017, devex #129 March 2017) > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23623: ------------------------------- Sprint: devex #127 February 2017, devex #128 February 2017, devex #131 April 2017 (was: devex #127 February 2017, devex #128 February 2017) > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > Attachments: jira.txt, prepare-am1.txt, run.04262017.log, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23652) coretests composite site not updated when publishing to /static and /stable

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23652: ------------------------------- Sprint: devex #127 February 2017, devex #128 February 2017, devex #131 April 2017 (was: devex #127 February 2017, devex #128 February 2017) > coretests composite site not updated when publishing to /static and /stable > --------------------------------------------------------------------------- > > Key: JBIDE-23652 > URL: https://issues.jboss.org/browse/JBIDE-23652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 4.4.4.Final > > > Realized the other day that the composite*.xml files in http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ and http://download.jboss.org/jbosstools/neon/stable/updates/coretests/ were not updated after 4.4.0.Alpha1... and probably should be part of what's updated when we release to /development, /stable, /static, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23322: ------------------------------- Sprint: devex #128 February 2017, devex #131 April 2017 (was: devex #128 February 2017) > create mojo that takes as input a list of URLs and a name, and generates a composite site > ----------------------------------------------------------------------------------------- > > Key: JBIDE-23322 > URL: https://issues.jboss.org/browse/JBIDE-23322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > > In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 1 or more URLs. > So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files: > {code} > target/composite/compositeContent.xml > target/composite/compositeArtifacts.xml > target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index ) > {code} > Secondary use case would be to generate a composite site from subfolders in an existing folder, eg., to replace https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > So we could use this to create composite sites in folders like: > * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (invalid composite points to ../, which has no composite either) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/integrati... (no composite) > * http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ (up to date) > * http://download.jboss.org/jbosstools/static/neon/development/updates/core/ (invalid composite points to ../, which has no composite either) > * http://download.jboss.org/jbosstools/static/neon/development/updates/cent... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/earl... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/inte... (no composite) > * http://download.jboss.org/jbosstools/static/neon/development/updates/core... (composite out of date) > But also to point to remote (/stable/) URLs from pointer sites, like: > * http://download.jboss.org/jbosstools/neon/stable/updates/compositeArtifac... (up to date, name = JBoss Tools - Core + Central Update Site) > * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (composite missing) > * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (composite missing) > * http://download.jboss.org/jbosstools/neon/stable/updates/coretests/compos... (up to date, name = JBoss Tools 4.4.2.Final Stable Release Tests Site) > * http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests (404'd) > * http://download.jboss.org/jbosstools/neon/development/updates/compositeAr... (up to date, name = JBoss Tools - Core + Central Update Site) > * http://download.jboss.org/jbosstools/neon/development/updates/central/ (composite missing) > * http://download.jboss.org/jbosstools/neon/development/updates/earlyaccess/ (composite missing) > * http://download.jboss.org/jbosstools/neon/development/updates/coretests/c... (out of date, points to 4.4.0.Alpha1) > * http://download.jboss.org/jbosstools/neon/development/updates/integration... (404'd) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23963) Create and use Neon.3 target platform

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23963?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23963: ------------------------------- Sprint: devex #128 February 2017, devex #131 April 2017 (was: devex #128 February 2017) > Create and use Neon.3 target platform > ------------------------------------- > > Key: JBIDE-23963 > URL: https://issues.jboss.org/browse/JBIDE-23963 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: target-platform > Affects Versions: 4.4.4.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.4.Final > > Attachments: Screenshot_2017-03-24_11-10-30.png > > > Once available in March, we should move up to Neon.3 > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > jbt tp, > devstudio tp, > central tp; > jbt-build-sites (and parent pom), > devstudio site build (and devstudio root pom); > update install/matrix jobs to use new Eclipse JEE/platform binary; > mailing list announcements -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24182) wrap staging/release process with pipeline job

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24182?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24182: ------------------------------- Sprint: devex #131 April 2017 > wrap staging/release process with pipeline job > ---------------------------------------------- > > Key: JBIDE-24182 > URL: https://issues.jboss.org/browse/JBIDE-24182 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > In JBIDE-22819 I created a buildflow job to orchestrate the steps involved in staging or release of jbt/ds. > However, on CCI we can now write a pipeline job [1] in groovy, which can trigger downstream builds [2] and wait for approval/input [3] before continuing. This might be an ever better visualization & control for these stages/releases. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/vscode-j... -> https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile > [2] https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job > [3] https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile#L68 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24310) Add tycho.m2e 0.8.1 to Central

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24310?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24310: ------------------------------- Sprint: devex #131 April 2017 > Add tycho.m2e 0.8.1 to Central > ------------------------------ > > Key: JBIDE-24310 > URL: https://issues.jboss.org/browse/JBIDE-24310 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.4.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > > So that we can easily provide tycho.m2e 0.8.1 [1] to jbosstools and devstudio users, we should add it to the JBT/devstudio TPs, and make it available from Red Hat Central as a new connector. > [1] http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho... > This would also allow the Fuse tooling to depend on it from jbt/ds rather than it being downstream. > cc: [~jeffmaury] [~fbricon] [~aurelien.pupier] [~lhein] [~pleacu] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24320) Synchronize jbosstools-4.4.x and master

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24320?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24320: ------------------------------- Sprint: devex #131 April 2017 > Synchronize jbosstools-4.4.x and master > ---------------------------------------- > > Key: JBIDE-24320 > URL: https://issues.jboss.org/browse/JBIDE-24320 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.4.AM3 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.4.4.Final > > > Make sure jbosstools-4.4.x and master are properly synchronized before 10.4.0.GA. > At least we should have all relevant commits from master cherry-picked to jbosstools-4.4.x -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[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: devex #131 April 2017 > 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

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 April 2017