[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23036:
------------------------------------
With one -1, one +1, and a couple of +?? this has been postponed to the next sprint.
For the current sprint, we'll instead use the existing process for TP updates for Docker Tools *tomorrow* and _if needed_ again *next Wed*.
> Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23036
> URL: https://issues.jboss.org/browse/JBIDE-23036
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, openshift, target-platform
> Affects Versions: 4.4.1.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM1
>
>
> In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular:
> * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror)
> * remove docker/vagrant tooling from target platform
> * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23031) OpenShift can't push Docker Images with latest Docker Neon.1 bits
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23031?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23031:
-------------------------------
Sprint: devex #119 August 2016
> 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
> Fix For: 4.4.1.Final
>
>
> 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-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-23036:
----------------------------------------
FWIW, I dislike this idea. What we need is not multiple ways, sources, strategies to deal with dependency management nor a new way to spread out how we define dependencies; we need more agility for TP. IMO, fixing JBIDE-19911 would be much more reliable and generic.
> Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23036
> URL: https://issues.jboss.org/browse/JBIDE-23036
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, openshift, target-platform
> Affects Versions: 4.4.1.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular:
> * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror)
> * remove docker/vagrant tooling from target platform
> * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions
--
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 Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-23029:
---------------------------------------
Running single test could be sufficient while creating a new test but in the end it will run in suite (all tests suite or smoke suite). If you want to run test individually for some purpose, there should be created a requirement for connection AND/OR project which would set up a connection with a project for you automatically and it would be usable with annotation. For more reference about requirements in RedDeer see https://github.com/jboss-reddeer/reddeer/wiki/Requirements. I suggest creating a requirement configurable with XML file (rd.config property) and using it with some annotation on your test class, e.g. @SetUpOpenShift. To use connection details (such as username, server or project) it is possible to inject requirement properties/attributes into fields in your code. And it's important to don't forget add RunWith annotation with RedDeerSuite on top of a class, to run a test with RedDeer runner.
> 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