Skip artifacts between Congress assignments without S3 or similar external resources

Question

I use compilation and assembly of binary files that I would like to send for integration tests. However, they are lightweight and using an S3 bucket for permanent storage seems redundant. In addition, I control versions with semver-resource , which also seems to require S3 or something to support it.

Is there a way to set up a local working or similar blobstore? can i use postgres db to store my semester? it is small enough, it should fit into the database table.

Answer 1

The short answer is no.

Congress is designed in such a way that the Concourse deployment itself has no statelessness, clearly not ensuring the constancy of the artifact and the desire to be largely free from configuration.

This makes pipelines stand-alone, making your CI reproducible. If your Concourse server burns out, you haven't lost anything special. You can simply deploy one more and send the source pipeline. Then everything will continue from where it stopped: your versions will continue to count from where they were, instead of restarting from 0.0.0, and all your artifacts are still where they are.

With all that said, you can deploy your own Sb-compatible blob repository. Resource s3 should talk well with him.

Answer 2

We use the semver resource with gist. Just enter the clone id from the main page:

then set your resource: - name: version type: semver source: driver: git branch: master uri: {{version-url}} file: Version private_key: {{github-private-key}}