September 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-24899) Deploy Docker Image wizard: Image not found

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-24899?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-24899: ------------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Deploy Docker Image wizard: Image not found > ------------------------------------------- > > Key: JBIDE-24899 > URL: https://issues.jboss.org/browse/JBIDE-24899 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, docker, openshift > Affects Versions: 4.5.1.AM1 > Reporter: Josef Kopriva > Assignee: André Dietisheim > Priority: Major > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.13.0.Final > > Attachments: image-2017-08-29-09-50-20-927.png > > > Exception in Error log: > {code:java} > Failed to inspect image: '172.30.1.1:5000/test/hola:latest' > com.spotify.docker.client.exceptions.ImageNotFoundException: Image not found: 172.30.1.1:5000/test/hola:latest > at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1330) > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImageInfo(DockerConnection.java:896) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.lookupImageMetadata(DeployImageWizardModel.java:655) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:354) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: com.spotify.docker.client.exceptions.DockerRequestException: Request error: GET https://192.168.42.121:2376/images/172.30.1.1:5000/test/hola:latest/json: 404 > at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084) > at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2023) > at com.spotify.docker.client.DefaultDockerClient.inspectImage(DefaultDockerClient.java:1326) > ... 5 more > Caused by: javax.ws.rs.NotFoundException: HTTP 404 Not Found > at org.glassfish.jersey.client.JerseyInvocation.convertToException(JerseyInvocation.java:1008) > at org.glassfish.jersey.client.JerseyInvocation.translate(JerseyInvocation.java:816) > at org.glassfish.jersey.client.JerseyInvocation.access$700(JerseyInvocation.java:92) > at org.glassfish.jersey.client.JerseyInvocation$5.completed(JerseyInvocation.java:773) > at org.glassfish.jersey.client.ClientRuntime.processResponse(ClientRuntime.java:198) > at org.glassfish.jersey.client.ClientRuntime.access$300(ClientRuntime.java:79) > at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:180) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271) > at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267) > at org.glassfish.jersey.internal.Errors.process(Errors.java:315) > at org.glassfish.jersey.internal.Errors.process(Errors.java:297) > at org.glassfish.jersey.internal.Errors.process(Errors.java:267) > at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:340) > at org.glassfish.jersey.client.ClientRuntime$3.run(ClientRuntime.java:210) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > eclipse.buildId=11.1.0.AM1-v20170824-1835-B873 > java.version=1.8.0_141 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-26813) use latest openshift client 8.0.1

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26813?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26813: ------------------------------------- Fix Version/s: 4.13.0.AM1 > use latest openshift client 8.0.1 > --------------------------------- > > Key: JBIDE-26813 > URL: https://issues.jboss.org/browse/JBIDE-26813 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.12.0.Final > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Fix For: 4.13.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years

1
0
0 / 0

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

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26760?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26760: ---------------------------------- Description: 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, 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 was: 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 that can be found here: * [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...] *Job migration workflow:* * Check on best practices and migrate job according to them, use existing examples, 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. [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 > 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.13.0.Final > > > 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, 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.5#713005)

5 years

1
0
0 / 0

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

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26760?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26760: ---------------------------------- Description: 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 was: 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, 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 > 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.13.0.Final > > > 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.5#713005)

5 years

1
0
0 / 0

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

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26760?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26760: ---------------------------------- Description: 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 that can be found here: * [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...] *Job migration workflow:* * Check on best practices and migrate job according to them, use existing examples, 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. [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 was: 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 that can be found here: * [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...] job migration workflow: * Check on best practices and migrate job according to them, use existing examples, 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. [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 > 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.13.0.Final > > > 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 that can be found here: > * [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...] > *Job migration workflow:* > * Check on best practices and migrate job according to them, use existing examples, 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. > [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.5#713005)

5 years

1
0
0 / 0

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

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26760?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26760: ---------------------------------- Description: 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 that can be found here: * [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...] job migration workflow: * Check on best practices and migrate job according to them, use existing examples, 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. [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 was: 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 that can be found here: * [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...] job migration workflow: * Check on best practices and migrate job according to them, use existing examples, already migrated jobs * Verify that migration is successful by running it locally using jcasc [2]. * Create a PR and notify your component backup to get +1 on the PR or Let your backup to verify sub-task jira [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 > 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.13.0.Final > > > 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 that can be found here: > * [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...] > job migration workflow: > * Check on best practices and migrate job according to them, use existing examples, 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. > [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.5#713005)

5 years

1
0
0 / 0

[JBoss JIRA] (ERT-759) ToolItem setDisabledImage isn't used [EBZ#302918]

by Eric Williams (Jira)

[ https://issues.jboss.org/browse/ERT-759?page=com.atlassian.jira.plugin.sy... ] Eric Williams reassigned ERT-759: --------------------------------- Sprint: devex #172 Sep 2019 Assignee: Eric Williams > ToolItem setDisabledImage isn't used [EBZ#302918] > ------------------------------------------------- > > Key: ERT-759 > URL: https://issues.jboss.org/browse/ERT-759 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Friendly Jira Robot > Assignee: Eric Williams > Priority: Major > Labels: SWT, bzira > > I recently had a disabled handler for a command that also provided icon in the commandImages extension point. However, the disabled icon was not honored by the toolbar item, and instead Eclipse drew its own clumsy icon derived from the normal one. Setting the disabled icon directly on the toolbar contribution worked. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-26848) CRC server adapter: existing connection is not updated

by André Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26848?page=com.atlassian.jira.plugi... ] André Dietisheim updated JBIDE-26848: ------------------------------------- Description: Steps: # ASSERT: Have CRC server adapter # ASSERT: in openshift explorer: have connection # EXEC: in cmd-line: kill ~/.crc # EXEC: start server adapter # ASSERT: it complains that crc is not set up, asks if it should set it up # EXEC: ok to set it up # ASSERT: server is [started] # EXEC: refresh connection in openshift explorer Result: Connection wont work, it's an outdated connection to a crc cluster that doesnt exist any more. Server adapter didnt update the connection. was: steps: # ASSERT: Have CRC server adapter # ASSERT: in openshift explorer: have connection # EXEC: in cmd-line: kill ~/.crc # EXEC: start server adapter # ASSERT: it complains that crc is not set up, asks if it should set it up # EXEC: ok to set it up # ASSERT: server is [started] # EXEC: refresh connection in openshift explorer Result: Connection wont work, it's an outdated connection to a crc cluster that doesnt exist any more. Server adapter didnt update the connection. > CRC server adapter: existing connection is not updated > ------------------------------------------------------ > > Key: JBIDE-26848 > URL: https://issues.jboss.org/browse/JBIDE-26848 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Priority: Major > Fix For: 4.13.0.Final > > > Steps: > # ASSERT: Have CRC server adapter > # ASSERT: in openshift explorer: have connection > # EXEC: in cmd-line: kill ~/.crc > # EXEC: start server adapter > # ASSERT: it complains that crc is not set up, asks if it should set it up > # EXEC: ok to set it up > # ASSERT: server is [started] > # EXEC: refresh connection in openshift explorer > Result: > Connection wont work, it's an outdated connection to a crc cluster that doesnt exist any more. Server adapter didnt update the connection. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-26848) CRC server adapter: existing connection is not updated

by André Dietisheim (Jira)

André Dietisheim created JBIDE-26848: ---------------------------------------- Summary: CRC server adapter: existing connection is not updated Key: JBIDE-26848 URL: https://issues.jboss.org/browse/JBIDE-26848 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.13.0.AM1 Reporter: André Dietisheim Fix For: 4.13.0.Final steps: # ASSERT: Have CRC server adapter # ASSERT: in openshift explorer: have connection # EXEC: in cmd-line: kill ~/.crc # EXEC: start server adapter # ASSERT: it complains that crc is not set up, asks if it should set it up # EXEC: ok to set it up # ASSERT: server is [started] # EXEC: refresh connection in openshift explorer Result: Connection wont work, it's an outdated connection to a crc cluster that doesnt exist any more. Server adapter didnt update the connection. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years

1
0
0 / 0

[JBoss JIRA] (ERT-759) ToolItem setDisabledImage isn't used [EBZ#302918]

by Friendly Jira Robot (Jira)

Friendly Jira Robot created ERT-759: --------------------------------------- Summary: ToolItem setDisabledImage isn't used [EBZ#302918] Key: ERT-759 URL: https://issues.jboss.org/browse/ERT-759 Project: Eclipse Release Train Issue Type: Task Components: Platform Reporter: Friendly Jira Robot I recently had a disabled handler for a command that also provided icon in the commandImages extension point. However, the disabled icon was not honored by the toolbar item, and instead Eclipse drew its own clumsy icon derived from the normal one. Setting the disabled icon directly on the toolbar contribution worked. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2019