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

Put more control in targeting file to parse #1

Open
DonaldChung-HK opened this issue Oct 21, 2022 · 2 comments
Open

Put more control in targeting file to parse #1

DonaldChung-HK opened this issue Oct 21, 2022 · 2 comments

Comments

@DonaldChung-HK
Copy link
Contributor

Since some pipeline only runs on single system so it might be useful to turn the key to look for file name into a list so that it can target different number and name of log files for different pipelines.

@DonaldChung-HK
Copy link
Contributor Author

I put in a fix for controlling what file to parse for individual pipeline. it adds the -t for adding list of os keys and -f for adding list of corresponding file names to parse for a pipeline/Job and you use another -t and -f to do this for another one. Here is an example where you only want to monitor Mac in build_packages_from_branch and all in main_nightly_deployment_prototype

python main.py -u 'https://builds.mantidproject.org/' -p 'build_packages_from_branch' 'main_nightly_deployment_prototype' -n 30 -t "Mac" -f "darwin17.log" -t "Mac" "Linux" "Windows" -f "darwin17.log" "linux-gnu.log" "msys.log"

Note that unlike normal command-line application the order which the -t and -f flags are added is important as they correspond to the position of pipeline in -p argument

@DonaldChung-HK
Copy link
Contributor Author

Probably might require a more robust solution

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

1 participant