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

version-specific builds #100

Open
1 of 2 tasks
brucellino opened this issue Aug 8, 2017 · 3 comments
Open
1 of 2 tasks

version-specific builds #100

brucellino opened this issue Aug 8, 2017 · 3 comments

Comments

@brucellino
Copy link
Member

brucellino commented Aug 8, 2017

The configuration matrix for ROOT is quite complex. We don't yet have a plugin that can easily filter out the "wrong" combinations of OS/compiler/ROOT version. I propose as a workaround to

  • provide version-specific scripts
  • split the ROOT-5 from ROOT-6 builds - creating separate jobs for ROOT-5 and ROOT-6.

In this way, we could probably get them to pass independently and make debugging the builds a bit easier.

yay/nay ?

@brucellino brucellino self-assigned this Aug 8, 2017
@bazinski
Copy link
Contributor

bazinski commented Aug 8, 2017

I agree re the split in builds

@brucellino
Copy link
Member Author

ok, I've created root5-delpoy and renamed root-deploy to root6-deploy.

the jobs are - I THINK ! - configured to be treiggered only if there are changes to the scripts which affect them. IE, if build-5.sh changes, only the root5-deploy job will be triggered.

Furthermore, the matrices have been appropriately reduced, pinning the v6x ersions to the root6 job and vice-versa for v5. The GCC axis has also been pruned, with root 5 only using gcc5 and root6 using gcc5 and 6.

@bazinski
Copy link
Contributor

bazinski commented Aug 8, 2017

root5 can stay on gcc4.9 only.
as for root6 ja on gcc6 only should be fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants