November 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-26792) OpenShift ITests: Fix failing ServerAdapterFromResourceTest

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26792?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26792: ------------------------------- Fix Version/s: 4.14.0.AM1 (was: 4.13.0.Final) > OpenShift ITests: Fix failing ServerAdapterFromResourceTest > ----------------------------------------------------------- > > Key: JBIDE-26792 > URL: https://issues.jboss.org/browse/JBIDE-26792 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, openshift > Affects Versions: 4.13.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.14.0.AM1 > > > Test is failing on Jenkins: > {code:java} > org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: > Timeout after: 120 s.: The following jobs are still running: > Publishing to nodejs-example (Service) at OpenShift (127.0.0.1)... > Stopping nodejs-example (Service) at OpenShift (127.0.0.1) > Building workspace > at org.jboss.tools.openshift.ui.bot.test.application.v3.adapter.ServerAdapterFromResourceTest.removeAdapterIfExists(ServerAdapterFromResourceTest.java:128) > {code} > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26791) Migration of QE Infra provisioning jobs under dev-platform/cci-config

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26791?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26791: ------------------------------- Fix Version/s: 4.14.0.AM1 (was: 4.13.0.Final) > Migration of QE Infra provisioning jobs under dev-platform/cci-config > --------------------------------------------------------------------- > > Key: JBIDE-26791 > URL: https://issues.jboss.org/browse/JBIDE-26791 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.14.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26788) Prepare write up of using & examples on jcasc + cci-config for codeready studio/adapters on PSI jenkins

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26788?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26788: ------------------------------- Fix Version/s: 4.14.0.AM1 (was: 4.13.0.Final) > Prepare write up of using & examples on jcasc + cci-config for codeready studio/adapters on PSI jenkins > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26788 > URL: https://issues.jboss.org/browse/JBIDE-26788 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.14.0.AM1 > > > Prepare short readme & docs of steps, procedures, examples, etc. for using jcasc [1] + codeready studio declaration repo [2] , all for usage on psi jenkins [3]. > [1]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc > [2]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config > [3]: https://issues.jboss.org/browse/JBIDE-26737 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26786) Add windows machines templates and configure them to be able to connect to studio-jenkins-csb-codeready jenkins

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26786?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26786: ------------------------------- Fix Version/s: 4.14.0.AM1 (was: 4.13.0.Final) > Add windows machines templates and configure them to be able to connect to studio-jenkins-csb-codeready jenkins > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26786 > URL: https://issues.jboss.org/browse/JBIDE-26786 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.14.0.AM1 > > > This issue aims to use windows machine on jenkins on PSI. Due to need of a test to be using UI env. there is a connection initialization script that makes a connection to jenkins master (JNLP agent using TCP on 50000) from the agent after machine is spawned. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26763) Migrate JSF integration tests into job DSL

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26763?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26763: ------------------------------- Fix Version/s: 4.14.0.AM1 (was: 4.13.0.Final) > Migrate JSF integration tests into job DSL > ------------------------------------------ > > Key: JBIDE-26763 > URL: https://issues.jboss.org/browse/JBIDE-26763 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.14.0.AM1 > > > Rewrite QE integration tests into job DSL and place them under dev-platform/cci-config repo -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26762) Migrate CDK integration tests into job DSL

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26762?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26762: ------------------------------- Fix Version/s: 4.14.0.AM1 (was: 4.13.0.Final) > Migrate CDK integration tests into job DSL > ------------------------------------------ > > Key: JBIDE-26762 > URL: https://issues.jboss.org/browse/JBIDE-26762 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests, qa > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.14.0.AM1 > > > Rewrite QE integration tests into job DSL and place them under dev-platform/cci-config repo -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26761) Migrate Batch integration tests into job DSL

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26761?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26761: ------------------------------- Fix Version/s: 4.14.0.AM1 (was: 4.13.0.Final) > Migrate Batch integration tests into job DSL > -------------------------------------------- > > Key: JBIDE-26761 > URL: https://issues.jboss.org/browse/JBIDE-26761 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.14.0.AM1 > > > Rewrite QE integration tests into job DSL and place them under dev-platform/cci-config repo -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26760) Migrate QE integration tests jobs into job DSL under dev-platform/cci-config repo

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26760?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26760: ------------------------------- Fix Version/s: 4.14.0.AM1 (was: 4.13.0.Final) > Migrate QE integration tests jobs into job DSL under dev-platform/cci-config repo > --------------------------------------------------------------------------------- > > Key: JBIDE-26760 > URL: https://issues.jboss.org/browse/JBIDE-26760 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.13.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: integration_tests, jenkins, jenkins_pipeline > Fix For: 4.14.0.AM1 > > > As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices. > *Job migration workflow:* > * Check on best practices and migrate job according to them, use existing examples of already migrated jobs > * Verify that migration is successful by running it locally using jcasc [2]. And share the test results in your sub-tasks jira. > * Create a PR and notify your component backup to get +1 on the PR. > *Best Practices* > * [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pag...] > * [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts] > * [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job...] > * [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types] > * [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers] > * [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready] > * [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM] > Some other are still in doing: > * [Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEo...] > * [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters] > * [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+a...] > [1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config > [2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26759) Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_4 to version 5.4.4.Final

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26759?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26759: ------------------------------- Fix Version/s: 4.14.0.AM1 (was: 4.13.0.Final) > Update hibernate tools dependency of org.jboss.tools.hibernate.runtime.v_5_4 to version 5.4.4.Final > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-26759 > URL: https://issues.jboss.org/browse/JBIDE-26759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.12.0.Final > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Major > Fix For: 4.14.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26878) Improve validation of CRC Binary and Pull Secret File in CRC Server Wizard and Editor

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26878?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26878: ------------------------------- Fix Version/s: 4.14.0.AM1 (was: 4.13.0.Final) > Improve validation of CRC Binary and Pull Secret File in CRC Server Wizard and Editor > ------------------------------------------------------------------------------------- > > Key: JBIDE-26878 > URL: https://issues.jboss.org/browse/JBIDE-26878 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.13.0.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Major > Fix For: 4.14.x, 4.14.0.AM1 > > > I can image improved validation of Pull secret file that is available in CRC Server wizard and Server Editor. > Missing validation of CRC Binary: > * Please select a valid CRC Binary, which would check that file is really a crc binary - we used similar validation for minishift where (I f I recall it right) we checked in process the output from `minishift version` or `minishift status` command. Something similar I can imagine to be used for crc. Since `crc status` could return different outputs, version seems to be better option. I would agree to postpone this validation once the crc is GA. then please ignore this and create new jira issue. Thanks! > I can imagine all of those validation in action for pull secret path input: > * Path does not exist > * Is not a file > * Is not executable (user cannot read the file) > * Is not a valid Pull secret file (probably check for if file's content is a valid json and/or we can probably validate if json's first object is "auths"? This would be nice, but simple json validation seems fine) > I believe that last three points could be validated at once by reading the file's content and creating valid json object, or else showing the error that given path is no valid a secret file. It's up implementation, right? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 November 2019