Bug 902112

Summary:	It is unnecessarily difficult to trigger a rebuild
Product:	OKD	Reporter:	Clayton Coleman <ccoleman>
Component:	Pod	Assignee:	Dan McPherson <dmcphers>
Status:	CLOSED DUPLICATE	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	2.x	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-26 00:18:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Clayton Coleman 2013-01-20 22:40:53 UTC

Occasionally, users may have state on their gear that is out of sync with their repo and their git directory. The only way to trigger the build and deploy hooks is to push a useless change to their Git repository.  Instead, it would be better to either run a node command (via SSH) to rebuild the gear, or to send a command to the broker to rebuild that gear.  Essentially, the "make the gear match what the repo+hooks should be in".

Concrete use case:

1) Build script downloads code and unpacks it to be used by the cartridge
2) User wants to clear the current state
3) User has to SSH in, delete the directory, then make a Git change, push it back up to the server.

In this scenario the user's Git history becomes filled with useless commits "do something / do that" etc.  Allowing the user to run:

   rebuild.sh

from the gear, or calling

   rhc rebuild <gearid>

from the RHC command, or by hitting a UI action which says "rebuild gear" would limit this scenario.

In general, this action is similar to establishing a new gear.

Comment 1 Dan McPherson 2013-01-21 03:20:13 UTC

Sounds like a user story.

Comment 2 Dan McPherson 2013-01-26 00:18:01 UTC


*** This bug has been marked as a duplicate of bug 867965 ***