- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Sep 9 2022
Sep 9 2022
ardumont committed R260:da7245d8bf66: archive-staging: Deploy pubdev ingestion stack (authored by ardumont).
archive-staging: Deploy pubdev ingestion stack
ardumont changed the status of T4517: staging: Deploy pubdev, a subtask of T4465: Ingest pub.dev (Dart, Flutter), from Open to Work in Progress.
ardumont committed R260:e0ae21cf308f: staging/loader_package: Deploy new release v4.0 (authored by ardumont).
staging/loader_package: Deploy new release v4.0
ardumont closed T4135: staging: Deploy graphql service, a subtask of T4103: Setup a staging environment for GraphQL APIs, as Resolved.
ardumont closed T4135: staging: Deploy graphql service, a subtask of T4134: Package the graphql service, as Resolved.
Sep 8 2022
Sep 8 2022
ardumont moved T4135: staging: Deploy graphql service from code-review/await-feedback/pause to deployed/landed/monitoring on the System administration board.
ardumont updated the title for P1446 icinga not happy about missing 'host' from whatever icinga dude! be awesome to each other! to icinga not happy about missing 'host'.
ardumont committed rSPSITEfa7e071f4f7f: Add static check on the staging graphql instance 2/2 (authored by ardumont).
Add static check on the staging graphql instance 2/2
ardumont updated the title for P1446 icinga not happy about missing 'host' from whatever icinga dude! be awesome with each other! to whatever icinga dude! be awesome to each other!.
w00t!
ardumont committed rSPSITEdc47d24839ee: Add static check on the staging graphql instance (authored by ardumont).
Add static check on the staging graphql instance
Check some graphql specific content at the same time
ardumont added a comment to D8422: tests/data/README.md: Use 'python3' executable instead of 'python'.
the venv is recommended, but stubborn people like me don't use it :)
ardumont committed rSKCONF41c675db5a4c: archive-staging: Switch branch to development branch to test changes (authored by ardumont).
archive-staging: Switch branch to development branch to test changes
ardumont committed R260:e326c3e94e81: archive-staging: Activate npm package loader (authored by ardumont).
archive-staging: Activate npm package loader
ardumont committed R260:9a678ecd94f2: Use swh-loader-package image for package loaders (authored by ardumont).
Use swh-loader-package image for package loaders
ardumont committed R259:223d96dc21eb: Add new swh-loader-package application (authored by ardumont).
Add new swh-loader-package application
one question inline.
ardumont committed R260:a916c5c6b601: Use swh-loader-highpriority image for highpriority or package loader (authored by ardumont).
Use swh-loader-highpriority image for highpriority or package loader
ardumont committed R260:779e0c46e4e6: Use swh-loader-highpriority image for highpriority or package loader (authored by ardumont).
Use swh-loader-highpriority image for highpriority or package loader
ardumont committed rSKCONF8498a800ccaa: archive-staging: Switch branch to development branch to test changes (authored by ardumont).
archive-staging: Switch branch to development branch to test changes
ardumont committed R260:90da5d2fee72: Use swh-loader-highpriority image for highpriority or package loader (authored by ardumont).
Use swh-loader-highpriority image for highpriority or package loader
ardumont committed rDDOC3108fa1e33fa: service-urls: Update public with graphql instance (authored by ardumont).
service-urls: Update public with graphql instance
ardumont committed R259:9196f22cf16f: Add new swh-loader-highpriority application (authored by ardumont).
Add new swh-loader-highpriority application
No feedback received but some deposits are showing up in the staging deposit db.
So i'm assuming all is fine.
ardumont moved T4399: OIN -> SWH deposit connection from code-review/await-feedback/pause to deployed/landed/monitoring on the System administration board.
It seems to no longer be a problem now.
So closing.
ardumont closed T4330: Deploy maven stack in production, a subtask of T1724: Maven Central repository support, as Resolved.
if you say so ¯\_(ツ)_/¯
'python' may be Python 2,...
ardumont moved T4330: Deploy maven stack in production from in-progress to deployed/landed/monitoring on the System administration board.
Checks:
- task has been scheduled by the scheduler runner process [1]
- listing is being consumed by one worker [2]
- 'maven' listed origins is steadily growing [3]
- New 'maven' listed origins are getting scheduled for ingestion [4]
- maven loaders are ingesting those [5]
ardumont committed rSPSITE11749c11a9cd: production: Update lister to consume maven listing (authored by ardumont).
production: Update lister to consume maven listing
Schedule maven-central listing:
swhscheduler@saatchi:~$ curl -s https://repo1.maven.org/maven2/ | head -2 <!DOCTYPE html> <html> swhscheduler@saatchi:~$ curl -s https://maven-exporter.internal.softwareheritage.org/export-maven-central.fld | head -2 doc 0 field 0 swhscheduler@saatchi:~$ curl -s http://saatchi.internal.softwareheritage.org:5008/ <html> <head><title>Software Heritage scheduler RPC server</title></head> <body> <p>You have reached the <a href="https://www.softwareheritage.org/">Software Heritage</a> scheduler RPC server.<br /> See its <a href="https://docs.softwareheritage.org/devel/swh-scheduler/">documentation and API</a> for more information</p> </body> </html>swhscheduler@saatchi:~$ swh scheduler --url http://saatchi.internal.softwareheritage.org:5008/ \ > task add list-maven-full \ > url=https://repo1.maven.org/maven2/ \ > index_url=https://maven-exporter.internal.softwareheritage.org/export-maven-central.fld Created 1 tasks
Finally, export is done on maven central [1], the fld is computed [2]...
And it's also exposed, hence reachable from lister worker nodes.
ardumont renamed T4511: production: Save Code Now requests for bazaar origins are not scheduled from Save Code Now requests for bazaar origins are not scheduled to production: Save Code Now requests for bazaar origins are not scheduled.
ardumont changed the status of T4511: production: Save Code Now requests for bazaar origins are not scheduled from Open to Work in Progress.
ardumont added a comment to T4511: production: Save Code Now requests for bazaar origins are not scheduled.
This is fixed now.
ardumont committed rSPSITE7315d4f32329: worker/instance: Allow sentry setup to be deactivated (authored by ardumont).
worker/instance: Allow sentry setup to be deactivated
ardumont committed rSPSITE79ffa5465bb1: Make scheduler runner priority schedule save code now bzr origins (authored by ardumont).
Make scheduler runner priority schedule save code now bzr origins
ardumont committed rSPSITEdfd4db9c045a: Make save code now workers consume bzr origins (authored by ardumont).
Make save code now workers consume bzr origins
ardumont committed R260:9f4ef7847c3f: staging/lister: Deploy new release v3.0 (authored by ardumont).
staging/lister: Deploy new release v3.0
ardumont committed R259:3204e8456821: swh.lister: Generate new frozen requirements with release v3.0.0 (authored by ardumont).
swh.lister: Generate new frozen requirements with release v3.0.0
ardumont changed the status of T4330: Deploy maven stack in production, a subtask of T1724: Maven Central repository support, from Open to Work in Progress.
ardumont changed the status of T4330: Deploy maven stack in production from Open to Work in Progress.
ardumont moved T4459: Deploy swh-indexer > v2.6 on staging then production from in-progress to Weekly backlog on the System administration board.
ardumont renamed T4459: Deploy swh-indexer > v2.6 on staging then production from Deploy swh-indexer v2.4 on production and staging to Deploy swh-indexer > v2.5 on production and staging.
ardumont moved T4144: Elastic worker infrastructure from Weekly backlog to in-progress on the System administration board.
ardumont committed R260:f19493032390: archive-staging: Limit replica set to 2 per swh deployments (authored by ardumont).
archive-staging: Limit replica set to 2 per swh deployments
ardumont committed rSKCONFd9be9b5bfd32: archive-staging: Switch back application branch to master (authored by ardumont).
archive-staging: Switch back application branch to master
ardumont committed R260:90e4a70d64b4: archive/loader: Prepare configuration file within init-container (authored by ardumont).
archive/loader: Prepare configuration file within init-container
ardumont committed R260:3b6644706c54: archive/loader: Use init-container to prepare configuration file (authored by ardumont).
archive/loader: Use init-container to prepare configuration file