February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21087) Manage Project dialog reorganizes the project list after deleting project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21087?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21087. --------------------------------- Fix Version/s: 4.3.1.CR1 4.4.0.Alpha1 (was: 4.4.x) Assignee: Jeff Cantrill Resolution: Done Seems to have been fixed by JBIDE-21633 > Manage Project dialog reorganizes the project list after deleting project > ------------------------------------------------------------------------- > > Key: JBIDE-21087 > URL: https://issues.jboss.org/browse/JBIDE-21087 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > Deleting a project using the Manage Project dialog causes the table to refresh and project are randomly sorted. We should sort the projects by name as they appear in the table so the view is consistent between operations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20497) New Application shows New Project wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20497?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20497: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.1.CR1) > New Application shows New Project wizard > ----------------------------------------- > > Key: JBIDE-20497 > URL: https://issues.jboss.org/browse/JBIDE-20497 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Labels: application_wizard, openshift_v3 > Fix For: 4.4.x > > > When running Create New Application and I have no project a separate dialog pops up asking for Create New project with no real explanation. > Could the Create project step not be something that gets to be a page in New Application or somehow not be so "separate" and at least with some info that you need to create project before creating application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20507) Remove cursor from a retrieve token styled text

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20507?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20507. --------------------------------- Fix Version/s: 4.3.1.CR1 4.4.0.Alpha1 (was: 4.4.x) Resolution: Out of Date This seems to be fixed now > Remove cursor from a retrieve token styled text > ----------------------------------------------- > > Key: JBIDE-20507 > URL: https://issues.jboss.org/browse/JBIDE-20507 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > In a New Connection dialog there is a styled text with link "Enter a token or retrieve a new one." Problem is that styled text contains cursor. Cursor is shown on a position after clicking on the position inside the styled text. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21657: ---------------------------------- Assignee: Nick Boldt > 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 > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > 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)

10 years, 2 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21657: ------------------------------- Fix Version/s: 4.3.1.CR1 4.4.0.Alpha1 > 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 > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > 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)

10 years, 2 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21657: ------------------------------- Affects Version/s: 4.3.1.Beta2 4.4.0.Alpha1 > 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 > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > 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)

10 years, 2 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21657: ------------------------------------ I'm thinking we should publish these to a separate URL from /builds/ since these are only PRs. Perhaps a /pulls/ folder? http://download.jboss.org/jbosstools/neon/snapshots/pulls/jbosstools-buil... Then users can still roll up these builds with -Djbosstools-build-type=neon/snapshots/pulls ! > 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 > Reporter: Nick Boldt > > 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)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21307) Server Adapter: ensure oc binary that's used for rsync is v1.1.0.1+

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21307?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21307: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Server Adapter: ensure oc binary that's used for rsync is v1.1.0.1+ > ------------------------------------------------------------------- > > Key: JBIDE-21307 > URL: https://issues.jboss.org/browse/JBIDE-21307 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: oc_binary, openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Because of https://github.com/openshift/origin/issues/6109 publishing with the server adapter (which does a oc rsync behind the scenes) only properly works with oc v1.1.0.1. Versions below require the user to manually > {code} > oc login --server=<server that we publish to> --token=... > {code} > We should check the version and warn if the user is using an oc that is older than this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21657: ---------------------------------- Summary: 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 Reporter: Nick Boldt 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)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21625) Server adapter: Enable debug mode on OpenShift servers

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21625?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21625 at 2/5/16 4:29 PM: ------------------------------------------------------------------ As specificed in CLOUD-243: Enabling debugging in our eap-images works via an env var {code} com.redhat.dev-mode com.redhat.dev-mode.port {code} In [oc|https://docs.openshift.com/enterprise/3.0/dev_guide/environment_variab...] one can do {code} $ oc env <object-selection> KEY_1=VAL_1 ... KEY_N=VAL_N [<set-env-options>] [<common-options>] {code} Those get picked on pod deployment. So we can change the deployment config resource and start for the triggered build to finish or change the number of replicas 1->0->1 {quote} (06:19:17 PM) kconner: adietisheim: The env needs to be set when the pod starts, you may find that modifying the dc will redeploy it {quote} You can achieve this by changing the deployment config in Eclipse: * for the deployment config changes, add to spec.containers.ports : {code} { "name" : "debug", "containerPort" : 9876, "protocol" : "TCP" } {code} * and to spec.containers.env: {code} { "name" : "DEBUG", "value" : "true" }, { "name" : "DEBUG_PORT", "value" : "9876" } {code} was (Author: adietish): As specificed in CLOUD-243: Enabling debugging in our eap-images works via an env var {code} com.redhat.dev-mode com.redhat.dev-mode.port {code} In [oc|https://docs.openshift.com/enterprise/3.0/dev_guide/environment_variab...] one can do {code} $ oc env <object-selection> KEY_1=VAL_1 ... KEY_N=VAL_N [<set-env-options>] [<common-options>] {code} Those get picked on pod deployment. So we can change the deployment config resource and start for the triggered build to finish or change the number of replicas 1->0->1 {quote} (06:19:17 PM) kconner: adietisheim: The env needs to be set when the pod starts, you may find that modifying the dc will redeploy it {quote} > Server adapter: Enable debug mode on OpenShift servers > ------------------------------------------------------ > > Key: JBIDE-21625 > URL: https://issues.jboss.org/browse/JBIDE-21625 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Need to easily enable debug mode on EAP/Node images. That should allow hot reloading of server.js or java classes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 February 2016