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

build: use maven 3.6 --no-transfer-progress #340

Merged
merged 1 commit into from
May 9, 2022

Conversation

sjd78
Copy link
Member

@sjd78 sjd78 commented May 7, 2022

The github action CI build log tends to contain a large amount of
log lines for the transfer progress of downloading dependencies.
This can make a prohibitively large log file to be able to view
it on the github action page.

Use maven 3.6 and the option --no-transfer-progress to vastly reduce
the log output to where we can actually scroll the the bottom of the
output on the action's web page.

Note: maven is a separate module on centos 8 stream. Copr chroot
configs will need to be checked. Enabling at least maven 3.6 is
requried.

The github action CI build log tends to contain a large amount of
log lines for the transfer progress of downloading dependencies.
This can make a prohibitively large log file to be able to view
it on the github action page.

Use maven 3.6 and the option `--no-transfer-progress` to vastly reduce
the log output to where we can actually scroll the the bottom of the
output on the action's web page.

Note: maven is a separate module on centos 8 stream.  Copr chroot
configs will need to be checked.  Enabling at least maven 3.6 is
requried.
@sjd78
Copy link
Member Author

sjd78 commented May 7, 2022

With the maven cache enabled, there isn't much of a change. But if the maven cache expires or ./automation/build_rpm.sh is run outside of github, the build log will still be around 32,000 lines.

Copy link
Member

@sandrobonazzola sandrobonazzola left a comment

Choose a reason for hiding this comment

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

ok for me

Copy link
Member

@mwperina mwperina left a comment

Choose a reason for hiding this comment

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

So let's try. If it causes problem in COPR or brew, then we can revert

@mwperina mwperina merged commit 95969d1 into oVirt:master May 9, 2022
mwperina added a commit to mwperina/ovirt-engine that referenced this pull request May 9, 2022
Passing --no-transfer-progress within EXTRA_BUILD_FLAGS introduced
in oVirt#340 broke engine build
in COPR, so we need to move that option into MAVEN_OPTS instead.

Signed-off-by: Martin Perina <mperina@redhat.com>
@sjd78 sjd78 deleted the maven_no_transfer_progress branch May 10, 2022 15:03
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.

None yet

3 participants