Open sukrit007 opened 8 years ago
@mmoulton @kennedyj @kennedyj @ctrimble @dtackett @jacobheun Thoughts ? Please update the issue.
Being able to rebuild from the image factory is good. It would be nice to have this button in the context of the service as well.
If the intent is to rebuild the image I think this would work well, I'd be curious to know what the circumstances are for rebuilding the same commit.
Most of the scenarios I've needed to re-trigger a hook for wasn't to build, but was instead to deploy the built image, this is overkill for that and we should use the orchestrator hook for triggering a re-deploy.
@kennedyj I hit this problem when a bug is discovered in a dependency. Since we do not have a good way to propagate dependency changes, this is a manual process.
In my use case, I usually just want to rebuild the last commit on a branch. It would be nice to have a button just for that, in the context of the deployed branch.
Thinking about it more, I think having the button with the app is more appropriate since the image factory jobs aren't persisted.
A new button in this group of tools would be sweet.
I like the button in app group. Something like :
My use cases:
The update option can give you 2 options:
I think the options are good and adding it to the button group sounds good.
Here's a link to the material icon for update, we can use any of the material icons easily though, https://design.google.com/icons/#ic_update
As a developer, I need ability to re-trigger image-factory build without having a need to go to github to trigger the hooks so that developers with non-admin privileges to repository can re-trigger the image-factory build for existing commit sha.
UPDATE Based on discussions with Josh, Christian we should: