Michael DeHaan
Michael DeHaan
It's easy to type in a repo URL for a project but leave the repo type set to None. If we try to build a project with a repo URL...
If the sudo user is left blank, confusing error messages can result, that would be more clear if we didn't allow it to be blank. I am proposing the sudo_user...
When a build fails due to a problem with the build script (or sudo, whatever), we get an exception like this: 2019-01-08 15:03:56,751 - vespene - ERROR - an error...
https://talk.msphere.io/t/unsure-how-to-use-output-variables/114/2
Certain types of objects - projects in particular, would be great if they had a copy button. This button can copy all fields but should present a dialog to enter...
Per forum discussion, a .vespene file should be able to define more than one project: --- name: "Tommys Project" script: "scripts/example.sh" timeout: 60 repo_branch: master variables: testvar: "hello!" luggage_code: "5150"...
In the security guide we should talk about putting the vespene_build user in the same group as the vespene user, and then we can expose "permissions_hex" on the worker pool...
For easier sudo configuration with the sudo isolation plugin, we really want the vespene user to be in sudoers. This is not something that the setup automation currently sets up....
On each page, just as build details, it would be nice to be able to stop the build without going back to the build list. To do this, we should...
In particular, there are some things to document here at least: https://talk.msphere.io/t/setup-questions/21/34