[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!
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!
> 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!
--
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: jenkins-pipeline-template.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
>
>
> 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
[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!
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!
> 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
>
>
> 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
[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: (was: jenkins-pipeline-template.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-variants.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
[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!
> 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
>
>
> 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
[JBoss JIRA] (JBIDE-24226) Fix Jolokia Mbean listing in JMX navigator to have it matching the RMI based implementation
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24226?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-24226:
-----------------------------------------
it seems that the elements in the JMX Navigator are grouped by the property in the order they are provided. the order is not the same with Jolokia at this place org.jboss.tools.jmx.core.tree.NodeBuilder.addToTree(Node, ObjectName, MBeanServerConnection) for instance:
for RMI:
{noformat}
type=MemoryManager,name=CodeCacheManager,
type=MemoryManager,name=CodeCacheManager,
type=MemoryManager,name=CodeCacheManager,
{noformat}
for Jolokia:
{noformat}
name=CodeCacheManager,type=MemoryManager,
name=CodeCacheManager,type=MemoryManager,
name=CodeCacheManager,type=MemoryManager,
{noformat}
> Fix Jolokia Mbean listing in JMX navigator to have it matching the RMI based implementation
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-24226
> URL: https://issues.jboss.org/browse/JBIDE-24226
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.4.4.AM1
> Reporter: Aurélien Pupier
> Attachments: image-2017-04-05-10-05-18-535.png
>
>
> If I understand well, for RMI, the top level Mbean are grouped by types. For Jolokia there is no grouping.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24125) Import wizard: adapt ITs to changes introduced in JBIDE-24048
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24125?page=com.atlassian.jira.plugi... ]
Radim Hopp updated JBIDE-24125:
-------------------------------
Fix Version/s: 4.4.4.Final
> Import wizard: adapt ITs to changes introduced in JBIDE-24048
> -------------------------------------------------------------
>
> Key: JBIDE-24125
> URL: https://issues.jboss.org/browse/JBIDE-24125
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Assignee: Radim Hopp
> Fix For: 4.4.4.Final
>
>
> In JBIDE-24048 changes have been done to the import wizard. We should change the ITs to cover these changes.
> @rhopp @bdshadow can you please test this since it's a rather larger change and provides changes in how it behaves?
> * Validations were extended:
> ** is the existing clone destination a git repo?
> ** is the existing clone destination a clone of the source that is used in OpenShift?
> * We now also ask the user if he wants to checkout the correct branch (the one that's used in OpenShift) in the existing git repo
> * UI was slightly changed according to requests made in JBIDE-21935
> * We now also close the wizard dialog before executing the import. This should allow the user to continue working.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years