[JBoss JIRA] Created: (JBIDE-2764) Split up build(s) in smaller pieces
by Max Rydahl Andersen (JIRA)
Split up build(s) in smaller pieces
-----------------------------------
Key: JBIDE-2764
URL: https://jira.jboss.org/jira/browse/JBIDE-2764
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Build/Releng
Reporter: Max Rydahl Andersen
Fix For: LATER
Currently our build is very monolithic (for no real good reason) and that results in the build being very slow, not easy to see which component cause a failure since all dependents will also fail, respins takes alot of time ;(
We should split up the build in smaller parts (not necessarily all the way down to modules) which makes it possible to build the various part more or less independently by just being able to take the generated artifacts from dependent builds.
It would also be beneficial if the compile, test and upload parts gets separated so e.g. tests can be executed on separate platforms without having a full rebuild.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] Created: (JBIDE-7365) Trying to start a stopped EC2 instance results in infinite starting task
by Jeff Johnston (JIRA)
Trying to start a stopped EC2 instance results in infinite starting task
------------------------------------------------------------------------
Key: JBIDE-7365
URL: https://jira.jboss.org/browse/JBIDE-7365
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Jeff Johnston
Using deltacloud 0.0.7, when an EC2 instance is stopped, it is no longer listed as TERMINATED as it was
in deltacloud 0.0.5. Instead, it is listed as STOPPED and the REST interface reports that a START action is
possible. This is not true. An EC2 instance, once stopped, is terminated and cannot be restarted. The Deltacloud
tools get the available actions from the REST interface and so if a user attempts to start the instance, the tools will
allow this and set up a task to wait for the state to change from STOPPED, but this will never happen and the task remains in the
task list indefinitely due to the fact that the task cannot be cancelled.
The Deltacloud tools currently does not support cancelling state-change-wait tasks because they are necessary to keep
the cached data up-to-date (e.g. we need to know when an instance in PENDING becomes RUNNING and if the user
has stopped an instance, we need to know when it is officially STOPPED or TERMINATED as this affects available actions,
for example. The task continuously waits and refreshes the instance, waiting for a state change. If a user requests another action,
the current wait-task will be cancelled and the new one will take it's place (e.g. one can STOP a PENDING instance that hasn't
achieved RUNNING state yet).
A bug has been opened against Deltacloud server: https://bugzilla.redhat.com/show_bug.cgi?id=64285 regarding the invalid
action/state settings for the stopped EC2 instance.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] Created: (JBIDE-7569) Cloud View: should show that tree is still loading
by Andre Dietisheim (JIRA)
Cloud View: should show that tree is still loading
--------------------------------------------------
Key: JBIDE-7569
URL: https://jira.jboss.org/browse/JBIDE-7569
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.0.CR1
how to reproduce:
1) make sure you have a connection to a deltacloud server that is connected to your ec2 account
2) make sure you have an instance on ec2 (running or not)
3) go to the cloud view: open the instances branch
Result:
It is initially empty (although you have a running/stopped instance). If you wait for a while it will suddently appear.
Expected result:
The branch should show an child "retrieving...." (like in SVN/CVS explorer) and update the branch as soons as the instances are retrieved from ec2
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] Created: (JBIDE-7541) EC2 kernel and ramdisk images should be restricted for use in launching instances
by Jeff Johnston (JIRA)
EC2 kernel and ramdisk images should be restricted for use in launching instances
---------------------------------------------------------------------------------
Key: JBIDE-7541
URL: https://jira.jboss.org/browse/JBIDE-7541
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Jeff Johnston
Assignee: Andre Dietisheim
EC2 clouds have added new image types: kernel images and ramdisk images. They are identified by their ids which start with aki and ari respectively. These are meant to be specified in addition to a machine image (ami). They cannot be launched directly and when this is attempted, a backend error occurs which causes the Deltacloud Tools to throw a DeltaCloudClientException.
To handle this, it is recommended that the Find Images button in the Launch Instance dialog start with a image id filter of ami. This will then by default show valid machine images. In addition, the Launch Image dialog should issue an error message if the image id does not start with ami and the cloud is EC2.
The Cloud Viewer should restrict launching an image by right-clicking to only images that start with ami (when the cloud is EC2).
The deltacloud folks need to be contacted to see if the optional kernel images and ramdisk images are valid parameters to the launch instance REST interface. If yes, the Launch Instance dialog can be optionally expanded to add 2 new text entry fields for the Kernel image id and ramdisk image id. Each of these would have an accompanying Find button which would filter so that aki and ari images were shown. It would be a simple upgrade to the Find Image dialog to set a default initial filter which would allow filtering the image ids appropriately in each case.
Error checking could likewise ensure that the image ids for these fields started with the correct characters. For non-EC2 clouds, these fields would not be shown.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years