July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24765) implement workaround for blocked branches when we need to update parent poms automatically

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24765?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24765: ------------------------------- Fix Version/s: 4.5.1.AM1 > implement workaround for blocked branches when we need to update parent poms automatically > ------------------------------------------------------------------------------------------ > > Key: JBIDE-24765 > URL: https://issues.jboss.org/browse/JBIDE-24765 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Once protected branches are implemented, branching/tagging & simple root pom updates may not be possible w/o a review. > So, we need to implement an automated workflow that looks like this: > * submit a PR, then > * script a review (by a different user), then > * merge the PR -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24764: ------------------------------- Fix Version/s: 4.5.x > migrate fusetools job from fusesource jenkins to dev-platform jenkins > --------------------------------------------------------------------- > > Key: JBIDE-24764 > URL: https://issues.jboss.org/browse/JBIDE-24764 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Fix For: 4.5.x > > > {quote} > Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job" > for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI > don't know exactly pros and cons, Lars reported the advantages: > * more slaves > * faster > * easier to manage with the other JBoss Tools job > the issue is that it is not working: > * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded > * one test is failing > * and a third issue now seems that it goes into timeout{quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24764: ---------------------------------- Assignee: Nick Boldt > migrate fusetools job from fusesource jenkins to dev-platform jenkins > --------------------------------------------------------------------- > > Key: JBIDE-24764 > URL: https://issues.jboss.org/browse/JBIDE-24764 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.x > > > {quote} > Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job" > for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI > don't know exactly pros and cons, Lars reported the advantages: > * more slaves > * faster > * easier to manage with the other JBoss Tools job > the issue is that it is not working: > * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded > * one test is failing > * and a third issue now seems that it goes into timeout{quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24243) migrate Fuse Tools builds to JBT infrastructure/process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24243 at 7/26/17 11:04 AM: -------------------------------------------------------------- 1. Re: blockers, I pinged about those in MM but not sure if anyone replied. I'll reopen this issue since they're apparently legit blockers and legit not yet done. 2. I'm not sure what you mean by "test structure harmonized" - can you open a subtask JIRA & explain what you need / what's missing in detail? 3. {quote}What about the integration of Fuse Tooling in the branch/tag process of JBoss Tools? I think that it was added in script but not yet functional, right?{quote} It's as functional as it can be given your repos won't let me push directly to them w/o a review. To further automate this, I've opened JBIDE-24765. We'll need something along those lines if jbosstools-openshift decides to also implement "do not push w/o review" on that repo, as per JBIDE-24439. 4. {quote}someone from Fuse Tooling took time to read the full JBoss Tools dev doc{quote} - do you want to open a subtask JIRA for that and assign it to "someone" to do? Or really, should EVERYONE in Fuse Tooling do that? Off the top of my head, the things you should be doing are: * features w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * plugins w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * test plugins w/ sources aggregated onto the jbosstools site: DONE * features in Central for JBT and devstudio: DONE * features should use `license-feature="org.jboss.tools.foundation.license.feature" license-feature-version="0.0.0"`: DONE for all 5 features {code} $➔ for f in $(find . -name feature.xml); do echo $f ; cat $f | grep foundation.license; done ./transformation/features/org.jboss.tools.fuse.transformation.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./jmx/features/org.fusesource.ide.jmx.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./core/features/org.fusesource.ide.core.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./servers/features/org.fusesource.ide.server.extensions.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" ./editor/features/org.fusesource.ide.camel.editor.feature/feature.xml license-feature="org.jboss.tools.foundation.license.feature" {code} * plugins should have the updated license terms/address: "General Counsel, 100 East Davie St., Raleigh NC 27601 USA" * copyrights should state Red Hat, Inc. and others., with current date, and EPL 1.0 license (unless it's another license?) * new features and plugins should follow the above rules when created was (Author: nickboldt): 1. Re: blockers, I pinged about those in MM but not sure if anyone replied. I'll reopen this issue since they're apparently legit blockers and legit not yet done. 2. I'm not sure what you mean by "test structure harmonized" - can you open a subtask JIRA & explain what you need / what's missing in detail? 3. {quote}What about the integration of Fuse Tooling in the branch/tag process of JBoss Tools? I think that it was added in script but not yet functional, right?{quote} It's as functional as it can be given your repos won't let me push directly to them w/o a review. If you need some additional work done on that, such as me scripting the process of... * submitting a PR, then * scripting a review (by a different user), then * merging the PR ... I can open a JIRA for that. We'll need something along those lines if jbosstools-openshift decides to also implement "do not push w/o review" on that repo, as per JBIDE-24439. 4. {quote}someone from Fuse Tooling took time to read the full JBoss Tools dev doc{quote} - do you want to open a subtask JIRA for that and assign it to "someone" to do? Or really, should EVERYONE in Fuse Tooling do that? Off the top of my head, the things you should be doing are: * features w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * plugins w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * test plugins w/ sources aggregated onto the jbosstools site: DONE * features in Central for JBT and devstudio: DONE * features should use `license-feature="org.jboss.tools.foundation.license.feature" license-feature-version="0.0.0"` and plugins should have the updated license terms/address: "General Counsel, 100 East Davie St., Raleigh NC 27601 USA" * copyrights should state Red Hat, Inc. and others., with current date, and EPL 1.0 license (unless it's another license?) * new features and plugins should follow the above rules when created > migrate Fuse Tools builds to JBT infrastructure/process > ------------------------------------------------------- > > Key: JBIDE-24243 > URL: https://issues.jboss.org/browse/JBIDE-24243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, fusetools, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Fuse Tooling currently has jobs under this view: https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/staging/builds/integration-stac... > ** https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/integration/updates/integration... > which publish integration, development or stable update sites. > As part of the migration of Fuse Tooling into JBoss Tools 4.5 for Oxygen, this path will change to something like: > * http://download.jboss.org/jbosstools/*oxygen*/snapshots/builds/fuse-tooling/ > * http://download.jboss.org/jbosstools/*oxygen*/staging/updates/fuse-tooling/ > We will also need to ensure that JBT composites/aggregates are configured to pick up these features/plugins. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24765) implement workaround for blocked branches when we need to update parent poms automatically

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24765: ---------------------------------- Summary: implement workaround for blocked branches when we need to update parent poms automatically Key: JBIDE-24765 URL: https://issues.jboss.org/browse/JBIDE-24765 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build Affects Versions: 4.5.1.AM1 Reporter: Nick Boldt Once protected branches are implemented, branching/tagging & simple root pom updates may not be possible w/o a review. So, we need to implement an automated workflow that looks like this: * submit a PR, then * script a review (by a different user), then * merge the PR -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24243) migrate Fuse Tools builds to JBT infrastructure/process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24243: ------------------------------------ 1. Re: blockers, I pinged about those in MM but not sure if anyone replied. I'll reopen this issue since they're apparently legit blockers and legit not yet done. 2. I'm not sure what you mean by "test structure harmonized" - can you open a subtask JIRA & explain what you need / what's missing in detail? 3. {quote}What about the integration of Fuse Tooling in the branch/tag process of JBoss Tools? I think that it was added in script but not yet functional, right?{quote} It's as functional as it can be given your repos won't let me push directly to them w/o a review. If you need some additional work done on that, such as me scripting the process of... * submitting a PR, then * scripting a review (by a different user), then * merging the PR ... I can open a JIRA for that. We'll need something along those lines if jbosstools-openshift decides to also implement "do not push w/o review" on that repo, as per JBIDE-24439. 4. {quote}someone from Fuse Tooling took time to read the full JBoss Tools dev doc{quote} - do you want to open a subtask JIRA for that and assign it to "someone" to do? Or really, should EVERYONE in Fuse Tooling do that? Off the top of my head, the things you should be doing are: * features w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * plugins w/ sources aggregated onto the jbosstools site (and into devstudio too): DONE * test plugins w/ sources aggregated onto the jbosstools site: DONE * features in Central for JBT and devstudio: DONE * features should use `license-feature="org.jboss.tools.foundation.license.feature" license-feature-version="0.0.0"` and plugins should have the updated license terms/address: "General Counsel, 100 East Davie St., Raleigh NC 27601 USA" * copyrights should state Red Hat, Inc. and others., with current date, and EPL 1.0 license (unless it's another license?) * new features and plugins should follow the above rules when created > migrate Fuse Tools builds to JBT infrastructure/process > ------------------------------------------------------- > > Key: JBIDE-24243 > URL: https://issues.jboss.org/browse/JBIDE-24243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, fusetools, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Fuse Tooling currently has jobs under this view: https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/staging/builds/integration-stac... > ** https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/integration/updates/integration... > which publish integration, development or stable update sites. > As part of the migration of Fuse Tooling into JBoss Tools 4.5 for Oxygen, this path will change to something like: > * http://download.jboss.org/jbosstools/*oxygen*/snapshots/builds/fuse-tooling/ > * http://download.jboss.org/jbosstools/*oxygen*/staging/updates/fuse-tooling/ > We will also need to ensure that JBT composites/aggregates are configured to pick up these features/plugins. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24764: ---------------------------------- Summary: migrate fusetools job from fusesource jenkins to dev-platform jenkins Key: JBIDE-24764 URL: https://issues.jboss.org/browse/JBIDE-24764 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build Affects Versions: 4.5.0.Final Reporter: Nick Boldt {quote} Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job" for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI don't know exactly pros and cons, Lars reported the advantages: * more slaves * faster * easier to manage with the other JBoss Tools job the issue is that it is not working: * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded * one test is failing * and a third issue now seems that it goes into timeout{quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22799) Create integration tests PR check job for server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22799?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22799: --------------------------------------- It started running all the PRs, so it will take a while before it's my testing PR's turn: https://github.com/jbosstools/jbosstools-server/pull/526 You can see that the check is called Central-Integration-tests - I fixed that in the jenkins job's config. > Create integration tests PR check job for server > ------------------------------------------------ > > Key: JBIDE-22799 > URL: https://issues.jboss.org/browse/JBIDE-22799 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Martin Malina > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24681) ITests: Get rid of AbstractCreateApplicationTest

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24681?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-24681: ------------------------------- Sprint: devex #135 July 2017 > ITests: Get rid of AbstractCreateApplicationTest > ------------------------------------------------ > > Key: JBIDE-24681 > URL: https://issues.jboss.org/browse/JBIDE-24681 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.5.0.Final > > > Use requirements instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24681) ITests: Get rid of AbstractCreateApplicationTest

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24681?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-24681: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.x) > ITests: Get rid of AbstractCreateApplicationTest > ------------------------------------------------ > > Key: JBIDE-24681 > URL: https://issues.jboss.org/browse/JBIDE-24681 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.5.0.Final > > > Use requirements instead. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 July 2017