[JBoss JIRA] (JBIDE-25068) working directory when running 'minishift version' may not exist
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25068?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25068:
---------------------------------------
I verified the patch during debugging, since I do not see easier way how to reproduce the bug. I put a breakpoint in the updated code, deleted the folder and checked that it will be re-created if it does not exist.
> working directory when running 'minishift version' may not exist
> ----------------------------------------------------------------
>
> Key: JBIDE-25068
> URL: https://issues.jboss.org/browse/JBIDE-25068
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, server
> Affects Versions: 4.5.1.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM3
>
>
> In rare situations, the working directory we've chosen (a temporary folder in metadata) when running minishift command may not exist.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24764) migrate fusetools job from fusesource jenkins to dev-platform jenkins
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24764?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-24764.
--------------------------------
> migrate fusetools job from fusesource jenkins to dev-platform jenkins
> ---------------------------------------------------------------------
>
> Key: JBIDE-24764
> URL: https://issues.jboss.org/browse/JBIDE-24764
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.1.AM3
>
> Attachments: dev-platform__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt, fuse-am3-building-OK.png, fuse-master-job-on-dev-platform-jenkins.png, fuse-master-job-on-fusesource-jenkins.png, fusesource__dev-platform__org.fusesource.ide.jmx.camel.tests.integration.diff.png, fusesource__org.fusesource.ide.jmx.camel.tests.integration_target_work%20sp(a)xn--c_-bja.metadata_.log.txt, throttle-concurrent.png, two_jobs_in_parallel.png
>
>
> {quote}
> Lars reenabled it https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> We are still using the one on fusesource jenkins right, it is the only place we have a "controlled job"
> for the migration to dev-platform, I don't know. Lars decided with you (?) (someone from Jboss tools team) to move to this CI
> don't know exactly pros and cons, Lars reported the advantages:
> * more slaves
> * faster
> * easier to manage with the other JBoss Tools job
> the issue is that it is not working:
> * our tests are failing too often when starting from a empty .m2 repository because some corrupted jars are downloaded
> * one test is failing
> * and a third issue now seems that it goes into timeout{quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24939) update target platform & Central to Oxygen.1
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24939?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-24939.
--------------------------------
Verified, closing.
> update target platform & Central to Oxygen.1
> --------------------------------------------
>
> Key: JBIDE-24939
> URL: https://issues.jboss.org/browse/JBIDE-24939
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.5.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.1.AM3
>
> Attachments: 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff-ignoreVersions.txt, 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff-ignoreVersions_sorted_no_featurejars_no_sources.txt, 4.70.2.Final_4.71.0.AM2-SNAPSHOT_p2diff.txt, p2diff.considerversions.txt, p2diff.ignoreversions.txt
>
>
> Issue to track changes to target platform after AM1.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25046) Can't find CDK for registry discovery when 2 connections are defined for CDK
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25046?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25046:
---------------------------------------
I would like someone to verify my verification steps: This is because I took steps to reproduce/verify that everything is working as [~jeffmaury] wrote in description, except I am having a little difference here. I will include also another step necessary (ie. cdk being started via cli beforehand).
1. EXEC: CDK 3 started in cli (to get url)
2. EXEC: Add OS 3 connection for admin (no registry url is set)
3. EXEC: Add OS 3 connection for developer (no registry url is set)
4. EXEC: Define CDK 3 (not 3.2+!) server adapter.
5. EXEC: Stop running CDK3 server adapter in cli
5. EXEC: Start CDK 3 via server adapter
6. ASSERT: CDK3 is started - PASS
7. ASSERT: OS 3 developer connection is updated (image registry url is set) - PASS
8. ASSERT: OS 3 admin connection is not updated (no image registry url) - PASS
9. EXEC: OS 3 admin connection discovery button is pressed
10. ASSERT: OS 3 admin connection image registry url is updated - PASS
You can see the difference here, as it is developer's connection that is updated with proper image registry url when cdk 3 is started in IDE, not admin's connection. I do not think this is a problem at all, or I am mistaken? Another question is if it should be also verified on new CDK server adapter (3.2+)? WDYT [~jeffmaury], [~adietish], [~rob.stryker]?
Devstudio: 11.1.0.AM3-v20171005-1232-B1225
CDK3: minishift v1.3.1+a2d3799, CDK v3.1.1-1
> Can't find CDK for registry discovery when 2 connections are defined for CDK
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25046
> URL: https://issues.jboss.org/browse/JBIDE-25046
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: cdk, cdk_server_adapter_, explorer, openshift, openshift_v3
> Fix For: 4.5.1.AM3
>
>
> EXEC: define an Openshift connection for CDK/admin
> EXEC: define an Openshift connection for CDK/developer
> EXEC: define a CDK3 server
> EXEC: start the CDK 3 server
> ASSERT: the CDK/admin OS3 connection is updated (registry not empty)
> ASSERT: the CDK/developer OS3 connection is not updated (registry empty)
> EXEC: on the CDK/developer OS3 connection, click the DIscover buttoon
> ASSERT: the registry URL is updated, not the error dialog is displayed
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months