July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22757: --------------------------------------- Thanks, [~nickboldt], PR 124 is merged and we don't require a similar fix for RedDeer 1.0.x since we don't plan on using it much longer (in fact we just released 1.0.2 and will put the branch on hold for now) and it's set in jenkins, so it's fine. So I consider all is done for RedDeer wrt this JIRA. > jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug) > ----------------------------------------------------------------- > > Key: JBIDE-22757 > URL: https://issues.jboss.org/browse/JBIDE-22757 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.1.AM2 > > Attachments: buildID-broken.png > > > Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER. > [1] https://issues.jenkins-ci.org/browse/JENKINS-26520 > [2] https://issues.jenkins-ci.org/browse/JENKINS-26626 > So instead of timestamped build folders, we're seeing things like this: > !buildID-broken.png|thumbnail! > Workaround until fixed in Jenkins: > {code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code} > Or, try using BUILD_TIMESTAMP instead? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22802) Change test project from eclipse plugin to maven projec

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22802?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-22802: ---------------------------------- Summary: Change test project from eclipse plugin to maven projec (was: Change test project frmo eclipse plugin to maven project) > Change test project from eclipse plugin to maven projec > ------------------------------------------------------- > > Key: JBIDE-22802 > URL: https://issues.jboss.org/browse/JBIDE-22802 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.4.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.4.1.AM2 > > > Former test project was an eclipse plugin and with changes made in this sprint it had became faulty. Convert project into maven project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22747) Several context menu items in context menu of an OpenShift 2 server adapter do not work

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22747?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22747: ------------------------------------ I cannot reproduce with master > Several context menu items in context menu of an OpenShift 2 server adapter do not work > --------------------------------------------------------------------------------------- > > Key: JBIDE-22747 > URL: https://issues.jboss.org/browse/JBIDE-22747 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v2 > Fix For: 4.4.1.AM3 > > > When I click on some context menu items on OpenShift 2 Server adapter, nothing happens. It works when opened via context menu of an application in OpenShift explorer view. > Following context menu items are not working: > - OpenShift - Port Forwarding... > - OpenShift - Tail Files... > - OpenShift - Snapshot - Save... > - OpenShift - Snapshot - Restore/Deploy... > - OpenShift - Details... > - OpenShift - Edit Embedded Cartridges... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22695) Environment Variables of application deployment should have different workflow

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22695?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22695: ------------------------------------ I think we should keep the workflow simple and having 2 deployment configs will confuse the user but we should also check that the reset button will also restored deleted variables > Environment Variables of application deployment should have different workflow > ------------------------------------------------------------------------------ > > Key: JBIDE-22695 > URL: https://issues.jboss.org/browse/JBIDE-22695 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > > Reset All button in Environment Var wizard dialog should get application to default state. At the moment it reset environment variables in the table just to the values at the point of opening the wizard. If I would delete some environment variables and confirm changes, but I would find out I broke something and I would like to rollback it to original state, I would try to reset it with Reset All button. But it won't work for me. This is causing the more serious issue: > Because we edit same deployment configuration and start deployments from it and in the same time we set number of replicas in other deployment configs to zero. So we don't have the original deployment config and thus we cannot rollback easily (well there is a way but nasty one - edit replication controller, copy and paste environment variables to the deployment config, save it and deploy latest). > There are 2 options: > a) Create a new deployment configuration for a new (modified) set of environment variables and create a new replication controller (deployment) from this deployment configuration. There is one con - it can lead to many deployment configurations and replication controllers (for each deployment configuration there would be one replication controller). > b) Just edit current replication controller (deployment) of an application or create a new one from an existing but with modified env. vars and with correct amount of replicas and set replicas in the previous to 0. And then let respin pods with correct setup. One of those approaches (create/edit RC) would be, I think, more satisfying. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3822) Disable the annoying "This program might not have installed correctly" on cancelation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3822?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3822: -------------------------------- Attachment: devsuite.manifest Attached manifest file generated for .exe file generated by electron packager. The only difference is requestedExecutionLevel@level is set to requireAdministrator > Disable the annoying "This program might not have installed correctly" on cancelation > ------------------------------------------------------------------------------------- > > Key: JBDS-3822 > URL: https://issues.jboss.org/browse/JBDS-3822 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3 > > Attachments: devsuite.manifest > > > Upon closing/cancelling the installer before going through the entire installation process, Windows will open a dialog saying "This program might not have installed correctly" and the user has to somehow confirm it. > This should be avoided by providing an application manifest that indicates support for certain Windows versions. > Docs here: > https://msdn.microsoft.com/en-us/library/dd371711%28VS.85%29.aspx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3822) Disable the annoying "This program might not have installed correctly" on cancelation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3822?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3822: ------------------------------------- Possible fix is: 1. Bring back resource hacker tool 2. Add [^devsuite.manifest]into repository 3. Run in the end of the build {code}ResourceHacker.exe -addoverwrite devsuite-1.0.0-GA-installer.exe, devsuite-1.0.0-GA-installer.exe, devsuite.manifest,24,1,1033{code} > Disable the annoying "This program might not have installed correctly" on cancelation > ------------------------------------------------------------------------------------- > > Key: JBDS-3822 > URL: https://issues.jboss.org/browse/JBDS-3822 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3 > > > Upon closing/cancelling the installer before going through the entire installation process, Windows will open a dialog saying "This program might not have installed correctly" and the user has to somehow confirm it. > This should be avoided by providing an application manifest that indicates support for certain Windows versions. > Docs here: > https://msdn.microsoft.com/en-us/library/dd371711%28VS.85%29.aspx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3948) Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3948?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3948: -------------------------------- Sprint: devex #118 July 2016 > Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer > ------------------------------------------------------------------------------------------ > > Key: JBDS-3948 > URL: https://issues.jboss.org/browse/JBDS-3948 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > Nightly CDK builds have sha256 checksums and metadata.txt. DevSuite build should use that to check if new download for CDK resources is required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3948) Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3948?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3948: -------------------------------- Sprint: (was: devex #118 July 2016) > Use CDK nightly builds metadata to include nightly CDK build into DevSuite Bundl Installer > ------------------------------------------------------------------------------------------ > > Key: JBDS-3948 > URL: https://issues.jboss.org/browse/JBDS-3948 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.1.0.AM1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > Nightly CDK builds have sha256 checksums and metadata.txt. DevSuite build should use that to check if new download for CDK resources is required. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3875) Split gulpfile.js to multiple modules to simplify maintenance

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3875?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3875: -------------------------------- Sprint: devex #114 May 2016 (was: devex #114 May 2016, devex #118 July 2016) > Split gulpfile.js to multiple modules to simplify maintenance > ------------------------------------------------------------- > > Key: JBDS-3875 > URL: https://issues.jboss.org/browse/JBDS-3875 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Pavol Pitonak > Labels: havoc > Fix For: 11.0.0.AM1 > > > Following up from JBDS-3851. Split the gulpfile into separate modules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3979) Set user agent for http requests from DevSuite Installer

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3979?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3979: ----------------------------- > Set user agent for http requests from DevSuite Installer > -------------------------------------------------------- > > Key: JBDS-3979 > URL: https://issues.jboss.org/browse/JBDS-3979 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.1.0.AM3 > > > Current implementation does not set user agent at all, where it should be the same as in Chromium with additional info to be able to distinguish installer requests in http logs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016