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

Logs in CI #9

Open
mssun opened this issue Jun 24, 2018 · 3 comments
Open

Logs in CI #9

mssun opened this issue Jun 24, 2018 · 3 comments

Comments

@mssun
Copy link
Contributor

mssun commented Jun 24, 2018

mkpkg does not write logs to CI when successful build a package. (https://ci.mesalock-linux.org/mesalock-linux/mkpkg/26/4)

This is not informative when building packages with a shell command: https://ci.mesalock-linux.org/mesalock-linux/mesalock-distro/62/5

@Arcterus
Copy link
Contributor

When you refer to logs do you mean the ones in the build directory? If so I don't think those should be dumped by default (maybe unless there's an error). IMO they should be dumped when the --verbose option is given, but this may require disabling parallel building and the progress bars as --verbose should probably just write any build output as soon as it's available (like with makepkg).

@Arcterus
Copy link
Contributor

Arcterus commented Jun 25, 2018

A short-term solution for this without using --verbose would be to just dump the log after building a package in build-all.sh.

@mssun
Copy link
Contributor Author

mssun commented Jun 25, 2018

No, I mean a simple output showing the current status (which one is started) and build result (successful or failed).

In the CI environment, the progress bar is disabled, we need some meta information similar with the one in the progress bar.

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

No branches or pull requests

2 participants