[JBoss JIRA] (JBIDE-20843) enable automated cleanup for versionwatch reports
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-20843:
----------------------------------
Summary: enable automated cleanup for versionwatch reports
Key: JBIDE-20843
URL: https://issues.jboss.org/browse/JBIDE-20843
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.3.0.CR1, 4.4.0.Alpha1
Reporter: Nick Boldt
Currently, versionwatch dumps 4 log files into a folder; 1000s of builds later, the folder is unmanageable.
So, migrate to use rsync.sh instead.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-20779) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20779?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-20779.
------------------------------
Resolution: Done
* versionwatch updated to new version 0.4.100 (in prep for fixes in master such as JBDS-3531)
* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwat... upadted to include versions of JBDS (9|10) instead of (8|9)
* http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwatc... >= 2879
* output: http://download.jboss.org/jbosstools/neon/snapshots/builds/devstudio.vers...
* build-ci updated to 4.4.0.Alpha1
* new job created: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-ci_...
* http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-ci_4... >=1
* output: https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20779
> URL: https://issues.jboss.org/browse/JBIDE-20779
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks:
> 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.)
> Otherwise:
> 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT
> {code}
> 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20803 at 9/30/15 12:34 PM:
--------------------------------------------------------------
{quote}
a) it is mixing a stable release with snapshots
{quote}
Actually, it's a STAGING / CI site prior to release. If it was the released site, you'd see 9.0, not 9.0.0.GA.
But yes, the long URL shouldn't appear once we're out of CI / staging. In fact, it doesn't.
{code:title=https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L152}
jboss.discovery.site.integration-stack.url|devstudio|9.0=https://devstudi...
{code}
Looking at the section of the file I think you were referring to, I see that we've already fixed the problem you were reprting since the URL for JBDS IS discovery is now much simpler - https://devstudio.redhat.com/9.0/staging/updates/
{code:title=https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L133-L141}
### when staging 9.0.0.GA (CR2)
jboss.discovery.directory.url|devstudio|9.0.0.GA=https://devstudio.redhat...
jboss.discovery.site.url|devstudio|9.0.0.GA=https://devstudio.redhat.com/...
jboss.discovery.earlyaccess.site.url|devstudio|9.0.0.GA=https://devstudio...
# 4.3.mars version of devstudio-earlyaccess.properties should be edited here, so the discovery job can fetch it: https://devstudio.redhat.com/9.0/snapshots/updates/earlyaccess.properties...
jboss.discovery.earlyaccess.list.url|devstudio|9.0.0.GA=https://devstudio...
# JBDSIS is not yet live so point at latest JBDS site instead
#jboss.discovery.site.integration-stack.url|devstudio|9.0.0.GA=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/
jboss.discovery.site.integration-stack.url|devstudio|9.0.0.GA=https://dev...
{code}
Anything left to do in this JIRA? I think it's done, other than debating the correct use & interpretation of the CI, staging, and release (development or stable) blocks in the ide-config.properties file.
was (Author: nickboldt):
{quote}
a) it is mixing a stable release with snapshots
{quote}
Actually, it's a STAGING / CI site prior to release. If it was the released site, you'd see 9.0, not 9.0.0.GA.
But yes, the long URL shouldn't appear once we're out of CI / staging. In fact, it doesn't.
{code:title=https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L152}
jboss.discovery.site.integration-stack.url|devstudio|9.0=https://devstudi...
{code}
Anything left to do in this JIRA? I think it's done, other than debating the correct use & interpretation of the CI, staging, and release (development or stable) blocks in the ide-config.properties file.
> script process for merging IS jars into JBT/JBDS discovery sites
> ----------------------------------------------------------------
>
> Key: JBIDE-20803
> URL: https://issues.jboss.org/browse/JBIDE-20803
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, discovery, integration-platform
> Affects Versions: 4.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Final
>
>
> Need to document and script how to get the IS jars into the JBT/JBDS discovery sites.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20803:
------------------------------------
{quote}
a) it is mixing a stable release with snapshots
{quote}
Actually, it's a STAGING / CI site prior to release. If it was the released site, you'd see 9.0, not 9.0.0.GA.
But yes, the long URL shouldn't appear once we're out of CI / staging. In fact, it doesn't.
{code:title=https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L152}
jboss.discovery.site.integration-stack.url|devstudio|9.0=https://devstudi...
{code}
Anything left to do in this JIRA? I think it's done, other than debating the correct use & interpretation of the CI, staging, and release (development or stable) blocks in the ide-config.properties file.
> script process for merging IS jars into JBT/JBDS discovery sites
> ----------------------------------------------------------------
>
> Key: JBIDE-20803
> URL: https://issues.jboss.org/browse/JBIDE-20803
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, discovery, integration-platform
> Affects Versions: 4.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Final
>
>
> Need to document and script how to get the IS jars into the JBT/JBDS discovery sites.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBDS-3533) Unable to update/install the plug-ins
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3533?page=com.atlassian.jira.plugin.... ]
Mickael Istria reassigned JBDS-3533:
------------------------------------
Assignee: Denis Golovin (was: Mickael Istria)
> Unable to update/install the plug-ins
> -------------------------------------
>
> Key: JBDS-3533
> URL: https://issues.jboss.org/browse/JBDS-3533
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.GA
> Environment: Development
> Reporter: Vikram Jammula
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 9.x
>
> Attachments: check Updates.png, security.jpg
>
>
> An error occurred while collecting items to be installed
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
> No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months