April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22244) BZ-JIRA job configuration does not take timezones into account

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-22244: ------------------------------------- Summary: BZ-JIRA job configuration does not take timezones into account Key: JBIDE-22244 URL: https://issues.jboss.org/browse/JBIDE-22244 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Reporter: Xavier Coulon it seems like the default {{HOURS}} value ('2') for the job that copies bugzilla issues into JIRA (in the ERT project) is not enough to catch the changes. This might be due to the timezones, since the script run by the job and the job itself do not use the same timezone. for example: - I created an issue in BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=492420 on 2016-04-26 03:07:04 EDT - I then manually kicked the job with the {{HOURS}} value set to {{2}} (Build #2073 - Apr 26, 2016 3:19:03 AM). (I assume the TZ is EDT here, too.) - The script output contains the following lines: {{code}} 03:19:10 [DEBUG] Current datetime: 2016-04-26 07:19:09.521272 (UTC) 03:19:10 [DEBUG] xmlrpc post: {'status_whiteboard': 'RHT', 'last_change_time': '2016-04-26 04:19'} 03:19:10 [DEBUG] buglist get: https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT&chfieldfr... 03:19:10 [DEBUG] Found 0 bugzillas to process {{code}} In the mean time, setting the {{HOURS}} value to '6', I was able to get the issue created in JIRA. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint-... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22244) BZ-JIRA job configuration does not take timezones into account

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22244?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22244: ---------------------------------- Affects Version/s: 4.3.1.Final > BZ-JIRA job configuration does not take timezones into account > -------------------------------------------------------------- > > Key: JBIDE-22244 > URL: https://issues.jboss.org/browse/JBIDE-22244 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Final > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > > it seems like the default {{HOURS}} value ('2') for the job that copies bugzilla issues into JIRA (in the ERT project) is not enough to catch the changes. This might be due to the timezones, since the script run by the job and the job itself do not use the same timezone. > for example: > - I created an issue in BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=492420 on 2016-04-26 03:07:04 EDT > - I then manually kicked the job with the {{HOURS}} value set to {{2}} (Build #2073 - Apr 26, 2016 3:19:03 AM). (I assume the TZ is EDT here, too.) > - The script output contains the following lines: > {{code}} > 03:19:10 [DEBUG] Current datetime: 2016-04-26 07:19:09.521272 (UTC) > 03:19:10 [DEBUG] xmlrpc post: {'status_whiteboard': 'RHT', 'last_change_time': '2016-04-26 04:19'} > 03:19:10 [DEBUG] buglist get: https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT&chfieldfr... > 03:19:10 [DEBUG] Found 0 bugzillas to process > {{code}} > In the mean time, setting the {{HOURS}} value to '6', I was able to get the issue created in JIRA. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint-... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22244) BZ-JIRA job configuration does not take timezones into account

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22244?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-22244: ------------------------------------- Assignee: Max Rydahl Andersen > BZ-JIRA job configuration does not take timezones into account > -------------------------------------------------------------- > > Key: JBIDE-22244 > URL: https://issues.jboss.org/browse/JBIDE-22244 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Final > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > > it seems like the default {{HOURS}} value ('2') for the job that copies bugzilla issues into JIRA (in the ERT project) is not enough to catch the changes. This might be due to the timezones, since the script run by the job and the job itself do not use the same timezone. > for example: > - I created an issue in BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=492420 on 2016-04-26 03:07:04 EDT > - I then manually kicked the job with the {{HOURS}} value set to {{2}} (Build #2073 - Apr 26, 2016 3:19:03 AM). (I assume the TZ is EDT here, too.) > - The script output contains the following lines: > {{code}} > 03:19:10 [DEBUG] Current datetime: 2016-04-26 07:19:09.521272 (UTC) > 03:19:10 [DEBUG] xmlrpc post: {'status_whiteboard': 'RHT', 'last_change_time': '2016-04-26 04:19'} > 03:19:10 [DEBUG] buglist get: https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT&chfieldfr... > 03:19:10 [DEBUG] Found 0 bugzillas to process > {{code}} > In the mean time, setting the {{HOURS}} value to '6', I was able to get the issue created in JIRA. > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint-... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-164) Improve connection detection in connection wizard [EBZ#475892]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-164: --------------------------------------- Summary: Improve connection detection in connection wizard [EBZ#475892] Key: ERT-164 URL: https://issues.jboss.org/browse/ERT-164 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot The wizard should not block the UI when opening (especially when connection settings are found but no Docker daemon is available) Also, in case of connection test failure, an error dialog with the root cause would be interesting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-165) Refactor the Connection Wizard [EBZ#492420]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-165: --------------------------------------- Summary: Refactor the Connection Wizard [EBZ#492420] Key: ERT-165 URL: https://issues.jboss.org/browse/ERT-165 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon (4.6) Refactor the connection wizard to provide: - a table with all existing Docker instances (native, Docker for Mac/Windows and Docker Machine) - a simplified form to specify custom settings, more directly based on the env variables that are used by the Docker CLI client (DOCKER_HOST, DOCKER_TLS_VERIFY and DOCKER_CERT_PATH) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22207) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Hibernate]

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22207?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-22207. ----------------------------- Resolution: Done All the missing commits have either a corresponding commit in master or are not relevant to master. > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Hibernate] > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22207 > URL: https://issues.jboss.org/browse/JBIDE-22207 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Rob Stryker > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Hibernate]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-hibernate at https://github.com/jbosstools/jbosstools-hibernate/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "fe17a3" is the last common ancestor of jbosstools-4.3.x and master > fe17a3 is 226 commits ago in branch master > fe17a3 is 14 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-hibernate//commit/40d70e779b0f4e... > - https://github.com/jbosstools/jbosstools-hibernate//commit/470f7350047717... > - https://github.com/jbosstools/jbosstools-hibernate//commit/1aebe78228b378... > - https://github.com/jbosstools/jbosstools-hibernate//commit/e4ef139e682ab0... > - https://github.com/jbosstools/jbosstools-hibernate//commit/4433454f98bcd9... > - https://github.com/jbosstools/jbosstools-hibernate//commit/af17a74daccaf0... > - https://github.com/jbosstools/jbosstools-hibernate//commit/0cfa89c8a3686f... > - https://github.com/jbosstools/jbosstools-hibernate//commit/d30996173ae1a7... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Hibernate task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-21857: -------------------------------------- JMX will not work out of the box with OpenShift: http://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.ht... > Hot class reload doesn't work on OpenShift > ------------------------------------------ > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Thomas Mäder > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > Attachments: HCRFailure.zip > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3849) Store downloaded requirements for bundled installer between builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3849?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3849: ----------------------------- Attachment: jbds-jar-0-length-in-7zip.png Reason is that the jbds.jar file embedded in C:\Users\nboldt\Documents\GitHub\developer-platform-install\dist\win\jboss-devstudio-platform-win32-x64.7z\ contains 0 bytes, which suggests that the function called back BEFORE the copy was complete (or there was a file lock somehow). [^jbds-jar-0-length-in-7zip.png] > Store downloaded requirements for bundled installer between builds > ------------------------------------------------------------------ > > Key: JBDS-3849 > URL: https://issues.jboss.org/browse/JBDS-3849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Nick Boldt > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: jbds-jar-0-length-in-7zip.png, works-but-too-small.png > > > Now build downloads all bundled binaries in every build, because the got wiped out by clean task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3849) Store downloaded requirements for bundled installer between builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3849?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3849 at 4/25/16 10:28 PM: ------------------------------------------------------------ New PR... https://github.com/redhat-developer-tooling/developer-platform-install/pu... With Denis' help, this task will block doing the 7 downloads and 7 copies before proceeding to the next task. However, I end up with a 1GB .exe instead of a 1.5GB one, despite having the correct file sizes in the prefetch-dependencies cache folder & in the dist/win/jboss-devstudio-platform-win32-x64 folder: {code} $➔ du -sch * 84K cdk.zip 844K cygwin.exe 518M jbds.jar 74M jdk.zip 14M oc.zip 352K pscp.exe 927M rhel-vagrant-virtualbox.box 1.5G total {code} !works-but-too-small.png! was (Author: nickboldt): New PR... https://github.com/redhat-developer-tooling/developer-platform-install/pu... With Denis' help, this task will block doing the 7 downloads and 7 copies before proceeding to the next task. However, I end up with a 1GB .exe instead of a 1.5GB one. !works-but-too-small.png! > Store downloaded requirements for bundled installer between builds > ------------------------------------------------------------------ > > Key: JBDS-3849 > URL: https://issues.jboss.org/browse/JBDS-3849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Nick Boldt > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: works-but-too-small.png > > > Now build downloads all bundled binaries in every build, because the got wiped out by clean task. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3849) Store downloaded requirements for bundled installer between builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3849?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3849 at 4/25/16 10:27 PM: ------------------------------------------------------------ New PR... https://github.com/redhat-developer-tooling/developer-platform-install/pu... With Denis' help, this task will block doing the 7 downloads and 7 copies before proceeding to the next task. However, I end up with a 1GB .exe instead of a 1.5GB one. !works-but-too-small.png! was (Author: nickboldt): New PR... https://github.com/redhat-developer-tooling/developer-platform-install/pu... With Denis' help, this task will block doing the 7 downloads and 7 copies before proceeding to the next task. However, I end up with a 1GB .exe instead of a 1.5GB one. > Store downloaded requirements for bundled installer between builds > ------------------------------------------------------------------ > > Key: JBDS-3849 > URL: https://issues.jboss.org/browse/JBDS-3849 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Nick Boldt > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: works-but-too-small.png > > > Now build downloads all bundled binaries in every build, because the got wiped out by clean task. -- 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 April 2016