[JBoss JIRA] (JBIDE-21340) Deploy from existing project git constraints are too stringent
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21340?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21340:
-------------------------------
Fix Version/s: 4.3.1.Beta2
(was: 4.3.1.Beta1)
> Deploy from existing project git constraints are too stringent
> --------------------------------------------------------------
>
> Key: JBIDE-21340
> URL: https://issues.jboss.org/browse/JBIDE-21340
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.Beta2
>
>
> There are currently 2 constraints when deploying ane existing project to OpenShift 3 that are really really annoying:
> - if the project is shared with git but dirty, you can't proceed with project deployment on openshift. This constraint is completely unnecessary and should be lifted
> - if the project was cloned using git/ssh protocol, it can't be deployed directly (http(s) is required). This should actually just be a warning, the user can modify the git url to use http(s) in the next page
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21340) Deploy from existing project git constraints are too stringent
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21340?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21340:
-------------------------------
Labels: (was: respin-a)
> Deploy from existing project git constraints are too stringent
> --------------------------------------------------------------
>
> Key: JBIDE-21340
> URL: https://issues.jboss.org/browse/JBIDE-21340
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.Beta2
>
>
> There are currently 2 constraints when deploying ane existing project to OpenShift 3 that are really really annoying:
> - if the project is shared with git but dirty, you can't proceed with project deployment on openshift. This constraint is completely unnecessary and should be lifted
> - if the project was cloned using git/ssh protocol, it can't be deployed directly (http(s) is required). This should actually just be a warning, the user can modify the git url to use http(s) in the next page
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21340) Deploy from existing project git constraints are too stringent
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21340?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21340:
------------------------------------
Slip to Beta2; not a blocker for Beta1.
> Deploy from existing project git constraints are too stringent
> --------------------------------------------------------------
>
> Key: JBIDE-21340
> URL: https://issues.jboss.org/browse/JBIDE-21340
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Fix For: 4.3.1.Beta2
>
>
> There are currently 2 constraints when deploying ane existing project to OpenShift 3 that are really really annoying:
> - if the project is shared with git but dirty, you can't proceed with project deployment on openshift. This constraint is completely unnecessary and should be lifted
> - if the project was cloned using git/ssh protocol, it can't be deployed directly (http(s) is required). This should actually just be a warning, the user can modify the git url to use http(s) in the next page
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21342) [CDK] multiple duplicate docker connections created after multiple starts
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21342?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21342:
-------------------------------------
Saw the same issue on OSX yesterday:
!http://content.screencast.com/users/fbricon/folders/Jing/media/eff44303-b13c-4dc1-954a-06f964baf983/00000263.png|width=480!
> [CDK] multiple duplicate docker connections created after multiple starts
> -------------------------------------------------------------------------
>
> Key: JBIDE-21342
> URL: https://issues.jboss.org/browse/JBIDE-21342
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.3.1.Beta1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.3.1.Beta1, 4.3.1.Beta2, 4.4.0.Alpha1
>
> Attachments: IMG_1145.jpg
>
>
> After starting and stopping the CDK multiple times, multiple docker connections exist.
> This does not seem replicatable on linux; only windows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months