March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23961: ------------------------------------- Fix Version/s: 4.5.0.AM1 > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: debugging, nodejs, server_adapter > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24024) Server adapter editor, wizard: better tell me what the settings are for

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24024: ---------------------------------------- Summary: Server adapter editor, wizard: better tell me what the settings are for Key: JBIDE-24024 URL: https://issues.jboss.org/browse/JBIDE-24024 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.3.Final Reporter: Andre Dietisheim Fix For: 4.5.0.AM1 Attachments: image-2017-03-03-11-43-41-941.png, image-2017-03-03-11-44-46-410.png A server adapter will publish local files to a pod in OpenShift (via rsync). Our wizard and server adapter editors allows to set the adapter to fullfill this task. The wizard and the editor do a poor job explaining the purpose of those settings though: The wizard generically states that it does "file synchronization" but fails to tell "from" where to "where" !image-2017-03-03-11-43-41-941.png! The editor is even poorer in usability. It wont say anything about file synchronization and even mixes settings for the source and destination: !image-2017-03-03-11-44-46-410.png! "Source Path" should be right below the "Eclipse Project" since it's providing further details for it. "Pod Deployment Path" should be right below "Resource" (år "Service" in older verisions of this editor" since it provides the path on pods that are identified by "Resource". Ideally we'd also add labels "From" and "To" (or similar means to better identify the settings) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24023) Server adapter editor: I have no indication of what project the selected service is located in

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24023: ---------------------------------------- Summary: Server adapter editor: I have no indication of what project the selected service is located in Key: JBIDE-24023 URL: https://issues.jboss.org/browse/JBIDE-24023 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.3.Final Reporter: Andre Dietisheim Fix For: 4.5.0.AM1 Attachments: image-2017-03-03-10-45-25-851.png steps to reproduce: # ASSERT: have 2 nodejs (or eap- or any other) application running in 2 different projects, where you used the same template for both of them. Ex. "nodejs-example" in project "myPOC" and "nodejs-example" in project "myProject". # EXEC: create a server adapter for 1 of them # EXEC: open up the server adapter editor and look into "Service:" Result: You have no idea what service this adapter is publishing to, the one in "myPOC" or the one in "myProject"? !image-2017-03-03-10-45-25-851.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1052) Use relative paths in composite files

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1052?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1052. ------------------------------------ Verified > Use relative paths in composite files > ------------------------------------- > > Key: JBTIS-1052 > URL: https://issues.jboss.org/browse/JBTIS-1052 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 4.4.1.Final > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 10.1.0.GA > > > File at > http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... > contains absolute paths > {code} > <children size="2"> > <child location="http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta..."/> > <child location="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.1.Fi..."/> > </children> > {code} > I suggest to use relative paths as it in DevstudioIS at > https://devstudio.redhat.com/10.0/staging/updates/integration-stack/compo... > {code} > <children size="2"> > <child location="10.1.0.GA/"/> > <child location="10.1.0.GA/targetplatform/"/> > </children> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4297) ensure downstream jobs can trigger via script & token or set up downstream groovy listener

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4297?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4297: ----------------------------- Description: Seems that Bos MW can't see CCI: {code} 20:57:25 + curl 'https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi...' 20:57:25 curl: (7) couldn't connect to host{code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... So we need another way to hook this up until all jobs can be migrated to CCI. Perhaps the listener hook used here will work: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... !groovy-listener.png|thumbnail! {code} URL xpath = new URL('http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas...'); File last = new File('/tmp/${JOB_NAME}_lastBuildNumber.txt'); //println "last.toPath() = " + last.toPath() if (last.exists()) { File check = new File('/tmp/${JOB_NAME}_checkBuildNumber.txt'); //println "check.toPath() = " + check.toPath() check.delete(); check.createNewFile(); check << xpath.openStream(); print "Compare buildNumber = " + check.text + " to lastBuildNumber = " + last.text; boolean status = !check.text.equals(last.text); java.nio.file.Files.copy(check.toPath(), last.toPath(), java.nio.file.StandardCopyOption.REPLACE_EXISTING); return status; } else { last << xpath.openStream(); print "Fetch lastBuildNumber = " + last.text; return true; } {code} was: Seems that Bos MW can't see CCI: {code} 20:57:25 + curl 'https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi...' 20:57:25 20:57:25 curl: (7) couldn't connect to host {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... So we need another way to hook this up until all jobs can be migrated to CCI. Perhaps the listener hook used here will work: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... !groovy-listener.png|thumbnail! {code} URL xpath = new URL('http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas...'); File last = new File('/tmp/${JOB_NAME}_lastBuildNumber.txt'); //println "last.toPath() = " + last.toPath() if (last.exists()) { File check = new File('/tmp/${JOB_NAME}_checkBuildNumber.txt'); //println "check.toPath() = " + check.toPath() check.delete(); check.createNewFile(); check << xpath.openStream(); print "Compare buildNumber = " + check.text + " to lastBuildNumber = " + last.text; boolean status = !check.text.equals(last.text); java.nio.file.Files.copy(check.toPath(), last.toPath(), java.nio.file.StandardCopyOption.REPLACE_EXISTING); return status; } else { last << xpath.openStream(); print "Fetch lastBuildNumber = " + last.text; return true; } {code} > ensure downstream jobs can trigger via script & token or set up downstream groovy listener > ------------------------------------------------------------------------------------------ > > Key: JBDS-4297 > URL: https://issues.jboss.org/browse/JBDS-4297 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Affects Versions: 10.4.0.AM1 > Reporter: Nick Boldt > Fix For: 10.4.0.AM1, 11.0.0.AM1 > > Attachments: groovy-listener.png > > > Seems that Bos MW can't see CCI: > {code} > 20:57:25 + curl 'https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi...' > 20:57:25 curl: (7) couldn't connect to host{code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > So we need another way to hook this up until all jobs can be migrated to CCI. > Perhaps the listener hook used here will work: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > !groovy-listener.png|thumbnail! > {code} > URL xpath = new URL('http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas...'); > File last = new File('/tmp/${JOB_NAME}_lastBuildNumber.txt'); //println "last.toPath() = " + last.toPath() > if (last.exists()) > { > File check = new File('/tmp/${JOB_NAME}_checkBuildNumber.txt'); //println "check.toPath() = " + check.toPath() > check.delete(); check.createNewFile(); > check << xpath.openStream(); > print "Compare buildNumber = " + check.text + " to lastBuildNumber = " + last.text; > boolean status = !check.text.equals(last.text); > java.nio.file.Files.copy(check.toPath(), last.toPath(), java.nio.file.StandardCopyOption.REPLACE_EXISTING); > return status; > } else { > last << xpath.openStream(); > print "Fetch lastBuildNumber = " + last.text; > return true; > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4297) ensure downstream jobs can trigger via script & token or set up downstream groovy listener

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4297?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4297: -------------------------------- Assignee: Nick Boldt > ensure downstream jobs can trigger via script & token or set up downstream groovy listener > ------------------------------------------------------------------------------------------ > > Key: JBDS-4297 > URL: https://issues.jboss.org/browse/JBDS-4297 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Affects Versions: 10.4.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.4.0.AM1, 11.0.0.AM1 > > Attachments: groovy-listener.png > > > Seems that Bos MW can't see CCI: > {code} > 20:57:25 + curl 'https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi...' > 20:57:25 curl: (7) couldn't connect to host{code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > So we need another way to hook this up until all jobs can be migrated to CCI. > Perhaps the listener hook used here will work: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > !groovy-listener.png|thumbnail! > {code} > URL xpath = new URL('http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas...'); > File last = new File('/tmp/${JOB_NAME}_lastBuildNumber.txt'); //println "last.toPath() = " + last.toPath() > if (last.exists()) > { > File check = new File('/tmp/${JOB_NAME}_checkBuildNumber.txt'); //println "check.toPath() = " + check.toPath() > check.delete(); check.createNewFile(); > check << xpath.openStream(); > print "Compare buildNumber = " + check.text + " to lastBuildNumber = " + last.text; > boolean status = !check.text.equals(last.text); > java.nio.file.Files.copy(check.toPath(), last.toPath(), java.nio.file.StandardCopyOption.REPLACE_EXISTING); > return status; > } else { > last << xpath.openStream(); > print "Fetch lastBuildNumber = " + last.text; > return true; > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4297) ensure downstream jobs can trigger via script & token or set up downstream groovy listener

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4297?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4297: ----------------------------- Fix Version/s: 10.4.0.AM1 11.0.0.AM1 > ensure downstream jobs can trigger via script & token or set up downstream groovy listener > ------------------------------------------------------------------------------------------ > > Key: JBDS-4297 > URL: https://issues.jboss.org/browse/JBDS-4297 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Affects Versions: 10.4.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.4.0.AM1, 11.0.0.AM1 > > Attachments: groovy-listener.png > > > Seems that Bos MW can't see CCI: > {code} > 20:57:25 + curl 'https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi...' > 20:57:25 curl: (7) couldn't connect to host{code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > So we need another way to hook this up until all jobs can be migrated to CCI. > Perhaps the listener hook used here will work: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > !groovy-listener.png|thumbnail! > {code} > URL xpath = new URL('http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas...'); > File last = new File('/tmp/${JOB_NAME}_lastBuildNumber.txt'); //println "last.toPath() = " + last.toPath() > if (last.exists()) > { > File check = new File('/tmp/${JOB_NAME}_checkBuildNumber.txt'); //println "check.toPath() = " + check.toPath() > check.delete(); check.createNewFile(); > check << xpath.openStream(); > print "Compare buildNumber = " + check.text + " to lastBuildNumber = " + last.text; > boolean status = !check.text.equals(last.text); > java.nio.file.Files.copy(check.toPath(), last.toPath(), java.nio.file.StandardCopyOption.REPLACE_EXISTING); > return status; > } else { > last << xpath.openStream(); > print "Fetch lastBuildNumber = " + last.text; > return true; > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4297) ensure downstream jobs can trigger via script & token

by Nick Boldt (JIRA)

Nick Boldt created JBDS-4297: -------------------------------- Summary: ensure downstream jobs can trigger via script & token Key: JBDS-4297 URL: https://issues.jboss.org/browse/JBDS-4297 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Sub-task Components: build Affects Versions: 10.4.0.AM1 Reporter: Nick Boldt Attachments: groovy-listener.png Seems that Bos MW can't see CCI: {code} 20:57:25 + curl 'https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi...' 20:57:25 20:57:25 curl: (7) couldn't connect to host {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... So we need another way to hook this up until all jobs can be migrated to CCI. Perhaps the listener hook used here will work: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... !groovy-listener.png|thumbnail! {code} URL xpath = new URL('http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas...'); File last = new File('/tmp/${JOB_NAME}_lastBuildNumber.txt'); //println "last.toPath() = " + last.toPath() if (last.exists()) { File check = new File('/tmp/${JOB_NAME}_checkBuildNumber.txt'); //println "check.toPath() = " + check.toPath() check.delete(); check.createNewFile(); check << xpath.openStream(); print "Compare buildNumber = " + check.text + " to lastBuildNumber = " + last.text; boolean status = !check.text.equals(last.text); java.nio.file.Files.copy(check.toPath(), last.toPath(), java.nio.file.StandardCopyOption.REPLACE_EXISTING); return status; } else { last << xpath.openStream(); print "Fetch lastBuildNumber = " + last.text; return true; } {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4297) ensure downstream jobs can trigger via script & token or set up downstream groovy listener

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4297?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4297: ----------------------------- Summary: ensure downstream jobs can trigger via script & token or set up downstream groovy listener (was: ensure downstream jobs can trigger via script & token) > ensure downstream jobs can trigger via script & token or set up downstream groovy listener > ------------------------------------------------------------------------------------------ > > Key: JBDS-4297 > URL: https://issues.jboss.org/browse/JBDS-4297 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Affects Versions: 10.4.0.AM1 > Reporter: Nick Boldt > Attachments: groovy-listener.png > > > Seems that Bos MW can't see CCI: > {code} > 20:57:25 + curl 'https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/devstudi...' > 20:57:25 > 20:57:25 curl: (7) couldn't connect to host > {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > So we need another way to hook this up until all jobs can be migrated to CCI. > Perhaps the listener hook used here will work: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > !groovy-listener.png|thumbnail! > {code} > URL xpath = new URL('http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas...'); > File last = new File('/tmp/${JOB_NAME}_lastBuildNumber.txt'); //println "last.toPath() = " + last.toPath() > if (last.exists()) > { > File check = new File('/tmp/${JOB_NAME}_checkBuildNumber.txt'); //println "check.toPath() = " + check.toPath() > check.delete(); check.createNewFile(); > check << xpath.openStream(); > print "Compare buildNumber = " + check.text + " to lastBuildNumber = " + last.text; > boolean status = !check.text.equals(last.text); > java.nio.file.Files.copy(check.toPath(), last.toPath(), java.nio.file.StandardCopyOption.REPLACE_EXISTING); > return status; > } else { > last << xpath.openStream(); > print "Fetch lastBuildNumber = " + last.text; > return true; > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-487) Fix open retry logic to allow cancellation and stop on DockerExplorerContentProvider dispose [EBZ#513029]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-487: --------------------------------------- Summary: Fix open retry logic to allow cancellation and stop on DockerExplorerContentProvider dispose [EBZ#513029] Key: ERT-487 URL: https://issues.jboss.org/browse/ERT-487 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon.3 (4.6) The new logic to retry opening a connection does not propertly support cancellation in the Tasks view. Logic is also needed to shut down any remaining threads at Eclipse termination. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 March 2017