Bitnami container images
Go to file
Fran Mulero 0fb6918cb6 [containers/*] CD pipeline (#20)
* Add CD pipeline for each commit to master

Signed-off-by: Fran Mulero <fmulero@vmware.com>

* Amend branch name

Signed-off-by: Fran Mulero <fmulero@vmware.com>

* Amend regular expression to get diffent flavors

Signed-off-by: Fran Mulero <fmulero@vmware.com>

* Remove scheduled CD pipelin. Not needed anymore

Signed-off-by: Fran Mulero <fmulero@vmware.com>

* Detect all commits in a push

Signed-off-by: Fran Mulero <fmulero@vmware.com>

* Fix event reference

Signed-off-by: Fran Mulero <fmulero@vmware.com>

* Fix issues with github events

Signed-off-by: Fran Mulero <fmulero@vmware.com>

* Rename actions and outputs with clearer descriptions

Signed-off-by: Fran Mulero <fmulero@vmware.com>

* Fix job dependencies

Signed-off-by: Fran Mulero <fmulero@vmware.com>

* Update .github/workflows/cd-pipeline.yaml

Signed-off-by: Fran Mulero <fmulero@vmware.com>

Co-authored-by: Jose Antonio Carmona <joancafom@icloud.com>

* Update .github/workflows/cd-pipeline.yaml

Signed-off-by: Fran Mulero <fmulero@vmware.com>

Co-authored-by: Jose Antonio Carmona <joancafom@icloud.com>

* Apply suggestions

Signed-off-by: Fran Mulero <fmulero@vmware.com>

Co-authored-by: Jose Antonio Carmona <joancafom@icloud.com>
2022-07-15 17:37:30 +02:00
.github [containers/*] CD pipeline (#20) 2022-07-15 17:37:30 +02:00
.vib [containers/*] Publish workflow (#19) 2022-07-12 18:06:40 +02:00
bitnami 6.0.1-debian-11-r0 release 2022-07-14 03:13:53 +00:00
scripts Get commits in the right order (#21) 2022-07-15 16:43:54 +02:00
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE.md
README.md Update README.md 2022-07-12 22:43:57 +02:00

README.md

CI Scheduled VIB Sync containers repositories

Bitnami Containers

Bitnami is currently working on unifying all container sources repositories into a single location. In the meantime, it will be synchronized in a daily manner to receive all the updates from the other repositories.

NOTE: We use the latest commit to know the missing ones to sync. Do not edit this repository manually or the sync will be broken. If you edit this repo please run the sync workflow manually providing: - how many commits you added into the shift parameter. - the container you affected into the container parameter.

If the latest commit has been done directly in this repository and not all the containers have that commit, the sync will fail because the commit won't be found in upstream and the shift won't be the same for all the containers