Hi Rickard, Thanks for the reply. I've not done any Go and it all looks greek to me, but I guess it's worth a shot. For registering, are you talking about setting the "BuilderId" here: https://github.com/hashicorp/packer/blob/master/builder/file/builder.go#L18 to mitchellh.vmware? And not something like "packer.import"?
Also, maybe I'm just confused, but are you suggesting that Packer should _NOT_ be used as a part of a CI/CD pipeline? If so, is there another tool you can recommend? As I've not found a tool that even compares to Packer... Essentially what we have is one build pipeline that spits out artifacts to an artifact repository. then we have another pipeline that consumes that artifact, validates the image for that environment, then someone has to manually come along and publish that artifact to their "production" environment. At least in my mind, it seems like a lot of wasted compute cycles to have to reprovision the OS every time someone wants to consume the artifact. In other CI pipelines, we have say a C program. Dev checks out code, makes changes, commits it. That commit kicks off a build which compiles the code and publishes it to an internal bintray. From there other dev teams consume the binary from bintray in their jenkins pipelines, and when the change is decided it's acceptable it's pushed to "production". It would be silly if every team had to recompile that code, just to test it with their application. Especially considering compiling C programs can sometimes take hours. >From my perspective, Packer seems like the perfect tool to enable this CI/CD pattern that we're using... in my mind, if I have 10 teams consuming a packer artifact, it's a complete waste of time to force them all to rebuild a base image. Again, if I'm barking up the wrong tree here and Packer isn't supposed to be used as part of CI/CD please set me straight... but we'd really hate to stop using it because Packer really is such a great tool that solves all of our problems save this one minor disconnect. Thanks, Jon A On Tuesday, October 10, 2017 at 11:25:33 PM UTC-5, Rickard von Essen wrote: > > The situation is the same. It's not possible and it steps away a bit from > the purpose of Packer. > > Regarding the null builder it's main purpose is to speed up development of > provisioners and their script, since you can quickly iterate over them > without the need of launching and destroying instances. The purpose of the > file builder is similar but for exercising a post-processor. > > If you want this it's easy to fork the file builder to "import" builder, > which needs to take file list or glob etc of the files to include and also > set the correct builder id (mitchellh.vmware-esx or mitchellh.vmware). > > // Rickard > > > > On 10 October 2017 at 23:03, qubitrenegade <[email protected] > <javascript:>> wrote: > >> Correct link to previous post >> <https://groups.google.com/forum/#!searchin/packer-tool/qubitrenegade%7Csort:relevance/packer-tool/Dz1BSsK6nqI/y49Q8CgrEQAJ> >> >> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/packer-tool/9fdc942a-8ca2-4fb1-9136-94ee30bd4275%40googlegroups.com >> >> <https://groups.google.com/d/msgid/packer-tool/9fdc942a-8ca2-4fb1-9136-94ee30bd4275%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/7ce1a259-14c6-41e9-8c03-ce079e1eb479%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
