samson
                                
                                
                                
                                    samson copied to clipboard
                            
                            
                            
                        Web interface for deployments, with plugin architecture and kubernetes support
Tags and commit hashes should be stable but branch tips are not. At the moment we only bust for `master` thanks to https://github.com/zendesk/samson/pull/511.
Is it possible to make this constant `Changeset::PullRequest::JIRA_ISSUE` configurable by env var?
We should have a small utility script that allows us to easily see information about running jobs, eg: - what jobs are running - for how long - pid It...
We don't currently have GitHub configured, so we're getting an exception on [`GITHUB.compare(repo, previous_commit, commit) `](https://github.com/zendesk/samson/blob/master/app/models/changeset.rb#L15) being called.
Restrict users rights by stages and projects
Currently "Commits" tab on deploy page shows all commits. There is no way to see if there are commits that aren't part of a PR (eg. commits directly to master)....
very hard to see where output is coming from at, ideally foldable commands like travis does (fold output under the command it came from)
Samson waits until the deploy job is finished running before it persists the log. If the job is killed for some reason, then the deploy log is left empty, regardless...
We ran into a scenario today where we stood up a fresh Samson instance, created a new project for a github repo, checked `Update Pull Request after deployment`, and ran...
As an admin, if I stop a deploy started by someone else. Samson says that the original deploy stopped the deploy (on the deploy page). It doesn't say anywhere who...