Skip to content

Execute CI on activemq-5.19.x and activemq-6.2.x branches#1957

Open
jbonofre wants to merge 1 commit intoapache:mainfrom
jbonofre:ci-on-branches
Open

Execute CI on activemq-5.19.x and activemq-6.2.x branches#1957
jbonofre wants to merge 1 commit intoapache:mainfrom
jbonofre:ci-on-branches

Conversation

@jbonofre
Copy link
Copy Markdown
Member

No description provided.

@jbonofre
Copy link
Copy Markdown
Member Author

@cshannon I guess we should consider backporting from flaky tests fixes here. Or exclude these flaky tests on the branches. For context, the flaky tests fixes have been done only on the main branch.

@cshannon
Copy link
Copy Markdown
Contributor

@cshannon I guess we should consider backporting from flaky tests fixes here. Or exclude these flaky tests on the branches. For context, the flaky tests fixes have been done only on the main branch.

Hmm yeah I forgot about that, maybe we should wait until we release 6.3.0 to turn it on then on the 6.3.x branch. A lot of the flaky tests didn't get backported.

Maybe for 6.2.x and 5.19.x we can at least just run a quick 10 minute test profile (enable some basic tests) and make sure it compiles etc for now.

@jbonofre
Copy link
Copy Markdown
Member Author

@cshannon that's reasonable. For context, the checks (CI) don't have to pass to merge on the branches (only on main). So, we can merge PRs even if the CI didn't pass successfully.

@cshannon
Copy link
Copy Markdown
Contributor

@cshannon that's reasonable. For context, the checks (CI) don't have to pass to merge on the branches (only on main). So, we can merge PRs even if the CI didn't pass successfully.

Ah ok, maybe we just leave it on then. As long as we can merge.

@cshannon
Copy link
Copy Markdown
Contributor

cshannon commented Apr 24, 2026

We can also start back porting some of the fixes, especially if 5.19.x will be maintained for a while

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants