October 11, 2021 Community Meeting

[adambkaplan]

• Please add a topic in this thread and add a link to the Github issue associated with the topic.
• Please make sure you give folks enough time to review/discuss the topic offline on Github before coming into the meeting
• (optional) Paste the image of an animal 😸

[adambkaplan]

Nomination: @shahulsonhal to shipwright-io/build reviewers list (and join the organization!).

[gabemontero]

We have a "new" user beginning to report issues / citing difficulties:

• Image cannot be pulled due to unauthorized with private container registry build#895
• Permission denied to mkdir /.docker build#896

FYI, he is a member of the larger "devtools" team here at RH that the other RH regular community members are a part of

Disclaimer: I'll be on PTO Oct 11 and will miss this discussion, but wanted to raise awareness in case the github notifications for these get lost in the shuffle, and/or nobody gets cycles to look at it before the Oct 11 call.

[SaschaSchwarze0]

Looking for an owner with a red hat for SHIP-0024: Surfacing Errors to BuildRuns #30.

              .,;>>%%%%%>>;,.                                              
           .>%%%%%%%%%%%%%%%%%%%%>,.                                       
         .>%%%%%%%%%%%%%%%%%%>>,%%%%%%;,.                                  
       .>>>>%%%%%%%%%%%%%>>,%%%%%%%%%%%%,>>%%,.                            
     .>>%>>>>%%%%%%%%%>>,%%%%%%%%%%%%%%%%%,>>%%%%%,.                       
   .>>%%%%%>>%%%%>>,%%>>%%%%%%%%%%%%%%%%%%%%,>>%%%%%%%,                    
  .>>%%%%%%%%%%>>,%%%%%%>>%%%%%%%%%%%%%%%%%%,>>%%%%%%%%%%.                 
 .>>%%%%%%%%%%>>,>>>>%%%%%%%%%%'..`%%%%%%%%,;>>%%%%%%%%%>%%.               
.>>%%%>>>%%%%%>,%%%%%%%%%%%%%%.%%%,`%%%%%%,;>>%%%%%%%%>>>%%%%.             
>>%%>%>>>%>%%%>,%%%%%>>%%%%%%%%%%%%%`%%%%%%,>%%%%%%%>>>>%%%%%%%.           
>>%>>>%%>>>%%%%>,%>>>%%%%%%%%%%%%%%%%`%%%%%%%%%%%%%%%%%%%%%%%%%%.          
>>%%%%%%%%%%%%%%,>%%%%%%%%%%%%%%%%%%%'%%%,>>%%%%%%%%%%%%%%%%%%%%%.         
>>%%%%%%%%%%%%%%%,>%%%>>>%%%%%%%%%%%%%%%,>>%%%%%%%%>>>>%%%%%%%%%%%.        
>>%%%%%%%%;%;%;%%;,%>>>>%%%%%%%%%%%%%%%,>>>%%%%%%>>;";>>%%%%%%%%%%%%.      
`>%%%%%%%%%;%;;;%;%,>%%%%%%%%%>>%%%%%%%%,>>>%%%%%%%%%%%%%%%%%%%%%%%%%%.    
 >>%%%%%%%%%,;;;;;%%>,%%%%%%%%>>>>%%%%%%%%,>>%%%%%%%%%%%%%%%%%%%%%%%%%%%.  
 `>>%%%%%%%%%,%;;;;%%%>,%%%%%%%%>>>>%%%%%%%%,>%%%%%%'%%%%%%%%%%%%%%%%%%%>>.
  `>>%%%%%%%%%%>,;;%%%%%>>,%%%%%%%%>>%%%%%%';;;>%%%%%,`%%%%%%%%%%%%%%%>>%%>.
   >>>%%%%%%%%%%>> %%%%%%%%>>,%%%%>>>%%%%%';;;;;;>>,%%%,`%     `;>%%%%%%>>%%
   `>>%%%%%%%%%%>> %%%%%%%%%>>>>>>>>;;;;'.;;;;;>>%%'  `%%'          ;>%%%%%>
    >>%%%%%%%%%>>; %%%%%%%%>>;;;;;;''    ;;;;;>>%%%                   ;>%%%%
    `>>%%%%%%%>>>, %%%%%%%%%>>;;'        ;;;;>>%%%'                    ;>%%%
     >>%%%%%%>>>':.%%%%%%%%%%>>;        .;;;>>%%%%                    ;>%%%'
     `>>%%%%%>>> ::`%%%%%%%%%%>>;.      ;;;>>%%%%'                   ;>%%%' 
      `>>%%%%>>> `:::`%%%%%%%%%%>;.     ;;>>%%%%%                   ;>%%'  
       `>>%%%%>>, `::::`%%%%%%%%%%>,   .;>>%%%%%'                   ;>%'   
        `>>%%%%>>, `:::::`%%%%%%%%%>>. ;;>%%%%%%                    ;>%,   
         `>>%%%%>>, :::::::`>>>%%%%>>> ;;>%%%%%'                     ;>%,  
          `>>%%%%>>,::::::,>>>>>>>>>>' ;;>%%%%%                       ;%%, 
            >>%%%%>>,:::,%%>>>>>>>>'   ;>%%%%%.                        ;%% 
             >>%%%%>>``%%%%%>>>>>'     `>%%%%%%.                           
             >>%%%%>> `@@a%%%%%%'     .%%%%%%%%%.                          
             `a@@a%@'    `%a@@'       `a@@a%a@@a'

[SaschaSchwarze0]

Reminder: consider making your community membership public: https://github.com/orgs/shipwright-io/people

      /`·.¸
     /¸...¸`:·
 ¸.·´  ¸   `·.¸.·´)
: © ):´;      ¸  {
 `·.¸ `·  ¸.·´\`·¸)
     `\\´´\¸.·´

[SaschaSchwarze0]

v0.6.0 sync, remaining TODOs:

• Get comments in Goreleaser package management #47 addressed and merged
• Create v0.6.0 release for the CLI
• Update CLI installation instruction in WIP Updates for v0.6.0 #56
• Check comment Doc updates for v0.6.0 #54

                (`.              
                 \ `.           
                  )  `._..---._
\`.       __...---`         o  )
 \ `._,--'           ,    ___,'
  ) ,-._          \  )   _,-' 
 /,'    ``--.._____\/--''  

[SaschaSchwarze0]

We noticed a short-coming of the Buildpacks build strategy: as we bypass pack, the environment variables are not working. They are expected to be stored in files under /platform/env. @shahulsonhal currently develops some code that copies environment variables to as directory. Beside the container environment variables, we also plan to support an optional .env(rc) file. I think it makes sense to offer this feature as open source as well and make use of it in our Buildpacks sample strategies (and suggest it for the upstream Tekton catalog) - it makes the environment variables story complete for Buildpacks.

The strategy then looks like this:

kind: ClusterBuildStrategy
metadata:
  name: buildpacks-v3
spec:
  buildSteps:
    - name: prepare-platform-env
      image: somerepo, maybe quay.io/shipwright/prepare-platform-env
      command:
        - /ko-app/prepare-platform-env
      args:
        - --env-rc=$(params.shp-source-context)
        - --target=/platform/env
        - --blacklist=KUBERNETES*
      volumeMounts:
       - mountPath: /platform/env
         name: platform-env
    - name: build-and-push
      image: docker.io/paketobuildpacks/builder:full
      [...]
      volumeMounts:
       - mountPath: /platform/env
         name: platform-env

Side note for those who are unaware: our controller automatically adds an emptyDir volume to the TaskRun for each volumeMount's unique name that it finds.

Question:

Do we want to provide images that enhance specific sample build strategies as part of Shipwright Build ? Or should we maintain a separate repo for this ?

 ___            ___
/   \          /   \
\_   \        /  __/
 _\   \      /  /__
 \___  \____/   __/
     \_       _/
       | @ @  \_
       |
     _/     /\
    /o)  (o/\ \_
    \_____/ /
      \____/

[SaschaSchwarze0]

• Let's make @shahulsonhal a reviewer ! PR is in the build repo.
• In general a good practice to look at issues from time to time to see if some user asks for some help that is easy to give. Beside that we conclude that we will look in detail at grooming
• Matthias: add a slack message to our channel when a new issue is opened ? Con: clutters the channel. Pro: one does not miss things. Jason: worth a shot and revisit in a month. Adam: don't know how to achieve it. Let's ask in #slack-admin channel. Sascha will quickly do this after the meeting. Edit: see https://kubernetes.slack.com/archives/C4M06S5HS/p1633960687039200
• Corey and Adam are going to look at the errors ship.
• v0.6.0 release work:
  • Sample GitHub action that uses goreleaser: https://github.com/homeport/build-load/blob/main/.github/workflows/release.yml.
  • CLI MVP: just cross-compiled binary, we can look package for the next iteration
  • Blog post: Sascha will fix remaining TODOs, reviewers please review
  • Adam will check the docs copy to include fixes from Sascha
• Regarding Buildpacks environment variables. In the latest version in Tekton, it is there: https://github.com/tektoncd/catalog/blob/main/task/buildpacks/0.3/buildpacks.yaml, writes env vars to /platform/env. For shipwright we would do something similar, just not take from a param but from the "real" environment. Still worth checking their opinion on envrc support.

[gabemontero]

/close

[openshift-ci]

@gabemontero: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.