May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22372) Publish CI snapshots to a directory containing BUILD_ALIAS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22372?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22372: ------------------------------------ So this is a variation / automation of the process of creating staged builds for QE. Instead of * /snapshots/builds/ (many folders with unique BUILD#s & a symlinked latest one) * pushed at some point to /staging/4.4.0.Alpha2/, /staging/4.4.0.Alpha3/, /staging/4.4.0.Alpha4/ We would have * /snapshots/builds/4.4.0.Alpha2/ (many folders with unique BUILD#s & a symlinked latest one) * /snapshots/builds/4.4.0.Alpha3/ (many folders with unique BUILD#s & a symlinked latest one) * /snapshots/builds/4.4.0.Alpha4/ (many folders with unique BUILD#s & a symlinked latest one) * pushed at some point to /staging/4.4.0.Alpha2/, /staging/4.4.0.Alpha3/, /staging/4.4.0.Alpha4/ > Publish CI snapshots to a directory containing BUILD_ALIAS > ---------------------------------------------------------- > > Key: JBIDE-22372 > URL: https://issues.jboss.org/browse/JBIDE-22372 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Fix For: 4.4.0.Alpha3 > > > To avoid even more "crossing streams", we could consider also adding the BUILD_ALIAS to the URL of snapshots sites produced by CI. An advantage is that building a new version wouldn't require to cleanup the /4.4.neon branch for example. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-210) Bump Plug/Feature version for 3.8.0 [EBZ#494559]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-210: --------------------------------------- Summary: Bump Plug/Feature version for 3.8.0 [EBZ#494559] Key: ERT-210 URL: https://issues.jboss.org/browse/ERT-210 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Priority: Blocker Fix For: Neon (4.6) RC3 Scan between MARS.RC2 R-3.7.2 >> NEON I-3.8.0-20160524010110 shows that this plugins needs to be bumped: << Modified plugins >> org.eclipse.wst.jsdt.debug.ui [1.0.500.v201604281715] NEON I-3.8.0-20160524010110 [1.0.500.v201502261613] MARS.RC2 R-3.7.2-20160217020110 org.eclipse.wst.jsdt.debug.core [3.1.200.v201603100113] NEON I-3.8.0-20160524010110 [3.1.200.v201502261613] MARS.RC2 R-3.7.2-20160217020110 org.eclipse.wst.jsdt.debug.rhino [1.0.400.v201603171345] NEON I-3.8.0-20160524010110 [1.0.400.v201503300052] MARS.RC2 R-3.7.2-20160217020110 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-210) Bump Plug/Feature version for 3.8.0 [EBZ#494559]

by Friendly Jira Robot (JIRA)

[ https://issues.jboss.org/browse/ERT-210?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot resolved ERT-210. ------------------------------------- Resolution: Done > Bump Plug/Feature version for 3.8.0 [EBZ#494559] > ------------------------------------------------ > > Key: ERT-210 > URL: https://issues.jboss.org/browse/ERT-210 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: 3.8_RC3, Debug, bzira > Fix For: Neon (4.6) RC3 > > > Scan between MARS.RC2 R-3.7.2 >> NEON I-3.8.0-20160524010110 shows that this plugins needs to be bumped: > << Modified plugins >> > org.eclipse.wst.jsdt.debug.ui > [1.0.500.v201604281715] NEON I-3.8.0-20160524010110 > [1.0.500.v201502261613] MARS.RC2 R-3.7.2-20160217020110 > org.eclipse.wst.jsdt.debug.core > [3.1.200.v201603100113] NEON I-3.8.0-20160524010110 > [3.1.200.v201502261613] MARS.RC2 R-3.7.2-20160217020110 > org.eclipse.wst.jsdt.debug.rhino > [1.0.400.v201603171345] NEON I-3.8.0-20160524010110 > [1.0.400.v201503300052] MARS.RC2 R-3.7.2-20160217020110 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22411) update TPs to latest Docker/Vagrant tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22411?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22411: ------------------------------------ Plan is to move to RC3 or RC4 bits for the next TP update. If you need me to move us up sooner to something else (RC1 or RC2) please escalate to [~akazakov] and have him authorize an earlier TP change in JBIDE-22367. > update TPs to latest Docker/Vagrant tooling > ------------------------------------------- > > Key: JBIDE-22411 > URL: https://issues.jboss.org/browse/JBIDE-22411 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/update-neon-docker-rc2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22355) JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22355?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22355: ------------------------------------ Sprint 114 ended May 24 [1]. So, all the bits built for that sprint will have a date stamp with 0519 or 0520 in them. Sprint 115 will end June 14. So, all the bits built for that sprint will have a date stamp likely around with 0609 or 0610 in them. Is that concrete enough or do you need me to dump a list of plugins and features from the last staged build [2] so you can see all the actual qualifiers? [1] https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j... [2] http://download.jboss.org/jbosstools/neon/staging/updates/core/4.4.0.Alpha2/ Note that for org.eclipse.wst.jsdt.nodejs.feature or org.eclipse.linuxtools.docker.feature there are no such Alpha/Beta/CR qualifiers. Just a datestamp. But we know they're from M7, so they're Beta quality. When we move up to the RC3/4 bits, we'll know they're CR/Final quality. There are other ways to know how good your bits are than simply by looking at the artifact jar file names. > JBT component CI build qualifiers still say Alpha1, but Alpha1 is released in JIRA and we're building toward Alpha2 > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22355 > URL: https://issues.jboss.org/browse/JBIDE-22355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.x > > > Build qualifiers, parent pom version, and version of parent pom referenced by components are still Alpha1. > All those should be moved to Alpha2 (they should be moved just when branching/releasing actually) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22304) Server Editor: Pod deployment path is not shown

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22304?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22304: ----------------------------------- Assignee: Viacheslav Kabanovich > Server Editor: Pod deployment path is not shown > ----------------------------------------------- > > Key: JBIDE-22304 > URL: https://issues.jboss.org/browse/JBIDE-22304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_editor > Fix For: 4.4.0.Alpha3 > > > In Server Adapter wizard is not shown Pod deployment path. Widget supposed to display the path is empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22420) Application Wizard: Finish button is still enabled upon selection of a builder image if a template was selected before

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22420?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22420: ------------------------------------------ rebased and merged into master. > Application Wizard: Finish button is still enabled upon selection of a builder image if a template was selected before > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22420 > URL: https://issues.jboss.org/browse/JBIDE-22420 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > If I select a template in New OpenShift Application wizard, the Finish button is enabled and it is possible to skip all wizard pages and have created an application. If I select a builder image in the wizard, Finish is disabled (although on the next wizard page it gets enabled even I do not set any other value manually). But having selecting a template at first in the wizard and then selecting a build image, Finish button is still enabled. Click on the button cause NPE with following stack trace: > {code}Unable to create resources to deploy image null > java.lang.IllegalArgumentException: newValue is null > at org.jboss.dmr.ModelNode.set(ModelNode.java:499) > at com.openshift.internal.restclient.model.Service.setSelector(Service.java:115) > at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.stubService(DeployImageJob.java:254) > at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.generateResources(DeployImageJob.java:150) > at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.doRun(DeployImageJob.java:99) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22420) Application Wizard: Finish button is still enabled upon selection of a builder image if a template was selected before

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22420?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-22420: ---------------------------------------- Assignee: Viacheslav Kabanovich Resolution: Done > Application Wizard: Finish button is still enabled upon selection of a builder image if a template was selected before > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22420 > URL: https://issues.jboss.org/browse/JBIDE-22420 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > If I select a template in New OpenShift Application wizard, the Finish button is enabled and it is possible to skip all wizard pages and have created an application. If I select a builder image in the wizard, Finish is disabled (although on the next wizard page it gets enabled even I do not set any other value manually). But having selecting a template at first in the wizard and then selecting a build image, Finish button is still enabled. Click on the button cause NPE with following stack trace: > {code}Unable to create resources to deploy image null > java.lang.IllegalArgumentException: newValue is null > at org.jboss.dmr.ModelNode.set(ModelNode.java:499) > at com.openshift.internal.restclient.model.Service.setSelector(Service.java:115) > at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.stubService(DeployImageJob.java:254) > at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.generateResources(DeployImageJob.java:150) > at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.doRun(DeployImageJob.java:99) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21134) Move easymport plugins from playground component

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21134?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21134: ------------------------------------- PR applied in central > Move easymport plugins from playground component > ------------------------------------------------ > > Key: JBIDE-21134 > URL: https://issues.jboss.org/browse/JBIDE-21134 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.4.0.Alpha1 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha3 > > > Easymport is in the default installation of JBDS so it might be time to move it from playground component? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22420) Application Wizard: Finish button is still enabled upon selection of a builder image if a template was selected before

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22420?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22420: ------------------------------------- Steps to Reproduce: # ASSERT: have connection with a project in the openshift explorer # EXEC: pick New > Application in the context menu of your project # ASSERT: wizard page with templates and builder images shows up, "Finish" is disabled # EXEC: select a builder image (entry with a box icon as opposed to a lightning) # ASSERT: "Finish" stays disabled # EXEC: select a template (entry with a lightning) # ASSERT: "Finish" gets enabled # EXEC: select a builder image Result: "Finish" is enabled even though it should be disabled. > Application Wizard: Finish button is still enabled upon selection of a builder image if a template was selected before > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22420 > URL: https://issues.jboss.org/browse/JBIDE-22420 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > > If I select a template in New OpenShift Application wizard, the Finish button is enabled and it is possible to skip all wizard pages and have created an application. If I select a builder image in the wizard, Finish is disabled (although on the next wizard page it gets enabled even I do not set any other value manually). But having selecting a template at first in the wizard and then selecting a build image, Finish button is still enabled. Click on the button cause NPE with following stack trace: > {code}Unable to create resources to deploy image null > java.lang.IllegalArgumentException: newValue is null > at org.jboss.dmr.ModelNode.set(ModelNode.java:499) > at com.openshift.internal.restclient.model.Service.setSelector(Service.java:115) > at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.stubService(DeployImageJob.java:254) > at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.generateResources(DeployImageJob.java:150) > at org.jboss.tools.openshift.internal.ui.job.DeployImageJob.doRun(DeployImageJob.java:99) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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