[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-23136:
------------------------------------------
[~adietish] thank you for your comment!
Yes, we're doing the same. See [my comment above|https://issues.jboss.org/browse/JBIDE-23136?focusedCommentId=133522...]:
1) we're creating an image stream: !FedoraImageStream.png|thumbnail!
2) create Deployment Config
and this 2 step results an image with no tag
> Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-23136
> URL: https://issues.jboss.org/browse/JBIDE-23136
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Final
> Reporter: Marián Labuda
> Assignee: Dmitrii Bocharov
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.3.AM2
>
> Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png
>
>
> I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see:
> 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB
> Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411
> Steps to reproduce:
> - have a project with a file named {{Dockerfile}} with the following content (1 line):
> {code}
> FROM fedora:latest
> {code}
> - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}})
> - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}.
> - In the wizard, select the option to push the image to the registry (add a dummy port if needed)
> - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides a lot of packages
by Václav Kadlčík (JIRA)
[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ]
Václav Kadlčík commented on JBDS-4257:
--------------------------------------
just a terminology nit: the requires/provides in RPMs are not "packages" but "capabilities"
> rh-eclipse46-devstudio provides a lot of packages
> -------------------------------------------------
>
> Key: JBDS-4257
> URL: https://issues.jboss.org/browse/JBDS-4257
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.3.0.AM2
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Minor
> Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png
>
>
> I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
> !yum_install_rh-eclipse46.png|thumbnail!
> [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
> He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages.
> [^rh-eclipse46_provides.txt]
> [^rh-eclipse46-devstudio_provides.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides a lot of packages
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4257:
-------------------------------
Description:
I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
!yum_install_rh-eclipse46.png|thumbnail!
[~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages.
[^rh-eclipse46_provides.txt]
[^rh-eclipse46-devstudio_provides.txt]
was:
I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
!yum_install_rh-eclipse46.png|thumbnail!
[~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 providel 4 packages, devstudio provides 539 packages.
[^rh-eclipse46_provides.txt]
[^rh-eclipse46-devstudio_provides.txt]
> rh-eclipse46-devstudio provides a lot of packages
> -------------------------------------------------
>
> Key: JBDS-4257
> URL: https://issues.jboss.org/browse/JBDS-4257
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.3.0.AM2
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Minor
> Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png
>
>
> I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
> !yum_install_rh-eclipse46.png|thumbnail!
> [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
> He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages.
> [^rh-eclipse46_provides.txt]
> [^rh-eclipse46-devstudio_provides.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides a lot of packages
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4257:
-------------------------------
Description:
I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
!yum_install_rh-eclipse46.png|thumbnail!
[~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 providel 4 packages, devstudio provides 539 packages.
[^rh-eclipse46_provides.txt]
[^rh-eclipse46-devstudio_provides.txt]
was:
I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
!yum_install_rh-eclipse46.png|thumbnail!
[~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 providel 4 packages, devstudio provides 539 packages.
[^rh-eclipse46_provides.txt][^rh-eclipse46-devstudio_provides.txt]
> rh-eclipse46-devstudio provides a lot of packages
> -------------------------------------------------
>
> Key: JBDS-4257
> URL: https://issues.jboss.org/browse/JBDS-4257
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.3.0.AM2
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Minor
> Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png
>
>
> I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
> !yum_install_rh-eclipse46.png|thumbnail!
> [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
> He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 providel 4 packages, devstudio provides 539 packages.
> [^rh-eclipse46_provides.txt]
> [^rh-eclipse46-devstudio_provides.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides a lot of packages
by Lukáš Valach (JIRA)
Lukáš Valach created JBDS-4257:
----------------------------------
Summary: rh-eclipse46-devstudio provides a lot of packages
Key: JBDS-4257
URL: https://issues.jboss.org/browse/JBDS-4257
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: build, rpm
Affects Versions: 10.3.0.AM2
Environment: RHEL7
Reporter: Lukáš Valach
Assignee: Nick Boldt
Priority: Minor
Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png
I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
!yum_install_rh-eclipse46.png|thumbnail!
[~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 providel 4 packages, devstudio provides 539 packages.
[^rh-eclipse46_provides.txt][^rh-eclipse46-devstudio_provides.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-23733:
------------------------------------------
Before creating a PR with any change to ITests I will at first try to run them on CCI.
So lets say I have made a new test for cdi. My branch is cdi_newTest on rawagner fork of jbosstools-integration-tests repository. Before creating a PR I want to see if the new test is running fine on Mac/Linux/Windows. So I will run this job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... with TESTS_FORK set to "rawagner" and TEST_BRANCH to "cdi_newTest".
If we would group cdi,jsf,seam, batch to one javaee job how would I be able to run just cdi part to see if the change works fine on all platforms ? I guess this could be somehow configured but we QE dont divide the components based on which repo they are in - so currently javaee components are owned by 2 or 3 different people. So with the workflow described above we could be blocked by each other or we would have to allow parallel execution which seems a bit messy to me.
We could divide the QE jobs based on owner instead of repo - so my job would consist of browsersim,vpe,hibernate,livereload. But I think that job's name should express what components it is running and I have no idea what the name would look like :)
> Merge .smoke and .nightly integration jobs into a single job and run them weekly
> --------------------------------------------------------------------------------
>
> Key: JBIDE-23733
> URL: https://issues.jboss.org/browse/JBIDE-23733
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rastislav Wagner
> Fix For: 4.4.3.Final
>
>
> Purpose:
> a) easier maintenance of jobs / tests
> b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests
> c) more frequent full integration runs (rather than once per sprint, once per week)
> Tests to merge are in this view:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1024) SY - Fix SwitchYardEditorImplementationsTest
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1024:
----------------------------------------
Summary: SY - Fix SwitchYardEditorImplementationsTest
Key: JBTIS-1024
URL: https://issues.jboss.org/browse/JBTIS-1024
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: QE, switchyard
Affects Versions: 4.4.0.Final
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
Fix For: 4.4.0.Final
Attachments: org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.addDroolsImplementationWithNewJavaInterfaceTest.png
Error Message
No matching widget found with Matcher matching when all matchers match: [Matcher matching widget with the same type as or type extending class org.eclipse.swt.custom.CCombo]
class org.eclipse.swt.custom.CCombo with text 'EXECUTE'
Stacktrace
org.jboss.reddeer.core.exception.CoreLayerException: No matching widget found with Matcher matching when all matchers match: [Matcher matching widget with the same type as or type extending class org.eclipse.swt.custom.CCombo]
class org.eclipse.swt.custom.CCombo with text 'EXECUTE'
at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:183)
at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:136)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:101)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:71)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:56)
at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:47)
at org.jboss.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:103)
at org.jboss.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:78)
at org.jboss.reddeer.swt.widgets.AbstractWidget.<init>(AbstractWidget.java:41)
at org.jboss.tools.switchyard.reddeer.widget.DefaultCCombo.<init>(DefaultCCombo.java:32)
at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addItem(ImplementationKnowledgePage.java:135)
at org.jboss.tools.switchyard.reddeer.preference.implementation.ImplementationKnowledgePage.addOperation(ImplementationKnowledgePage.java:49)
at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.checkOperationsProperties(SwitchYardEditorImplementationsTest.java:732)
at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.checkDroolsOperationsProperties(SwitchYardEditorImplementationsTest.java:722)
at org.jboss.tools.switchyard.ui.bot.test.SwitchYardEditorImplementationsTest.addDroolsImplementationWithNewJavaInterfaceTest(SwitchYardEditorImplementationsTest.java:455)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months