April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23924) Properties: display properties for a buildconfig with build type "Binary"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23924?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23924: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.4.AM3) > Properties: display properties for a buildconfig with build type "Binary" > ------------------------------------------------------------------------- > > Key: JBIDE-23924 > URL: https://issues.jboss.org/browse/JBIDE-23924 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24146) Support pipeline deployment style

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24146?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24146: ------------------------------------------ [~jeffmaury] next version is 4.4.4.Final. Normally we would not add new features in the last sprint for a Final version. Do we keep this approach and reschedule this to 4.5.0.AM1? > Support pipeline deployment style > --------------------------------- > > Key: JBIDE-24146 > URL: https://issues.jboss.org/browse/JBIDE-24146 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, wizard > Fix For: 4.4.4.Final > > Attachments: jenkins-pipeline-template.png, jenkins-variants.png, pipeline-build.png, webui-edit-pipeline-file.png > > > In the web-console jenkins pipelines are supported in the following way: > * when opening up an empty project you get a special template: > !jenkins-pipeline-template.png! > * which offers 2 different jenkins variants (and a full example that contains app source and build pipeline): > !jenkins-variants.png! > * once executed you get a special build type *pipeline* > !pipeline-build.png! > * the full example template is using the following build config with the strategy type *JenkinsPipeline*: > {code} > apiVersion: v1 > kind: BuildConfig > metadata: > name: sample-pipeline > namespace: gulu > selfLink: /oapi/v1/namespaces/gulu/buildconfigs/sample-pipeline > uid: 12dec3c8-1948-11e7-a217-0251082287a6 > resourceVersion: '3757' > creationTimestamp: '2017-04-04T15:05:00Z' > labels: > app: jenkins-pipeline-example > name: sample-pipeline > template: application-template-sample-pipeline > annotations: > pipeline.alpha.openshift.io/uses: >- > [{"name": "nodejs-mongodb-example", "namespace": "", "kind": > "DeploymentConfig"}] > spec: > triggers: > - type: GitHub > github: > secret: secret101 > - type: Generic > generic: > secret: secret101 > runPolicy: Serial > source: > type: None > strategy: > type: JenkinsPipeline > jenkinsPipelineStrategy: > jenkinsfile: >- > node('nodejs') { > stage 'build' > openshiftBuild(buildConfig: 'nodejs-mongodb-example', showBuildLogs: > 'true') > stage 'deploy' > openshiftDeploy(deploymentConfig: 'nodejs-mongodb-example') > } > output: {} > resources: {} > postCommit: {} > nodeSelector: null > status: > lastVersion: 1 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24146) Support pipeline deployment style

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24146?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24146: ------------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Support pipeline deployment style > --------------------------------- > > Key: JBIDE-24146 > URL: https://issues.jboss.org/browse/JBIDE-24146 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, wizard > Fix For: 4.4.4.Final > > Attachments: jenkins-pipeline-template.png, jenkins-variants.png, pipeline-build.png, webui-edit-pipeline-file.png > > > In the web-console jenkins pipelines are supported in the following way: > * when opening up an empty project you get a special template: > !jenkins-pipeline-template.png! > * which offers 2 different jenkins variants (and a full example that contains app source and build pipeline): > !jenkins-variants.png! > * once executed you get a special build type *pipeline* > !pipeline-build.png! > * the full example template is using the following build config with the strategy type *JenkinsPipeline*: > {code} > apiVersion: v1 > kind: BuildConfig > metadata: > name: sample-pipeline > namespace: gulu > selfLink: /oapi/v1/namespaces/gulu/buildconfigs/sample-pipeline > uid: 12dec3c8-1948-11e7-a217-0251082287a6 > resourceVersion: '3757' > creationTimestamp: '2017-04-04T15:05:00Z' > labels: > app: jenkins-pipeline-example > name: sample-pipeline > template: application-template-sample-pipeline > annotations: > pipeline.alpha.openshift.io/uses: >- > [{"name": "nodejs-mongodb-example", "namespace": "", "kind": > "DeploymentConfig"}] > spec: > triggers: > - type: GitHub > github: > secret: secret101 > - type: Generic > generic: > secret: secret101 > runPolicy: Serial > source: > type: None > strategy: > type: JenkinsPipeline > jenkinsPipelineStrategy: > jenkinsfile: >- > node('nodejs') { > stage 'build' > openshiftBuild(buildConfig: 'nodejs-mongodb-example', showBuildLogs: > 'true') > stage 'deploy' > openshiftDeploy(deploymentConfig: 'nodejs-mongodb-example') > } > output: {} > resources: {} > postCommit: {} > nodeSelector: null > status: > lastVersion: 1 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23626: ------------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: oc_binary, preferences > Fix For: 4.4.4.Final > > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3 (it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24185) Server adapter: approach to set nodejs/eap apps to debugging is inconsistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24185?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24185: ------------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Server adapter: approach to set nodejs/eap apps to debugging is inconsistent > ---------------------------------------------------------------------------- > > Key: JBIDE-24185 > URL: https://issues.jboss.org/browse/JBIDE-24185 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Fix For: 4.4.4.Final > > > * eap > ** if you want to debug you have to set *DEBUG* env variable in the rc to *true*. The env variable key is defined in the docker image label *"com.redhat.dev-mode"*. > {code} > "com.redhat.dev-mode": "DEBUG:true", > {code} > ** to use a custom debugging port you can set the *DEBUG_PORT* env var. The default port is 8787 as defined in the docker image label > {code} > "com.redhat.dev-mode.port": "DEBUG_PORT:8787" > {code} > * nodejs > ** to debug a nodejs application you have to set *DEV_MODE* to *true* and also set *DEBUG_PORT* to some value, even though the docker image label defines the default port as being *5858* > {code} > "com.redhat.dev-mode": "DEV_MODE:false", > "com.redhat.dev-mode.port": "DEBUG_PORT:5858", > {code} > The documentation actually confirms the fact that :5858 is the default: https://docs.openshift.org/latest/using_images/s2i_images/nodejs.html#nod... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20529: ------------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Master JIRA for XML Validation Problems > --------------------------------------- > > Key: JBIDE-20529 > URL: https://issues.jboss.org/browse/JBIDE-20529 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples, server > Reporter: Rob Stryker > Assignee: Andre Dietisheim > Labels: xtriage > Fix For: 4.4.4.Final > > > This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21593) Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21593?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21593: ------------------------------------- Fix Version/s: 4.4.4.Final (was: 4.4.4.AM3) > Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21593 > URL: https://issues.jboss.org/browse/JBIDE-21593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: Fedora 22, GTK 3. > Reporter: Marián Labuda > Labels: application_wizard, explorer, openshift_v3 > Fix For: 4.4.4.Final > > Attachments: empty_project.png > > > When I am opening a new OpenShift application wizard on OpenShift 3 connection where are no projects yet, at first project dialog to create a new project is opened. Upon creation of a new project, dialog is closed and I am "redirected" back to application wizard, where newly created project should be preselected. Problem is the new project is shown as empty tree item in OpenShift explorer (this happens also if new project dialog is opened directly from the context menu of a clean connection) what makes new OpenShift application wizard unusable, because there are no projects in combo, no matter what. See following screenshot > !empty_project.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24179) Command to tune autoscaling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24179?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24179: ------------------------------------- Fix Version/s: 4.5.0.AM1 > Command to tune autoscaling > --------------------------- > > Key: JBIDE-24179 > URL: https://issues.jboss.org/browse/JBIDE-24179 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24177) Command to tune storage

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24177?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24177: ------------------------------------- Fix Version/s: 4.5.0.AM1 > Command to tune storage > ----------------------- > > Key: JBIDE-24177 > URL: https://issues.jboss.org/browse/JBIDE-24177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24174) When deploying user should be able to set the health checks (readiness and liveness)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24174?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24174: ------------------------------------- Fix Version/s: 4.5.0.AM1 > When deploying user should be able to set the health checks (readiness and liveness) > ------------------------------------------------------------------------------------ > > Key: JBIDE-24174 > URL: https://issues.jboss.org/browse/JBIDE-24174 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v2, wizard > Fix For: 4.5.0.AM1 > > > Note: this is not yet supported with the OCP web console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017