Måndagen 15 maj 2017 kl. 10:17:13 UTC+2 skrev Fredrik Wendt: > > For M2, we could pull history from API, and try to keep track of stage > counters. >
Then you know the counter values, but what do you do when you set it up again? Use a pipeline label which is the pipeline counter plus an offset based on the old value? (I'm personally not very happy about the LABEL / COUNTER distinction.) Or do you plan to hack the h2 database? Or perform dummy builds until you catch up with the numbers? You're not relying on any artifacts in the GoCD artifacts repository? We perform backups regularly to a predefined location, so we have server.artifactsdir set in cruise-config.xml for that. We currently rely on manually restoring that. We haven't set up an automated restore mechanism, and we haven't sorted out exactly what to do when we've restored if it turns out that we have builds in our repositories which are ahead of the restored GoCD context. -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
