[JBoss JIRA] (JBIDE-24125) Import wizard: adapt ITs to changes introduced in JBIDE-24048
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24125?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-24125:
------------------------------------
We have 4 cases that should be covered by tests:
* there's a folder with the name of the clone but it's no git repo
* there's a folder with the name of the clone, it's a git folder but remote is not pointing to the same source, so it looks like it's not the right source
* there's a folder with the same name as the clone, it's a git repo but there's no remote at all, looks like it's not the right source
* there's a folder with the same name, it's a git repo, it points to the same source as what's being built in OpenShift, but the branch that we want to check does not exist yet
> Import wizard: adapt ITs to changes introduced in JBIDE-24048
> -------------------------------------------------------------
>
> Key: JBIDE-24125
> URL: https://issues.jboss.org/browse/JBIDE-24125
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Assignee: Radim Hopp
>
> In JBIDE-24048 changes have been done to the import wizard. We should change the ITs to cover these changes.
> @rhopp @bdshadow can you please test this since it's a rather larger change and provides changes in how it behaves?
> * Validations were extended:
> ** is the existing clone destination a git repo?
> ** is the existing clone destination a clone of the source that is used in OpenShift?
> * We now also ask the user if he wants to checkout the correct branch (the one that's used in OpenShift) in the existing git repo
> * UI was slightly changed according to requests made in JBIDE-21935
> * We now also close the wizard dialog before executing the import. This should allow the user to continue working.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-23869:
------------------------------------
Steps to Reproduce:
- install JBDS with the CDK (using the DevStudio installer for instance, so using CDK 2.x)
- Deploy a FIS project on OpenShift (see https://www.youtube.com/watch?v=Ko4mNaQsCvI )
- Try to connect to the jolkia instance through JMX Navigator, right-click Add connection... and use Jolokia
- use something like: https://10.1.2.2:8443/api/v1/namespaces/test1/pods/camel-ose-springboot-x... without checking SSL certificates
was:
- Deploy a FIS project on openShift
- Try to connect to the jolkia instance through JMX Navigator, right-click Add connection... and use Jolokia
- use somethign like: https://10.1.2.2:8443/api/v1/namespaces/test1/pods/camel-ose-springboot-x... withotu checking SSl certificates
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.4.4.AM2
>
> Attachments: image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-23869:
------------------------------------
Steps to Reproduce:
- install JBDS with the CDK (using the DevStudio installer for instance, so using CDK 2.x)
- Deploy a FIS project on OpenShift (see https://www.youtube.com/watch?v=Ko4mNaQsCvI )
- Try to connect to the jolokia instance through JMX Navigator, right-click Add connection... and use Jolokia
- use something like: https://10.1.2.2:8443/api/v1/namespaces/test1/pods/camel-ose-springboot-x... without checking SSL certificates
was:
- install JBDS with the CDK (using the DevStudio installer for instance, so using CDK 2.x)
- Deploy a FIS project on OpenShift (see https://www.youtube.com/watch?v=Ko4mNaQsCvI )
- Try to connect to the jolkia instance through JMX Navigator, right-click Add connection... and use Jolokia
- use something like: https://10.1.2.2:8443/api/v1/namespaces/test1/pods/camel-ose-springboot-x... without checking SSL certificates
> ClassCastException with Jolokia connection
> ------------------------------------------
>
> Key: JBIDE-23869
> URL: https://issues.jboss.org/browse/JBIDE-23869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, openshift
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: jmx, jolokia, openshift
> Fix For: 4.4.4.AM2
>
> Attachments: image-2017-02-06-13-54-27-708.png
>
>
> !image-2017-02-06-13-54-27-708.png|thumbnail!
> {noformat}
> !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767
> !MESSAGE An internal error occurred during: "Connect Job".
> !STACK 0
> java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long
> at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:195)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24133) org.jboss.tools.central.reddeer 2.1.3.v20170130-1737 requires 'bundle org.jboss.tools.runtime.reddeer [3.2.3, 3.3.0)' but it could not be found
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24133?page=com.atlassian.jira.plugi... ]
Martin Malina reassigned JBIDE-24133:
-------------------------------------
Assignee: Jeff MAURY (was: Martin Malina)
Jeff, can you merge this?
> org.jboss.tools.central.reddeer 2.1.3.v20170130-1737 requires 'bundle org.jboss.tools.runtime.reddeer [3.2.3,3.3.0)' but it could not be found
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24133
> URL: https://issues.jboss.org/browse/JBIDE-24133
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 4.4.4.AM2
>
>
> Problem running the composite install job [1] - can't find org.jboss.tools.runtime.reddeer [3.2.3,3.3.0).
> {code}
> [p2.dir] Installation failed.
> [p2.dir] !SESSION 2017-03-24 21:14:43.235 -----------------------------------------------
> [p2.dir] eclipse.buildId=4.7.0.I20170126-1030
> --
> [p2.dir] !MESSAGE Cannot complete the install because one or more required items could not be found.
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2017-03-24 21:15:23.659
> [p2.dir] !MESSAGE Software being installed: JBoss Tools - Tests - JBoss Central Developer Resources 2.1.3.v20170130-1737 (org.jboss.tools.central.test.feature.source.feature.group 2.1.3.v20170130-1737)
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2017-03-24 21:15:23.659
> [p2.dir] !MESSAGE Missing requirement: Central Reddeer 2.1.3.v20170130-1737 (org.jboss.tools.central.reddeer 2.1.3.v20170130-1737) requires 'bundle org.jboss.tools.runtime.reddeer [3.2.3,3.3.0)' but it could not be found
> [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2017-03-24 21:15:23.659
> [p2.dir] !MESSAGE Cannot satisfy dependency:
> [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2017-03-24 21:15:23.659
> [p2.dir] !MESSAGE From: JBoss Tools - Tests - JBoss Central 2.1.3.v20170130-1737 (org.jboss.tools.central.test.feature.feature.group 2.1.3.v20170130-1737)
> --
> [p2.dir] !MESSAGE Cannot satisfy dependency:
> [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2017-03-24 21:15:23.659
> [p2.dir] !MESSAGE From: JBoss Tools - Tests - JBoss Central Developer Resources 2.1.3.v20170130-1737 (org.jboss.tools.central.test.feature.source.feature.group 2.1.3.v20170130-1737)
> --
> [p2.dir] Cannot complete the install because one or more required items could not be found.
> [p2.dir] Software being installed: JBoss Tools - Tests - JBoss Central Developer Resources 2.1.3.v20170130-1737 (org.jboss.tools.central.test.feature.source.feature.group 2.1.3.v20170130-1737)
> [p2.dir] Missing requirement: Central Reddeer 2.1.3.v20170130-1737 (org.jboss.tools.central.reddeer 2.1.3.v20170130-1737) requires 'bundle org.jboss.tools.runtime.reddeer [3.2.3,3.3.0)' but it could not be found
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: JBoss Tools - Tests - JBoss Central 2.1.3.v20170130-1737 (org.jboss.tools.central.test.feature.feature.group 2.1.3.v20170130-1737)
> [p2.dir] To: org.jboss.tools.central.reddeer [2.1.3.v20170130-1737]
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: JBoss Tools - Tests - JBoss Central Developer Resources 2.1.3.v20170130-1737 (org.jboss.tools.central.test.feature.source.feature.group 2.1.3.v20170130-1737)
> [p2.dir] To: org.jboss.tools.central.test.feature.feature.group [2.1.3.v20170130-1737]
> [p2.dir] Application failed, log file location: /mnt/hudson_workspace/workspace/jbosstools-composite-install_master/eclipse/configuration/1490390083328.log
> !SESSION 2017-03-24 21:14:40.982 -----------------------------------------------{code}
> -- [1] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/jbosstools-compo...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24135) Clean up old vscode builds and establish file retention / cleanup policy
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24135?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-24135:
-------------------------------------
[~nickboldt] see https://github.com/redhat-developer/vscode-java/issues
> Clean up old vscode builds and establish file retention / cleanup policy
> ------------------------------------------------------------------------
>
> Key: JBIDE-24135
> URL: https://issues.jboss.org/browse/JBIDE-24135
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Fix For: 4.4.4.AM3
>
>
> Discovered today that there are many jdt-language-server builds in http://download.jboss.org/jbosstools/static/vscode/ and since many of these predate the migration to eclipse, rename, and reversioning of the project, it would probably make sense to delete these obsolete artifacts.
> * java-server 1.0.x
> * java-server 0.1.x
> * jdt-language-server 0.1 older than 4 weeks ago
> Since the /static/ folder is reserved for permanent artifacts that will be Akamai mirrored for performance, and since these biweekly updates are NOT permanent stable releases, we might want to consider using a different folder, such as:
> /neon/snapshots/vscode
> /neon/integration/vscode
> etc.
> Going forward, we need to establish how often to delete old artifacts/builds. If builds are not conforming to the schema used by jbosstools-* projects, then a new tool for cleanup will need to be created.
> Today, build folders are automatically deleted when they're too old, eg., from http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer... if they conform to a datestamp like http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24135) Clean up old vscode builds and establish file retention / cleanup policy
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24135?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24135:
------------------------------------
BTW, what's the issue tracker for vscode? Eclipse bugzilla? this JIRA? something else? cc: [~fbricon] [~gercan]
> Clean up old vscode builds and establish file retention / cleanup policy
> ------------------------------------------------------------------------
>
> Key: JBIDE-24135
> URL: https://issues.jboss.org/browse/JBIDE-24135
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Fix For: 4.4.4.AM3
>
>
> Discovered today that there are many jdt-language-server builds in http://download.jboss.org/jbosstools/static/vscode/ and since many of these predate the migration to eclipse, rename, and reversioning of the project, it would probably make sense to delete these obsolete artifacts.
> * java-server 1.0.x
> * java-server 0.1.x
> * jdt-language-server 0.1 older than 4 weeks ago
> Since the /static/ folder is reserved for permanent artifacts that will be Akamai mirrored for performance, and since these biweekly updates are NOT permanent stable releases, we might want to consider using a different folder, such as:
> /neon/snapshots/vscode
> /neon/integration/vscode
> etc.
> Going forward, we need to establish how often to delete old artifacts/builds. If builds are not conforming to the schema used by jbosstools-* projects, then a new tool for cleanup will need to be created.
> Today, build folders are automatically deleted when they're too old, eg., from http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer... if they conform to a datestamp like http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24135) Clean up old vscode builds and establish file retention / cleanup policy
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24135?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24135:
------------------------------------
I suspect your definition of "permanent" and "stable" are not the same as mine.
If it's a supported release [1] with a lifecycle of customer support and dates when end of service levels occur, then it can go in /static/ because it's permanent & stable.
If it's neither permanent nor stable... it should go somewhere else.
[1] https://access.redhat.com/support/policy/updates/jboss_notes
> Clean up old vscode builds and establish file retention / cleanup policy
> ------------------------------------------------------------------------
>
> Key: JBIDE-24135
> URL: https://issues.jboss.org/browse/JBIDE-24135
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Fix For: 4.4.4.AM3
>
>
> Discovered today that there are many jdt-language-server builds in http://download.jboss.org/jbosstools/static/vscode/ and since many of these predate the migration to eclipse, rename, and reversioning of the project, it would probably make sense to delete these obsolete artifacts.
> * java-server 1.0.x
> * java-server 0.1.x
> * jdt-language-server 0.1 older than 4 weeks ago
> Since the /static/ folder is reserved for permanent artifacts that will be Akamai mirrored for performance, and since these biweekly updates are NOT permanent stable releases, we might want to consider using a different folder, such as:
> /neon/snapshots/vscode
> /neon/integration/vscode
> etc.
> Going forward, we need to establish how often to delete old artifacts/builds. If builds are not conforming to the schema used by jbosstools-* projects, then a new tool for cleanup will need to be created.
> Today, build folders are automatically deleted when they're too old, eg., from http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer... if they conform to a datestamp like http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years