You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ?
The text was updated successfully, but these errors were encountered:
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.
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
In this way, we could probably get them to pass independently and make debugging the builds a bit easier.
yay/nay ?
The text was updated successfully, but these errors were encountered: