Publish artifacts/packages/softwares installed as part of bake using packer

[Rajendra Kumar]

Hi All,

I am looking for below solutions

1. Dry run mode: How can I publish the list of softwares, packages, artifacts going into the bake without baking an ami ?

It can rpm packages, yum packages, installed via wget, python modules , kernel and os upgardes etc etc ..

2. Does Packer provide any out of the box solution for this?

3. is there any other 3rd party software apart from packer which provides this solution ?

Thanks!

Raj

[Alvaro Miranda Aguilera]

Hello

It seems you want to check the CD Continous delivery part of your CI/CD story on those packages.

If you have an app, and you do development, at some point you will cut a release.

That release can be created into a package tested (from the package) and then store on a asset storage.

That is not the main aim of packer, that best done with other tools.

If you use GitHub for software you can use the release part to create a version release, then your CI can package the app and upload to the release part.

Once that part of the problem is solved, your packer project can consume versioning packaged assetts.

Alvaro.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/25100a76-016c-4a47-bc00-d416924036df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro