August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20152) script the process of branching and tagging based on buildinfo.json

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20152?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20152: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build-ci/pull/132, https://github.com/jbdevstudio/jbdevstudio-devdoc/pull/129 (was: https://github.com/jbdevstudio/jbdevstudio-ci/pull/152, https://github.com/jbosstools/jbosstools-build-ci/pull/132, https://github.com/jbdevstudio/jbdevstudio-devdoc/pull/129) > script the process of branching and tagging based on buildinfo.json > ------------------------------------------------------------------- > > Key: JBIDE-20152 > URL: https://issues.jboss.org/browse/JBIDE-20152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 4.3.0.CR1 > > > {quote} > Last time I suggested we created a file with a line for each repo, like: > {code}jbosstools/jbosstools-hibernate, 13asd123asd232, jbosstools-4.3.0.Beta1{code} > You had a txt file before that had this information but in a hard-to-parse format. > I can try parse the buildinfo.json too but thought if you had the simpler one I could use that instead. > /max {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20194) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20194?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20194: ---------------------------------------- [~nickboldt] could you please update https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... Since it looks like we have to keep url="..." in: {code} <license url="%licenseURL"> %license </license> {code} > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 > ------------------------------------------------------------------------- > > Key: JBIDE-20194 > URL: https://issues.jboss.org/browse/JBIDE-20194 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3481 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20430) Missing Provider and Feature Name in websocket feature

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-20430: -------------------------------------- Summary: Missing Provider and Feature Name in websocket feature Key: JBIDE-20430 URL: https://issues.jboss.org/browse/JBIDE-20430 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.3.0.Beta2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.3.0.CR1 Attachments: websockets.png -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20430) Missing Provider and Feature Name in websocket feature

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20430?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20430: ----------------------------------- Attachment: websockets.png > Missing Provider and Feature Name in websocket feature > ------------------------------------------------------ > > Key: JBIDE-20430 > URL: https://issues.jboss.org/browse/JBIDE-20430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.CR1 > > Attachments: websockets.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20430) Missing Provider and Feature Name in websocket feature

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20430?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20430: ----------------------------------- Description: !websockets.png! > Missing Provider and Feature Name in websocket feature > ------------------------------------------------------ > > Key: JBIDE-20430 > URL: https://issues.jboss.org/browse/JBIDE-20430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.3.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.CR1 > > Attachments: websockets.png > > > !websockets.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20402) Contribute "Deploy to Openshift" menu in Docker Tools' Image view

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20402?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20402: ------------------------------------- I've created a sub task JBIDE-20429 for the work needed to be done upstream. > 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: Jeff Cantrill > 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 > * tag and push image to registry (tag=repo/project/stream) > ** repo is either assumed to be Dockerhub, or the route to the OS registry > * 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-20402) Contribute "Deploy to Openshift" menu in Docker Tools' Image view

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20402?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20402: ----------------------------------- Assignee: Jeff Cantrill (was: Xavier Coulon) > 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: Jeff Cantrill > 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 > * tag and push image to registry (tag=repo/project/stream) > ** repo is either assumed to be Dockerhub, or the route to the OS registry > * 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-20429) Expose Docker Image info required by OpenShift integration

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20429?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20429: ----------------------------------- Assignee: Xavier Coulon > Expose Docker Image info required by OpenShift integration > ---------------------------------------------------------- > > Key: JBIDE-20429 > URL: https://issues.jboss.org/browse/JBIDE-20429 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker, upstream > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20429) Expose Docker Image info required by OpenShift integration

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20429?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20429: -------------------------------- Description: In order to support JBIDE-20402, docker tooling needs to expose : ports env variables volumes > Expose Docker Image info required by OpenShift integration > ---------------------------------------------------------- > > Key: JBIDE-20429 > URL: https://issues.jboss.org/browse/JBIDE-20429 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker, upstream > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.CR1 > > > In order to support JBIDE-20402, docker tooling needs to expose : > ports > env variables > volumes -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20429) Expose Docker Image info required by OpenShift integration

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20429?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20429: -------------------------------- Description: In order to support JBIDE-20402, docker tooling needs to expose : - ports - env variables - volumes was: In order to support JBIDE-20402, docker tooling needs to expose : ports env variables volumes > Expose Docker Image info required by OpenShift integration > ---------------------------------------------------------- > > Key: JBIDE-20429 > URL: https://issues.jboss.org/browse/JBIDE-20429 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker, upstream > Affects Versions: 4.3.0.Beta2 > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.0.CR1 > > > In order to support JBIDE-20402, docker tooling needs to expose : > - ports > - env variables > - volumes -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 August 2015