[JBoss JIRA] (JBIDE-26714) Change all occurences of OpenShift 3 by OpenShift
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26714?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26714.
---------------------------------
I have not found any occurrences of OpenShift 3.
Closing.
Verified in:
Red Hat CodeReady Studio
Version: 12.13.0.AM1
Build id: AM1-v20190901-2225-B4919
Build date: 20190901-2225
> Change all occurences of OpenShift 3 by OpenShift
> -------------------------------------------------
>
> Key: JBIDE-26714
> URL: https://issues.jboss.org/browse/JBIDE-26714
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.12.0.Final
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.13.0.AM1
>
>
> Now that JBoss Tools supports OCP4 in the same way that OCP3, we should replace all occurence of OpenShift 3 by OpenShift
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 4 months
[JBoss JIRA] (JBIDE-26744) Server adapter: "Clean" required after changing the war name
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26744?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26744.
---------------------------------
Works as expected.
Verified in:
Red Hat CodeReady Studio
Version: 12.13.0.AM1
Build id: AM1-v20190901-2225-B4919
Build date: 20190901-2225
> Server adapter: "Clean" required after changing the war name
> ------------------------------------------------------------
>
> Key: JBIDE-26744
> URL: https://issues.jboss.org/browse/JBIDE-26744
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: server_adapter
> Fix For: 4.13.0.AM1
>
>
> *Steps*:
> # EXEC: create a new app by using the *jboss-webserver31-tomcat8-openshift:1.2* builder image
> # ASSERT: *websocket-chat* application is imported into your workspace
> # ASSERT: server adapter *jboss-webserver31-tomcat* is created
> # ASSERT: In OpenShift explorer, below the service jboss-webserver31-tomcat*, you have the running pod (build is finished, pod running)
> # EXEC: start the server adapter
> # EXEC: open the server adapter editor and switch to "Deployment" Tag
> # EXEC: edit "Deployment Location"
> *Result*:
> Server adapter is syncing, but in the "Console" you dont see new files being transferred
> *Expected Result*:
> As soon as a new deployment location is set, the new destination should be synced to the pod.
> *Workaround*:
> "Clean" the server adapter.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 4 months
[JBoss JIRA] (JBIDE-24498) Deploy Docker Image wizard: results dialog is not very informative
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-24498?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-24498.
---------------------------------
Closing, dialog is improved.
Verified in:
Red Hat CodeReady Studio
Version: 12.13.0.AM1
Build id: AM1-v20190901-2225-B4919
Build date: 20190901-2225
> Deploy Docker Image wizard: results dialog is not very informative
> ------------------------------------------------------------------
>
> Key: JBIDE-24498
> URL: https://issues.jboss.org/browse/JBIDE-24498
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.13.0.AM1
>
> Attachments: image-2017-05-23-11-07-21-461.png, pod-deploy-failed.png, pod-deploy-failed.png, resource-summary-dialog.png
>
>
> steps to reproduce:
> # ASSERT: have a docker connection
> # ASSERT: have an OpenShift connection
> # EXEC: in "Docker Explorer": select an image and pick "Deploy to OpenShift..."
> # ASSERT: deploy docker image wizard pops up
> # EXEC: provide settings and finish the wizard
> Result:
> A dialog pops up informing you about the result of your deployment.
> !image-2017-05-23-11-07-21-461.png!
> But the dialog is not very informative, it's far from obvious what the different informations are all about:
> * If there's an error deploying (ex. you have chosen to "Push to the registry" but the registry is not reachable from the local docker daemon that holds the image that you want to deploy) the error is displayed in the title area. It's not visible at first sight that it's an error. Only by reading you're discovering it. (ex. add an error decorator)
> * There's a list of items. Nothing in the dialog tells the user what these items are.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 4 months
[JBoss JIRA] (JBIDE-26807) Add missing templates of the OSes used in CodeReady Studio certification matrix into PSI jenkins
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26807?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-26807:
----------------------------------
Description:
Add missing jenkins cloud templates into new PSI jenkins with proper flavors and label (medium, x64, jbds, etc). OSes missing:
* fedora 29, 30
* static macs: bigmek, domek, zamek, dev-platform-mac1, dev-platform-mac2
* ubuntu 19.04, 18.04
> Add missing templates of the OSes used in CodeReady Studio certification matrix into PSI jenkins
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26807
> URL: https://issues.jboss.org/browse/JBIDE-26807
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, qa
> Affects Versions: 4.13.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Major
> Labels: jenkins
> Fix For: 4.13.0.Final
>
>
> Add missing jenkins cloud templates into new PSI jenkins with proper flavors and label (medium, x64, jbds, etc). OSes missing:
> * fedora 29, 30
> * static macs: bigmek, domek, zamek, dev-platform-mac1, dev-platform-mac2
> * ubuntu 19.04, 18.04
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 4 months