civet
civet copied to clipboard
idaholab
Continuous Integration, Verification, Enhancement, and Testing
I changed the `buildconfig` of a recipe and then invalidated an existing job that uses that recipe. The build config didn't change. Invalidating should update the config so that this...
Currently the client just cycles through the list of servers and tries to run the top priority job from that server. It might be a better idea to get a...
We could set the commit status on the SHAs for devel and master in addition to PRs. For the master branch this would allow to quickly see when something started...
Currently when viewing a repository we only show branches that have had the status set. We should probably show all branches that have had jobs run against it, regardless of...
Currently with GitLab, if the user creating a MR hasn't granted the correct permissions on their branch, civet can't fill out certain database information it needs to initiate testing. This...
We are currently updating GitLab frequently and we have no good way to actually test that the new server will behave in a good way. Currently we would have to...
Currently we specify dependencies by specifying just the recipe name. If the recipe has multiple build configs then all configs must pass to move on to the next stage. For...
There are multiple cases where the main CIVET server has to talk to the git server (like GitHub). If internet is slow or GitHub is down then it causes severe...
The sequence is 1. Someone creates a PR. 2. They push a new commit while CIVET is building. So CIVET cancels the current jobs and starts testing the new commit....
Currently when we get a PR event we create jobs no matter what. There have been several cases where people submit PRs to a non-default branch and then the tests...