[JBoss JIRA] (JBIDE-23978) OpenShift New and Noteworthy for 4.4.3.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23978?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23978:
-------------------------------
Fix Version/s: 4.4.3.Final
> OpenShift New and Noteworthy for 4.4.3.Final
> -----------------------------------------------------
>
> Key: JBIDE-23978
> URL: https://issues.jboss.org/browse/JBIDE-23978
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdk, openshift
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.3.Final
>
>
> Andre Dietisheim,
> 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... {code}JBIDE-23968 #comment Create N&N for OpenShift 4.4.3.Final #close{code}... 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.3.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.3.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.3.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23978) OpenShift New and Noteworthy for 4.4.3.Final
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23978?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-23978.
------------------------------
Resolution: Done
> OpenShift New and Noteworthy for 4.4.3.Final
> -----------------------------------------------------
>
> Key: JBIDE-23978
> URL: https://issues.jboss.org/browse/JBIDE-23978
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdk, openshift
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.3.Final
>
>
> Andre Dietisheim,
> 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... {code}JBIDE-23968 #comment Create N&N for OpenShift 4.4.3.Final #close{code}... 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.3.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.3.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.3.Final.adoc file, adding: {code}page-include-previous: false{code}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23882:
------------------------------------
You probably only need to run against the EA repo, since it's a superset of the Central one. But for 10.4 rpm, you should use the _4.4.neon URLs, since _master is now for 11.0 (Oxygen).
You could also have a second job that runs against the Integration Stack site - since that changes at a different cadence than jbt/ds, it ought to be a separate job that runs on a different frequency.
Hope that helps! (I posted similar comments in JBDS-4263.)
> Automate test of installation of software from Red Hat Central into devstudio RPM
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23882
> URL: https://issues.jboss.org/browse/JBIDE-23882
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Environment: RHEL7, devstudio RPM
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Fix For: 4.4.4.AM1
>
>
> We need to catch problems like in JBDS-4263.
> [~lvalach] said: {quote}
> I think I should automate test of installation from Central, because this procedure is quite time consuming.
> {quote}
> [~nickboldt] said: {quote}
> before you do that might want to look at the existing automated tests we have:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g....
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p....
> of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root
> maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally
> so ... partial automation
> {quote}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month