Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Obsolete
-
Affects Version/s: Current Version
-
Fix Version/s: None
-
Component/s: OIOIOI
-
Labels:None
Description
Sometimes we update Vagrantfile, so it works, but later someone forgets to update it alongside with his/her change, so I wanted to suggest a nightly test which does vagrant up from scratch[1] and after a while checks some simple scenarios[2].
[1] Deletes previous VM and creates a new one installing everything
[2] User registration, contest creation, submitting some code, etc and checking the HTTP answers if it is really what we want and not some 500s errors.
[1] Deletes previous VM and creates a new one installing everything
[2] User registration, contest creation, submitting some code, etc and checking the HTTP answers if it is really what we want and not some 500s errors.
Activity
- All
- Comments
- History
- Activity
- Transitions
- Commits
Connect your code to JIRA
Link every code change to JIRA just by adding an issue keys in commit messages. Bridge the gap back to your source and know which changes fixed which JIRA issues.
Git & Mercurial in the cloud
Collaborate across unlimited private code repositories.
Git behind the firewall
Manage and collaborate on Git repositories behind a firewall.
Browse and search code
Browse, search, and track source code repositories.
