January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21392) Composite install job is disabled and also component jobs are disabled therefore there is no nightly build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21392?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21392: ------------------------------------ To Max's point about being surprised that jobs get disabled, it's all part of the staging for QE process so that we don't accidentally overwrite a stage-in-progress: https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... But that said, I should probably add a note to the RELEASE docs [1], [2] to ensure that we re-enable them (as appropriate) once a release is complete. [1] https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... [2] https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... Problem arises that the release guide ends when the email templates have been sent to the project manager for the "... is available!" email announcements. So I would still need to remember to go back into the guide AFTER all my stuff is done and after all Alexey/Chris/Len/PaulRobinson's stuff is done. Almost need a post-release-prep-for-next-milestone guide, or even better... ... to generate a task jira as part of the staging/release process to remind me to not only re-enable jobs, but to set the correct github branches & other job parameters too: JBIDE-21407. > Composite install job is disabled and also component jobs are disabled therefore there is no nightly build > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21392 > URL: https://issues.jboss.org/browse/JBIDE-21392 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Beta2 > > > Job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... is marked as disabled and also component jobs such as http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_... and others are disabled. There was no build since 2015-12-16. Maybe it was disabled as a consequence/side effect of JBIDE-21145. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21407) staging/release guides should generate task jiras to remind releng to re-enable disabled jobs once staging or release is done

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21407: ---------------------------------- Summary: staging/release guides should generate task jiras to remind releng to re-enable disabled jobs once staging or release is done Key: JBIDE-21407 URL: https://issues.jboss.org/browse/JBIDE-21407 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.3.1.Beta1 Reporter: Nick Boldt Amend both staging and release guides such that disabled jobs are appropriately re-enabled at the correct time: once staging/release announcement emails are sent *if there's a planned future milestone*. Verify this is correctly done for 4.3.1.Beta2, as that will also require the same on/off/on steps as were done for 4.3.1.Beta1 (JBIDE-21392). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21407) staging/release guides should generate task jiras to remind releng to re-enable disabled jobs once staging or release is done

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21407?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21407: ---------------------------------- Assignee: Nick Boldt > staging/release guides should generate task jiras to remind releng to re-enable disabled jobs once staging or release is done > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21407 > URL: https://issues.jboss.org/browse/JBIDE-21407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > Amend both staging and release guides such that disabled jobs are appropriately re-enabled at the correct time: once staging/release announcement emails are sent *if there's a planned future milestone*. > Verify this is correctly done for 4.3.1.Beta2, as that will also require the same on/off/on steps as were done for 4.3.1.Beta1 (JBIDE-21392). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21407) staging/release guides should generate task jiras to remind releng to re-enable disabled jobs once staging or release is done

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21407?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21407: ------------------------------- Fix Version/s: 4.3.1.Beta2 > staging/release guides should generate task jiras to remind releng to re-enable disabled jobs once staging or release is done > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21407 > URL: https://issues.jboss.org/browse/JBIDE-21407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > Amend both staging and release guides such that disabled jobs are appropriately re-enabled at the correct time: once staging/release announcement emails are sent *if there's a planned future milestone*. > Verify this is correctly done for 4.3.1.Beta2, as that will also require the same on/off/on steps as were done for 4.3.1.Beta1 (JBIDE-21392). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21405) Add RedDeer 1.0.1 to target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21405?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21405: ------------------------------------ Looks like you already have red deer as part of your root pom: https://github.com/jbosstools/jbosstools-integration-tests/blob/jbosstool... So... why do you need it in the TP too? Who else will consume it, other than the integration-tests project? FWIW, if you wanted to include the JBT TP in your root pom (to get swtbot), you could use http://download.jboss.org/jbosstools/mars/snapshots/updates/ (a composite site including both the JBT and JBT TP bits) instead of http://download.jboss.org/jbosstools/mars/snapshots/updates/core/$\{jboss... (JBT bits only). https://github.com/jbosstools/jbosstools-integration-tests/blob/jbosstool... > Add RedDeer 1.0.1 to target platform > ------------------------------------ > > Key: JBIDE-21405 > URL: https://issues.jboss.org/browse/JBIDE-21405 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > We would like to add RedDeer 1.0.1 to target platform. > Note that we don't have 1.0.1 ready yet, it will be released soon (should be in time to make it to Beta2). Currently we have 1.0.0. But I'm creating this JIRA now to find out if anything is needed to be done for this to happen. > Github repo: https://github.com/jboss-reddeer/reddeer > Wiki: https://github.com/jboss-reddeer/reddeer/wiki > 1.0.0 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/ > 1.0.1 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.1/ (not available yet) > Feature: org.jboss.reddeer.eclipse.feature -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15339) Create version/change auditor/reporting tool

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15339?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15339: ------------------------------------ * Goal: be able to more easily see if a feature or plugin needs to be upversioned ** JBIDE-19056 A Mojo to validate a version (compared to baseline) ** also have https://github.com/jbosstools/jbosstools-versionwatch/ running for all JBDS builds to audit all org.jboss / com.jboss + all upstream IU versions ** *DONE* * Goal: be able to more easily see if a commit in github has been built into the jars in an update site ** buildinfo.json is produced for each and every update site now; includes upstream URLs, github SHAs, github project URLs *** https://devstudio.redhat.com/10.0/snapshots/updates/core/master/buildinfo... *** http://download.jboss.org/jbosstools/neon/snapshots/updates/core/master/b... *** http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bas... ** https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.3.x/u... for auditing when we're in code freeze / some jobs are disabled ** *DONE* * Goal: be able to more easily see what has changed between two builds (with links to relevant Jenkins, JIRA, Github, upstream URLs, TP URLs) ** Jenkins job name is already captured in buildinfo.json, as WORKSPACE for each job contains the JOB_NAME. Do we need anything else? ** Github & upstream URLs are already captured in buildinfo.json; see examples above ** sounds like we need some add to buildinfo.json to capture TP URLs ** not sure what we need to do for a link back to JIRA... just a generic link to JBIDE or JBDS? Or multiple links for each JIRA changed/closed between builds? [~maxandersen] [~mickael_istria] [~mmalina] can you help explain this requirement and how we might use such a report? Is this something you see value in creating, or are we good enough w/ all the above tools, mojos & metadata in buildinfo.json to close this issue? > Create version/change auditor/reporting tool > -------------------------------------------- > > Key: JBIDE-15339 > URL: https://issues.jboss.org/browse/JBIDE-15339 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, updatesite > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: versioning > Fix For: 4.3.x > > > Plugin/Feature Version Auditor > Goal: be able to more easily see if a feature or plugin needs to be upversioned > Goal: be able to more easily see if a commit in github has been built into the jars in an update site > Goal: be able to more easily see what has changed between two builds (with links to relevant Jenkins, JIRA, Github, upstream URLs, TP URLs) > Output: generate a report of: > plugins, features in JBT or JBDS by version, md5 #, JIRA #s related to latest commits, jenkins build IDs > Include URL links to content/metadata: Github, Jenkins, JIRA, dl.jb.org (upstream sites which feed the aggregates, target platforms, composites, etc.) > May also include some parallel work to provide improvements to QA's versionwatch tool (https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch ) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3579) Fuse archetype catalog cannot be added with JBDS 9

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3579?page=com.atlassian.jira.plugin.... ] Fred Bricon edited comment on JBDS-3579 at 1/5/16 11:32 AM: ------------------------------------------------------------ When querying the catalog from CLI, an exception is thrown in RemoteCatalogArchetypeDataSource.getArchetypeCatalog(properties) (as expected since archetype-catalog.xml was appended to the url) : {quote} org.apache.maven.wagon.ResourceDoesNotExistException: File: https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archet... , ReasonPhrase:Not Found. {quote} That Exception is caught in the outer catch block (https://git-wip-us.apache.org/repos/asf?p=maven-archetype.git;a=blob;f=ar...) which then falls back on using the actual catalog url and succeeds. In m2e 1.6+ however, a different transport mechanism (OkHttp) is used. The transport connects to the url, then proceeds to try to parse the content of the temporary file supposed to hold the catalog. Parsing fails and an ArchetypeDataSourceException is thrown, which is intercepted and rethrown in https://git-wip-us.apache.org/repos/asf?p=maven-archetype.git;a=blob;f=ar... instead. was (Author: fbricon): When querying the catalog from CLI, an exception is thrown in RemoteCatalogArchetypeDataSource.getArchetypeCatalog(properties) (as expected since archetype-catalog.xml was appended to the url) : {quote} org.apache.maven.wagon.ResourceDoesNotExistException: File: https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archet... , ReasonPhrase:Not Found. {quote} RemoteCatalogArchetypeDataSource.getArchetypeCatalog(properties). That Exception is caught in the outer catch block (https://git-wip-us.apache.org/repos/asf?p=maven-archetype.git;a=blob;f=ar...) which then falls back on using the actual catalog url and succeeds. In m2e 1.6+ however, a different transport mechanism (OkHttp) is used. The transport connects to the url, then proceeds to try to parse the content of the temporary file supposed to hold the catalog. Parsing fails and an ArchetypeDataSourceException is thrown, which is intercepted and rethrown in https://git-wip-us.apache.org/repos/asf?p=maven-archetype.git;a=blob;f=ar... instead. > Fuse archetype catalog cannot be added with JBDS 9 > -------------------------------------------------- > > Key: JBDS-3579 > URL: https://issues.jboss.org/browse/JBDS-3579 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: maven > Affects Versions: 9.0.0.GA > Reporter: Keith Babo > Assignee: Fred Bricon > > When adding the Fuse Integration Services archetype catalog to JBDS 9, the IDE reports that the catalog is empty. This works in Eclipse and I've heard reports that it also works in earlier versions of JBDS (although I have not confirmed this personally). > Archetype catalog in question: > https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archet... > Steps to reproduce: > - Preferences -> Maven -> Archetypes -> Add Remote Catalog > - Add URL above for Catalog File > - Click Verify ... and you get the message "Remote catalog is empty" > - Click Finish and try to use the catalog from the New Maven Project wizard and the message is "No archetypes available for this catalog." > Impact here is that Fuse customers looking to use Fuse on OpenShift cannot use JBDS to create new projects using our Maven archetypes (the primary means of getting started). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3579) Fuse archetype catalog cannot be added with JBDS 9

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3579?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3579: ----------------------------------- When querying the catalog from CLI, an exception is thrown in RemoteCatalogArchetypeDataSource.getArchetypeCatalog(properties) (as expected since archetype-catalog.xml was appended to the url) : {quote} org.apache.maven.wagon.ResourceDoesNotExistException: File: https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archet... , ReasonPhrase:Not Found. {quote} RemoteCatalogArchetypeDataSource.getArchetypeCatalog(properties). That Exception is caught in the outer catch block (https://git-wip-us.apache.org/repos/asf?p=maven-archetype.git;a=blob;f=ar...) which then falls back on using the actual catalog url and succeeds. In m2e 1.6+ however, a different transport mechanism (OkHttp) is used. The transport connects to the url, then proceeds to try to parse the content of the temporary file supposed to hold the catalog. Parsing fails and an ArchetypeDataSourceException is thrown, which is intercepted and rethrown in https://git-wip-us.apache.org/repos/asf?p=maven-archetype.git;a=blob;f=ar... instead. > Fuse archetype catalog cannot be added with JBDS 9 > -------------------------------------------------- > > Key: JBDS-3579 > URL: https://issues.jboss.org/browse/JBDS-3579 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: maven > Affects Versions: 9.0.0.GA > Reporter: Keith Babo > Assignee: Fred Bricon > > When adding the Fuse Integration Services archetype catalog to JBDS 9, the IDE reports that the catalog is empty. This works in Eclipse and I've heard reports that it also works in earlier versions of JBDS (although I have not confirmed this personally). > Archetype catalog in question: > https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archet... > Steps to reproduce: > - Preferences -> Maven -> Archetypes -> Add Remote Catalog > - Add URL above for Catalog File > - Click Verify ... and you get the message "Remote catalog is empty" > - Click Finish and try to use the catalog from the New Maven Project wizard and the message is "No archetypes available for this catalog." > Impact here is that Fuse customers looking to use Fuse on OpenShift cannot use JBDS to create new projects using our Maven archetypes (the primary means of getting started). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21391) upstream IU version decreases

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21391?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21391: ------------------------------------ Story points = 3: fix UI for summary, detail; fix instructions in README/install.jbds.sh > upstream IU version decreases > ----------------------------- > > Key: JBIDE-21391 > URL: https://issues.jboss.org/browse/JBIDE-21391 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > As of Neon M4, -three- two IUs have versions which decreased relative to their Mars.1 versions. > {code} > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 Version must be higher than 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 Version must be higher than 2.2.101.v20150826-1318 > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Additionally, this IU is incorrectly reported as being a version decrease: > {code}org.eclipse.ecf.provider.filetransfer.httpclient4 1.0.2000.v20150810-1719 Error: Version 1.1.0.v20151130-0157 must be higher than 1.0.2000.v20150810-1719 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21391) upstream IU version decreases

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21391?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21391: ------------------------------- Story Points: 3 > upstream IU version decreases > ----------------------------- > > Key: JBIDE-21391 > URL: https://issues.jboss.org/browse/JBIDE-21391 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > As of Neon M4, -three- two IUs have versions which decreased relative to their Mars.1 versions. > {code} > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 Version must be higher than 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 Version must be higher than 2.2.101.v20150826-1318 > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Additionally, this IU is incorrectly reported as being a version decrease: > {code}org.eclipse.ecf.provider.filetransfer.httpclient4 1.0.2000.v20150810-1719 Error: Version 1.1.0.v20151130-0157 must be higher than 1.0.2000.v20150810-1719 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 January 2016