Fork me on GitHub
#circleci
<
2020-01-07
>
borkdude11:01:28

@marc-omorain Since artifact urls are not public (unlike with Github actions) I'd like to have an easy way to publish these OR to make them public by default. E.g. post the link to a Slack channel so people know where to grab the latest nightly builds. There was a feature request for it here: https://discuss.circleci.com/t/easily-get-artifact-url/10394/2 But it was closed without any reaction...

borkdude11:01:47

I could cobble together something myself, but I can't related some information from the link to what's going on inside the build:



CIRCLE_BUILD_NUM=3317

borkdude11:01:44

So maybe the second number is a fixed number for the project. And the /0 is also a fixed number? This might be easier than I thought

Marc O'Morain11:01:59

The /0 is the index of the parallel container as far as I know

Marc O'Morain11:01:39

So it will always be 0 unless you are using parallelism, in which case it will be 0, 1, 2… for each container

borkdude11:01:23

That seems doable then

Marc O'Morain11:01:46

`

201467090
Is the ID in GitHub of your project

Marc O'Morain11:01:26

Things I wished that the first engineers did not do at CircleCI: used GH IDs as our own internal IDs 😞

polymeris11:01:14

There is an API to get the artifact links: https://circleci.com/docs/api/v2/#get-a-job-39-s-artifacts (the API itself requires you to be authed)

borkdude12:01:05

ok: #babashka_circleci_builds 🙂