search

trilinos / Trilinos

Primary repository for the Trilinos Project
https://trilinos.org/
Other
1.21k stars 564 forks source link

Change default Trilinos CDash site to internal site #10876

Open bartlettroscoe opened 2 years ago

bartlettroscoe commented 2 years ago

CC: @trilinos/framework

Description

Currently, the default Trilinos CDash site is testing.sandia.gov/cdash/. But the Trilinos Framework team commissioned the creation of an internal SNL SRN site trilinos-cdash.sandia.gov and moved all PR builds and Master Merge builds to submit to that site.

However, the ATDM Trilinos builds and a few other nightly builds are still submitted to testing.sandia.gov/cdash/.

We can't remove testing.sandia.gov/cdash/ because we need a site that external Trilinos developers (and developers on the SON) can submit Trilinos builds to and we need that site to support TriBITS development.

This Issue is to change the default CDash site to trilinos-cdash.sandia.gov.

Tasks

bartlettroscoe commented 2 years ago

Note that his also requires changing from 'http' to 'https' to do the dual submit to the site testing-dev.sandia.gov.

bartlettroscoe commented 2 years ago

See PR #10887.

bartlettroscoe commented 2 years ago

As of merge commit https://github.com/trilinos/Trilinos/commit/2850ea46302aedf47a203c435c7a7f64545468d4, this change should be reflected in the ATDM Trilinos builds starting tomorrow.

bartlettroscoe commented 2 years ago

For some reason the update of the 'atdm-nightly' branch did not occur last night. As of this morning the most recent commits on that branch were:

$git log-short --name-status --graph github/atdm-nightly --not github/develop
* 9a0b81c8926 "Merge remote-tracking branch 'origin/develop' into atdm-nightly"
| Author: trilinos-autotester <trilinos@sandia.gov>
| Date:   Sun Aug 14 21:05:08 2022 -0600 (35 hours ago)
| 
* 3cf52032526 "Merge remote-tracking branch 'origin/develop' into atdm-nightly"
| Author: trilinos-autotester <trilinos@sandia.gov>
| Date:   Sat Aug 13 21:05:08 2022 -0600 (2 days ago)
| 
* a61c15b53ac "Merge remote-tracking branch 'origin/develop' into atdm-nightly"
| Author: trilinos-autotester <trilinos@sandia.gov>
| Date:   Fri Aug 12 21:05:06 2022 -0600 (3 days ago)
...

Therefore, I just manually updated that branch by merging in the 'atdm-nightly-manual-updates' branch.

bartlettroscoe commented 2 years ago

FYI: I just merged the revert commit 830f24a0eeb to the 'atdm-nightly-manual-updates' and the 'atdm-nightly' branches that undoes the merge of the branch from PR #10887. I then rebased the commits in that topic branch so when they get merged to the 'atdm-nightly' branch later, they will be seen as new commits and merged in and change to trilinos-cdash.sandia.gov.

bartlettroscoe commented 2 years ago

@e10harvey, as we agreed in https://github.com/trilinos/Trilinos/pull/10887#issuecomment-1218444261, I am turning this over to you and the framework team.

Let me know if you have questions about this.

I am taking another shot and moving TriBITS to use my.cdash.org with the help of Kitware. If that works out, I will not have any need for an externally accessible CDash site and we can let testing.sandia.gov and testing-dev.sandia.gov move internally.

mayrmt commented 2 years ago

@bartlettroscoe will test results for Trilinos PRs from external contributors still be accessible from the outside?

bartlettroscoe commented 2 years ago

@bartlettroscoe will test results for Trilinos PRs from external contributors still be accessible from the outside?

@mayrmt, the site testing.sandia.gov/cdash/ does not show any PR build results. PR and Master Merge results are only posted to an internal CDash site trilinos-cdash.sandia.gov (which is clear if you look at the links provided in the PR comments). It has been that way for a while now. Moving testing.sandia.gov/cdash/ internally (or getting rid of it altogether) does not change anything currently going on with Trilinos PR testing.

You will need to directly contact @ccober6 and/or @mmwolf about when that might change.

github-actions[bot] commented 1 year ago

This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity. If you would like to keep this issue open please add a comment and/or remove the MARKED_FOR_CLOSURE label. If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE. If it is ok for this issue to be closed, feel free to go ahead and close it. Please do not add any comments or change any labels or otherwise touch this issue unless your intention is to reset the inactivity counter for an additional year.