#release-engineering (2021-10)

jenkins_ci All things CI/CD. Specific emphasis on Codefresh and CodeBuild with CodePipeline.

CI/CD Discussions

Archive: https://archive.sweetops.com/release-engineering/

2021-10-07

2021-10-06

Zach avatar

ugh. testing this out and the ‘reusable workflow’ must be in a public repository

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

same with private actions

Zach avatar

thats a real bummer

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

but with private actions, there’s a workaround - you can as a step clone the private repo

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

then call uses on the local checkout

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

can. you try that?

Zach avatar

I don’t understand githubs ‘thing’ with public repos

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

ya, so the whole community that pays them is snubbed from using the best features

Zach avatar

Not sure if that would work in this case since the call_workflow requires calling a repository with a branch version

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
Zach avatar

hm ok I’ll try that later

Zach avatar

for now I will write them a sternly worded letter of complaint

1
Scott Mathson avatar
Scott Mathson

Hah! I had the same reaction to this feature. The kinds of things I’d want to DRY up have absolutely no utility to the the wider community. Seems like a silly limitation

Zach avatar

Github support got back to me and said that yes, the use of this feature for private repos is GitHub Enterprise only.

2
    keyboard_arrow_up