Package Details: concourse 7.11.2-2

Git Clone URL: https://aur.archlinux.org/concourse.git (read-only, click to copy)
Package Base: concourse
Description: Concourse is a container-based continuous thing-doer written in Go and Elm
Upstream URL: https://concourse-ci.org
Keywords: ci ci-cd concourse continuous-delivery continuous-integration elm go pipelines
Licenses: custom:Apache-2.0
Conflicts: concourse-bin
Submitter: bramswenson
Maintainer: cheatsc
Last Packager: cheatsc
Votes: 4
Popularity: 0.000001
First Submitted: 2017-03-08 08:58 (UTC)
Last Updated: 2024-06-09 05:00 (UTC)

Pinned Comments

cheatsc commented on 2024-05-30 22:44 (UTC) (edited on 2024-05-30 22:51 (UTC) by cheatsc)

@gbourant Thank you for reporting. I assume that this patch is also required for v7.11.2. I'll try the patch this night.

Also if a strange error occurs use export UV_USE_IO_URING=0

I've faced the same problem. I'll set the environment variable on PKGBUILD or announce here until it will be resolved.

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

cheatsc commented on 2021-10-15 14:03 (UTC) (edited on 2021-10-15 14:21 (UTC) by cheatsc)

Recently, git resource cannot fetch repository as follows:

selected worker: concourse-worker
Cloning into '/tmp/git-resource-repo-cache'...
fatal: unable to access 'https://source.denx.de/u-boot/u-boot.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

This problem probably relates that expired root CA of Let's encrypt...

https://letsencrypt.org/ja/docs/dst-root-ca-x3-expiration-september-2021/

cheatsc commented on 2021-07-30 07:28 (UTC)

From 7.4.0, concourse does not use hardcoded paths by the following commits:

  • 9078d3962eb340d096f8eb2beb05e0349150fc98
  • 8e96b380a9dca717ddef0b03e14f685429c6b6ba

concourse makes the paths from the own directory.

Therefore, users should use --containerd-init-bin /usr/lib/concourse/bin/init and --containerd-cni-plugins-dir /usr/lib/cni/ for workers

ragouel commented on 2020-04-29 03:31 (UTC) (edited on 2020-04-29 03:45 (UTC) by ragouel)

From Concourse docs

The concourse worker command automatically configures and runs gdn, but depending on the environment you're running Concourse in, you may need to pop open the hood and configure a few things

Since I don't use this package, I don't know its' inner workings. If you can provide a guide on how it works and what it requires (a Wiki page would be nice), I can look into it.

EDIT: It seems upstream updated to 5.5.11 which looks like a rollback?. I'm updating this to latest release.

Cheers.

hendres commented on 2020-04-28 18:41 (UTC)

Hi @raguel

I had some time to dig in.

as mentioned by @coderobe there are some missing dependencies. At least the gdn binary.

Regards Harm

ragouel commented on 2020-04-10 11:37 (UTC)

@coderobe concourse-6.0.0.tar.gz does not contain the source files for the binaries found in concourse-6.0.0-linux-amd64.tgz.

coderobe commented on 2020-04-09 22:07 (UTC)

This doesn't build most of the assets the upstream binary contains; Compare the resulting package size of 64 MiB (17 compressed) vs upstreams' 750+ MiB (compressed!).

Have you tried creating a ci runner?

ragouel commented on 2020-04-09 20:11 (UTC)

@hendres you can email me the unit files or post a github gist. I'm not entirely sure about the security hooks. I assume both ways are valid.

hendres commented on 2020-04-09 18:56 (UTC)

I am thinking about some service units and also a wiki page, can I push you the services in a branch (that leaves my knowing on aur)? Should the certificates be created in a post install hook (security/entropy)? Do you want to have a look at the wiki page before publishing?

ragouel commented on 2020-04-09 18:37 (UTC)

You're welcome @hendres.

hendres commented on 2020-04-09 18:34 (UTC)

Thank you for the update @ragouel