I have started to use the "Publish Over CIFS Plugin" because I have tried
to move some of our build machines to Amazon EC2.
I formerly just did a file copy to our Windows server file share from the
Windows slaves because they were running as users with the correct
permissions.
Anyway, in
Ah yes, I didn't catch that distinction in OP's scenario.
On Thursday, May 9, 2013 10:50:03 AM UTC-5, Mandeville, Rob wrote:
>
> Foxgang: I think you still need to create the properties file because
> you are calculating the value within a build step. Even if you set an
> environment variable
On Thursday, May 9, 2013 1:02:58 PM UTC-7, Mandeville, Rob wrote:
>
> I believe that the behavior you are seeing is by design. The concurrent
> builds checkbox allows you to run multiple instances of that job at all,
> but the SCM poller will only launch one at a time. Basically, with the
> ch
Chris Marks wrote:
>
> I haven't used Jenkins in a large Git environment, but perhaps those
> who have problems with the performance could file bugs related to
> their experiences in specific situations if they haven't already? It
> would benefit the community to have a bullet-proof Git plugin tha
William Soula wrote:
> Look into the github trigger where pushes to a repo causes the webhook to hit
> the url for the job and it will check for changes and build. Thus no polling
> is involved.
>
> http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/
>
Unfor
Look into the github trigger where pushes to a repo causes the webhook to hit
the url for the job and it will check for changes and build. Thus no polling
is involved.
http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/
I'd like to suggest the Jenkins Job
Les Mikesell wrote:
> On Fri, May 10, 2013 at 12:38 PM, JonathanRRogers
> wrote:
>> Jenkins' git plugin performs poorly with hundreds of branches in a single
>> repository. I haven't tried it with hundreds of repositories, but I wouldn't
>> be surprised if that also performed poorly. I now avoid t
On Fri, May 10, 2013 at 12:38 PM, JonathanRRogers
wrote:
>
> Jenkins' git plugin performs poorly with hundreds of branches in a single
> repository. I haven't tried it with hundreds of repositories, but I wouldn't
> be surprised if that also performed poorly. I now avoid the git plugin
> entirely
You may also want to look into the Jenkins job dsl plugin (
https://github.com/jenkinsci/job-dsl-plugin/) for providing an easier way
to create and manage jobs in Jenkins.
I haven't used Jenkins in a large Git environment, but perhaps those who
have problems with the performance could file bugs re
I'm not using post commit hooks... But those would probably work well for
your situation. For us we don't build on every commit currently. But if you
take a look at the remote api you can probably make it work that way pretty
easily.
You can use cURL to trigger it here's one of our urls to trigger
On Fri, May 10, 2013 at 10:44 AM, Benjamin Lau wrote:
> I also use git commands directly. If you make it so your build is
> identical for all of your repositories you could have a single
> parameterized job which has parameters for the repo and branch (unless
> everything is always in master).
>
I also use git commands directly. If you make it so your build is identical
for all of your repositories you could have a single parameterized job
which has parameters for the repo and branch (unless everything is always
in master).
To make this easier to work with I also wrote some shell scripts
On Friday, May 10, 2013 1:23:41 PM UTC-4, Jon Drukman wrote:
>
> I am looking into using Jenkins as a tool for continuous deployment. A
> commit to a git repository triggers building of rpms, updating a yum repo,
> possibly triggering production machines to do a yum update, etc. I've set
> up
I am looking into using Jenkins as a tool for continuous deployment. A
commit to a git repository triggers building of rpms, updating a yum repo,
possibly triggering production machines to do a yum update, etc. I've set
up a test project, and Jenkins seems like it provides a lot of useful
fun
I have a project in Jenkins that is triggered by an svn poll. I'd like the
job to grab a list of files that were committed using svn and pass them to
a c# program being run from an exe.
Any ideas on how i could do this?
--
You received this message because you are subscribed to the Google Gro
Hello,
I am trying to use the Monitoring plugin to get information about the JVM
of an app that runs on remote slave machines. This plugin does give me
detailed information about a JVM on the slave machine, but not the one I
care about. Do you know how I can specify which JVM or process id on
What's the output on the command line? The way JJB works is it will take a
hash of the configuration and unless that changes it won't rerun the job. So
if you ran it once and it failed, unless you change the configuration it will
not retry to create the job.
Will
I found a reply by @stussy saying he was using the beta of the Planned
Parenthood plugin. Does anyone know where to get that plugin?
http://jenkins.361315.n4.nabble.com/Job-Inheritance-td4653700.html
http://www.cloudbees.com/jenkins-user-conference-2012-san-francisco.cb
--
You received this m
Hi,
Does anyone know if there is a solution to load a list of subfolders from a
remote directory exposed via Apache HTTP server in Jenkins?
I am thinking of having a "Releases" location that will store multiple
subfolders ( something like: Relaease 05.05.2013, Release 05.12.2013) Each
subfolde
I have noticed that from time-to-time that certain Jenkins jobs disappear from
the dashboard although the data still exists in the .jenkins filesystem. If I
restart tomcat my jobs will be re-displayed on the dashboard. I noticed that
bug
https://issues.jenkins-ci.org/browse/JENKINS-15156
sa
That's indeed a big drawback in my approach because some of my tests
uses system global semaphores.
So I have to rethink my approach :-(
Thanks for your hint.
Felix
On 2013-05-08 22:15, Dean Yu wrote:
When I was working at Yahoo!, and we started working with
Hudson/Jenkins, we originally went
Hi
We are running Jenkins LTS release 1.480.3 and are using SVN Plugin v.1.39.
This means that the Jenkins workspaces are in svn 1.6 format.
I want to upgrade to SVN Plugin v1.45, which create workspaces in svn 1.7
format.
Normally in Subversion, the user is prompted to perform 'svn upgrade'
22 matches
Mail list logo
