January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23733: ---------------------------------- Summary: Merge .smoke and .nightly integration jobs into a single job and run them weekly Key: JBIDE-23733 URL: https://issues.jboss.org/browse/JBIDE-23733 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-tests Affects Versions: 4.4.3.AM1 Reporter: Nick Boldt Purpose: a) easier maintenance of jobs / tests b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests c) more frequent full integration runs (rather than once per sprint, once per week) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23733: ---------------------------------- Assignee: Nick Boldt > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23733: ---------------------------------- Assignee: Rastislav Wagner (was: Nick Boldt) > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23733: ------------------------------- Description: Purpose: a) easier maintenance of jobs / tests b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests c) more frequent full integration runs (rather than once per sprint, once per week) Tests to merge are in this view: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... was: Purpose: a) easier maintenance of jobs / tests b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests c) more frequent full integration runs (rather than once per sprint, once per week) > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) > Tests to merge are in this view: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21857: ---------------------------------------- Assignee: Andre Dietisheim (was: Rob Stryker) > Hot code replacement 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: Andre Dietisheim > Fix For: 4.4.3.AM2 > > Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > 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 (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23729) Implement integration ui tests for validation of job.xml file in design view tab

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23729?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23729: ---------------------------------- Story Points: 8 > Implement integration ui tests for validation of job.xml file in design view tab > --------------------------------------------------------------------------------- > > Key: JBIDE-23729 > URL: https://issues.jboss.org/browse/JBIDE-23729 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.4.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: batch, integration_tests > Fix For: 4.4.3.AM2 > > > Implement ui int. tests for batch job.xml validation that is used in design view tab. It is a subset of features referenced in [jira|https://issues.jboss.org/browse/JBIDE-23728]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23728) Add new batch integration UI tests for validating the source in job.xml file

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23728?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23728: ---------------------------------- Story Points: 12 (was: 8) > Add new batch integration UI tests for validating the source in job.xml file > ---------------------------------------------------------------------------- > > Key: JBIDE-23728 > URL: https://issues.jboss.org/browse/JBIDE-23728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.4.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: batch, integration-test > Fix For: 4.4.3.AM2 > > > Implement integration ui tests for validation feature of batch job.xml file. Manipulate with xml file via source tab and check its functionality resulting in Problems View. > 1. Ref element contains valid name of specific artifact > 2. Properties link to valid java field of #jobProperties["xyz"] > 3. Id is unique > 4. Attributes next and to refer to id of step | split | flow | decision at the same level as the current execution element > 5. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level > 6. Sequence of execution elements defined by @next and @to should not loop. > 7. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4237) Generate CVE vulnerability report for devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4237?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4237: ---------------------------------- For PMD specifically, we could move from PMD 4.0.7 (net.sourceforge.pmd.eclipse.plugin_4.0.7.v20150522-1709) to the latest 5.5 release, which might resolve some of these issues. Haven't updated PMD since 2015/05, so we're past due for an update [1]. See JBIDE-23730 [1] https://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/ > Generate CVE vulnerability report for devstudio > ----------------------------------------------- > > Key: JBDS-4237 > URL: https://issues.jboss.org/browse/JBDS-4237 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, versionwatch > Affects Versions: 10.3.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.3.0.AM2 > > Attachments: Screenshot_2017-01-10_18-58-03.png, Screenshot_2017-01-10_19-04-45.png > > > 0. download http://dl.bintray.com/jeremy-long/owasp/dependency-check-1.4.4-release.zip > 1. download latest CI build update site zip, target platform zip, central zip, etc. > 2. unpack update site zips > 3. unpack dep-check zip > 4. generate CVE report for each fetched zip: > {code} > ./dependency-check.sh --disableAssembly -s /path/to/update-site/plugins/ --project devstudio_check -o WORKSPACE/path/to/report/folder/ > {code} > Should use https://wiki.jenkins-ci.org/display/JENKINS/OWASP+Dependency-Check+Plugin for better reporting and maybe even enable this on every project job (once moved to CCI Jenkins). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23728) Add new batch integration UI tests for validating the source in job.xml file

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23728?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-23728: ---------------------------------- Story Points: 8 > Add new batch integration UI tests for validating the source in job.xml file > ---------------------------------------------------------------------------- > > Key: JBIDE-23728 > URL: https://issues.jboss.org/browse/JBIDE-23728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.4.2.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: batch, integration-test > Fix For: 4.4.3.AM2 > > > Implement integration ui tests for validation feature of batch job.xml file. Manipulate with xml file via source tab and check its functionality resulting in Problems View. > 1. Ref element contains valid name of specific artifact > 2. Properties link to valid java field of #jobProperties["xyz"] > 3. Id is unique > 4. Attributes next and to refer to id of step | split | flow | decision at the same level as the current execution element > 5. Attributes 'flow/stop/@restart', 'step/stop/@restart' should refer to id of step | split | flow | decision at the job level > 6. Sequence of execution elements defined by @next and @to should not loop. > 7. Value of attribute 'include/@class' and 'exclude/@class' is qualified name of an exception class. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21857: ------------------------------------- Sprint: devex #123 November 2016, devex #126 January 2017 (was: devex #123 November 2016) > Hot code replacement 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: Rob Stryker > Fix For: 4.4.3.AM2 > > Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > 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 (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 January 2017