September 2016 - jbosstools-issues

[JBoss JIRA] (JBTIS-881) Fix Windows/Mac specific issues in tests

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-881?page=com.atlassian.jira.plugin.... ] stanislav kaleta updated JBTIS-881: ----------------------------------- Affects Version/s: 4.3.0.Final (was: 4.3.1.Final) > Fix Windows/Mac specific issues in tests > ---------------------------------------- > > Key: JBTIS-881 > URL: https://issues.jboss.org/browse/JBTIS-881 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-881) Fix Windows/Mac specific issues in tests

by stanislav kaleta (JIRA)

stanislav kaleta created JBTIS-881: -------------------------------------- Summary: Fix Windows/Mac specific issues in tests Key: JBTIS-881 URL: https://issues.jboss.org/browse/JBTIS-881 Project: JBoss Tools Integration Stack Issue Type: Enhancement Components: QE, teiid Affects Versions: 4.3.1.Final Reporter: stanislav kaleta Assignee: stanislav kaleta -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-881) Fix Windows/Mac specific issues in tests

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-881?page=com.atlassian.jira.plugin.... ] stanislav kaleta updated JBTIS-881: ----------------------------------- Fix Version/s: 4.3.1.Final > Fix Windows/Mac specific issues in tests > ---------------------------------------- > > Key: JBTIS-881 > URL: https://issues.jboss.org/browse/JBTIS-881 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22728) Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22728: ------------------------------------ Subtasks ongoing so slip to 4.4.2.AM1. > Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22728 > URL: https://issues.jboss.org/browse/JBIDE-22728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.2.AM1 > > Attachments: console.log.txt, getProjectRootPomParents.tsk.txt > > > Current process for moving all the JBT projects to the latest parent pom involves generating 15+ JIRAs assigned to the various project leads, so they can all adopt the latest parent pom, verify their build works, and push the change. > With the advent of PR build jobs, we can now streamline this a little: > instead of creating Task JIRAs, create PRs & let them run automatically. > if they pass, push them in automatically (via script that Alexey or Denis would run) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22728) Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22728: ------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22728 > URL: https://issues.jboss.org/browse/JBIDE-22728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.2.AM1 > > Attachments: console.log.txt, getProjectRootPomParents.tsk.txt > > > Current process for moving all the JBT projects to the latest parent pom involves generating 15+ JIRAs assigned to the various project leads, so they can all adopt the latest parent pom, verify their build works, and push the change. > With the advent of PR build jobs, we can now streamline this a little: > instead of creating Task JIRAs, create PRs & let them run automatically. > if they pass, push them in automatically (via script that Alexey or Denis would run) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23090) instead of running the getProjectRootPomParents.sh script on jenkins, reference it in the email

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23090?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23090: ------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > instead of running the getProjectRootPomParents.sh script on jenkins, reference it in the email > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23090 > URL: https://issues.jboss.org/browse/JBIDE-23090 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Fix For: 4.4.2.AM1 > > > instead of running the getProjectRootPomParents.sh script on jenkins, reference it in the email so that Alexey or Jeff can run it locally in their /tmp folder > 1. script how to fetch jbosstools-build-ci > 2. script how to then run getProjectRootPomParents.sh -w1 /tmp/some-folder/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in commit messages so JIRAs are closed automatically

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23091: ------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > use #close smart tag in commit messages so JIRAs are closed automatically > ------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Fix For: 4.4.2.AM1 > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 commented on JBIDE-23017: ------------------------------------ Forgot to merge this, but then, it wouldn't be of much value if sshfs is only on ONE slave. :( No progress on https://engineering.redhat.com/rt/Ticket/Display.html?id=416218 since Aug 19. > 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.1.AM1 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3544) Improve Eclipse Neon Platform

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3544?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3544: --------------------------------- Fix Version/s: 10.2.0.GA (was: 10.1.0.GA) > Improve Eclipse Neon Platform > ----------------------------- > > Key: JBDS-3544 > URL: https://issues.jboss.org/browse/JBDS-3544 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: integration, requirements > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 10.2.0.GA > > > As a Developer I would like Eclipse platform to improve so I can work faster and not be frustrated -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3954) Target Platform Requirements for JBDS 10.1.0.GA

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3954?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3954: ----------------------------- > Target Platform Requirements for JBDS 10.1.0.GA > ----------------------------------------------- > > Key: JBDS-3954 > URL: https://issues.jboss.org/browse/JBDS-3954 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: 3rd-party-certification > Affects Versions: 10.1.0.AM1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 10.1.0.GA > > > Track changes to third party inclusions in JBDS 10.1.0 - target platforms, Central, Early Access, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 September 2016