3:56 p.m.
Craig,
I think you are confusing my confusion ;-)
My point is, we're not going to invest in #2 on Ubuntu. Sure, we could. Not
gonna do it, unless it puts RHEL where I want it to be. Why on Earth would
we spend engineering resources to enable Ubuntu runners on GitHub Actions?
And, yes right after I fired off the email, I realized these were
implemented by Docker, not GitHub (the company). I view this as a two part
Feature:
1. Make RHEL available as a runner at GitHub. This would justify investment
in building #2
2. Create GitHub actions code for automation, which would live in the
containers (aka Podman) community
3. Perhaps productize these as some sort of RHEL/UBI content which people
could depend on Red Hat for. AKA, a productized version of #2.
But, getting #1 done first is key, because our goals as a company are not
to use Podman engineers to enable Ubuntu in a key place where developer
eyeballs and fingers are working. This is essentially free marketing which
we should not leave on the table. Also, this ties into a much bigger,
strategic initiative that I have as the RHEL Server product manager - make
RHEL available everywhere (GitHub Actions, make it work in GitLab (still
working on that), make UBI an Official Image on DockerHub, build out Podman
Desktop for Mac/Windows, enable RHEL in WSL2. There's a common theme to all
of these. Availability of RHEL.
In marketing there's the concept of zero, first, second, and third moments
of truth. I won't bore you with all of the details, but we're failing
(worst) at the first moment of truth. The customer goes into the frozen
pizza aisle and there's no Red Baron pizza to even buy. In this case, it's
no RHEL available at GitHub Actions (as well as Digital Ocean, Linode,
CircleCI, CirrusCI, Windows Store for WSL2, etc). We need the Red Baron
pizza in the frozen foods section at all grocery stores.
Then, it's worth building out automation to drive consumption.
Best Regards
Scott M
On Thu, May 26, 2022 at 3:52 PM Nalin Dahyabhai <nalin(a)redhat.com> wrote:
On Thu, May 26, 2022 at 12:42:30PM -0400, Craig Rodrigues wrote:
> Hi,
>
> For Docker, there are a number of GitHub Actions with good documentation
> that can be used
> to build containers, and push them to registries using docker
build/buildx.
>
> I've started using these Actions:
>
> https://github.com/docker/setup-buildx-action/
> https://github.com/docker/docker-login-action/
> https://github.com/docker/build-push-action
> https://github.com/docker/metadata-action
>
> docs:
>
https://docs.github.com/en/actions/publishing-packages/publishing-docker-...
>
> These docs and actions are actually quite good when setting up
> automation in GitHub for building/pushing containers.
>
> Are there equivalent GitHub Actions for using podman?
Its focus is broader, so it includes actions focused on integrating with
OpenShift, but the "redhat-actions" organization includes a few actions
I've been meaning to try out to get familiar with actions in general,
and automating some builds/pushes that I currently do by running a
script:
https://github.com/redhat-actions/podman-login
https://github.com/redhat-actions/buildah-build
https://github.com/redhat-actions/push-to-registry
The names, at least, suggest that they aim to fill similar roles.
HTH,
Nalin
_______________________________________________
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io
--
<https://www.redhat.com/en/about/press-releases/red-hat-defines-new-epicen...
Scott McCarty
Product Management - RHEL Server
Email: smccarty(a)redhat.com
Phone: 312-660-3535
Cell: 330-807-1043
Web: http://crunchtools.com