Sam Gleske
Sam Gleske
https://github.com/samrocketman/gitlab-mirrors/blob/master/docs/upgrade/upgrade_0.3.x-0.4.x.md Contains being certified for `pyapi-gitlab` but it was actually certified to use `python-gitlab3`. Documentation should be updated.
@axilleas I have a question for you. I'd like to contribute best practice documentation which can be used in RHEL. https://github.com/gitlabhq/gitlab-recipes/tree/master/install/centos There is already CentOS documentation but my idea of...
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/slaves/NodeProvisioner.java#L792 set to zero
I'd much rather use [my own .gitignore](https://github.com/github/gitignore/pull/1763) rather than the includes defined in this plugin. Credentials should be included because they're encrypted and protected by the `secret.key` file. Additionally, the...
When running a basic shell a user might want the full environment provided by `.jervis.yml`. By using the `jervisSh` pipeline step, a user can call a shell script but have...
When a toolchain value contains the word `true` or `false`, then it is misinterpreted as a boolean and a toolchain validation error occurs. Admins should have the flexibility to name...
[Jervis API](https://sam.gleske.net/jervis-api/) already has thorough documentation. This documentation is for Jenkins administrators to provide to their end users who would be using Jenkins with Jervis deployed within a company. Depending...
JSON has been great... but YAML is more flexible and user-friendly than JSON for admins to add support. JSON will always be supported for compatibility. However, it would be nice...
Often, a user will override language lifecycles. This is usually done when they want to do everything in a user-provided Jenkinsfile and not rely on the default Jervis-provided build lifecycle...
# Tasks - [x] Planning - [ ] Implementation (`PipelineGenerator` interface should remain mostly the same with a rewrite for `MultiPlatformGenerator`) - [ ] API Documentation - [ ] Refactor...