Hello all,
I ultimately figured out a way.. Infact, I change the approach from having
multiple projects and kept it to a single project at Jenkins level.
I declared few params in project as BUILD_BRANCH and PUSH_BRANCH.
Next, I setup a cron job which passes these params in a CURL based query
I am thinking of trying an unconventional way. I can put current build # in
a file. Read that file on next build # and +1 it. All the projects can use
this file for their build # and this approach wont need any manual
intervention to supply build # as parameter.
Not sure but worth a try as I feel.
Perhaps you could:
1. setup separate build for each branch, each job has a parameter to
specify the build number
2. setup master job that has parameter to specify which branch to build.
This job will have a build number that increments. This job starts the
desired branch build passing the curre
Hello Michael,
I really appreciate that you found time to answer my query.
But, my requirement is to have separate projects in jenkins. I run various
integration tests after building binary. Idea is to do the same for all new
branches. I have setup cron to run these builds.
If I keep it para
If you want to share a single build number over all branch builds, you will
want to configure your job to accept a branch name to be built. Then run
as a parameterized build and specify the branch to build. This will give
you build numbers like this:
master: 1
master: 2
branch-a: 3
branch-b:
Hi,
Thanks for the reply. I went through those links. I believe my requirement
is a bit different from those.
I would need a universal sequence/build number which can be used by
multiple projects in Jenkins.
Regards
AB
On Friday, February 26, 2016 at 8:34:14 PM UTC+5:30, Victor Martinez wr
Hi,
You don't need to use Capital Cases at all, lower cases are in good shape
and easy to read.
Coming back to your questions:
- https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin
might help you to set those numbers based on token/attributes
- https://wiki.jenkins-ci.org/
Hi Group!
I have a requirement where I have 2-3 branches from a common master (say
A-dev, B-dev2.0, C-Qa) and I want to run Jenkins for each branch and check
stability of my code and binaries.
Currently I run Jenkins Project for 'master' branch only and with each
build I get a iterative next
