[jbosstools-issues] [JBoss JIRA] (JBIDE-24243) migrate Fuse Tools builds to JBT infrastructure/process
Nick Boldt (JIRA)
issues at jboss.org
Wed Jul 26 11:19:00 EDT 2017
[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440642#comment-13440642 ]
Nick Boldt edited comment on JBIDE-24243 at 7/26/17 11:18 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
devdoc docs to read include:
* https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_source_bundles_features_and_src_zips.adoc
* https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_checks.adoc
* https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to_add_a_plugin_or_feature_to_an_existing_project.adoc
* https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to_add_a_test_plugin_or_feature.adoc
* https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/target_platforms/target_platforms_updates.adoc
* https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/publishing_features_downstream.adoc
* https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/third_party.adoc
* https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/versioning.adoc
* https://github.com/jbosstools/jbosstools-devdoc/blob/master/community/code_freezes.adoc
* https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/tagging_branching.adoc
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.
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
> 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%20Tooling/
> * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20Tooling/job/Fuse-Tooling-9.2.x-Update-Site/111/parameters/ -> http://download.jboss.org/jbosstools/neon/staging/builds/integration-stack/fuse-tooling/9.2.0.CI/
> ** https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20Tooling/job/Fuse-Tooling-9.2.x-Update-Site-Publish/64/parameters/ -> http://download.jboss.org/jbosstools/neon/integration/updates/integration-stack/fuse-tooling/9.2.0.CI/
> 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)
More information about the jbosstools-issues
mailing list