[JBoss JIRA] (WFLY-10145) mvn versions:set -DnewVersion=xxxx does not replace component-matrix/pom.xml
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-10145?page=com.atlassian.jira.plugin... ]
Kabir Khan updated WFLY-10145:
------------------------------
Description:
Similar to WFCORE-3718, using mvn versions:set -DnewVersion=12.0.0.Beta1, leaves component-matrix/pom.xml untouched.
{code}
$git grep "\-SNAPSHOT"
component-matrix/pom.xml: <version>13.0.0.Alpha1-SNAPSHOT</version>
{code}
was:
{quote}
[2:26 PM] Kabir Khan: @ctomc following https://developer.jboss.org/wiki/WildFlyCoreReleaseProcess, and using
mvn versions:set -DnewVersion=5.0.0.Alpha2
[2:26 PM] Kabir Khan: it seems to keep component-matrix/pom.xml as -SNAPSHOT
[2:26 PM] Kabir Khan: $git grep "\-SNAPSHOT"
component-matrix/pom.xml: <version>5.0.0.Alpha2-SNAPSHOT</version>
[2:27 PM] Tomaz Cerar: damn, that is not good
[2:27 PM] Tomaz Cerar: versions plugin is bit stupid in some cases
[2:27 PM] Kabir Khan: Should it be in the list of modules?
[2:27 PM] Tomaz Cerar: it is
{quote}
All other versions are correctly replaced. I'd hazard a guess that this also happens in WF full.
CC [~brian.stansberry] - for the 5.0.0.Alpha2 release I'm using the old find/sed way
> mvn versions:set -DnewVersion=xxxx does not replace component-matrix/pom.xml
> ----------------------------------------------------------------------------
>
> Key: WFLY-10145
> URL: https://issues.jboss.org/browse/WFLY-10145
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Kabir Khan
> Assignee: Tomaz Cerar
>
> Similar to WFCORE-3718, using mvn versions:set -DnewVersion=12.0.0.Beta1, leaves component-matrix/pom.xml untouched.
> {code}
> $git grep "\-SNAPSHOT"
> component-matrix/pom.xml: <version>13.0.0.Alpha1-SNAPSHOT</version>
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFLY-10145) mvn versions:set -DnewVersion=xxxx does not replace component-matrix/pom.xml
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-10145?page=com.atlassian.jira.plugin... ]
Kabir Khan moved WFCORE-3719 to WFLY-10145:
-------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-10145 (was: WFCORE-3719)
Component/s: Build System
(was: Domain Management)
Affects Version/s: (was: 5.0.0.Alpha2)
> mvn versions:set -DnewVersion=xxxx does not replace component-matrix/pom.xml
> ----------------------------------------------------------------------------
>
> Key: WFLY-10145
> URL: https://issues.jboss.org/browse/WFLY-10145
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Kabir Khan
> Assignee: Tomaz Cerar
>
> {quote}
> [2:26 PM] Kabir Khan: @ctomc following https://developer.jboss.org/wiki/WildFlyCoreReleaseProcess, and using
> mvn versions:set -DnewVersion=5.0.0.Alpha2
> [2:26 PM] Kabir Khan: it seems to keep component-matrix/pom.xml as -SNAPSHOT
> [2:26 PM] Kabir Khan: $git grep "\-SNAPSHOT"
> component-matrix/pom.xml: <version>5.0.0.Alpha2-SNAPSHOT</version>
> [2:27 PM] Tomaz Cerar: damn, that is not good
> [2:27 PM] Tomaz Cerar: versions plugin is bit stupid in some cases
> [2:27 PM] Kabir Khan: Should it be in the list of modules?
> [2:27 PM] Tomaz Cerar: it is
> {quote}
> All other versions are correctly replaced. I'd hazard a guess that this also happens in WF full.
> CC [~brian.stansberry] - for the 5.0.0.Alpha2 release I'm using the old find/sed way
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-107) Openshift Cluster Allocation
by Matt Mahoney (JIRA)
[ https://issues.jboss.org/browse/SWSQE-107?page=com.atlassian.jira.plugin.... ]
Matt Mahoney reassigned SWSQE-107:
----------------------------------
Assignee: Matt Mahoney (was: Michael Foley)
> Openshift Cluster Allocation
> ----------------------------
>
> Key: SWSQE-107
> URL: https://issues.jboss.org/browse/SWSQE-107
> Project: Swift Sunshine QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Matt Mahoney
>
> We now have (3) Openshift clusters, for which we will want to define use allocation for each (aka: how will these cluster be used).
> On one of these clusters, we will want to have our 'Production' CI pipeline.
> b21 -> Currently general usage for pipeline automation and manual testing
> b12 -> Newly created, and unused
> b11 -> Newly created, and unused
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (WFCORE-3719) mvn versions:set -DnewVersion=xxxx does not replace component-matrix/pom.xml
by Kabir Khan (JIRA)
Kabir Khan created WFCORE-3719:
----------------------------------
Summary: mvn versions:set -DnewVersion=xxxx does not replace component-matrix/pom.xml
Key: WFCORE-3719
URL: https://issues.jboss.org/browse/WFCORE-3719
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 5.0.0.Alpha2
Reporter: Kabir Khan
Assignee: Tomaz Cerar
{quote}
[2:26 PM] Kabir Khan: @ctomc following https://developer.jboss.org/wiki/WildFlyCoreReleaseProcess, and using
mvn versions:set -DnewVersion=5.0.0.Alpha2
[2:26 PM] Kabir Khan: it seems to keep component-matrix/pom.xml as -SNAPSHOT
[2:26 PM] Kabir Khan: $git grep "\-SNAPSHOT"
component-matrix/pom.xml: <version>5.0.0.Alpha2-SNAPSHOT</version>
[2:27 PM] Tomaz Cerar: damn, that is not good
[2:27 PM] Tomaz Cerar: versions plugin is bit stupid in some cases
[2:27 PM] Kabir Khan: Should it be in the list of modules?
[2:27 PM] Tomaz Cerar: it is
{quote}
All other versions are correctly replaced. I'd hazard a guess that this also happens in WF full.
CC [~brian.stansberry] - for the 5.0.0.Alpha2 release I'm using the old find/sed way
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-107) Openshift Cluster Allocation
by Matt Mahoney (JIRA)
[ https://issues.jboss.org/browse/SWSQE-107?page=com.atlassian.jira.plugin.... ]
Matt Mahoney commented on SWSQE-107:
------------------------------------
My straw-man suggestion:
* Use b21 for general manual and automation testing, including CI pipeline testing. Reason to not use b21 for CI Production is that it is already used for various testing purposes, so leave this cluster's use as-is.
* Use *b11* for a "Production" CI pipeline, somewhat locked down and ONLY used for CI
May need to add another blade to accommodate paralleled automation runs
* Use b12 for testing as well, but keep it updated with latest Istio, Kiali and Service-Mesh deployments.
> Openshift Cluster Allocation
> ----------------------------
>
> Key: SWSQE-107
> URL: https://issues.jboss.org/browse/SWSQE-107
> Project: Swift Sunshine QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Michael Foley
>
> We now have (3) Openshift clusters, for which we will want to define use allocation for each (aka: how will these cluster be used).
> On one of these clusters, we will want to have our 'Production' CI pipeline.
> b21 -> Currently general usage for pipeline automation and manual testing
> b12 -> Newly created, and unused
> b11 -> Newly created, and unused
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-107) Openshift Cluster Allocation
by Matt Mahoney (JIRA)
[ https://issues.jboss.org/browse/SWSQE-107?page=com.atlassian.jira.plugin.... ]
Matt Mahoney updated SWSQE-107:
-------------------------------
Summary: Openshift Cluster Allocation (was: Openshift Cluster Allication)
> Openshift Cluster Allocation
> ----------------------------
>
> Key: SWSQE-107
> URL: https://issues.jboss.org/browse/SWSQE-107
> Project: Swift Sunshine QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Michael Foley
>
> We now have (3) Openshift clusters, for which we will want to define use allocation for each (aka: how will these cluster be used).
> On one of these clusters, we will want to have our 'Production' CI pipeline.
> b21 -> Currently general usage for pipeline automation and manual testing
> b12 -> Newly created, and unused
> b11 -> Newly created, and unused
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-107) Openshift Cluster Allication
by Matt Mahoney (JIRA)
Matt Mahoney created SWSQE-107:
----------------------------------
Summary: Openshift Cluster Allication
Key: SWSQE-107
URL: https://issues.jboss.org/browse/SWSQE-107
Project: Swift Sunshine QE
Issue Type: QE Task
Reporter: Matt Mahoney
Assignee: Michael Foley
We now have (3) Openshift clusters, for which we will want to define use allocation for each (aka: how will these cluster be used).
On one of these clusters, we will want to have our 'Production' CI pipeline.
b21 -> Currently general usage for pipeline automation and manual testing
b12 -> Newly created, and unused
b11 -> Newly created, and unused
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month