February 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-3893) Refactor target platforms from jbdevstudio to devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3893?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3893: ----------------------------- Sprint: devex #116 June 2016, devex #128 February 2017 (was: devex #116 June 2016) > Refactor target platforms from jbdevstudio to devstudio > ------------------------------------------------------- > > Key: JBDS-3893 > URL: https://issues.jboss.org/browse/JBDS-3893 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: target-platform, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: LATER > > > In https://github.com/jbosstools/jbosstools-target-platforms/commits/4.60.x we should finally adopt consistent naming/branding for the devstudio target platforms, using devstudio instead of jbdevstudio. > Affected: publishing/staging/release scripts, jenkins jobs, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20177) migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20177?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20177: ------------------------------- Sprint: (was: devex #128 February 2017) > migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20177 > URL: https://issues.jboss.org/browse/JBIDE-20177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > If we can migrate this logic into the mojo... > {code} > if [[ ${skipRevisionCheckWhenPublishing} == "true" ]] || [[ $(. ${WORKSPACE}/sources/util/checkLatestPublishedSHA.sh -s ${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo -t http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...) == "true" ]]; then > {code} > ... we'll be able to remove this step in all jobs: > {code} > <hudson.tasks.Maven> > <targets>-U -e org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack</targets> > <mavenName>maven-3.2.5</mavenName> > <properties>artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Beta2-SNAPSHOT:zip > outputDirectory=${WORKSPACE}/sources > trimVersion=true > mdep.stripClassifier=true > mdep.stripVersion=true</properties> > <usePrivateRepository>false</usePrivateRepository> > <settings class="jenkins.mvn.DefaultSettingsProvider"/> > <globalSettings class="jenkins.mvn.DefaultGlobalSettingsProvider"/> > </hudson.tasks.Maven> > {code} > ... and instead, just pass in those vars to maven: > {code} > -DskipRevisionCheckWhenPublishing=${skipRevisionCheckWhenPublishing} > -DcheckLatestPublishedSHA_SOURCE_PATH=${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo > -DcheckLatestPublishedSHA_TARGET_PATH=http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-build-sites.aggregate.${projectName}-site_${jbosstools_site_stream}/latest/all/repo/ > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23678: ------------------------------- Sprint: devex #128 February 2017 > remediation required installing jbosstools 4.4.3.AM1 on Neon.2 > -------------------------------------------------------------- > > Key: JBIDE-23678 > URL: https://issues.jboss.org/browse/JBIDE-23678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM1 > > Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png > > > Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have newer versions of JSON/JSDT plugins in our target platform than are in Neon.2. > Install manifest contains: > * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions), > * 1.6.201 (2 versions), and > * 2.0.200 (1 version) - *total 7 references*! > Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23623: ------------------------------- Sprint: devex #127 February 2017, devex #128 February 2017 (was: devex #127 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.AM2 > > Attachments: jira.txt, prepare-am1.txt, 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)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23510) [devdoc] document sources in target platform zip & use of PDE Source Lookup feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23510?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23510: ------------------------------- Sprint: devex #127 February 2017, devex #128 February 2017 (was: devex #127 February 2017) > [devdoc] document sources in target platform zip & use of PDE Source Lookup feature > ----------------------------------------------------------------------------------- > > Key: JBIDE-23510 > URL: https://issues.jboss.org/browse/JBIDE-23510 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, devdoc, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM1 > > > So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to build a targetplatform with all the sources - done in JBIDE-23481. > [1] https://github.com/fbricon/pde.source.lookup/ > [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... > Once we have sources in the JBT targetplatform repo, need to update devdoc [2] and add instructions (also write a blog!) about how to install/use the PDE Source Lookup plugin > 1. install the PDE source lookup plugin > 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site > 3. for something you want sources, use the plugin and see if it can resolve sources -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23652: ------------------------------- Sprint: devex #127 February 2017, devex #128 February 2017 (was: devex #127 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.AM1 > > > 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)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3510) Include Buildship in jbosstools and devstudio OOTB

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3510?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3510: ----------------------------- Sprint: devex #128 February 2017 > Include Buildship in jbosstools and devstudio OOTB > -------------------------------------------------- > > Key: JBDS-3510 > URL: https://issues.jboss.org/browse/JBDS-3510 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: 3rd-party-certification, 3rd-party-dependencies, central-update > Affects Versions: 9.0.0.CR1, 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 11.0.0.AM1 > > > {quote} > support for Gradle via BuildShip project is set to be included in Eclipse Mars SR1. > Something we probably need to at least test/coexist with in near future. > /max{quote} > Info: > * https://gradle.org/eclipse/ > * https://projects.eclipse.org/projects/tools.buildship > Update sites: > * http://download.eclipse.org/buildship/updates/e45/releases > * http://download.eclipse.org/buildship/updates/e45/milestones/1.0 > * http://download.eclipse.org/buildship/updates/e45/snapshots/1.0 > (also should be in Mars.1 release [1] coming out in a few weeks) > [1] https://wiki.eclipse.org/Mars/Simultaneous_Release_Plan#Mars.1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23317) Create and use Oxygen.M5 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, devex #125 December 2016, devex #127 February 2017, devex #128 February 2017 (was: devex #120 September 2016, devex #125 December 2016, devex #127 February 2017) > Create and use Oxygen.M5 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.5.0.AM1 > > > Once available on Feb 02/2017, we should create a new 4.70.0.AM1-SNAPSHOT target platform containing Oxygen.0.M5 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 (v7.2.3#72005)

9 years, 1 month

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, devex #128 February 2017 (was: devex #119 August 2016, devex #120 September 2016, devex #121 October 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.x > > > 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)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20177) migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20177?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20177: ------------------------------- Sprint: devex #128 February 2017 > migrate skipRevisionCheckWhenPublishing and checkLatestPublishedSHA into jbosstools-releng-publish deploy mojo > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20177 > URL: https://issues.jboss.org/browse/JBIDE-20177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > If we can migrate this logic into the mojo... > {code} > if [[ ${skipRevisionCheckWhenPublishing} == "true" ]] || [[ $(. ${WORKSPACE}/sources/util/checkLatestPublishedSHA.sh -s ${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo -t http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...) == "true" ]]; then > {code} > ... we'll be able to remove this step in all jobs: > {code} > <hudson.tasks.Maven> > <targets>-U -e org.apache.maven.plugins:maven-dependency-plugin:2.9:unpack</targets> > <mavenName>maven-3.2.5</mavenName> > <properties>artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Beta2-SNAPSHOT:zip > outputDirectory=${WORKSPACE}/sources > trimVersion=true > mdep.stripClassifier=true > mdep.stripVersion=true</properties> > <usePrivateRepository>false</usePrivateRepository> > <settings class="jenkins.mvn.DefaultSettingsProvider"/> > <globalSettings class="jenkins.mvn.DefaultGlobalSettingsProvider"/> > </hudson.tasks.Maven> > {code} > ... and instead, just pass in those vars to maven: > {code} > -DskipRevisionCheckWhenPublishing=${skipRevisionCheckWhenPublishing} > -DcheckLatestPublishedSHA_SOURCE_PATH=${WORKSPACE}/sources/aggregate/${projectName}-site/target/fullSite/all/repo > -DcheckLatestPublishedSHA_TARGET_PATH=http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-build-sites.aggregate.${projectName}-site_${jbosstools_site_stream}/latest/all/repo/ > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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