Multi-pipeline branch unexpected disabled-- how to enable?
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 build status for the branch is "disabled", the Github webhook no longer triggers build, and I see no place in the UI to declare the branch "enabled" again. I've tried restarting Jenkins and rescanning the repo. Suggestions for surgical fixes as well as large hammers are welcome. Thanks, Mark -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/35063de6-cdc1-4bef-8eb7-ab6a4543a163%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
How to dynamically get list of branches or pull requests in Jenkinsfile/groovy?
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: 'Branch to deploy', name: 'branch', defaultValue: 'develop'], ]) Instead of hardcoding a list branch names, how can I dynamically build this list based on the list of the pull requests that are already known to Jenkins in our multlbranch pipeline configuration? Jenkins is configured to automatically build new pull requests already. Thanks, Mark -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a0c15c4e-805c-4a41-bdf6-9cf42014b23e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Recommending for cleaning up old builds when multibranch pipeline is in use?
Thanks for reply, and for providing both the Pipeline syntax formats. This
is the first time I noticed that there are two distinct Pipeline syntaxes.
I'm trying out the Scripted Pipeline syntax now.
I tried to find documentation on the difference between 'numToKeepStr' and
'artifactNumToKeepStr' but couldn't. I set them both the same number in
hopes that will have the desired effect of saving a particular number of
builds.
Mark
On Wednesday, March 1, 2017 at 4:08:53 AM UTC-5, Baptiste Mathus wrote:
>
> I don't think there's something per branch, but you probably want to
> either search JIRA and/or file a new feature request about it.
>
> You shouldn't need a special plugin, this is a standard feature. Here's
> the way to do it with Declarative Pipeline:
>
> pipeline {
> options {
> 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 <ma...@rideamigos.com
> >:
>
>> 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 the recommended way to clean-up builds from multi-branch pipeline
>> projects? Ideally I'd like different pruning policies for different
>> branches.
>>
>> Thanks,
>>
>> Mark
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/1d9e0343-bbce-474f-a4fe-7623a4f39aaf%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/jenkinsci-users/1d9e0343-bbce-474f-a4fe-7623a4f39aaf%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/ec6ee4ea-0deb-45f4-ba64-b5ad4f33ff8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Recommending for cleaning up old builds when multibranch pipeline is in use?
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 the recommended way to clean-up builds from multi-branch pipeline projects? Ideally I'd like different pruning policies for different branches. Thanks, Mark -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1d9e0343-bbce-474f-a4fe-7623a4f39aaf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
