Details
Resolved
Minor
Description
Names from: https://sio2.mimuw.edu.pl/api/docs/
There is no way to check problem_id after package_upload, within API.
It makes impossible automatic reuploading package inside CI, without checking id by hand.
Because of that, API is much less useful than it could be.
Possible solution:
- package_upload returns package_id,
- package_id allows to check upload status (and problem_id if upload was successful).
Other solutions are also possible:
- Possibility to use package_id instead of problem_id.
- Reserving problem_id at the beginning. On fail, it is still reserved and waiting for package reupload.
There is no way to check problem_id after package_upload, within API.
It makes impossible automatic reuploading package inside CI, without checking id by hand.
Because of that, API is much less useful than it could be.
Possible solution:
- package_upload returns package_id,
- package_id allows to check upload status (and problem_id if upload was successful).
Other solutions are also possible:
- Possibility to use package_id instead of problem_id.
- Reserving problem_id at the beginning. On fail, it is still reserved and waiting for package reupload.
Issue Links
- relates to
-
SIO-2394
Improve API support for problem package CI (meta-ticket)
-
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.
