As a DevOps I spend a lot of time in Jenkins, automating stuff. Often pipelines will misbehave and I need ways of debugging things: Println Obviously the easiest way of getting information out of the running pipeline. Simulating a “breakpoint” Adding a somewhere in the pipeline pauses execution at that point which lets me check… Continue Reading debugging jenkinsfiles
Check Jenkins’ own documentation for an unnecessarily complicated but at least almost complete overview of available input declarations: https://jenkins.io/doc/pipeline/steps/pipeline-input-step/ Get a list of available types here: https://github.com/jenkinsci/extended-choice-parameter-plugin/blob/master/src/main/java/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition.java#L90 Get a list of all parameters of the ExtendedChoiceParamterDefinition here: https://github.com/jenkinsci/extended-choice-parameter-plugin/blob/master/src/main/java/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition.java#L344 This SO was useful to get an idea of how to use it in pipelines and resulted… Continue Reading use jenkin’s ExtendedChoiceParameterDefinition for multi-select user input
This is just a quick repost of RUN A SHELL FROM JENKINS USING SUDO (UBUNTU) Disclaimer: This is UNSAFE and you should NEVER do it unless in a protected, shielded and non-public-accessible dev environment. This is not even safe enough for a permanent testing environment.