August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20362) Extracting of a download runtime is slow on Mac

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20362?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20362: --------------------------------------- Great to see that you can reproduce it! I commented on the bug. > Extracting of a download runtime is slow on Mac > ----------------------------------------------- > > Key: JBIDE-20362 > URL: https://issues.jboss.org/browse/JBIDE-20362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > While playing with the Download runtime fuctionality, I noticed that once a runtime (e.g. EAP 6.2) is downloaded, the extraction takes very long. I think it used to be fast and the extraction was done without any progress reporting. But now it seems that every subdirectory in the archive is being printed out which slows it down. > This extraction process took 1 min 23 sec for EAP 6.2 and I have an SSD. On a command line, this would take a few seconds. > I think the solution may be to simply show "Extracting" without printing out each file/directory that is being extracted. > (Furthermore, the progress bar does not reflect the progress - it seems there is still only perhaps 5 % done and then it's suddenly over.) > I can record a screencast if you like, but I think this should be easy to replicate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23009) Cannot connect to cdk 2.2 docker in Docker Explorer

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23009?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23009: --------------------------------------- Cool, thanks. I created a bug in adb: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/511 > Cannot connect to cdk 2.2 docker in Docker Explorer > --------------------------------------------------- > > Key: JBIDE-23009 > URL: https://issues.jboss.org/browse/JBIDE-23009 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Critical > > When I start CDK 2.2, docker connection is correctly created, but it cannot connect. There is no error message anywhere. > If I try to create a connection manually, using details from "vagrant service-manager env", the ping fails and it doesn't work either. > Connection from CLI, on the other hand, to this docker daemon works fine - when I run the export commands: > {code} > export DOCKER_HOST=tcp://172.28.128.3:2376 > export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > export DOCKER_TLS_VERIFY=1 > export DOCKER_API_VERSION=1.22 > {code} > and then try for example "docker ps" or "docker run hello-world". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-19911 at 8/17/16 4:20 AM: ----------------------------------------------------------------- Alternative approach: * Generating the change ** Job mirrors sourceSite ** job publishes mirror (scp) it to targetMirror ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target ** job runs "mvn fix-version ..." on multiple/*.target ** Job generates PR * Verifying and annotating PR (done with JBIDE-22308) ** "mvn clean verify -Pmultiple2repo" on multiple/*.target ** p2diff Those 2 parts can be implemented sepearately. The part about verification is/should be a subset of the actual TP build, the only difference is that it doesn't upload new snapshot Maven artifacts nor site. was (Author: mickael_istria): Alternative approach: * Generating the change ** Job mirrors sourceSite ** job publishes mirror (scp) it to targetMirror ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target ** job runs "mvn fix-version ..." on multiple/*.target ** Job generates PR * Verifying and annotating PR ** "mvn clean verify -Pmultiple2repo" on multiple/*.target ** p2diff Those 2 parts can be implemented sepearately. The part about verification is/should be a subset of the actual TP build, the only difference is that it doesn't upload new snapshot Maven artifacts nor site. > Create a (manual) job to update a given 3rd-party project on TP > --------------------------------------------------------------- > > Key: JBIDE-19911 > URL: https://issues.jboss.org/browse/JBIDE-19911 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Mickael Istria > Fix For: 4.4.x > > > For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request. > * Input: sourceSite, initialMirror (as found in .target), targetMirror > * Then > ** job mirros the sourceSite > ** job publishes (scp) it to targetMirror > ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target > ** job runs "mvn fix-version ..." on multiple/*.target > ** "mvn clean verify -Pmultiple2repo" on multiple/*.target > ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER > ** p2diff > ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19911) Create a (manual) job to update a given 3rd-party project on TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19911?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19911: ---------------------------------------- With JBIDE-22308, p2diff are now generated on any (regular or TP) build. That's one step less to implement. > Create a (manual) job to update a given 3rd-party project on TP > --------------------------------------------------------------- > > Key: JBIDE-19911 > URL: https://issues.jboss.org/browse/JBIDE-19911 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Mickael Istria > Fix For: 4.4.x > > > For 3rd-party sites that are regularly changing, we could provide a Jenkins job that would automatically update the .target and provide the pull request. > * Input: sourceSite, initialMirror (as found in .target), targetMirror > * Then > ** job mirros the sourceSite > ** job publishes (scp) it to targetMirror > ** job runs "sed s/initialMirror/targetMirror/" on multiple/*.target > ** job runs "mvn fix-version ..." on multiple/*.target > ** "mvn clean verify -Pmultiple2repo" on multiple/*.target > ** git add multiple/*.target; git commit -m "Update initialMirror to targetMirror"; git push origin HEAD:change-BUILD_NUMBER > ** p2diff > ** Put p2diff as a comment on PR: https://developer.github.com/v3/pulls/comments/#create-a-comment -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22305: ---------------------------------------- JBIDE-19911 is about the same thing except it only targets a single repository from the TP. > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.x > > Attachments: git.diff.txt > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23013) Pull Docker Tooling bits into JBT builds more frequently

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23013?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23013: ---------------------------------------- Fixing JBIDE-19911 (which was created in the scope of thym/aerogear) would fix that. > Pull Docker Tooling bits into JBT builds more frequently > -------------------------------------------------------- > > Key: JBIDE-23013 > URL: https://issues.jboss.org/browse/JBIDE-23013 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Nick Boldt > > It would be cool if we could update the Docker Tooling bits in our TP more frequently, i.e. weekly or even nightly. I know that currently it is quite a big effort to update TP. So we would need to simplify this somehow. > So this is a suggestion, but I don't know how we would do it or if it's doable at all. > Here's a bit of background: > Today I spotted this blocking bug in docker tooling: > https://issues.jboss.org/browse/JBIDE-23011 > It was probably brought into JBT TP in the last update of the TP - this JIRA: > https://issues.jboss.org/browse/JBIDE-22885 - 4 days ago. > Jeff Maury suggested, that it's a bad idea to update our TP this close to our release (AM3 in this case). But currently we don't have any other option. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23009) Cannot connect to cdk 2.2 docker in Docker Explorer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23009?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-23009: --------------------------------------- Hello [~mmalina], As I explained above, the Docker daemon in CDK 2.2 returns a response that contains the list of containers in a JSON format, but the 'content' header is {{text/plain}} instead of {{application/json}} and thus, the Docker client does not know how to handle/deserialize the response message. We should see if this problem occurs in the latest 2.2 build and raise the issue upstream (CDK team) if it is the case. > Cannot connect to cdk 2.2 docker in Docker Explorer > --------------------------------------------------- > > Key: JBIDE-23009 > URL: https://issues.jboss.org/browse/JBIDE-23009 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Critical > > When I start CDK 2.2, docker connection is correctly created, but it cannot connect. There is no error message anywhere. > If I try to create a connection manually, using details from "vagrant service-manager env", the ping fails and it doesn't work either. > Connection from CLI, on the other hand, to this docker daemon works fine - when I run the export commands: > {code} > export DOCKER_HOST=tcp://172.28.128.3:2376 > export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > export DOCKER_TLS_VERIFY=1 > export DOCKER_API_VERSION=1.22 > {code} > and then try for example "docker ps" or "docker run hello-world". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22990) OpenShift New and Noteworthy for 4.4.1.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22990?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22990: ---------------------------------- Assignee: Jeff MAURY (was: Andre Dietisheim) > OpenShift New and Noteworthy for 4.4.1.AM3 > ------------------------------------------ > > Key: JBIDE-22990 > URL: https://issues.jboss.org/browse/JBIDE-22990 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.1.AM3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3986) support building devstudio on windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3986?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3986: -------------------------------- Sprint: devex #118 July 2016, devex #119 August 2016 (was: devex #118 July 2016) > support building devstudio on windows > ------------------------------------- > > Key: JBDS-3986 > URL: https://issues.jboss.org/browse/JBDS-3986 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.1.0.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Support building devstudio on windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3982) create rh-eclipse46-devstudio rpm for linux installs

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3982?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3982: -------------------------------- Sprint: devex #118 July 2016, devex #119 August 2016 (was: devex #118 July 2016) > create rh-eclipse46-devstudio rpm for linux installs > ---------------------------------------------------- > > Key: JBDS-3982 > URL: https://issues.jboss.org/browse/JBDS-3982 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.AM3 > > > wrap new update site (JBDS-3981) in a rh-eclipse46-devstudio*.rpm so we can install it on Fedora 24 and RHEL 7 > will need to port http://download.jboss.org/jbosstools/updates/scripted-install/director.xml to bash so it can be called along with rpmbuilder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2016