Le 12 août 2022 à 12:12, Conner UK, Jim via lists.cloudfoundry.org <jim.conner=fil.com@...> a écrit :

At my place of work, we have concourse jobs which sends us messages on our MS Teams channel whenever a new release appears. Maybe this will be useful for someone else too.

 

Here’s some sanitised snippets from our release-notification-pipeline.

 

***

resources:

- name: java-buildpack-release

  type: github-release

  source:

    user: cloudfoundry

    repository: java-buildpack

    release: true

    access_token: ((github_token))

 

- name: notify-new-java-buildpack-releases

  plan:

  - do:

    - in_parallel:

      - get: release-notifications-pipeline

      - get: release-repo

        resource: java-buildpack-release

        params:

          globs: [notthisthing] # because we only want to watch for tag changes & data, not the release tgz itself (proxy won't allow download of it)

        trigger: true

    - task: check-versions

      config:

        platform: linux

        inputs:

        - name: release-notifications-pipeline

        - name: release-repo

        image_resource:

          type: docker-image

          source:

            repository: ((any_docker_image_which_has_curl_and_jq))

            tag: latest

        run:

          path: cf-deployment-notifications/check_versions.sh

      params:

        RELEASE_NAME: java-buildpack

        TEAMS_WEBHOOK_URL: ((ms_teams_webhook_url))

    timeout: 15m

***

 

.. and the source for the check_versions.sh script.

 

***

#!/bin/bash

 

set -e

 

if [[ -f "release-repo/body" ]]; then

  split --line-bytes=7500 release-repo/body release-repo/release-body-

 

  for file in $(find release-repo -name "release-body-*" | sort )

  do

    request_body=$(jq -n --arg body "$(cat "${file}")" --arg title "New $RELEASE_NAME $(cat release-repo/version) release" '{title: $title, text: $body}')

    curl -if -X POST --data "${request_body}" -k "${TEAMS_WEBHOOK_URL}"

    rm "${file}"

  done

else

  request_body=$(jq -n --arg body "The author was too lazy to add a release note" --arg title "New $RELEASE_NAME $(cat release-repo/version) release" '{title: $title, text: $body}')

  curl -if -X POST --data "${request_body}" -k "${TEAMS_WEBHOOK_URL}"

fi

***

 

Jim

 

 

From: <cf-dev@...> on behalf of Benjamin Gandon <benjamin@...>
Reply to: "cf-dev@..." <cf-dev@...>
Date: Friday, 12 August 2022 at 10:42
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] Buildpack deployment in cflinuxfs3 stack for AWS

 

Hi Carlos, The release notes for the classical Cloud Foundry Node.js Buildpack are in GitHub : https://github.com/cloudfoundry/nodejs-buildpack/releases These need to be read regularly by a human for taking action when necessary, like when 

Hi Carlos,

 

The release notes for the classical Cloud Foundry Node.js Buildpack are in GitHub : https://github.com/cloudfoundry/nodejs-buildpack/releases

These need to be read regularly by a human for taking action when necessary, like when some language versions are discontinued.

 

For newer Paketo buildpacks, I’ve raised some similar concern in the Paketo Slack last year:

https://paketobuildpacks.slack.com/archives/CULAS8ACD/p1616142574002300?thread_ts=1615586828.001200&cid=CULAS8ACD

 

What we would need is a way for buildpack consumers like us, to build automation (in Concourse or anything similar) that warns the correct people in the enterprise for taking action when some Buildpack is discontinuing some language version. I don’t know if there has been any progress on this since last year.

 

Benjamin

 

Le 4 août 2022 à 10:54, Delgado, Carlos via lists.cloudfoundry.org<carlos.delgado02=sap.com@...> a écrit :

 

Hello team,

 

I am interested to know about communications whenever a new buildpack is deployed and available in AWS cflinuxfs3 stack, in order to adapt our projects timely fashion, I am interested in Nodejs buildpack in particular, since a new version has been released recently that removed Node 12 and affected our deployments.

 

Do you know by any chance if such communication exists?

 

Many thanks,

BR.

 

 

Carlos Delgado

DevOps Lead, Customer Success Automation ES

SAP ESPAÑA, S.A. Torre Diagonal Mar - B1 C/, 08019 Barcelona, Spain

T +34 93 483-3238, M +34 678 684650, E carlos.delgado02@...

 

Pflichtangaben/Mandatory Disclosure Statement:

http://www.sap.com/impressum

 

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten.  Sollten Sie

diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der

E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail.

Vielen Dank.

 

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information.  If you have received

this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform

us immediately and destroy the original transmittal.

Thank you for your cooperation

 

<image001.png>

<image002.jpg>

 

 

---

The information transmitted is intended for the person or entity to which it is addressed and may contain confidential, privileged or copyrighted material. If you receive this in error, please contact the sender and delete the material from any computer. Any views or opinions expressed are those of the author and do not necessarily represent those of Fidelity International. All e-mails may be monitored. FIL Investments International (Reg. No.1448245), FIL Investment Services (UK) Limited (Reg. No. 2016555), FIL Pensions Management (Reg. No. 2015142), Financial Administration Services Limited (Reg. No. 1629709) and FIL Wealth Management Limited (Registered. No. 06121251) are authorised and regulated in the UK by the Financial Conduct Authority. FIL Life Insurance Limited (Reg No. 3406905) is authorised in the UK by the Prudential Regulation Authority and regulated in the UK by the Financial Conduct Authority and the Prudential Regulation Authority. Registered offices at Beech Gate, Millfield Lane, Lower Kingswood, Tadworth, Surrey KT20 6RP.

Le 4 août 2022 à 10:54, Delgado, Carlos via lists.cloudfoundry.org <carlos.delgado02=sap.com@...> a écrit :

Hello team,

 

I am interested to know about communications whenever a new buildpack is deployed and available in AWS cflinuxfs3 stack, in order to adapt our projects timely fashion, I am interested in Nodejs buildpack in particular, since a new version has been released recently that removed Node 12 and affected our deployments.

 

Do you know by any chance if such communication exists?

 

Many thanks,

BR.

 

 

Carlos Delgado

DevOps Lead, Customer Success Automation ES

SAP ESPAÑA, S.A. Torre Diagonal Mar - B1 C/, 08019 Barcelona, Spain

T +34 93 483-3238, M +34 678 684650, E carlos.delgado02@...

 

Pflichtangaben/Mandatory Disclosure Statement:

http://www.sap.com/impressum

 

Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten.  Sollten Sie

diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der

E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail.

Vielen Dank.

 

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information.  If you have received

this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform

us immediately and destroy the original transmittal.

Thank you for your cooperation

 

<image001.png>

<image002.jpg>

 

Hello folks! 

Postponing this month's CAB call to accommodate speakers. Will announce the new day/date/time shortly. 

Apologies for the inconvenience. 

Regards,

Ram

This change has been successfully rolled out, we're saving 50-70% on our default deployments, yay! "bbl up" with newer bbl versions will change your default VM types catalog. If you run CATS, read on...

Newer versions of BBL starting with 8.4.91 will deploy more modern and efficient VM sizes by default. Along the way we encountered a problem where the default configuration is less reliable in passing CATS, which makes sense because there's a lot less hardware deployed. A change from CATS timeout_scale: 1 to timeout_scale: 2 fixes the issue and the CATS still pass when run in parallel with 12 nodes only about 25% slower (which is acceptable). We plan to fix CATS timeout defaults eventually such that this timeout scaling configuration option is not required.

Using the 1AZ cf-deployment ops-file, the CATS now will always fail when run in parallel due to the smaller standardized diego cell size. To work around this, BBL v8.4.93 standardizes the "medium" (4 cores, 16GB) and "large" (8 cores, 32GB) VM sizes and introduces a "medium-highmem" (4 cores, 32GB) size. These additional standard sizes give operators and CF authors additional sizes to choose from for diego cells, such as this newly introduced ops file designed to make parallel CATS testing fast+reliable in a single-AZ minimal configuration.