infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joan Touzet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-13754) Add Build Name Setter plugin to ASF Jenkins
Date Mon, 27 Mar 2017 06:07:42 GMT

    [ https://issues.apache.org/jira/browse/INFRA-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15942697#comment-15942697
] 

Joan Touzet commented on INFRA-13754:
-------------------------------------

Hm. I don't want to trigger builds on all branches from a single commit, though. I want commits
on any given branch to trigger builds only on that branch. Am I misunderstanding?

If it's this plugin: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Plugin

then I'm wondering if it includes the ability to limit exactly which branches get built. We
don't want to build every single branch with this. I'd want to specify a regex of branches
that we do build.

> Add Build Name Setter plugin to ASF Jenkins
> -------------------------------------------
>
>                 Key: INFRA-13754
>                 URL: https://issues.apache.org/jira/browse/INFRA-13754
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>            Reporter: Joan Touzet
>
> CouchDB would like to request the Build Name Setter plugin to be added to Jenkins.
> We have a number of release branches in our repository, for example: 1.6.x, 1.7.x, 2.0.x,
2.1.x, 3.0.x as well as master. The release branches are used only for critical bugfixes and
for staging our releases.
> We'd like to turn on Jenkins to build these branches, but in doing so  it becomes very
difficult to understand the build status page. There is no information displayed as to which
run was on which branch.
> https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin would allow us to
name each build with the branch and/or git commit hash that represents the build that was
just built. This would ease our attempts to create a build status page.
> Would you please install this plugin for us?
> There is a workaround I can think of if you say no - we can just clone the build job
and create n jobs for n branches we wish to support. This does make Jenkins configuration
more of a hassle, though; any change made to one job will have to be manually copied to all
of the other jobs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message