On 02-05-2013 12:24, Pete wrote:
We have a similar setup and what we did to generate a new set of jobs
for a new branch was to create another Jenkins job that used the Jenkins
client api to create new jobs and modify the configuration of each job
to change the branch name. You can access the conf
Hi,
We have a project setup where several git branches have the same suite
of jenkins jobs. Each branch has
* --integrate
* --all-tests
* --packages
The "integrate" job is configured to build when a developer pushes a
commit and is used to implement "pre-verified commits". "all-tests" run
a
On 2012-07-05 09:19, Thomas Sondergaard wrote:
Just replying to my own post here :-)
I got to thinking about how the git-plugin detects changes. In my case
the branches that are built are typically new, so if the git-plugin is
checking against what it has built on that branch earlier, that wont
On 2012-07-05 08:54, Thomas Sondergaard wrote:
I have a jenkins job that is not sending emails to the individuals that
broke the build. I've attached the config.xml for the job.
Looking at a particular build (build #65) where jenkins failed to send
emails, I get some conflicting and surpr
I have a jenkins job that is not sending emails to the individuals that
broke the build. I've attached the config.xml for the job.
Looking at a particular build (build #65) where jenkins failed to send
emails, I get some conflicting and surprising information. Jenkins tells
me the job was trig
On 2012-06-13 21:00, Thomas Sondergaard wrote:
The win32 BUILD_URL should be obtainable by replacing arch=linux with
arch=win32 in the linux $BUILD_URL. Next I need to query the status of a
build. How do I do that? Is there a REST url, a la $BUILD_URL/status
that will give me back a status code
I need to build packages of our software on Linux and Windows. On Linux
we build rpms and on Windows we build msi installers. The tricky bit is
that we would like to include the msi-installers in a windows-clients
rpm for distribution purposes.
What we have done previously is to have two compl
On 2012-04-13 09:30, B.Latinville wrote:
Hi
Have a look at this issue :
https://issues.jenkins-ci.org/browse/JENKINS-13007
You should use git.exe instead of git.cmd.
You shall specify full path of git.exe in node option, Tool Locations.
Thanks, I'll give that a try!
Thomas
I have a problem with git checkout failing on Windows. It is a
multi-configuration job with an axies running on different slaves, and
it works on the linux slave. The job is configured to build branches
"origin/for-master/*" and merge to master before building.
I've pasted in the error that I'
On 2012-04-11 21:47, Sami Tikka wrote:
Probably not. AFAIK there is no way to tell git "this branch is now
ready and merged and it will never again receive new commits and it
can be deleted"
It is always possible to checkout an old branch and add new commits to it.
If you are concerned about th
On 2012-04-11 20:48, Thomas Sondergaard wrote:
On 2012-04-11 20:14, Thomas Sondergaard wrote:
2. How do you handle the situation, where there is more than one branch
undergoing development, ie I may have commits that should be merged to a
stable branch and other commits that should be pushed to
:14, Thomas Sondergaard
wrote:
The section "Using Git, Jenkins and pre-build branch merging" in the Jenkins
Git Plugin page describes how we can make jenkins merge changes on a feature
branch to a development branch, run the build and then finally push the
changes to the central reposi
On 2012-04-11 20:14, Thomas Sondergaard wrote:
2. How do you handle the situation, where there is more than one branch
undergoing development, ie I may have commits that should be merged to a
stable branch and other commits that should be pushed to the
master/unstable branch. In both cases I
The section "Using Git, Jenkins and pre-build branch merging" in the
Jenkins Git Plugin page describes how we can make jenkins merge changes
on a feature branch to a development branch, run the build and then
finally push the changes to the central repository.
I'd like to use this, but I have
On 2012-04-07 21:39, Sami Tikka wrote:
There is nothing special in how Jenkins gets the value of the PATH
environment variable: It inherits PATH from its parent process. What
the parent process is and why it sets PATH to the value you see,
depends on how you start Jenkins.
If you have used one o
When I execute a job containing the followin shell script
echo PATH=$PATH
on master and on a slave I get different outcomes.
== Job executed on master: ==
PATH=/sbin:/usr/sbin:/bin:/usr/bin
PATH when logging in with ssh as jenkins user:
/usr/lib64/ccache:/usr/local/bin:/bin:/usr/bin:/usr/sbin
16 matches
Mail list logo
