Thanks.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 21 2021
Jenkins CI job for building SWH docs when submitting diffs to swh-docs is now properly deployed and configured, time to abandon this.
Build is green
It's still missing " Define an architecture to fetch extrinsic metadata outside listers and loaders"
Build is green
Make the build passes again for last test.
Build is green
and fix the LOGGER.error usage
Build has FAILED
In T3677#72891, @moranegg wrote:In T3677#72872, @vlorentz wrote:Don't we already have this for deposits, as the meta-metadata?
If we do, please show me.
Build has FAILED
remove hardcoded log levels
Introduce warning to check the CI build fails
Remove file committed by mistake
Use single quotes for string litteral in groovy script
Build is green
This can be resolved :-)
Build has FAILED
Use ReadOnlyObjStorage and NonIterableObjStorage instead of NotImplementedError
Not that i get all that's in there though ;)
I trust in your tryouts.
In T3677#72872, @vlorentz wrote:The same might be true when the target is an origin-url.
It's not
This should be tested with a deposit of metadata-only with the target origin.
When the SWHID is without context the column origin in the deposit admin view shows the SWHID, which is very confusing by the wey.
I think we (or I should say- I) missed ambiguity of the concept origin.
Build is green
The same might be true when the target is an origin-url.
Rebase
Build is green
See https://jenkins.softwareheritage.org/job/DDOC/job/build-on-diff/13/ for more details.
Yes context is a better option.
Then target is not in the grouped context.
I'd rather call it "context" than "target-details", as this clearer (IMO), and consistent with the original terminology in https://docs.softwareheritage.org/devel/swh-storage/extrinsic-metadata-specification.html
Build is green
rebase
Contribution to the Grid5000 documentation for Fed4Fire.
Using Export As ansible, I unzipped the result.
Created another experiment (with 25min lifetime only) and it's going better:
I wanted to terminate the experiment but it looks like it must expire (although Grid5000 has the option to terminate a job).
The Grid5000 machines are found in the "
https://www.grid5000.fr/w/Fed4FIRE is the better documentation to use Grid5000 via Fed4Fire
@olasd I'd like to add dependencies to the CI job running swh-perfecthash (valgrind) so that it can verify the C implementation is clean. Would you be so kind as to point me in the right direction? I looked in https://forge.softwareheritage.org/source/swh-jenkins-jobs but could not find the keyword cmph and concluded it must be in another repository.
There is a monitor that shows all testbeds, among which is grid5000: