[JBoss JIRA] (JBDS-3306) Create Deployment from Template
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3306:
---------------------------------
Component/s: openshift
> Create Deployment from Template
> -------------------------------
>
> Key: JBDS-3306
> URL: https://issues.jboss.org/browse/JBDS-3306
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Burr Sutter
> Priority: Blocker
>
> Use Case #3
> Create Deployment from Template
> a) Assume OpenShift is started remotely and provides an entrypoint URL
> b) Assume end-user is logged in (ignore auth for now)
> c) Eclipse user will open a dialog and enter the URL from step a
> d) Eclipse user will then be presented with a list of templates from the template library
> (initially a set of files on the local filesystem until openshift has a real template library api)
> e) The template list should allow sorting so that higher priority items are at the top
> We will likely need some form of categorization for templates also
> f) The template list should be searchable by keyword
> g) Eclipse user will select a particular template and
> h) Create a new openshift deployment based on selected template
> i) follow steps JBDS-3297 f through j (clone, import, project facets, etc)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 6 months
[JBoss JIRA] (JBDS-3306) Create Deployment from Template
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3306?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3306:
-----------------------------
CDW pm_ack: ?
CDW release: ?
> Create Deployment from Template
> -------------------------------
>
> Key: JBDS-3306
> URL: https://issues.jboss.org/browse/JBDS-3306
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
> Priority: Blocker
>
> Use Case #3
> Create Deployment from Template
> a) Assume OpenShift is started remotely and provides an entrypoint URL
> b) Assume end-user is logged in (ignore auth for now)
> c) Eclipse user will open a dialog and enter the URL from step a
> d) Eclipse user will then be presented with a list of templates from the template library
> (initially a set of files on the local filesystem until openshift has a real template library api)
> e) The template list should allow sorting so that higher priority items are at the top
> We will likely need some form of categorization for templates also
> f) The template list should be searchable by keyword
> g) Eclipse user will select a particular template and
> h) Create a new openshift deployment based on selected template
> i) follow steps JBDS-3297 f through j (clone, import, project facets, etc)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 6 months
[JBoss JIRA] (JBDS-3306) Create Deployment from Template
by Burr Sutter (JIRA)
Burr Sutter created JBDS-3306:
---------------------------------
Summary: Create Deployment from Template
Key: JBDS-3306
URL: https://issues.jboss.org/browse/JBDS-3306
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Reporter: Burr Sutter
Priority: Blocker
Use Case #3
Create Deployment from Template
a) Assume OpenShift is started remotely and provides an entrypoint URL
b) Assume end-user is logged in (ignore auth for now)
c) Eclipse user will open a dialog and enter the URL from step a
d) Eclipse user will then be presented with a list of templates from the template library
(initially a set of files on the local filesystem until openshift has a real template library api)
e) The template list should allow sorting so that higher priority items are at the top
We will likely need some form of categorization for templates also
f) The template list should be searchable by keyword
g) Eclipse user will select a particular template and
h) Create a new openshift deployment based on selected template
i) follow steps JBDS-3297 f through j (clone, import, project facets, etc)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 6 months
[JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-15135:
-----------------------------------
Fix Version/s: 4.3.0.Alpha1
(was: 4.2.x)
> Attach metadata during assembly instead of publish time
> -------------------------------------------------------
>
> Key: JBIDE-15135
> URL: https://issues.jboss.org/browse/JBIDE-15135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.3.0.Alpha1
>
>
> In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site.
> Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 6 months