[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] we are not using http://download.jboss.org/jbosstools/static/vscode/ actively anymore. VS Code releases goes directly to VSCode marketplace. We are however using the staging more actively.
> 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.5.0.AM1
>
>
> 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)
8 years, 10 months
[JBoss JIRA] (JBIDE-24301) Error while building jbosstools-openshift-4.4.3
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24301:
------------------------------------------
[~jyoti-jboss] your paths are still very weird, please explain how to end up having these.
{quote}
[ERROR] Please refer to C:\jbosstools-server-4.4.3.x\jbosstools-server-jbosstools-4.4.3.x\jmx\tests\org.jboss.tools.jmx.core.test\target\surefire-reports for the individual test results.
{quote}
If I git clone what I told you to, I end up having a *jbosstools-server* folder:
{code}
adietish@Andres-MacBook-Pro /tmp git clone https://github.com/jbosstools/jbosstools-server
Cloning into 'jbosstools-server'...
remote: Counting objects: 108465, done.
remote: Compressing objects: 100% (166/166), done.
remote: Total 108465 (delta 86), reused 0 (delta 0), pack-reused 108228
Receiving objects: 100% (108465/108465), 88.12 MiB | 610.00 KiB/s, done.
Resolving deltas: 100% (49670/49670), done.
adietish@Andres-MacBook-Pro /tmp ll
total 1
drwxr-xr-x 12 adietish wheel 408B May 15 16:44 jbosstools-server
adietish@Andres-MacBook-Pro /tmp
{code}
And then, if you read the output very carefully, you'll see why the test is failing. You already have a daemon running on port :9999. This is blocking the tests from starting such a daemon:
{code}
[error] : java.rmi.server.ExportException: Port already in use: 9999; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
{code}
> Error while building jbosstools-openshift-4.4.3
> -----------------------------------------------
>
> Key: JBIDE-24301
> URL: https://issues.jboss.org/browse/JBIDE-24301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.3.Final
> Reporter: jyoti tumsare
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.4.Final
>
> Attachments: Error.PNG, issues.PNG, issues.txt, jboss-build.png, jbosstools-build.png, org.jboss.ide.eclipse.as.management.as7.png, target-platform.png
>
>
> To build jbosstools-openshift-4.4.3 I followed following steps
> 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3.
> 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found".
> 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months