[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:
-------------------------------------
Well technically speaking, most of the files are stable releases. We release ~ once every 2 weeks. *Some* binaries may not be actual releases, more like failed attempts, this is something we could check with the vscode-java tagged versions and select the ones to prune.
But if you really really want to clear some space, I guess we can start pruning the non-eclipse ones by now.
The risk, however unlikely, is for someone having installed vscode-java a few months ago and hasn't open a java file in vscode until now, or hasn't upgraded. Her java extension would fail to initialize
> 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-23833) Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23833?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23833:
------------------------------------
FYI, the reason for the jobs not publishing is an upstream one... which I hope to have fixed. But if you ever see red jobs or jobs that haven't published for a couple days in this view [1], don't hesitate to complain to me to escalate. :)
[1] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
> Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23833
> URL: https://issues.jboss.org/browse/JBIDE-23833
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, common
> Affects Versions: 4.4.3.AM2, 4.4.4.AM1
> Reporter: Mat Booth
> Assignee: Nick Boldt
> Fix For: 4.4.4.AM2
>
> Attachments: central-site-no-updated.png, eclipse.log.20170324-1612.txt, jbide23833-install.png
>
>
> Doing a smoke test for the release of 4.4.3.AM2 when I saw this error:
> {noformat}
> !ENTRY org.eclipse.mylyn.tasks.core 4 0 2017-02-01 16:23:23.127
> !MESSAGE Unexpected error while loading repository template extensions
> !SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2017-02-01 16:23:23.127
> !MESSAGE Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
> {noformat}
> I saw this in the log after performing the following:
> 0. Downloaded Neon.2 (I happened to choose the C/C++ distribution)
> 1. Install Abridged category from http://download.jboss.org/jbosstools/neon/development/updates/
> 2. Open Central Software/Updates tab, enable Early Access select and install everything
--
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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24133?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24133:
------------------------------------
Added more to the PR per Martin's review.
> 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: Martin Malina
> 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 Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24135?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-24135:
--------------------------------------
[~nickboldt] These are permanent stable releases but we can probably clear old ones.
[~fbricon] WDYT
> 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 updated JBIDE-24135:
-------------------------------
Description:
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...
was:
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.
> 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)
Nick Boldt created JBIDE-24135:
----------------------------------
Summary: 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
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.
--
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 reassigned JBIDE-24135:
----------------------------------
Assignee: Gorkem Ercan
> 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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years