You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's because bob archive only works locally where the artifacts are stored. It's poorly documented in the manpage.
Well, yes, indeed. Is this just because nobody cared to implement a remote bob archive or are there technical reasons?
There was no need yet. Until now it was sufficient to have a cron-job on the artifact server that works locally. Technically it is possible to implement that but it will require the HTTP endpoint to be a WebDAV resource (needs PROPFIND to list the directories). The shell backend might need a ls command too.
Extend the archive command to clean up a non local archive using a
custom plugin. Therefore the plugin manifest must contain
'archiveAccessors'. Each entry should point to a class inheriting from
'BaseArchiveAccess' providing the appropriate methods to access the
custom archive.
FixesBobBuildTool#340.
Extend the archive command to clean up a non local archive using a
custom plugin. Therefore the plugin manifest must contain
'archiveAccessors'. Each entry should point to a class inheriting from
'BaseArchiveAccess' providing the appropriate methods to access the
custom archive.
FixesBobBuildTool#340.
There was no need yet. Until now it was sufficient to have a cron-job on the artifact server that works locally. Technically it is possible to implement that but it will require the HTTP endpoint to be a WebDAV resource (needs
PROPFIND
to list the directories). Theshell
backend might need als
command too.Originally posted by @jkloetzke in #336 (comment)
The text was updated successfully, but these errors were encountered: