I'm using the latest version of Jenkins and related Pipeline plugins, and
our system has gotten into a stuck state.
A key branch is now in a "disabled" state for an unknown reason. The the
multi-pipeline is driven by a Jenkinsfile which hasn't changed in several
months.
Now that the the last
Currently I've got an input() call in my Jenkinsfile that prompts users to
select a branch name to manually deploy:
userInput = input(
id: 'userInput', message: 'Manual Deploy?', parameters: [
[$class: 'ChoiceParameterDefinition', choices:
'develop\nmaster\nPR-124', description: 'Branc
omoted, etc.
Some questions:
* Should the logging I see in the source code *always* be happening or
there something I need to do activate that logging?
* Should properties() call work outside a node block?
* Are there any serious drawbacks to just manually deleting old build
myself? Thi
buildDiscarder(logRotator(numToKeepStr: '20'))
> }
> ...
> }
>
> Or with scripted Pipeline:
> https://github.com/jenkinsci/jenkins/blob/master/Jenkinsfile#L17-L19
>
> HTH
>
> 2017-02-28 20:24 GMT+01:00 Mark Stosberg >:
>
>> For clean
For cleaning up old builds, the "Discard Old Builds" plugin is recommended:
https://wiki.jenkins-ci.org/display/JENKINS/Discard+Old+Build+plugin
However, the instructions for reference a "post build" step which doesn't
exist in the Configure interface for Multibranch Pipeline projects.
What's
