Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Streamline Maven Builds and CI #2327

Open
ThorbenLindhauer opened this issue May 27, 2020 · 1 comment
Open

Streamline Maven Builds and CI #2327

ThorbenLindhauer opened this issue May 27, 2020 · 1 comment
Labels
type:task Issues that are a change to the project that is neither a feature nor a bug fix.

Comments

@ThorbenLindhauer
Copy link
Member

This issue was imported from JIRA:

Field Value
JIRA Link CAM-11968
Reporter @ThorbenLindhauer
Has restricted visibility comments false

Let's make modernizations and simplifications in our CI and Maven build structure in order to

  • Reduce occurrence of build instabilities
  • Reduce infrastructure maintenance efforts
  • Increase PR build coverage
  • Reduce the risk of introducing build regressions during development ("build regression": a change that creates an issue in a release build or similar that we will only notice much later)

Please create sub-tasks for individual items

Breakdown:

Links:

@ThorbenLindhauer
Copy link
Member Author

This comment was imported from JIRA and written by user L3xJbNX

What is this name? This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.


I would create an additional task for upgrading the maven version: the maven version that we are currently using is quite outdated. Newer version are better suited for cloud environments since they implement more robust ways of handling connection resets/retries (see https://stackoverflow.com/questions/42024619/maven-build-gets-connection-reset-when-downloading-artifacts).
I see https://jira.camunda.com/browse/CAM-11822 is related to adapting the code for the new maven version, but there is nothing mentioned about actually upgrading the code.

As we go in this direction, build parallelization becomes more and more important to avoid very long build times. That's why I would also suggest adding https://jira.camunda.com/browse/CAM-11210 to the list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:task Issues that are a change to the project that is neither a feature nor a bug fix.
Projects
None yet
Development

No branches or pull requests

1 participant