[JBoss JIRA] (JBDS-4303) Show warning for virtualbox component if virtualization is not enabled or cannot be detected (macos)
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4303?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-4303:
-----------------------------------
I'm willing to bet that chance VT-x is disabled is dwindling somewhere in the decimals. All Intel based mac machines have this feature enabled and there is no way to change this setting in the system. Hence the only kind of user that might actually have it disabled I can think of is either one with ancient EFI Firmware, or one that actively hacked into it.
The whole point of my rant is, the typical mac user will not expect to be asked about virtualization on their system, because they expect it to just work, or just don't know what it means. I'm not a fan of the permanent warning message and I expect the mac users not to be either.
TL;DR: Is it worth it to show a warning all the time because some 0.x% of mac users might have the virtualization disabled (probably by their own fault) ?
> Show warning for virtualbox component if virtualization is not enabled or cannot be detected (macos)
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4303
> URL: https://issues.jboss.org/browse/JBDS-4303
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.3.0.AM2
> Reporter: Denis Golovin
> Assignee: Sudhir Verma
> Fix For: 10.4.0.AM2
>
>
> Current implementation shows errors and warning under item selected for installation.
> See confirmation page error message for virtualbox Installer [here|https://github.com/redhat-developer-tooling/developer-platform-insta...].
> Confirmation page controller should run Virtualization detection along with installed components detection and show warning under virtualbox item if it is detected or selected for install.
> If Virtualization firmware status cannot be detected (windows 7) message should say:
> * Make sure hardware virtualization is enabled on your platform if supported to improve performance.
> if Hardware Virtualization is Disabled:
> * Please enable hardware virtualization for your platform to improve performance
> If Hardware Virtualization is Enabled, no message is required.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24186) Eclipse workspace deadlocking during refresh/rebuild
by Beirti O'Nunain (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24186?page=com.atlassian.jira.plugi... ]
Beirti O'Nunain commented on JBIDE-24186:
-----------------------------------------
Sure. Will keep an eye out for the next occurrence
> Eclipse workspace deadlocking during refresh/rebuild
> ----------------------------------------------------
>
> Key: JBIDE-24186
> URL: https://issues.jboss.org/browse/JBIDE-24186
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, server
> Affects Versions: 4.4.3.Final
> Reporter: Beirti O'Nunain
> Assignee: Rob Stryker
> Fix For: 4.4.4.Final
>
>
> - Windows 7
> - Eclipse Neon.2 (4.6.2)
> - Developer Studio 10.3.0
> After a workspace SVN update, the rebuild in Eclipse hangs (Eclipse remains responsive for a short time) with the following jobs in the progress pane:
> + "Refreshing '/my-non-j2ee-webproject/target/m2e-wtp/web-resources'"
> + Updating Maven Project (Waiting)
> + Updating Maven Project (Waiting)
> + Updating Maven Project (Waiting)
> + Updating Maven Project (Waiting)
> ....
> The project referenced above is a simple web project with no J2EE or JBoss components, nor is it referenced by any servers in the workspace.
> Profiling with yourkit detects a deadlock in the following thread:
> Worker-33 <--- Frozen for at least 8m 27s
> org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
> org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
> org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
> org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
> I started profiling Yourkit when the build hung. It shows the following as the live call stack:
> Call Tree Time (ms) Level
> <All threads> 530944 1
> org.eclipse.linuxtools.internal.docker.core.DockerContainerRefreshManager$ContainerRefreshThread.run() 530086 2
> org.eclipse.equinox.launcher.Main.run(String[]) 436 2
> org.eclipse.core.internal.jobs.Worker.run() 421 2
> I've not found a workaround yet. Killing eclipse and cleaning the workspace sometimes avoids the issue. This issue does not happen in an Eclipse installation where JBoss tools has not been installed
> Eclipse remains responsive until another call to 'Server.getModules' happens. Below is the deadlock trace from when Eclipse completely hangs:
> Frozen threads found (potential deadlock)
> It seems that the following threads have not changed their stack for more than 10 seconds.
> These threads are possibly (but not necessarily!) in a deadlock or hung.
> main <--- Frozen for at least 2m 21s
> org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2527
> org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.getServers(IModule) ChangeTimeStampActionDelegate.java:150
> org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.buildActions() ChangeTimeStampActionDelegate.java:112
> org.jboss.ide.eclipse.as.ui.actions.ChangeTimeStampActionDelegate.selectionChanged(IAction, ISelection) ChangeTimeStampActionDelegate.java:69
> org.eclipse.ui.internal.PluginAction.refreshEnablement() PluginAction.java:206
> org.eclipse.ui.internal.PluginAction.selectionChanged(ISelection) PluginAction.java:273
> org.eclipse.ui.internal.PluginAction.selectionChanged(IWorkbenchPart, ISelection) PluginAction.java:297
> org.eclipse.ui.internal.e4.compatibility.SelectionService.notifyListeners(IWorkbenchPart, ISelection, ListenerList) SelectionService.java:259
> org.eclipse.ui.internal.e4.compatibility.SelectionService.handleSelectionChanged(MPart, Object, boolean) SelectionService.java:108
> org.eclipse.ui.internal.e4.compatibility.SelectionService.access$0(SelectionService, MPart, Object, boolean) SelectionService.java:92
> org.eclipse.ui.internal.e4.compatibility.SelectionService$1.selectionChanged(MPart, Object) SelectionService.java:67
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator$2.run() SelectionAggregator.java:126
> org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator.notifyListeners(MPart, Object) SelectionAggregator.java:123
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator.access$6(SelectionAggregator, MPart, Object) SelectionAggregator.java:121
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7$1.run() SelectionAggregator.java:231
> org.eclipse.e4.core.contexts.RunAndTrack.runExternalCode(Runnable) RunAndTrack.java:56
> org.eclipse.e4.ui.internal.workbench.SelectionAggregator$7.changed(IEclipseContext) SelectionAggregator.java:228
> org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(ContextChangeEvent) TrackableComputationExt.java:114
> org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(Set) EclipseContext.java:343
> org.eclipse.e4.core.internal.contexts.EclipseContext.set(String, Object) EclipseContext.java:358
> org.eclipse.e4.ui.internal.workbench.SelectionServiceImpl.setSelection(Object) SelectionServiceImpl.java:31
> org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.selectionChanged(SelectionChangedEvent) CompatibilityPart.java:450
> org.eclipse.jface.viewers.Viewer$1.run() Viewer.java:158
> org.eclipse.core.runtime.SafeRunner.run(ISafeRunnable) SafeRunner.java:42
> org.eclipse.ui.internal.JFaceUtil$1.run(ISafeRunnable) JFaceUtil.java:50
> org.eclipse.jface.util.SafeRunnable.run(ISafeRunnable) SafeRunnable.java:173
> org.eclipse.jface.viewers.Viewer.fireSelectionChanged(SelectionChangedEvent) Viewer.java:155
> org.eclipse.jface.viewers.StructuredViewer.updateSelection(ISelection) StructuredViewer.java:2191
> org.eclipse.jface.viewers.StructuredViewer.handleSelect(SelectionEvent) StructuredViewer.java:1229
> org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(SelectionEvent) StructuredViewer.java:1258
> org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(SelectionEvent) OpenStrategy.java:242
> org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy, SelectionEvent) OpenStrategy.java:236
> org.eclipse.jface.util.OpenStrategy$1.handleEvent(Event) OpenStrategy.java:405
> org.eclipse.swt.widgets.EventTable.sendEvent(Event) EventTable.java:84
> org.eclipse.swt.widgets.Display.sendEvent(EventTable, Event) Display.java:4418
> org.eclipse.swt.widgets.Widget.sendEvent(Event) Widget.java:1079
> org.eclipse.swt.widgets.Display.runDeferredEvents() Display.java:4236
> org.eclipse.swt.widgets.Display.readAndDispatch() Display.java:3824
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run() PartRenderingEngine.java:1121
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(MApplicationElement, IEclipseContext) PartRenderingEngine.java:1022
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(MApplicationElement) E4Workbench.java:150
> org.eclipse.ui.internal.Workbench$5.run() Workbench.java:693
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) Realm.java:336
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) Workbench.java:610
> org.eclipse.ui.PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) PlatformUI.java:148
> org.eclipse.ui.internal.ide.application.IDEApplication.start(IApplicationContext) IDEApplication.java:138
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Object) EclipseAppHandle.java:196
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Object) EclipseAppLauncher.java:134
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Object) EclipseAppLauncher.java:104
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(Object) EclipseStarter.java:388
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(String[], Runnable) EclipseStarter.java:243
> sun.reflect.NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) NativeMethodAccessorImpl.java (native)
> sun.reflect.NativeMethodAccessorImpl.invoke(Object, Object[]) NativeMethodAccessorImpl.java:62
> sun.reflect.DelegatingMethodAccessorImpl.invoke(Object, Object[]) DelegatingMethodAccessorImpl.java:43
> java.lang.reflect.Method.invoke(Object, Object[]) Method.java:498
> org.eclipse.equinox.launcher.Main.invokeFramework(String[], URL[]) Main.java:673
> org.eclipse.equinox.launcher.Main.basicRun(String[]) Main.java:610
> org.eclipse.equinox.launcher.Main.run(String[]) Main.java:1519
> Worker-33 <--- Frozen for at least 14m 43s
> org.eclipse.wst.server.core.internal.Server.getModules() Server.java:2526
> org.eclipse.wst.server.core.internal.Server.visit(IModuleVisitor, IProgressMonitor) Server.java:3035
> org.eclipse.wst.server.core.internal.Server$ResourceChangeJob.run(IProgressMonitor) Server.java:228
> org.eclipse.core.internal.jobs.Worker.run() Worker.java:55
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4303) Show warning for virtualbox component if virtualization is not enabled or cannot be detected (macos)
by Sudhir Verma (JIRA)
[ https://issues.jboss.org/browse/JBDS-4303?page=com.atlassian.jira.plugin.... ]
Sudhir Verma commented on JBDS-4303:
------------------------------------
Hi [~jrichter1] If you see VMX entry then CPU supports Intel VT-x feature, but it still may be disabled.
you can refer this link http://kb.parallels.com/en/5653.
> Show warning for virtualbox component if virtualization is not enabled or cannot be detected (macos)
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4303
> URL: https://issues.jboss.org/browse/JBDS-4303
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.3.0.AM2
> Reporter: Denis Golovin
> Assignee: Sudhir Verma
> Fix For: 10.4.0.AM2
>
>
> Current implementation shows errors and warning under item selected for installation.
> See confirmation page error message for virtualbox Installer [here|https://github.com/redhat-developer-tooling/developer-platform-insta...].
> Confirmation page controller should run Virtualization detection along with installed components detection and show warning under virtualbox item if it is detected or selected for install.
> If Virtualization firmware status cannot be detected (windows 7) message should say:
> * Make sure hardware virtualization is enabled on your platform if supported to improve performance.
> if Hardware Virtualization is Disabled:
> * Please enable hardware virtualization for your platform to improve performance
> If Hardware Virtualization is Enabled, no message is required.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[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:
-------------------------------------
Description:
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}
was:
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:
{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}
> 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.AM3
>
> Attachments: jenkins-pipeline-template.png, jenkins-variants.png, pipeline-build.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)
9 years
[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:
-------------------------------------
Description:
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:
{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}
was:
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!
> 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.AM3
>
> Attachments: jenkins-pipeline-template.png, jenkins-variants.png, pipeline-build.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:
> {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)
9 years
[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:
-------------------------------------
Attachment: pipeline-build.png
> 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.AM3
>
> Attachments: jenkins-pipeline-template.png, jenkins-variants.png, pipeline-build.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!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years