Skip to content
This repository was archived by the owner on Nov 4, 2025. It is now read-only.

Conversation

@yanavasileva
Copy link
Member

@yanavasileva yanavasileva self-assigned this Sep 30, 2025
@yanavasileva yanavasileva added the ci:postgresql Runs the builds for the PostgreSQL database. label Sep 30, 2025
Copy link
Member

@venetrius venetrius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❓ Should we also remove references from the camunda-bpm-platform/Jenkinsfile?

@yanavasileva yanavasileva marked this pull request as draft September 30, 2025 11:15
@yanavasileva yanavasileva added ci:all-as Runs the builds for all application servers. ci:skipTests Skips tests execution in Assembly and Distro-ee stages. and removed ci:postgresql Runs the builds for the PostgreSQL database. labels Sep 30, 2025
@yanavasileva yanavasileva marked this pull request as ready for review September 30, 2025 13:10
Copy link
Member

@venetrius venetrius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had one more question

Jenkinsfile Outdated
}
}
stage('engine-IT-tomcat-9-postgresql-142') {
stage('engine-IT-tomcat-9-postgresql-170') {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❓ Do we still need stages with tomcat-9?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the ticket description:

can we "just" keep the CI structure and replace Tomcat 9 with 11?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which also might mean that we keep only the CI but remove the tomcat 9 webapp module. 🤔 I will check

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right!

@venetrius venetrius self-requested a review September 30, 2025 14:07
Copy link
Member

@venetrius venetrius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me!
Should this wait until the end of code freeze before merging? It does not change behaviour but can effect the CI.

@yanavasileva yanavasileva added ci:no-build Prevents any CI stage from running. ci:jdk Runs the builds for all supported Java versions. and removed ci:skipTests Skips tests execution in Assembly and Distro-ee stages. labels Oct 6, 2025
@yanavasileva yanavasileva added ci:webapp-integration Runs the webapp integration builds. and removed ci:no-build Prevents any CI stage from running. labels Oct 6, 2025
@yanavasileva yanavasileva requested a review from venetrius October 6, 2025 10:20
Copy link
Member

@venetrius venetrius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Looks good to me

@yanavasileva yanavasileva merged commit 038ac69 into master Oct 6, 2025
9 checks passed
@yanavasileva yanavasileva deleted the 5028-rm-pg-14 branch October 6, 2025 12:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

ci:all-as Runs the builds for all application servers. ci:jdk Runs the builds for all supported Java versions. ci:webapp-integration Runs the webapp integration builds.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants