Request: eval context to help DRY up jobs #90
Comments
Are you able to try out the feature? Use the test docker image |
I'll try this out today. Currently trying to figure out why my mbp is stuck in a reboot loop with security update 10.12.6 o.O |
I'm not sure what I'm doing wrong: I changed:
to
This results in And if I force a re-trigger of the pipeline it fails after pulling the image:
I tried switching the repository to
|
And the extra-size is because it has test dependencies, don't worry about that for the final image. |
Thanks, that worked! Sorry about that >_< Yeah, this is the desired result! |
Great! I'll release an official release tonight. |
Done, pushed it to latest. |
Awesome, thank you!
…On Mon, Aug 21, 2017 at 10:56 PM JT Archie ***@***.***> wrote:
Done, pushed it to latest.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#90 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAf3OFi99XX1dD6fA1D4GhoefAqQ8fOnks5salFxgaJpZM4Owzgc>
.
|
Could you please evaluate the
context
parameter like here: https://github.com/cloudfoundry-community/slack-notification-resource/blob/c1686fb4b6ed41a4a28d6de497889e5fae7e2cfd/out#L99This will help D.R.Y. up job definitions where there are several build contexts and statuses used.
The text was updated successfully, but these errors were encountered: