Jump to: navigation, search

Search results

  • org/wiki/ThirdPartySystems/Fujitsu_C-Fabric_CI Fujitsu iRMC CIhttps://wiki.openstack.org/wiki/ThirdPartySystems/Fujitsu_iRMC_CI
    749 bytes (39 words) - 00:06, 16 December 2016
  • plan: "None" Other Fujitsu CI systems: Fujitsu ETERNUS CIhttps://wiki.openstack.org/wiki/ThirdPartySystems/Fujitsu_ETERNUS_CI Fujitsu C-Fabric CIhttps://wiki
    1 KB (80 words) - 08:14, 31 March 2021
  • inconvenience. Other Fujitsu CI systems: Fujitsu C-Fabric CIhttps://wiki.openstack.org/wiki/ThirdPartySystems/Fujitsu_C-Fabric_CI Fujitsu iRMC CIhttps://wiki
    1 KB (84 words) - 02:21, 27 December 2017
  • org/wiki/ThirdPartySystems/Fujitsu_ETERNUS_CI Fujitsu iRMC CIhttps://wiki.openstack.org/wiki/ThirdPartySystems/Fujitsu_iRMC_CI Fujitsu ISM CIhttps://wiki.openstack
    928 bytes (55 words) - 00:05, 16 December 2016
  • change the entry to {{ThirdPartySystemTableEntryDown|<your ci system name>}}Do you have a Gerrit CI account created for you by the Infrastructure team and
    10 KB (132 words) - 09:19, 3 June 2021
  • following comment is posted in a gerrit review: <CI NAME>-recheck So if your CI account name is "vendor", the CI should be able to be re-triggered by leaving
    8 KB (1,067 words) - 20:56, 12 March 2019
  • be re-added if the requirement is met in the Liberty release: Zadara Fujitsu Nexenta Support to add jitter to polling cycles to ensure pollsters are
    52 KB (6,613 words) - 16:00, 17 November 2015