[JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ]
Marián Labuda commented on JBDS-3258:
-------------------------------------
QE: Because of Max'es comments, please clean up end-user steps which are really related to advance docker tooling integration. Simply said, make it clear. Once it's done, QE give ack+ to this JIRA.
> Docker Tooling (Advanced Integration)
> -------------------------------------
>
> Key: JBDS-3258
> URL: https://issues.jboss.org/browse/JBDS-3258
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift, requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
>
> Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear.
> In addition to the basic integrations of pull, run, stop, commit and push
> boot2docker init
> boot2docker up
> boot2docker down
> boot2docker ip
> docker run -d
> docker ps
> docker rm
> docker rmi
> docker build
> End-user steps:
> 0) assumes boot2docker has been dowloaded and installed
> 1) boot2docker init : required to to insure boot2docker-vm is properly initialized
> 2) boot2docker up : starts the VirtualBox boot2docker-vm
> 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability.
> 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously
> 5) docker ps : allows me to see all my currently running containers
> 6) docker rm : allows me to kill a currently running container
> 7) docker rmi : allows me to remove a local image
> 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded
> 9) docker run : this new created image
> The docker build scenario can be triggered via a Maven plugin
> The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install)
> We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn. So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3268) Export a Cordova Application created using JBDS to FeedHenry
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3268?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3268:
-------------------------------
CDW qa_ack: +
> Export a Cordova Application created using JBDS to FeedHenry
> ------------------------------------------------------------
>
> Key: JBDS-3268
> URL: https://issues.jboss.org/browse/JBDS-3268
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aerogear-hybrid, requirements
> Reporter: Burr Sutter
> Assignee: Gorkem Ercan
> Fix For: 9.0.0.CR1
>
>
> As a HTML5-focused mobile application developer, I wish to use JBoss Tools and JBDS to craft my AngularJS+Ionic or jQuery Mobile-based application, testing it via CordovaSim, deploy the application to my iOS and/or Android phone and when I feel it is "about right", push it to FeedHenry's git URL.
> It is currently unclear how an end-user takes his/her JBDS Hybrid Mobile (Cordova) project and sets it up to support a git push to FH.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3272) JBoss Central HTML
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3272?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3272:
-------------------------------
CDW qa_ack: +
> JBoss Central HTML
> ------------------
>
> Key: JBDS-3272
> URL: https://issues.jboss.org/browse/JBDS-3272
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, requirements
> Reporter: Burr Sutter
>
> Convert JBoss Central into a HTML-based component. This should allow for easier long-term maintenance and faster/easier ad-hoc updates being pushed to users. In addition, better scalability should others wish to contribute wizards, archetypes, quickstarts and showcase examples.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ]
Len DiMaggio edited comment on JBDS-3273 at 1/19/15 10:49 AM:
--------------------------------------------------------------
QE review comment - QE ack pending resolution to question:
Do I read this JIRA correctly? We want a user, at any point in time, to be able to go to JBoss Central and retrieve/build the current set of an upstream project's quickstarts, even if the current set of quickstarts may be changing from day to day? What will happen when newly released quickstarts fail with JBDS? Will we separate stable/unstable quickstarts?
was (Author: ldimaggio):
QE review comment - QE ack pending resolution to question:
Do I read this JIRA correctly? We want a user, at any point in time, to be able to go to JBoss Central and retrieve/build the current set of an upstream project's quickstarts, even if the current set of quickstarts may be changing from day to day? What will happen when newly released quickstarts fail with JBDS?
> JBoss Central: Automatic upstream quickstart integration
> ---------------------------------------------------------
>
> Key: JBDS-3273
> URL: https://issues.jboss.org/browse/JBDS-3273
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 9.0.0.Beta1
>
>
> Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3273) JBoss Central: Automatic upstream quickstart integration
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3273?page=com.atlassian.jira.plugin.... ]
Len DiMaggio edited comment on JBDS-3273 at 1/19/15 10:49 AM:
--------------------------------------------------------------
QE review comment - QE ack pending resolution to question:
Do I read this JIRA correctly? We want a user, at any point in time, to be able to go to JBoss Central and retrieve/build the current set of an upstream project's quickstarts, even if the current set of quickstarts may be changing from day to day? What will happen when newly released quickstarts fail with JBDS?
was (Author: ldimaggio):
QE review comment - QE ack pending resolution to question:
Do I read this JIRA correctly? We want a user, at any point in time, to be able to go to JBoss Central and retrieve/build the current set of an upstream project's quickstarts, even if the current set of quickstarts may be changing from day to day?
> JBoss Central: Automatic upstream quickstart integration
> ---------------------------------------------------------
>
> Key: JBDS-3273
> URL: https://issues.jboss.org/browse/JBDS-3273
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: central, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Fix For: 9.0.0.Beta1
>
>
> Support a more dynamic JBoss Central with direct access to the upstream quickstarts - no longer requiring a fork and tweak to the current quickstarts. We will need some form of 'search UI' as the total list of quickstarts has grown dramatically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months