Changes between Initial Version and Version 4 of Ticket #4355


Ignore:
Timestamp:
08/07/2017 01:08:29 PM (3 years ago)
Author:
tlucas
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4355

    • Property Cc trev kvas added
    • Property Priority changed from Unknown to P3
    • Property Ready set
    • Property Owner set to tlucas
  • Ticket #4355 – Description

    initial v4  
    1313The release automation should deal with this situation without failing. I'm not sure what's the best way of dealing with this, I see two options: 
    1414 
    15 1. Before making any changes, we could check whether the ''downloads'' repo is outdated (or dirty, see #4354) and abort with an error message. (While at it, we could do the same check for the ''adblockpluschrome'' repository.) 
    16 2. Same as above but before warning about the situation, we attempt to handle it by updating the repository automatically, only aborting if that fails. (This is a bit trickier than it sounds, we also need to deal with committed but unpushed local changes e.g.) 
     15Before making any changes, the release automation should check whether the involved repositories, which are not listed in the dependencies-list, are outdated (or dirty, see #4354) and abort with an error message.