Conversation
b97fb42 to
ef20c27
Compare
ef20c27 to
57846a0
Compare
|
This could be extended easily enough to solve for #10 and #5. This changes the source of truth to be the Codebuild project. instead of the plugin This also allows us to start using native images out of Codebuild. We could conceivably add jenkins agent download/setup code in prebuild so we could use out of the box images from AWS. I would like to see the plugin move in this direction. |
|
Do I understand correctly that this change will require the user to provide the buildspec.yml? IMHO this should be optional, if one is bundled then use that one otherwise the plugin will provide one. |
As currently written, yes. The buildspec would be sourced from the Codebuild project instead of coming from Jenkins. I agree the change should be made in a backward compatible way. |
@alexisde - Forked and created new plugin instead - https://github.com/jenkinsci/codebuild-cloud-plugin |
Allow for the possibility of a freestyle custom buildspec.
This would allow the user to create a project with his/her own
buildspec.yamlfile which would therefore allow for more freedom and flexibility in their builds, but at the same time be compatible with the codebuilder agent to build the project via jnlp.For example, the user might have the following
buildspec.yamlfile:And what this PR does is simply replace the keywords
{{CODEBUILD_JENKINS_URL}}{{CODEBUILD_COMPUTER_JNLP_MAC}}and{{CODEBUILD_NODE_DISPLAY_NAME}}with an override with the runtime values for the Codebuild jenkins URL, Computer JNLP MAC and Node's display name.I got inspiration for this change when i needed to mount an NFS drive to cache maven dependencies and also be able to use Codebuild's own cache dir. More information on this use-case can be found here.