[JBoss JIRA] (JBIDE-24689) For JBIDE 4.5.0.Final: Prepare for 4.5.0.Final / 11.0.0.GA [fusetools]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24689?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24689:
------------------------------------
{quote}Nick Boldt latest minimal and maximal version are the same, is it normal?
{quote}
Yes, until we have an Oxygen.0 to build and an Oxygen.N to test (ie., we'll move MAX to Oxygen.1 in Aug/Sept, then to Oxygen.2, .3, etc.)
> For JBIDE 4.5.0.Final: Prepare for 4.5.0.Final / 11.0.0.GA [fusetools]
> ----------------------------------------------------------------------
>
> Key: JBIDE-24689
> URL: https://issues.jboss.org/browse/JBIDE-24689
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: fusetools
> Reporter: Nick Boldt
> Assignee: Aurélien Pupier
> Priority: Blocker
> Labels: task
> Fix For: 4.5.0.Final
>
>
> For JBIDE 4.5.0.Final [fusetools]: Please perform the following tasks:
>
> 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.5.0.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.5.0.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.5.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
>
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
>
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.0.AM1-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.0.AM1-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT
> {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 fusetools 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)
8 years, 8 months
[JBoss JIRA] (JBIDE-24561) replace TextFinderPublisher w/ new customizable log-parser plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24561?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24561:
-------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM2)
> replace TextFinderPublisher w/ new customizable log-parser plugin
> -----------------------------------------------------------------
>
> Key: JBIDE-24561
> URL: https://issues.jboss.org/browse/JBIDE-24561
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.Final
>
>
> Description setter plugin seems to take 80 mins to parse the console log.
> So maybe we don't need this any more? Seems a waste of time, if the overall build takes 2h35, this is more than 50% of the time taken!
> {code}
> 10:05:56 Terminating xvnc.
> 10:05:56 $ /usr/bin/vncserver -kill :33
> 10:05:57 Killing Xvnc process ID 9997
> 10:05:59 Archiving artifacts
> 10:05:59 Checking console output
> 11:26:12 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT'
> 11:26:12 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com
> {code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> {code}
> 10:04:53 Terminating xvnc.
> 10:04:53 $ /usr/bin/vncserver -kill :35
> 10:04:54 Killing Xvnc process ID 9993
> 10:04:56 Archiving artifacts
> 10:04:57 Checking console output
> 11:24:02 [description-setter] Description set: TP Version: 4.70.0.AM1-SNAPSHOT'
> 11:24:02 Sending e-mails to: jbosstools-builds(a)lists.jboss.org mistria(a)redhat.com nboldt(a)redhat.com nickboldt(a)gmail.com{code} -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24518) change github check frequency for CI builds from 8hrs to 20 mins
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24518?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24518:
-------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM2)
> change github check frequency for CI builds from 8hrs to 20 mins
> ----------------------------------------------------------------
>
> Key: JBIDE-24518
> URL: https://issues.jboss.org/browse/JBIDE-24518
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.Final
>
>
> Currently the jbosstools-* component project builds run every 8hrs, with a nightly buildflow also triggering a rebuild. But since breaking changes are frequently NOT fixed quickly enough as devs cannot or will not kick their own builds, we need to implement a better strategy to check github for changes more often.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23322) create mojo that takes as input a list of URLs and a name, and generates a composite site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23322?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23322:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.AM2)
> create mojo that takes as input a list of URLs and a name, and generates a composite site
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-23322
> URL: https://issues.jboss.org/browse/JBIDE-23322
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.x
>
>
> In https://issues.jboss.org/browse/WINDUP-1189 it was requested that tycho builds be able to produce a simple composite site, using as input 1 or more URLs.
> So, to generalize this for use by other projects, we need a mojo that can be configured with a set of URLs, and a site name, in order to produce three files:
> {code}
> target/composite/compositeContent.xml
> target/composite/compositeArtifacts.xml
> target/composite/p2.index (like https://devstudio.jboss.com/10.0/stable/updates/p2.index )
> {code}
> Secondary use case would be to generate a composite site from subfolders in an existing folder, eg., to replace https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u...
> So we could use this to create composite sites in folders like:
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (invalid composite points to ../, which has no composite either)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/integrati... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ (up to date)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/core/ (invalid composite points to ../, which has no composite either)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/cent... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/earl... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/inte... (no composite)
> * http://download.jboss.org/jbosstools/static/neon/development/updates/core... (composite out of date)
> But also to point to remote (/stable/) URLs from pointer sites, like:
> * http://download.jboss.org/jbosstools/neon/stable/updates/compositeArtifac... (up to date, name = JBoss Tools - Core + Central Update Site)
> * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/stable/updates/coretests/compos... (up to date, name = JBoss Tools 4.4.2.Final Stable Release Tests Site)
> * http://download.jboss.org/jbosstools/neon/stable/updates/integration-tests (404'd)
> * http://download.jboss.org/jbosstools/neon/development/updates/compositeAr... (up to date, name = JBoss Tools - Core + Central Update Site)
> * http://download.jboss.org/jbosstools/neon/development/updates/central/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/development/updates/earlyaccess/ (composite missing)
> * http://download.jboss.org/jbosstools/neon/development/updates/coretests/c... (out of date, points to 4.4.0.Alpha1)
> * http://download.jboss.org/jbosstools/neon/development/updates/integration... (404'd)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBDS-4448) JBDS install failure with no explanation
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4448?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4448:
--------------------------------
Fix Version/s: 11.0.0.GA
> JBDS install failure with no explanation
> -----------------------------------------
>
> Key: JBDS-4448
> URL: https://issues.jboss.org/browse/JBDS-4448
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.4.0.GA
> Environment: Mac, using DevSuite installer 1.4.1 GA
> Reporter: Bob Davis
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 11.0.0.GA
>
> Attachments: Screen Shot 2017-06-26 at 2.09.01 PM.png, install.log
>
>
> Installing RED HAT JBOSS DEVELOPER STUDIO10.4.0.GA failed, and no explanation or remediation such as "try again" or "remove ...", etc. was offered. The end user is stuck with no way out.
> Additionally, the "next step" displayed is "Get Started", but there is no way to get there, no button to "Next", or any indication of how to move forward to it.
> Quitting is the only option.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months