May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-181) Allow for search and pull images from any Docker registry [EBZ#469308]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-181: --------------------------------------- Summary: Allow for search and pull images from any Docker registry [EBZ#469308] Key: ERT-181 URL: https://issues.jboss.org/browse/ERT-181 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot The docker-client now allows for search on a docker registry, so we should leverage that API to search for images, display available info and let the user select the image(s) to pull on the current Docker deamon (ie, Docker host). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19698) Dispatch selection in containers view

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19698?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19698: --------------------------------------------- updated description since the important part is that our views notify eclipse selection has changed, not that there is direct coupling between views (i.e. docker explorer from container view) > Dispatch selection in containers view > ------------------------------------- > > Key: JBIDE-19698 > URL: https://issues.jboss.org/browse/JBIDE-19698 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.3.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: upstream > Fix For: 4.4.x > > > When the selection changes in the container and image view, it should be broadcasted so that other views dependent on selection (like Properties views) can react accordingly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19698) Dispatch selection in containers view

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19698?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19698: ---------------------------------------- Description: When the selection changes in the container and image view, it should be broadcasted so that other views dependent on selection (like Properties views) can react accordingly. (was: When the selection changes in the container view, it should be broadcasted so that other views (Docker Explorer and Properties views) can react accordingly.) > Dispatch selection in containers view > ------------------------------------- > > Key: JBIDE-19698 > URL: https://issues.jboss.org/browse/JBIDE-19698 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.3.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Labels: upstream > Fix For: 4.4.x > > > When the selection changes in the container and image view, it should be broadcasted so that other views dependent on selection (like Properties views) can react accordingly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19562) Allow for search and pull images from any Docker registry

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19562?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-19562. --------------------------------------- Resolution: Migrated to another ITS no need to have this issue open since there is upstream for it and thus tracked in ERT. > Allow for search and pull images from any Docker registry > --------------------------------------------------------- > > Key: JBIDE-19562 > URL: https://issues.jboss.org/browse/JBIDE-19562 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.x > > > The docker-client now allows for search on a docker registry, so we should leverage that API to search for images, display available info and let the user select the image(s) to pull on the current Docker deamon (ie, Docker host). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-146) Upgrade to Spotify client 3.6.4 [EBZ#492235]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-146?page=com.atlassian.jira.plugin.sy... ] Max Rydahl Andersen updated ERT-146: ------------------------------------ Sprint: devex #115 May 2017 > Upgrade to Spotify client 3.6.4 [EBZ#492235] > -------------------------------------------- > > Key: ERT-146 > URL: https://issues.jboss.org/browse/ERT-146 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > Fix For: Neon (4.6) > > > CQ was approved http://dev.eclipse.org/ipzilla/show_bug.cgi?id=11108, but third-party dependencies need to be added/upgraded into Eclipse Orbit, too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20733) Support for .dockerignore file

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20733?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-20733: ---------------------------------------- Sprint: devex #115 May 2017 > Support for .dockerignore file > ------------------------------ > > Key: JBIDE-20733 > URL: https://issues.jboss.org/browse/JBIDE-20733 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.x > > > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=469819 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-16) Add "Exec" command on a container, using Eclipse Terminal [EBZ#479336]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-16?page=com.atlassian.jira.plugin.sys... ] Max Rydahl Andersen updated ERT-16: ----------------------------------- Sprint: devex #114 May 2017 > Add "Exec" command on a container, using Eclipse Terminal [EBZ#479336] > ---------------------------------------------------------------------- > > Key: ERT-16 > URL: https://issues.jboss.org/browse/ERT-16 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > Add a command on the containers to run the "Docker exec" command that would rely on the Eclipse Terminal (org.eclipse.tm) (see bug 471672) to let the user run commands. > The command handler might open a dialog to confirm which command to run. By default it could be "/bin/bash" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21657: ---------------------------------------- As far as I understand, there is no point in creating a different job for master and branch, as long as they build the same way. The necessary parameter for a check build are/should be already in there respective pom, so the job config would be exactly the same and as we do not deploy to branch specific location, a single job can handle both. So, unless I get some objection when [~nickboldt] is back, here are my plans: * Rename https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server__p... to https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server__p... * Rename https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... to https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... * Remove https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13671: ---------------------------------------- {quote}That only describes the timestamp - it does not change the semantic part of the version and thus it exactly reveals the issue I mentioned. That if you installed v1.2.3-<sometimestamp> a month ago installing vs updating v1.2.3-<othertimestamp> today could/will behave in different installation.{quote} The compare-with-baseline Maven plugin prevents from creating a different v1.2.3-xxx if there is already one present in baseline. So if one installed v1.2.3-timestamp1 one day from a release, the mojo should prevent US from creating a new v1.2.3-timestamp2. See https://wiki.eclipse.org/Tycho/Release_Notes/0.24#compare-version-with-ba... A good usage of this plugin will prevent us from publishing multiple v1.2.3 xxx, making all you concerns at install-time impossible to occur. > Replace build timestamp in qualifier by last-mod-timestamp from git > ------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.0.Alpha2 > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21745) Unable to download EAP 7 Beta runtime using username without "@redhat.com"

by David Hladky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21745?page=com.atlassian.jira.plugi... ] David Hladky commented on JBIDE-21745: -------------------------------------- AFAIK this problem with non-email account names was fixed some time ago. As [~dcoughlin1] does not say it is wrong I suppose the subscription model was intentional. > Unable to download EAP 7 Beta runtime using username without "@redhat.com" > -------------------------------------------------------------------------- > > Key: JBIDE-21745 > URL: https://issues.jboss.org/browse/JBIDE-21745 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Final, 4.3.1.CR1 > Environment: JBDS 9.1.0.CR1, JBDS 9.0.0.GA > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > Trying to download EAP 7 Beta using login without "@redhat.com" fails on license agreement page. > Instead of license agreement being displayed, just message saying "It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!" is shown. Given link redirects to Red Hat Developers portal login. After successful login, message is shown: > {noformat} > You Entered All Necessary Information > Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip. > {noformat} > But even after that I'm unable to download that runtime with the same credentials. > Using login with "@redhat.com" I'm able to download the runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016