Details
New Feature
Resolved
Major
Description
As the infrastructure used during the contest preparation phase may be based on git (for example, OI currently is), it would be nice to have automatic deployment.
My idea is to link the master branch in gitlab with SIO2, so that the contest always contains the latest content of the master branch. We want to avoid manual management of packages, as to avoid potential mistakes.
I believe that simplest realization is to create one "shareable" link per task to upload packages. Link works like "reupload package", so it cannot affect other tasks or create a new one.
API should be easy to connect with CI (like GitLab CI).
Access to CI may have more persons than to SIO contest!
Link revoking would be nice.
My idea is to link the master branch in gitlab with SIO2, so that the contest always contains the latest content of the master branch. We want to avoid manual management of packages, as to avoid potential mistakes.
I believe that simplest realization is to create one "shareable" link per task to upload packages. Link works like "reupload package", so it cannot affect other tasks or create a new one.
API should be easy to connect with CI (like GitLab CI).
Access to CI may have more persons than to SIO contest!
Link revoking would be nice.
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.
