[JBoss JIRA] (JBIDE-23031) OpenShift can't push Docker Images with latest Docker Neon.1 bits
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23031?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-23031:
---------------------------------------
[~jjohnstn] moved this class in the public API in https://bugs.eclipse.org/bugs/show_bug.cgi?id=495251
Since Neon.1 is a minor release, we could not change the {{IDockerConnection}} interface, so you must cast the Docker connection instance into an {{IDockerConnection2}} to get access to the methods that will provide you with the progress handler associated with the PUSH operation:
{{IDockerConnection2.getDefaultPushImageProgressHandler(String image)}}
> OpenShift can't push Docker Images with latest Docker Neon.1 bits
> -----------------------------------------------------------------
>
> Key: JBIDE-23031
> URL: https://issues.jboss.org/browse/JBIDE-23031
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: docker, openshift
> Environment: DevStudio 10.1.0.AM3
> Docker Tooling 2.1.0.201608221023
> Reporter: Fred Bricon
> Priority: Blocker
>
> After installing Docker Tooling 2.1.0.201608221023 on top of Devstudio 10.1.0.AM3, when I try to push a docker image to openshift, I get this error:
> {noformat}
> java.lang.NoClassDefFoundError: org/eclipse/linuxtools/internal/docker/ui/views/ImagePushProgressHandler
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:66)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler cannot be found by org.jboss.tools.openshift.ui_3.3.0.v20160812-0126
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 3 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-14697) User library fileset cannot be modified
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14697?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-14697.
---------------------------------
Resolution: Done
I'm not able to replicate teh FNFE currently. This is fixed and the commit message is for JBIDE-22970
> User library fileset cannot be modified
> ---------------------------------------
>
> Key: JBIDE-14697
> URL: https://issues.jboss.org/browse/JBIDE-14697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: archives
> Affects Versions: 4.1.0.Beta1
> Reporter: Jaroslav Jankovič
> Assignee: Rob Stryker
> Fix For: 4.4.1.Final
>
>
> STEP: prepare two library filesets, lets say myLib1, myLib2 via preferences (Java -> Build Path -> User Libraries)
> STEP: create project with archives support
> STEP: create some archive in the project
> STEP: add new user library fileset in the archive (myLib1)
> STEP: select myLib1 in archives explorer, invoke its context menu and select Edit fileset
> STEP: in "User Library Fileset Wizard" dialog select myLib2, confirm it
> FAIL: there is still myLib in archives explorer, not myLib2 as it should be
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23029:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Integration tests: Tests should be able to run individually
> -----------------------------------------------------------
>
> Key: JBIDE-23029
> URL: https://issues.jboss.org/browse/JBIDE-23029
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.x
>
>
> We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need).
> This is even more true since running the whole suite is a lengthy task.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23029:
-------------------------------------
Fix Version/s: 4.4.x
(was: 4.5.x)
> Integration tests: Tests should be able to run individually
> -----------------------------------------------------------
>
> Key: JBIDE-23029
> URL: https://issues.jboss.org/browse/JBIDE-23029
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.x
>
>
> We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need).
> This is even more true since running the whole suite is a lengthy task.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23026) Integration tests: improve test stability
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23026?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23026:
-------------------------------------
Fix Version/s: 4.5.x
(was: 4.4.x)
> Integration tests: improve test stability
> -----------------------------------------
>
> Key: JBIDE-23026
> URL: https://issues.jboss.org/browse/JBIDE-23026
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.5.x
>
>
> There are several impediments to the test stability:
> * tests dont set up their env individually
> * some tests assert the oc binary, but this binary is not the same across platforms (oc, oc.exe, etc): org.jboss.tools.openshift.reddeer.requirement.OCBinary et org.jboss.tools.openshift.reddeer.utils.OpenShiftLabel
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23034) Rob Stryker PDD Work
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-23034:
-----------------------------------
Summary: Rob Stryker PDD Work
Key: JBIDE-23034
URL: https://issues.jboss.org/browse/JBIDE-23034
Project: Tools (JBoss Tools)
Issue Type: Task
Components: upstream
Affects Versions: 4.4.1.AM3
Reporter: Rob Stryker
Work to get the PDD document complete with devstudio stories.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23033) Spring Planning Script
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23033?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-23033:
--------------------------------
Fix Version/s: 4.4.1.AM3
Story Points: 4
Sprint: devex #119 August 2016
> Spring Planning Script
> ----------------------
>
> Key: JBIDE-23033
> URL: https://issues.jboss.org/browse/JBIDE-23033
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.1.AM3
>
>
> A script for the sprint planning meeting should be made. This script should help facilitate the following goals:
> 1) Devs should give a general idea of the main issues they are targeting for the sprint
> 2) Devs should indicate if they are fully booked with top-priority issues, or can bump some for others who need help
> 3) Devs should indicate if they have critical or major issues that need help that are not targeted to this sprint
> 4) QE, having more experience using the tools every day for months in both clean and dirty workspaces, should act partly as a project owner
> 4a) QE should list what they perceive as the most troublesome or annoying issues for the component they test (or other components)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23033) Spring Planning Script
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23033?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-23033:
--------------------------------
Issue Type: Task (was: Feature Request)
> Spring Planning Script
> ----------------------
>
> Key: JBIDE-23033
> URL: https://issues.jboss.org/browse/JBIDE-23033
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.1.AM3
>
>
> A script for the sprint planning meeting should be made. This script should help facilitate the following goals:
> 1) Devs should give a general idea of the main issues they are targeting for the sprint
> 2) Devs should indicate if they are fully booked with top-priority issues, or can bump some for others who need help
> 3) Devs should indicate if they have critical or major issues that need help that are not targeted to this sprint
> 4) QE, having more experience using the tools every day for months in both clean and dirty workspaces, should act partly as a project owner
> 4a) QE should list what they perceive as the most troublesome or annoying issues for the component they test (or other components)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months