[JBoss JIRA] (JBIDE-23547) OpenShift New and Noteworthy for 4.4.2.Final
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-23547:
----------------------------------
Summary: OpenShift New and Noteworthy for 4.4.2.Final
Key: JBIDE-23547
URL: https://issues.jboss.org/browse/JBIDE-23547
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: cdk, openshift
Reporter: Jeff MAURY
Priority: Critical
Search for your component's New and Noteworthy issues:
Queries:
* [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
* [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...]
* [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...]
* [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...]
If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them.
Document the ones relevant for OpenShift by submitting a pull request against:
* https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for OpenShift4.4.2.Final #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied.
If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue.
----
If there is nothing new or noteworthy for 4.4.2.Final since the AM3 release of OpenShift, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents.
If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.4.2.Final.adoc file here:
* https://github.com/jbosstools/jbosstools-website/tree/master/documentatio...
The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc.
However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.4.2.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-4201:
-------------------------------------
Lukas confirmed to me that the scenario of headless installation (as Nick pointed out, with the syntax of {code}java -jar /path/to/installer.jar /path/to/InstallConfigRecord.xml{code}) is tested. So I guess the only question that remains is if we want to treat this as a supported use case - let's wait for Rick on this one.
> CLI-only installation is available but does not provide necessary info
> ----------------------------------------------------------------------
>
> Key: JBDS-4201
> URL: https://issues.jboss.org/browse/JBDS-4201
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 10.2.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 10.x
>
> Attachments: InstallConfigRecord.xml
>
>
> I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected.
> Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it.
> My questions here are:
> - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens.
> - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4201:
------------------------------------
I can confirm that we are testing headless installation. It mean CLI installation with InstallConfigRecord.xml.
> CLI-only installation is available but does not provide necessary info
> ----------------------------------------------------------------------
>
> Key: JBDS-4201
> URL: https://issues.jboss.org/browse/JBDS-4201
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 10.2.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 10.x
>
> Attachments: InstallConfigRecord.xml
>
>
> I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected.
> Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it.
> My questions here are:
> - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens.
> - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4201:
-------------------------------
Comment: was deleted
(was: I can confirm that we are testing headless installation. It mean CLI installation with InstallConfigRecord.xml.)
> CLI-only installation is available but does not provide necessary info
> ----------------------------------------------------------------------
>
> Key: JBDS-4201
> URL: https://issues.jboss.org/browse/JBDS-4201
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 10.2.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 10.x
>
> Attachments: InstallConfigRecord.xml
>
>
> I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected.
> Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it.
> My questions here are:
> - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens.
> - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23384) Include integration-tests in staging and stable update sites
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23384?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23384:
---------------------------------------
[~nickboldt], I don't think we necessarily need the repo zip, but since others have it and you've already put some effort in it, let's do it. The PR looks fine.
> Include integration-tests in staging and stable update sites
> ------------------------------------------------------------
>
> Key: JBIDE-23384
> URL: https://issues.jboss.org/browse/JBIDE-23384
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: updatesite
> Affects Versions: 4.4.2.AM2
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.4.2.Final
>
>
> This will allow us the use case of running integration tests against the latest release of devstudio. This use case is required by EAP QE running our tests against their EAP development builds.
> Currently we have this repo:
> http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-t...
> We're referencing it from our root pom:
> https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po...
> And set up a repository definition for it.
> This allows us to run an individual test bundle.
> This is mostly useful to satisfy test dependencies - tests depend on RedDeer as a whole which is in the target platform. But most tests also have a RedDeer extension in the plugins directory:
> https://github.com/jbosstools/jbosstools-integration-tests/tree/master/pl...
> With that, let's move on to why it would be useful to have a stable repo for this, e.g. http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests/
> Imagine you want to run integration tests against the latest stable build. If you just checkout the integration tests and run a test plugin (using mvn verify), it will use everything from the latest nightly repos.
> So to use latest stable release (jbt 4.4.1.Final / devstudio 10.1.0.GA), you need a couple of things:
> 1. Checkout the corresponding branch of the integration tests - jbosstools-4.4.1.x in this case
> 2. Make sure the proper devstudio is used to test against:
> https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te...
> -Ddevstudio.repository=https://devstudio.redhat.com/10.0/stable/updates
> This also includes the TP, so RedDeer should be the correct version
> 3. Make sure the proper integration-tests repo is used for dependencies
> Now this is what we currently don't have. Our root pom will set up the snapshots repo:
> https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po...
> So that's why I would like to have a stable repo of this which I could use.
> There is a workaround - run "mvn install" on the whole integration-tests repo before you run your test. This will install the correct version in your local repo and that may be then used by your test. But maven will probably still prefer the newer versions from the snapshots repo that is set up in the pom.
> To give you an example what can break when you use the newest org.jboss.ide.eclipse.as.reddeer plugin, but run the EAP tests against devstudio 10.1.0.GA:
> The EAP 7 server adapter had 7.0 in the type name in 10.1.0.GA, but in current master it's 7.x (to accommodate for the upcoming EAP 7.1). So if you want to test EAP 7.0.1 CP candidate build against devstudio 10.1.0.GA it will fail on this.
> Sorry for the lengthy explanation, but I hope it's now clear why I'm requesting this.
> Also, I'd be happy to hear if you have some suggestions how to do it differently.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4201) CLI-only installation is available but does not provide necessary info
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-4201?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-4201:
-------------------------------------
This feature is provided by IzPack on which the installer is based. It's a good question whether or not this is supported. The answer is probably yes. [~lvalach], can you confirm, please?
> CLI-only installation is available but does not provide necessary info
> ----------------------------------------------------------------------
>
> Key: JBDS-4201
> URL: https://issues.jboss.org/browse/JBDS-4201
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 10.2.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 10.x
>
> Attachments: InstallConfigRecord.xml
>
>
> I had some feedback from another writer testing a procedure with devstudio. He was using a CLI-only VM and was confused because the installer worked but offered little information, as would be expected.
> Essentially, the non-GUI installation worked (java -jar devstudio_version.jar) but did not ask where to install devstudio, nor did it provide the default target folder it used. The GUI version asks if the user wants to deploy devstudio after the installation, but the non-GUI version does nothing. The resulting user experience was confusion, not knowing where devstudio was installed or how to start it.
> My questions here are:
> - is the non-GUI way a valid installation path? If yes, we should document it, and if not, we should mention it, either in the docs or when installation happens.
> - If the non-GUI installation is a valid path, it should replicate the questions in the wizard, such as where to install devstudio and which jdk to use, etc. The difference between the two installation paths causes confusion.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-23536:
----------------------------------
Summary: components.py should store the assigned user
Key: JBIDE-23536
URL: https://issues.jboss.org/browse/JBIDE-23536
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Affects Versions: 4.4.2.Final
Reporter: Jeff MAURY
Fix For: 4.4.3.AM1
The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23529) For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [openshift]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23529?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-23529.
------------------------------
Resolution: Done
> For JBIDE 4.4.2.Final: Prepare for 4.4.2.Final / 10.2.0.GA [openshift]
> ----------------------------------------------------------------------
>
> Key: JBIDE-23529
> URL: https://issues.jboss.org/browse/JBIDE-23529
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Friendly Jira Robot
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: task
> Fix For: 4.4.2.Final
>
>
> For JBIDE 4.4.2.Final [openshift]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: features plugins pom.xml pom.xml.orig README.md site tests *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: features plugins pom.xml pom.xml.orig README.md site tests *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for openshift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23516) Server Adapter: DC of debugged java application use nodejs debugging env var
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23516?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-23516.
---------------------------------
> Server Adapter: DC of debugged java application use nodejs debugging env var
> ----------------------------------------------------------------------------
>
> Key: JBIDE-23516
> URL: https://issues.jboss.org/browse/JBIDE-23516
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: debugging, openshift_v3, server_adapter
> Fix For: 4.4.2.Final
>
>
> When debugging an EAP application on OpenShift, deployment config is modified. In nodejs debugging there is added an environment variable DEV_MODE. For java debugging it is not necessary but I found it in deployment config. I compared deployment config before starting debugging and after and it was added by tooling.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4203) For JBDS 10.2.0.GA: Prepare for 4.4.2.Final / 10.2.0.GA [installer]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4203?page=com.atlassian.jira.plugin.... ]
Jeff MAURY reassigned JBDS-4203:
--------------------------------
Assignee: Denis Golovin
> For JBDS 10.2.0.GA: Prepare for 4.4.2.Final / 10.2.0.GA [installer]
> -------------------------------------------------------------------
>
> Key: JBDS-4203
> URL: https://issues.jboss.org/browse/JBDS-4203
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: installer
> Reporter: Friendly Jira Robot
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: task
> Fix For: 10.2.0.GA
>
>
> For JBDS 10.2.0.GA [installer]: Please perform the following tasks: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.2.Final or 10.2.0.GA [Unresolved JIRAs with fixVersion = 4.4.2.Final, 10.2.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.2.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.2.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: features installer LICENSE.txt p2-director plugins pom.xml pom.xml.orig README.adoc results rpm site *{color:orange}4.4.2.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.2.x{color}* branch: {code} git checkout master git pull origin master git checkout -b jbosstools-4.4.2.x git push origin jbosstools-4.4.2.x {code} Now, your root pom will use parent pom version: features installer LICENSE.txt p2-director plugins pom.xml pom.xml.orig README.adoc results rpm site *{color:blue}4.4.2.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.2.x{color}* branch, too. 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months