hg/svn support in save code now

---

Migrated from T1419 (view on Phabricator)

mentioned in merge request !100 (closed)

added Sprint 2018 12 Web app labels

added priority:High label

is there anything left, that is blocking the deployment of this? (otherwise it seems like an easy low-hanging fruit)

if there are blockers, it'd be nice to track them here as task dependencies

Are there any blockers left? It would be really nice to roll this out in the very near future.

we (@anlambert and I) will try to have this task closed ASAP (like today, if no big bad stopper arise in front of us)

mentioned in commit 508d1c74

mentioned in commit 04b06d85

closed

@rdicosmo , the possibility to submit hg and svn origin types through the "Save code now" form has been deployed to production [1]. I have submitted one origin of each type to save. Let's see if the underlying scheduler tasks get correctly executed before spreading the news to the wild.

• [1] https://archive.softwareheritage.org/browse/origin/save/

Thanks... looks like the tasks have been properly scheduled, but they have not been executed... some more polishing may be needed ...

Le jeu. 2 mai 2019 à 17:28, anlambert (Antoine Lambert) < forge@softwareheritage.org> a écrit :

anlambert added a comment.

@rdicosmo https://forge.softwareheritage.org/p/rdicosmo/ , the possibility to submit hg and svn origin types through the "Save code now" form has been deployed to production [1]. I have submitted one origin of each type to save. Let's see if the underlying scheduler tasks get correctly executed before spreading the news to the wild.

[1] https://archive.softwareheritage.org/browse/origin/save/

TASK DETAIL https://forge.softwareheritage.org/#1419

EMAIL PREFERENCES https://forge.softwareheritage.org/settings/panel/emailpreferences/

*To: *anlambert *Cc: *rdicosmo, anlambert, zack, douardda, lenamduytuan

Reopening this as the first submitted save code now tasks for hg and svn did not get executed so far (see [1]). Nevertheless, they have been scheduled so this looks like some extra workers configuration is needed in production.

• [1] https://archive.softwareheritage.org/browse/origin/save/#requests

reopened

There was a config/deployment bug on both the hg and svn loaders. Both bugs have been fixed and the tasks are running fine now.

assigned to @anlambert

closed

mentioned in issue swh-scheduler#1508 (closed)