Hi Magnus :-) Den måndag 15 maj 2017 kl. 15:08:35 UTC+2 skrev Magnus Lyckå: > > 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? >
Probably hack *shrug*. > You're not relying on any artifacts in the GoCD artifacts repository? > We only use GoCD artifacts to flow information from one pipeline to another. Transient information, such as names of infrastructure components (load balancers, cluster names, EC2 instances, ...) is stored outside GoCD, such as git repos. All other artifacts are stored elsewhere (Amazon AMIs, Docker images in ECR, terraform state in git repos). In short: we're happy to throw all artifacts away, and start over by issuing the root-most node in the pipeline mesh and just have it solve the rest. > 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. > One thing we did at another client, was to put the counter we used in a git repo. A simple python script would optimistically increase a number in a file, commit+push. Worked just fine. We did this before moving to GoCD (all restore attempts we'd made with Jenkins failed in one way or many, so ...) We could've used an external service like Redis and do an INCR or HINCRBY. / Fredrik -- 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.
