[JBoss JIRA] (JBIDE-26167) Import application: error message when trying to import from binary build config is not helpful
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26167?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26167:
-------------------------------------
Description:
steps:
# ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc"
{code}oc login <openshift-server>{code}
# ASSERT: in cmd-line: make sure you that you selected a project in "oc"
{code}oc project <openshift-project-name>{code}
# EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...:
{code}
$ git clone https://github.com/redhat-helloworld-msa/hello
$ cd hello/
$ oc new-build --binary --name=hello -l app=hello
$ mvn package -Popenshift
$ oc start-build hello --from-dir=. --follow
$ oc new-app hello -l app=hello,hystrix.enabled=true
$ oc expose service hello
{code}
# ASSERT: in Explorer: the application-service "hello" is visible
# EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard
RESULT:
The import fails with the following error:
!import-error.png!
The error is correct, the application was created with a binary source type buildconfig, but the error not helpful.
Here's the build config (notice *"source" > "type" > "Binary"*):
{code}
{
"metadata": {
"name": "hello",
"namespace": "jbide25000-2",
"selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello",
"uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd",
"resourceVersion": "360688",
"creationTimestamp": "2018-07-01T07:06:26Z",
"labels": {
"app": "hello"
},
"annotations": {
"openshift.io/generated-by": "OpenShiftNewBuild"
}
},
"spec": {
"triggers": [
{
"type": "GitHub",
"github": {
"secret": "N5TaoJVuWp-YBlwSktc3"
}
},
{
"type": "Generic",
"generic": {
"secret": "ehzK2N2Yv8JDryRFLI5j"
}
}
],
"runPolicy": "Serial",
"source": {
"type": "Binary",
"binary": {}
},
"strategy": {
"type": "Docker",
"dockerStrategy": {}
},
"output": {
"to": {
"kind": "ImageStreamTag",
"name": "hello:latest"
}
},
"resources": {},
"postCommit": {},
"successfulBuildsHistoryLimit": 5,
"failedBuildsHistoryLimit": 5
},
"status": {
"lastVersion": 1
},
"kind": "BuildConfig",
"apiVersion": "v1"
}
{code}
was:
steps:
# ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc"
{code}oc login <openshift-server>{code}
# ASSERT: in cmd-line: make sure you that you selected a project in "oc"
{code}oc project <openshift-project-name>{code}
# EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...:
{code}
$ git clone https://github.com/redhat-helloworld-msa/hello
$ cd hello/
$ oc new-build --binary --name=hello -l app=hello
$ mvn package -Popenshift
$ oc start-build hello --from-dir=. --follow
$ oc new-app hello -l app=hello,hystrix.enabled=true
$ oc expose service hello
{code}
# ASSERT: in Explorer: the application-service "hello" is visible
# EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard
RESULT:
The import fails with the following error:
!import-error.png!
The error is correct, the application was created with a binary buildconfig, but the error not helpful.
Here's the build config (notice "source" > "type" > "Binary":
{code}
{
"metadata": {
"name": "hello",
"namespace": "jbide25000-2",
"selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello",
"uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd",
"resourceVersion": "360688",
"creationTimestamp": "2018-07-01T07:06:26Z",
"labels": {
"app": "hello"
},
"annotations": {
"openshift.io/generated-by": "OpenShiftNewBuild"
}
},
"spec": {
"triggers": [
{
"type": "GitHub",
"github": {
"secret": "N5TaoJVuWp-YBlwSktc3"
}
},
{
"type": "Generic",
"generic": {
"secret": "ehzK2N2Yv8JDryRFLI5j"
}
}
],
"runPolicy": "Serial",
"source": {
"type": "Binary",
"binary": {}
},
"strategy": {
"type": "Docker",
"dockerStrategy": {}
},
"output": {
"to": {
"kind": "ImageStreamTag",
"name": "hello:latest"
}
},
"resources": {},
"postCommit": {},
"successfulBuildsHistoryLimit": 5,
"failedBuildsHistoryLimit": 5
},
"status": {
"lastVersion": 1
},
"kind": "BuildConfig",
"apiVersion": "v1"
}
{code}
> Import application: error message when trying to import from binary build config is not helpful
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-26167
> URL: https://issues.jboss.org/browse/JBIDE-26167
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Labels: import_wizard
> Attachments: import-error.png
>
>
> steps:
> # ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc"
> {code}oc login <openshift-server>{code}
> # ASSERT: in cmd-line: make sure you that you selected a project in "oc"
> {code}oc project <openshift-project-name>{code}
> # EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...:
> {code}
> $ git clone https://github.com/redhat-helloworld-msa/hello
> $ cd hello/
> $ oc new-build --binary --name=hello -l app=hello
> $ mvn package -Popenshift
> $ oc start-build hello --from-dir=. --follow
> $ oc new-app hello -l app=hello,hystrix.enabled=true
> $ oc expose service hello
> {code}
> # ASSERT: in Explorer: the application-service "hello" is visible
> # EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard
> RESULT:
> The import fails with the following error:
> !import-error.png!
> The error is correct, the application was created with a binary source type buildconfig, but the error not helpful.
> Here's the build config (notice *"source" > "type" > "Binary"*):
> {code}
> {
> "metadata": {
> "name": "hello",
> "namespace": "jbide25000-2",
> "selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello",
> "uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd",
> "resourceVersion": "360688",
> "creationTimestamp": "2018-07-01T07:06:26Z",
> "labels": {
> "app": "hello"
> },
> "annotations": {
> "openshift.io/generated-by": "OpenShiftNewBuild"
> }
> },
> "spec": {
> "triggers": [
> {
> "type": "GitHub",
> "github": {
> "secret": "N5TaoJVuWp-YBlwSktc3"
> }
> },
> {
> "type": "Generic",
> "generic": {
> "secret": "ehzK2N2Yv8JDryRFLI5j"
> }
> }
> ],
> "runPolicy": "Serial",
> "source": {
> "type": "Binary",
> "binary": {}
> },
> "strategy": {
> "type": "Docker",
> "dockerStrategy": {}
> },
> "output": {
> "to": {
> "kind": "ImageStreamTag",
> "name": "hello:latest"
> }
> },
> "resources": {},
> "postCommit": {},
> "successfulBuildsHistoryLimit": 5,
> "failedBuildsHistoryLimit": 5
> },
> "status": {
> "lastVersion": 1
> },
> "kind": "BuildConfig",
> "apiVersion": "v1"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26167) Import application: error message when trying to import from binary build config is not helpful
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26167?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26167:
-------------------------------------
Labels: import_wizard (was: )
> Import application: error message when trying to import from binary build config is not helpful
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-26167
> URL: https://issues.jboss.org/browse/JBIDE-26167
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Labels: import_wizard
> Attachments: import-error.png
>
>
> steps:
> # ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc"
> {code}oc login <openshift-server>{code}
> # ASSERT: in cmd-line: make sure you that you selected a project in "oc"
> {code}oc project <openshift-project-name>{code}
> # EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...:
> {code}
> $ git clone https://github.com/redhat-helloworld-msa/hello
> $ cd hello/
> $ oc new-build --binary --name=hello -l app=hello
> $ mvn package -Popenshift
> $ oc start-build hello --from-dir=. --follow
> $ oc new-app hello -l app=hello,hystrix.enabled=true
> $ oc expose service hello
> {code}
> # ASSERT: in Explorer: the application-service "hello" is visible
> # EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard
> RESULT:
> The import fails with the following error:
> !import-error.png!
> The error is correct, the application was created with a binary buildconfig, but the error not helpful.
> Here's the build config (notice "source" > "type" > "Binary":
> {code}
> {
> "metadata": {
> "name": "hello",
> "namespace": "jbide25000-2",
> "selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello",
> "uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd",
> "resourceVersion": "360688",
> "creationTimestamp": "2018-07-01T07:06:26Z",
> "labels": {
> "app": "hello"
> },
> "annotations": {
> "openshift.io/generated-by": "OpenShiftNewBuild"
> }
> },
> "spec": {
> "triggers": [
> {
> "type": "GitHub",
> "github": {
> "secret": "N5TaoJVuWp-YBlwSktc3"
> }
> },
> {
> "type": "Generic",
> "generic": {
> "secret": "ehzK2N2Yv8JDryRFLI5j"
> }
> }
> ],
> "runPolicy": "Serial",
> "source": {
> "type": "Binary",
> "binary": {}
> },
> "strategy": {
> "type": "Docker",
> "dockerStrategy": {}
> },
> "output": {
> "to": {
> "kind": "ImageStreamTag",
> "name": "hello:latest"
> }
> },
> "resources": {},
> "postCommit": {},
> "successfulBuildsHistoryLimit": 5,
> "failedBuildsHistoryLimit": 5
> },
> "status": {
> "lastVersion": 1
> },
> "kind": "BuildConfig",
> "apiVersion": "v1"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26167) Import application: error message when trying to import from binary build config is not helpful
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26167?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26167:
-------------------------------------
Description:
steps:
# ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc"
{code}oc login <openshift-server>{code}
# ASSERT: in cmd-line: make sure you that you selected a project in "oc"
{code}oc project <openshift-project-name>{code}
# EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...:
{code}
$ git clone https://github.com/redhat-helloworld-msa/hello
$ cd hello/
$ oc new-build --binary --name=hello -l app=hello
$ mvn package -Popenshift
$ oc start-build hello --from-dir=. --follow
$ oc new-app hello -l app=hello,hystrix.enabled=true
$ oc expose service hello
{code}
# ASSERT: in Explorer: the application-service "hello" is visible
# EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard
Result:
The import fails with the following error:
!import-error.png!
The error is correct, the application was created with a binary buildconfig, but the error not helpful.
Here's the build config (notice "source" > "type" > "Binary":
{code}
{
"metadata": {
"name": "hello",
"namespace": "jbide25000-2",
"selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello",
"uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd",
"resourceVersion": "360688",
"creationTimestamp": "2018-07-01T07:06:26Z",
"labels": {
"app": "hello"
},
"annotations": {
"openshift.io/generated-by": "OpenShiftNewBuild"
}
},
"spec": {
"triggers": [
{
"type": "GitHub",
"github": {
"secret": "N5TaoJVuWp-YBlwSktc3"
}
},
{
"type": "Generic",
"generic": {
"secret": "ehzK2N2Yv8JDryRFLI5j"
}
}
],
"runPolicy": "Serial",
"source": {
"type": "Binary",
"binary": {}
},
"strategy": {
"type": "Docker",
"dockerStrategy": {}
},
"output": {
"to": {
"kind": "ImageStreamTag",
"name": "hello:latest"
}
},
"resources": {},
"postCommit": {},
"successfulBuildsHistoryLimit": 5,
"failedBuildsHistoryLimit": 5
},
"status": {
"lastVersion": 1
},
"kind": "BuildConfig",
"apiVersion": "v1"
}
{code}
was:
steps:
# ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc"
{code}oc login <openshift-server>{code}
# ASSERT: in cmd-line: make sure you that you selected a project in "oc"
{code}oc project <openshift-project-name>{code}
# EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...:
{code}
$ git clone https://github.com/redhat-helloworld-msa/hello
$ cd hello/
$ oc new-build --binary --name=hello -l app=hello
$ mvn package -Popenshift
$ oc start-build hello --from-dir=. --follow
$ oc new-app hello -l app=hello,hystrix.enabled=true
$ oc expose service hello
{code}
# ASSERT: in Explorer: the application-service "hello" is visible
# EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard
Result:
The import fails with the following error:
The error is correct, the application was created with a binary buildconfig, but the error not helpful.
Here's the build config (notice "source" > "type" > "Binary":
{code}
{
"metadata": {
"name": "hello",
"namespace": "jbide25000-2",
"selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello",
"uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd",
"resourceVersion": "360688",
"creationTimestamp": "2018-07-01T07:06:26Z",
"labels": {
"app": "hello"
},
"annotations": {
"openshift.io/generated-by": "OpenShiftNewBuild"
}
},
"spec": {
"triggers": [
{
"type": "GitHub",
"github": {
"secret": "N5TaoJVuWp-YBlwSktc3"
}
},
{
"type": "Generic",
"generic": {
"secret": "ehzK2N2Yv8JDryRFLI5j"
}
}
],
"runPolicy": "Serial",
"source": {
"type": "Binary",
"binary": {}
},
"strategy": {
"type": "Docker",
"dockerStrategy": {}
},
"output": {
"to": {
"kind": "ImageStreamTag",
"name": "hello:latest"
}
},
"resources": {},
"postCommit": {},
"successfulBuildsHistoryLimit": 5,
"failedBuildsHistoryLimit": 5
},
"status": {
"lastVersion": 1
},
"kind": "BuildConfig",
"apiVersion": "v1"
}
{code}
> Import application: error message when trying to import from binary build config is not helpful
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-26167
> URL: https://issues.jboss.org/browse/JBIDE-26167
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Attachments: import-error.png
>
>
> steps:
> # ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc"
> {code}oc login <openshift-server>{code}
> # ASSERT: in cmd-line: make sure you that you selected a project in "oc"
> {code}oc project <openshift-project-name>{code}
> # EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...:
> {code}
> $ git clone https://github.com/redhat-helloworld-msa/hello
> $ cd hello/
> $ oc new-build --binary --name=hello -l app=hello
> $ mvn package -Popenshift
> $ oc start-build hello --from-dir=. --follow
> $ oc new-app hello -l app=hello,hystrix.enabled=true
> $ oc expose service hello
> {code}
> # ASSERT: in Explorer: the application-service "hello" is visible
> # EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard
> Result:
> The import fails with the following error:
> !import-error.png!
> The error is correct, the application was created with a binary buildconfig, but the error not helpful.
> Here's the build config (notice "source" > "type" > "Binary":
> {code}
> {
> "metadata": {
> "name": "hello",
> "namespace": "jbide25000-2",
> "selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello",
> "uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd",
> "resourceVersion": "360688",
> "creationTimestamp": "2018-07-01T07:06:26Z",
> "labels": {
> "app": "hello"
> },
> "annotations": {
> "openshift.io/generated-by": "OpenShiftNewBuild"
> }
> },
> "spec": {
> "triggers": [
> {
> "type": "GitHub",
> "github": {
> "secret": "N5TaoJVuWp-YBlwSktc3"
> }
> },
> {
> "type": "Generic",
> "generic": {
> "secret": "ehzK2N2Yv8JDryRFLI5j"
> }
> }
> ],
> "runPolicy": "Serial",
> "source": {
> "type": "Binary",
> "binary": {}
> },
> "strategy": {
> "type": "Docker",
> "dockerStrategy": {}
> },
> "output": {
> "to": {
> "kind": "ImageStreamTag",
> "name": "hello:latest"
> }
> },
> "resources": {},
> "postCommit": {},
> "successfulBuildsHistoryLimit": 5,
> "failedBuildsHistoryLimit": 5
> },
> "status": {
> "lastVersion": 1
> },
> "kind": "BuildConfig",
> "apiVersion": "v1"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26167) Import application: error message when trying to import from binary build config is not helpful
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26167?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26167:
-------------------------------------
Description:
steps:
# ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc"
{code}oc login <openshift-server>{code}
# ASSERT: in cmd-line: make sure you that you selected a project in "oc"
{code}oc project <openshift-project-name>{code}
# EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...:
{code}
$ git clone https://github.com/redhat-helloworld-msa/hello
$ cd hello/
$ oc new-build --binary --name=hello -l app=hello
$ mvn package -Popenshift
$ oc start-build hello --from-dir=. --follow
$ oc new-app hello -l app=hello,hystrix.enabled=true
$ oc expose service hello
{code}
# ASSERT: in Explorer: the application-service "hello" is visible
# EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard
RESULT:
The import fails with the following error:
!import-error.png!
The error is correct, the application was created with a binary buildconfig, but the error not helpful.
Here's the build config (notice "source" > "type" > "Binary":
{code}
{
"metadata": {
"name": "hello",
"namespace": "jbide25000-2",
"selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello",
"uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd",
"resourceVersion": "360688",
"creationTimestamp": "2018-07-01T07:06:26Z",
"labels": {
"app": "hello"
},
"annotations": {
"openshift.io/generated-by": "OpenShiftNewBuild"
}
},
"spec": {
"triggers": [
{
"type": "GitHub",
"github": {
"secret": "N5TaoJVuWp-YBlwSktc3"
}
},
{
"type": "Generic",
"generic": {
"secret": "ehzK2N2Yv8JDryRFLI5j"
}
}
],
"runPolicy": "Serial",
"source": {
"type": "Binary",
"binary": {}
},
"strategy": {
"type": "Docker",
"dockerStrategy": {}
},
"output": {
"to": {
"kind": "ImageStreamTag",
"name": "hello:latest"
}
},
"resources": {},
"postCommit": {},
"successfulBuildsHistoryLimit": 5,
"failedBuildsHistoryLimit": 5
},
"status": {
"lastVersion": 1
},
"kind": "BuildConfig",
"apiVersion": "v1"
}
{code}
was:
steps:
# ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc"
{code}oc login <openshift-server>{code}
# ASSERT: in cmd-line: make sure you that you selected a project in "oc"
{code}oc project <openshift-project-name>{code}
# EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...:
{code}
$ git clone https://github.com/redhat-helloworld-msa/hello
$ cd hello/
$ oc new-build --binary --name=hello -l app=hello
$ mvn package -Popenshift
$ oc start-build hello --from-dir=. --follow
$ oc new-app hello -l app=hello,hystrix.enabled=true
$ oc expose service hello
{code}
# ASSERT: in Explorer: the application-service "hello" is visible
# EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard
Result:
The import fails with the following error:
!import-error.png!
The error is correct, the application was created with a binary buildconfig, but the error not helpful.
Here's the build config (notice "source" > "type" > "Binary":
{code}
{
"metadata": {
"name": "hello",
"namespace": "jbide25000-2",
"selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello",
"uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd",
"resourceVersion": "360688",
"creationTimestamp": "2018-07-01T07:06:26Z",
"labels": {
"app": "hello"
},
"annotations": {
"openshift.io/generated-by": "OpenShiftNewBuild"
}
},
"spec": {
"triggers": [
{
"type": "GitHub",
"github": {
"secret": "N5TaoJVuWp-YBlwSktc3"
}
},
{
"type": "Generic",
"generic": {
"secret": "ehzK2N2Yv8JDryRFLI5j"
}
}
],
"runPolicy": "Serial",
"source": {
"type": "Binary",
"binary": {}
},
"strategy": {
"type": "Docker",
"dockerStrategy": {}
},
"output": {
"to": {
"kind": "ImageStreamTag",
"name": "hello:latest"
}
},
"resources": {},
"postCommit": {},
"successfulBuildsHistoryLimit": 5,
"failedBuildsHistoryLimit": 5
},
"status": {
"lastVersion": 1
},
"kind": "BuildConfig",
"apiVersion": "v1"
}
{code}
> Import application: error message when trying to import from binary build config is not helpful
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-26167
> URL: https://issues.jboss.org/browse/JBIDE-26167
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Attachments: import-error.png
>
>
> steps:
> # ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc"
> {code}oc login <openshift-server>{code}
> # ASSERT: in cmd-line: make sure you that you selected a project in "oc"
> {code}oc project <openshift-project-name>{code}
> # EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...:
> {code}
> $ git clone https://github.com/redhat-helloworld-msa/hello
> $ cd hello/
> $ oc new-build --binary --name=hello -l app=hello
> $ mvn package -Popenshift
> $ oc start-build hello --from-dir=. --follow
> $ oc new-app hello -l app=hello,hystrix.enabled=true
> $ oc expose service hello
> {code}
> # ASSERT: in Explorer: the application-service "hello" is visible
> # EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard
> RESULT:
> The import fails with the following error:
> !import-error.png!
> The error is correct, the application was created with a binary buildconfig, but the error not helpful.
> Here's the build config (notice "source" > "type" > "Binary":
> {code}
> {
> "metadata": {
> "name": "hello",
> "namespace": "jbide25000-2",
> "selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello",
> "uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd",
> "resourceVersion": "360688",
> "creationTimestamp": "2018-07-01T07:06:26Z",
> "labels": {
> "app": "hello"
> },
> "annotations": {
> "openshift.io/generated-by": "OpenShiftNewBuild"
> }
> },
> "spec": {
> "triggers": [
> {
> "type": "GitHub",
> "github": {
> "secret": "N5TaoJVuWp-YBlwSktc3"
> }
> },
> {
> "type": "Generic",
> "generic": {
> "secret": "ehzK2N2Yv8JDryRFLI5j"
> }
> }
> ],
> "runPolicy": "Serial",
> "source": {
> "type": "Binary",
> "binary": {}
> },
> "strategy": {
> "type": "Docker",
> "dockerStrategy": {}
> },
> "output": {
> "to": {
> "kind": "ImageStreamTag",
> "name": "hello:latest"
> }
> },
> "resources": {},
> "postCommit": {},
> "successfulBuildsHistoryLimit": 5,
> "failedBuildsHistoryLimit": 5
> },
> "status": {
> "lastVersion": 1
> },
> "kind": "BuildConfig",
> "apiVersion": "v1"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26167) Import application: error message when trying to import from binary build config is not helpful
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26167?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26167:
-------------------------------------
Attachment: import-error.png
> Import application: error message when trying to import from binary build config is not helpful
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-26167
> URL: https://issues.jboss.org/browse/JBIDE-26167
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Attachments: import-error.png
>
>
> steps:
> # ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc"
> {code}oc login <openshift-server>{code}
> # ASSERT: in cmd-line: make sure you that you selected a project in "oc"
> {code}oc project <openshift-project-name>{code}
> # EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...:
> {code}
> $ git clone https://github.com/redhat-helloworld-msa/hello
> $ cd hello/
> $ oc new-build --binary --name=hello -l app=hello
> $ mvn package -Popenshift
> $ oc start-build hello --from-dir=. --follow
> $ oc new-app hello -l app=hello,hystrix.enabled=true
> $ oc expose service hello
> {code}
> # ASSERT: in Explorer: the application-service "hello" is visible
> # EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard
> Result:
> The import fails with the following error:
> The error is correct, the application was created with a binary buildconfig, but the error not helpful.
> Here's the build config (notice "source" > "type" > "Binary":
> {code}
> {
> "metadata": {
> "name": "hello",
> "namespace": "jbide25000-2",
> "selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello",
> "uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd",
> "resourceVersion": "360688",
> "creationTimestamp": "2018-07-01T07:06:26Z",
> "labels": {
> "app": "hello"
> },
> "annotations": {
> "openshift.io/generated-by": "OpenShiftNewBuild"
> }
> },
> "spec": {
> "triggers": [
> {
> "type": "GitHub",
> "github": {
> "secret": "N5TaoJVuWp-YBlwSktc3"
> }
> },
> {
> "type": "Generic",
> "generic": {
> "secret": "ehzK2N2Yv8JDryRFLI5j"
> }
> }
> ],
> "runPolicy": "Serial",
> "source": {
> "type": "Binary",
> "binary": {}
> },
> "strategy": {
> "type": "Docker",
> "dockerStrategy": {}
> },
> "output": {
> "to": {
> "kind": "ImageStreamTag",
> "name": "hello:latest"
> }
> },
> "resources": {},
> "postCommit": {},
> "successfulBuildsHistoryLimit": 5,
> "failedBuildsHistoryLimit": 5
> },
> "status": {
> "lastVersion": 1
> },
> "kind": "BuildConfig",
> "apiVersion": "v1"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26167) Import application: error message when trying to import from binary build config is not helpful
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-26167:
----------------------------------------
Summary: Import application: error message when trying to import from binary build config is not helpful
Key: JBIDE-26167
URL: https://issues.jboss.org/browse/JBIDE-26167
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.6.0.AM3
Reporter: Andre Dietisheim
steps:
# ASSERT: in cmd-line: make sure you logged into an OpenShift server via "oc"
{code}oc login <openshift-server>{code}
# ASSERT: in cmd-line: make sure you that you selected a project in "oc"
{code}oc project <openshift-project-name>{code}
# EXEC: create the app according to the "oc" based steps in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello...:
{code}
$ git clone https://github.com/redhat-helloworld-msa/hello
$ cd hello/
$ oc new-build --binary --name=hello -l app=hello
$ mvn package -Popenshift
$ oc start-build hello --from-dir=. --follow
$ oc new-app hello -l app=hello,hystrix.enabled=true
$ oc expose service hello
{code}
# ASSERT: in Explorer: the application-service "hello" is visible
# EXEC: select the "hello" service and pick "Import Application..." & "Finish" the wizard
Result:
The import fails with the following error:
The error is correct, the application was created with a binary buildconfig, but the error not helpful.
Here's the build config (notice "source" > "type" > "Binary":
{code}
{
"metadata": {
"name": "hello",
"namespace": "jbide25000-2",
"selfLink": "/oapi/v1/namespaces/jbide25000-2/buildconfigs/hello",
"uid": "457ef557-7cfd-11e8-aa28-fee3ec9633cd",
"resourceVersion": "360688",
"creationTimestamp": "2018-07-01T07:06:26Z",
"labels": {
"app": "hello"
},
"annotations": {
"openshift.io/generated-by": "OpenShiftNewBuild"
}
},
"spec": {
"triggers": [
{
"type": "GitHub",
"github": {
"secret": "N5TaoJVuWp-YBlwSktc3"
}
},
{
"type": "Generic",
"generic": {
"secret": "ehzK2N2Yv8JDryRFLI5j"
}
}
],
"runPolicy": "Serial",
"source": {
"type": "Binary",
"binary": {}
},
"strategy": {
"type": "Docker",
"dockerStrategy": {}
},
"output": {
"to": {
"kind": "ImageStreamTag",
"name": "hello:latest"
}
},
"resources": {},
"postCommit": {},
"successfulBuildsHistoryLimit": 5,
"failedBuildsHistoryLimit": 5
},
"status": {
"lastVersion": 1
},
"kind": "BuildConfig",
"apiVersion": "v1"
}
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26164) internal packages are a mess
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26164?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26164:
-------------------------------------
Description:
Our package structure is a mess, especially internal ones are wrong.
Ex. org.jboss.tools.openshift ui:
There are 2 internal packages:
* org.jboss.tools.openshift.internal.ui
* org.jboss.tools.openshift.ui.internal
!image-2018-07-04-15-42-01-395.png!
Internal packages have to follow the base component name, which in our case is org.jboss.tools.openshift:
* org.jboss.tools.openshift.internal.ui: *{color:green}CORRECT{color}*
* org.jboss.tools.openshift.ui.internal: *{color:red}WRONG{color}*
For the background:
* https://wiki.eclipse.org/Naming_Conventions#Internal_Implementation_Packages:
{quote}
All implementation packages should be flagged as internal, with the tag occurring just after the major package name
{quote}
* http://wiki.eclipse.org/Naming_Conventions#Java_Packages
{quote}
org.eclipse.jdt.internal.core.compiler - Correct usage
org.eclipse.jdt.core.internal.compiler - Incorrect. internal should immediately follow project name.
org.eclipse.core.internal.resources - Correct usage
org.eclipse.internal.core.resources - Incorrect. internal should never immediately follow org.eclipse.
org.eclipse.core.resources.internal - Incorrect. internal should immediately follow Eclipse Platform component name.
{quote}
was:
Our package structure is a mess, especially internal ones are wrong.
Ex. org.jboss.tools.openshift ui:
There are 2 internal packages:
* org.jboss.tools.openshift.internal.ui
* org.jboss.tools.openshift.ui.internal
!image-2018-07-04-15-42-01-395.png!
Internal packages have to follow the base plugin name.
* org.jboss.tools.openshift.internal.ui: *{color:green}CORRECT{color}*
* org.jboss.tools.openshift.ui.internal: *{color:red}WRONG{color}*
> internal packages are a mess
> ----------------------------
>
> Key: JBIDE-26164
> URL: https://issues.jboss.org/browse/JBIDE-26164
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Priority: Minor
> Fix For: 4.9.x
>
> Attachments: image-2018-07-04-15-42-01-395.png
>
>
> Our package structure is a mess, especially internal ones are wrong.
> Ex. org.jboss.tools.openshift ui:
> There are 2 internal packages:
> * org.jboss.tools.openshift.internal.ui
> * org.jboss.tools.openshift.ui.internal
> !image-2018-07-04-15-42-01-395.png!
> Internal packages have to follow the base component name, which in our case is org.jboss.tools.openshift:
> * org.jboss.tools.openshift.internal.ui: *{color:green}CORRECT{color}*
> * org.jboss.tools.openshift.ui.internal: *{color:red}WRONG{color}*
> For the background:
> * https://wiki.eclipse.org/Naming_Conventions#Internal_Implementation_Packages:
> {quote}
> All implementation packages should be flagged as internal, with the tag occurring just after the major package name
> {quote}
> * http://wiki.eclipse.org/Naming_Conventions#Java_Packages
> {quote}
> org.eclipse.jdt.internal.core.compiler - Correct usage
> org.eclipse.jdt.core.internal.compiler - Incorrect. internal should immediately follow project name.
> org.eclipse.core.internal.resources - Correct usage
> org.eclipse.internal.core.resources - Incorrect. internal should never immediately follow org.eclipse.
> org.eclipse.core.resources.internal - Incorrect. internal should immediately follow Eclipse Platform component name.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26164) internal packages are a mess
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-26164:
----------------------------------------
Summary: internal packages are a mess
Key: JBIDE-26164
URL: https://issues.jboss.org/browse/JBIDE-26164
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.6.0.AM3
Reporter: Andre Dietisheim
Priority: Minor
Fix For: 4.9.x
Attachments: image-2018-07-04-15-42-01-395.png
Our package structure is a mess, especially internal ones are wrong.
Ex. org.jboss.tools.openshift ui:
There are 2 internal packages:
* org.jboss.tools.openshift.internal.ui
* org.jboss.tools.openshift.ui.internal
!image-2018-07-04-15-42-01-395.png!
Internal packages have to follow the base plugin name.
* org.jboss.tools.openshift.internal.ui: *{color:green}CORRECT{color}*
* org.jboss.tools.openshift.ui.internal: *{color:red}WRONG{color}*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months