[JBoss JIRA] (JBDS-3465) Consider using SpringIDE 3.7 (or 3.6.4?)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3465?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3465:
----------------------------------
Final IU/commit: https://github.com/jbosstools/jbosstools-discovery/commit/e81b0ecca3fc7ec...
{code}
> com.google.protobuf [2.4.0.v201105131100]
=== Summary ===
file:///home/nboldt/tru/disco/jbtcentraltarget/multiple/target/jbtcentral-multiple.target.repo/ contains 1 unique IUs
{code}
> Consider using SpringIDE 3.7 (or 3.6.4?)
> ----------------------------------------
>
> Key: JBDS-3465
> URL: https://issues.jboss.org/browse/JBDS-3465
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, target-platform
> Affects Versions: 9.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Marián Labuda
> Fix For: 9.0.0.CR1
>
> Attachments: install-spring-all-features.png, install-spring-sites.png
>
>
> There are new versions of SpringIDE available:
> {code:title=http://dist.springsource.com/release/TOOLS/update/e4.5}
> org.springframework.ide.eclipse.feature.feature.group 3.6.4.201503051146-RELEASE{code}
> {code:title=http://dist.springsource.com/snapshot/TOOLS/nightly/e4.5}
> org.springframework.ide.eclipse.feature.feature.group 3.7.0.201506181755-CI-B262{code}
> Which would we like to include in Central?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBDS-3465) Consider using SpringIDE 3.7 (or 3.6.4?)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3465?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-3465.
------------------------------
Resolution: Done
> Consider using SpringIDE 3.7 (or 3.6.4?)
> ----------------------------------------
>
> Key: JBDS-3465
> URL: https://issues.jboss.org/browse/JBDS-3465
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, target-platform
> Affects Versions: 9.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Marián Labuda
> Fix For: 9.0.0.CR1
>
> Attachments: install-spring-all-features.png, install-spring-sites.png
>
>
> There are new versions of SpringIDE available:
> {code:title=http://dist.springsource.com/release/TOOLS/update/e4.5}
> org.springframework.ide.eclipse.feature.feature.group 3.6.4.201503051146-RELEASE{code}
> {code:title=http://dist.springsource.com/snapshot/TOOLS/nightly/e4.5}
> org.springframework.ide.eclipse.feature.feature.group 3.7.0.201506181755-CI-B262{code}
> Which would we like to include in Central?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20069) OpenShift Feature is missing (in Installation Details)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20069?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20069:
--------------------------------------
Assignee: Denis Golovin
[~dgolovin] could you help with this issue?
> OpenShift Feature is missing (in Installation Details)
> ------------------------------------------------------
>
> Key: JBIDE-20069
> URL: https://issues.jboss.org/browse/JBIDE-20069
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Denis Golovin
> Priority: Critical
> Labels: help_wanted, openshift_v3
> Fix For: 4.3.0.CR1
>
> Attachments: missing-openshift-feature.png
>
>
> In Installation Details under tab Features should be located OpenShift feature (or OpenShift UI feature). But it is missing in JBT (also in JBDS).
> !missing-openshift-feature.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20402) Contribute "Deploy to Openshift" menu in Docker Tools' Image view
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20402?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-20402:
----------------------------------
Description:
To make this happen we will need docker tooling to provide:
* ports
* env variables
* volumes
A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
* Ask user about ports, additional env besides those already provided in the image, volumes,
* Ask about # of replicas, triggers
* push image to OS registry if
** image is not currently in Dockerhub
** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
* create an ImageStream for the selected image
* create a deploymentConfig for the selected image
* create a service for the image
* optionally create a route
Consider running oc new-app on an image to see what it generates
==================================================================
It's possible to contribute a new menu/handler to the Docker Tooling Images view.
We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
The following infos are required to actually be able to deploy the selected image onto OS:
- the local docker registry. OS will need a route to be able to access it
- the docker hub registry
- environment variables
- ports
- volumes
The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
was:
To make this happen we will need docker tooling to provide:
* ports
* env variables
* volumes
A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
* Ask user about ports, additional env besides those already provided in the image, volumes,
* Ask about # of replicas, triggers
* push image to OS registry if
** image is not currently in Dockerhub
** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
* create an ImageStream for the selected image
* create a deploymentConfig for the selected image
* create a service for the image
* optionally create a route
==================================================================
It's possible to contribute a new menu/handler to the Docker Tooling Images view.
We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
The following infos are required to actually be able to deploy the selected image onto OS:
- the local docker registry. OS will need a route to be able to access it
- the docker hub registry
- environment variables
- ports
- volumes
The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
> Contribute "Deploy to Openshift" menu in Docker Tools' Image view
> -----------------------------------------------------------------
>
> Key: JBIDE-20402
> URL: https://issues.jboss.org/browse/JBIDE-20402
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Labels: openshift_v3
> Fix For: 4.3.0.CR1
>
> Attachments: deployment_config.json, run image - screen 1.png, run image 2.png
>
>
> To make this happen we will need docker tooling to provide:
> * ports
> * env variables
> * volumes
> A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
> * Ask user about ports, additional env besides those already provided in the image, volumes,
> * Ask about # of replicas, triggers
> * push image to OS registry if
> ** image is not currently in Dockerhub
> ** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
> * create an ImageStream for the selected image
> * create a deploymentConfig for the selected image
> * create a service for the image
> * optionally create a route
> Consider running oc new-app on an image to see what it generates
> ==================================================================
> It's possible to contribute a new menu/handler to the Docker Tooling Images view.
> We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
> The following infos are required to actually be able to deploy the selected image onto OS:
> - the local docker registry. OS will need a route to be able to access it
> - the docker hub registry
> - environment variables
> - ports
> - volumes
> The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
> The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20402) Contribute "Deploy to Openshift" menu in Docker Tools' Image view
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20402?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-20402:
----------------------------------
Description:
To make this happen we will need docker tooling to provide:
* ports
* env variables
* volumes
A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
* Ask user about ports, additional env besides those already provided in the image, volumes,
* Ask about # of replicas, triggers
* push image to OS registry if
** image is not currently in Dockerhub
** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
* create an ImageStream for the selected image
* create a deploymentConfig for the selected image
* create a service for the image
==================================================================
It's possible to contribute a new menu/handler to the Docker Tooling Images view.
We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
The following infos are required to actually be able to deploy the selected image onto OS:
- the local docker registry. OS will need a route to be able to access it
- the docker hub registry
- environment variables
- ports
- volumes
The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
was:
To make this happen we will need docker tooling to provide:
* ports
* env variables
* volumes
A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
* Ask user about ports, env, volumes,
* Ask about # of replicas, triggers
* push image to OS registry if
** image is not currently in Dockerhub
** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
* create an ImageStream for the selected image
* create a deploymentConfig for the selected image
==================================================================
It's possible to contribute a new menu/handler to the Docker Tooling Images view.
We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
The following infos are required to actually be able to deploy the selected image onto OS:
- the local docker registry. OS will need a route to be able to access it
- the docker hub registry
- environment variables
- ports
- volumes
The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
> Contribute "Deploy to Openshift" menu in Docker Tools' Image view
> -----------------------------------------------------------------
>
> Key: JBIDE-20402
> URL: https://issues.jboss.org/browse/JBIDE-20402
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Labels: openshift_v3
> Fix For: 4.3.0.CR1
>
> Attachments: deployment_config.json, run image - screen 1.png, run image 2.png
>
>
> To make this happen we will need docker tooling to provide:
> * ports
> * env variables
> * volumes
> A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
> * Ask user about ports, additional env besides those already provided in the image, volumes,
> * Ask about # of replicas, triggers
> * push image to OS registry if
> ** image is not currently in Dockerhub
> ** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
> * create an ImageStream for the selected image
> * create a deploymentConfig for the selected image
> * create a service for the image
> ==================================================================
> It's possible to contribute a new menu/handler to the Docker Tooling Images view.
> We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
> The following infos are required to actually be able to deploy the selected image onto OS:
> - the local docker registry. OS will need a route to be able to access it
> - the docker hub registry
> - environment variables
> - ports
> - volumes
> The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
> The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20402) Contribute "Deploy to Openshift" menu in Docker Tools' Image view
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20402?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-20402:
----------------------------------
Description:
To make this happen we will need docker tooling to provide:
* ports
* env variables
* volumes
A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
* Ask user about ports, additional env besides those already provided in the image, volumes,
* Ask about # of replicas, triggers
* push image to OS registry if
** image is not currently in Dockerhub
** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
* create an ImageStream for the selected image
* create a deploymentConfig for the selected image
* create a service for the image
* optionally create a route
==================================================================
It's possible to contribute a new menu/handler to the Docker Tooling Images view.
We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
The following infos are required to actually be able to deploy the selected image onto OS:
- the local docker registry. OS will need a route to be able to access it
- the docker hub registry
- environment variables
- ports
- volumes
The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
was:
To make this happen we will need docker tooling to provide:
* ports
* env variables
* volumes
A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
* Ask user about ports, additional env besides those already provided in the image, volumes,
* Ask about # of replicas, triggers
* push image to OS registry if
** image is not currently in Dockerhub
** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
* create an ImageStream for the selected image
* create a deploymentConfig for the selected image
* create a service for the image
==================================================================
It's possible to contribute a new menu/handler to the Docker Tooling Images view.
We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
The following infos are required to actually be able to deploy the selected image onto OS:
- the local docker registry. OS will need a route to be able to access it
- the docker hub registry
- environment variables
- ports
- volumes
The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
> Contribute "Deploy to Openshift" menu in Docker Tools' Image view
> -----------------------------------------------------------------
>
> Key: JBIDE-20402
> URL: https://issues.jboss.org/browse/JBIDE-20402
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Labels: openshift_v3
> Fix For: 4.3.0.CR1
>
> Attachments: deployment_config.json, run image - screen 1.png, run image 2.png
>
>
> To make this happen we will need docker tooling to provide:
> * ports
> * env variables
> * volumes
> A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
> * Ask user about ports, additional env besides those already provided in the image, volumes,
> * Ask about # of replicas, triggers
> * push image to OS registry if
> ** image is not currently in Dockerhub
> ** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
> * create an ImageStream for the selected image
> * create a deploymentConfig for the selected image
> * create a service for the image
> * optionally create a route
> ==================================================================
> It's possible to contribute a new menu/handler to the Docker Tooling Images view.
> We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
> The following infos are required to actually be able to deploy the selected image onto OS:
> - the local docker registry. OS will need a route to be able to access it
> - the docker hub registry
> - environment variables
> - ports
> - volumes
> The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
> The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (JBIDE-20402) Contribute "Deploy to Openshift" menu in Docker Tools' Image view
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20402?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-20402:
----------------------------------
Description:
To make this happen we will need docker tooling to provide:
* ports
* env variables
* volumes
A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
* Ask user about ports, env, volumes,
* Ask about # of replicas, triggers
* push image to OS registry if
** image is not currently in Dockerhub
** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
* create an ImageStream for the selected image
* create a deploymentConfig for the selected image
==================================================================
It's possible to contribute a new menu/handler to the Docker Tooling Images view.
We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
The following infos are required to actually be able to deploy the selected image onto OS:
- the local docker registry. OS will need a route to be able to access it
- the docker hub registry
- environment variables
- ports
- volumes
The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
was:
It's possible to contribute a new menu/handler to the Docker Tooling Images view.
We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
The following infos are required to actually be able to deploy the selected image onto OS:
- the local docker registry. OS will need a route to be able to access it
- the docker hub registry
- environment variables
- ports
- volumes
The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
> Contribute "Deploy to Openshift" menu in Docker Tools' Image view
> -----------------------------------------------------------------
>
> Key: JBIDE-20402
> URL: https://issues.jboss.org/browse/JBIDE-20402
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Labels: openshift_v3
> Fix For: 4.3.0.CR1
>
> Attachments: deployment_config.json, run image - screen 1.png, run image 2.png
>
>
> To make this happen we will need docker tooling to provide:
> * ports
> * env variables
> * volumes
> A user will 'deploy to openshift'...I think they might see portions of the 'run image..' menus that are attached but not all. The workflow would be:
> * Ask user about ports, env, volumes,
> * Ask about # of replicas, triggers
> * push image to OS registry if
> ** image is not currently in Dockerhub
> ** OS registry has a route (this we might have to ask about. fail if it doesnt exist? )
> * create an ImageStream for the selected image
> * create a deploymentConfig for the selected image
> ==================================================================
> It's possible to contribute a new menu/handler to the Docker Tooling Images view.
> We'd like to be able to select a Docker image from the Docker tooling view, right-click on it and the "Deploy to Openshift"
> The following infos are required to actually be able to deploy the selected image onto OS:
> - the local docker registry. OS will need a route to be able to access it
> - the docker hub registry
> - environment variables
> - ports
> - volumes
> The docker tooling code is available at : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git
> The IDockerImage is accessible from the image view : http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Example of menu contribution: http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta...
> Currently the search image wizard is not reusable (internal package), if needed, this will require exposing it in Docker tooling for Mars SR1
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months