Re: AWS ECS Plugin

[Brandon Wagner]

I would like to run Docker containers for all of my software projects and
dynamically allocate build slaves via ECS (so that I can have a core
cluster that can do builds quickly; in contrast to spinning up an EC2
instance).

 For example, I have a Java application which is completely contained in a
Docker container (I can build it, run tests, and run the actual application
with Tomcat all within the container). I want to use this for a variety of
different purposes (dev, testing, qa, and production). In order to make it
reusable like that, I don't want to include Jenkins Slave packages and
expose ports. I'd rather deploy out a Jenkins-Slave container to my ECS
cluster, and then have that slave handle running my application's docker
container which also performs tests.

I also support other team applications which are already running docker
container builds in Jenkins (locally on the Jenkins Master). I want it to
be transparent to them that I'm "outsourcing" build slaves to ECS. It
shouldn't matter to them that I'm changing the way Jenkins is performing
builds.

Let me know if you (or anyone else) have suggestions based on my goals.

-Brandon Wagner


On Fri, Jan 22, 2016 at 2:48 PM, nicolas de loof 
wrote:

> privileged flag has been added to development build (
> https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/)
> anyway, DinD is probably not a good idea (there's really few docker usages
> to actually require it). What's your actual need ?
>
> 2016-01-22 20:46 GMT+01:00 Brandon Wagner :
>
>> So I ended up figuring my issue out. I think there were a couple of
>> issues. My JNLP port was set to 50,000 instead of 5,000 which the Jenkins
>> Docker Container I was using was mapping to the host port 5000. And my Load
>> Balancer in front of Jenkins was not forwarding port 5000 to the host (only
>> 443). Anyways, all of that is fixed and I can now run builds on slaves in
>> ECS.
>>
>> My next problem: I want to use docker-in-docker to run docker builds on
>> my docker jenkins slaves. I'm trying to use
>> https://github.com/tehranian/dind-jenkins-slave which looks good, but I
>> don't see an option on the Jenkins ECS plugin to run the slave as
>> privileged which is necessary for docker-in-docker.
>>
>>
>> -Brandon Wagner
>>
>> On Fri, Jan 22, 2016 at 7:11 AM, nicolas de loof <
>> nicolas.del...@gmail.com> wrote:
>>
>>> First look into jenkins logs.
>>> Also check on ECS a task definition has been created for jenkins-slaves.
>>> Also double check ECS nodes can ping your jenkins master URL.
>>>
>>> 2016-01-21 22:13 GMT+01:00 Brandon Wagner :
>>>
 I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin to
 deploy Jenkins Slave Containers for builds. I have an ECS cluster setup,
 and I have it configured in my Jenkins Configuration. Everything appears to
 be good until I try to build a job, restricting to the ecs cloud label I
 setup, and it just comes back with "(pending—
 Jenkins-Container-Cloud-456...164
 is
 offline)" .

 Does anyone know how to fix this, or have suggestions on debugging
 steps?

 --
 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/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Jenkins Users" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/jenkinsci-users/kSBWy3gBQbg/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, 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/CANMVJzks3yceTvUxrFd5cGo8tYwSFh%3D00V%3DzL%2BxJVB2kCmi%3DhQ%40mail.gmail.com
>>> 
>>> .
>>>
>>> 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
>> 

Re: AWS ECS Plugin

[Brandon Wagner]

So I ended up figuring my issue out. I think there were a couple of issues.
My JNLP port was set to 50,000 instead of 5,000 which the Jenkins Docker
Container I was using was mapping to the host port 5000. And my Load
Balancer in front of Jenkins was not forwarding port 5000 to the host (only
443). Anyways, all of that is fixed and I can now run builds on slaves in
ECS.

My next problem: I want to use docker-in-docker to run docker builds on my
docker jenkins slaves. I'm trying to use
https://github.com/tehranian/dind-jenkins-slave which looks good, but I
don't see an option on the Jenkins ECS plugin to run the slave as
privileged which is necessary for docker-in-docker.


-Brandon Wagner

On Fri, Jan 22, 2016 at 7:11 AM, nicolas de loof 
wrote:

> First look into jenkins logs.
> Also check on ECS a task definition has been created for jenkins-slaves.
> Also double check ECS nodes can ping your jenkins master URL.
>
> 2016-01-21 22:13 GMT+01:00 Brandon Wagner :
>
>> I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin to
>> deploy Jenkins Slave Containers for builds. I have an ECS cluster setup,
>> and I have it configured in my Jenkins Configuration. Everything appears to
>> be good until I try to build a job, restricting to the ecs cloud label I
>> setup, and it just comes back with "(pending—
>> Jenkins-Container-Cloud-456...164
>> is
>> offline)" .
>>
>> Does anyone know how to fix this, or have suggestions on debugging steps?
>>
>> --
>> 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/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/kSBWy3gBQbg/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CANMVJzks3yceTvUxrFd5cGo8tYwSFh%3D00V%3DzL%2BxJVB2kCmi%3DhQ%40mail.gmail.com
> 
> .
>
> 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/CAKgdMg-%2Bs99MCNpwJz99QBs0NTke7EV2Tt%3DWPEj5NZBzjkJaHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AWS ECS Plugin

[nicolas de loof]

privileged flag has been added to development build (
https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/)
anyway, DinD is probably not a good idea (there's really few docker usages
to actually require it). What's your actual need ?

2016-01-22 20:46 GMT+01:00 Brandon Wagner :

> So I ended up figuring my issue out. I think there were a couple of
> issues. My JNLP port was set to 50,000 instead of 5,000 which the Jenkins
> Docker Container I was using was mapping to the host port 5000. And my Load
> Balancer in front of Jenkins was not forwarding port 5000 to the host (only
> 443). Anyways, all of that is fixed and I can now run builds on slaves in
> ECS.
>
> My next problem: I want to use docker-in-docker to run docker builds on my
> docker jenkins slaves. I'm trying to use
> https://github.com/tehranian/dind-jenkins-slave which looks good, but I
> don't see an option on the Jenkins ECS plugin to run the slave as
> privileged which is necessary for docker-in-docker.
>
>
> -Brandon Wagner
>
> On Fri, Jan 22, 2016 at 7:11 AM, nicolas de loof  > wrote:
>
>> First look into jenkins logs.
>> Also check on ECS a task definition has been created for jenkins-slaves.
>> Also double check ECS nodes can ping your jenkins master URL.
>>
>> 2016-01-21 22:13 GMT+01:00 Brandon Wagner :
>>
>>> I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin to
>>> deploy Jenkins Slave Containers for builds. I have an ECS cluster setup,
>>> and I have it configured in my Jenkins Configuration. Everything appears to
>>> be good until I try to build a job, restricting to the ecs cloud label I
>>> setup, and it just comes back with "(pending—
>>> Jenkins-Container-Cloud-456...164
>>> is
>>> offline)" .
>>>
>>> Does anyone know how to fix this, or have suggestions on debugging
>>> steps?
>>>
>>> --
>>> 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/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-users/kSBWy3gBQbg/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, 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/CANMVJzks3yceTvUxrFd5cGo8tYwSFh%3D00V%3DzL%2BxJVB2kCmi%3DhQ%40mail.gmail.com
>> 
>> .
>>
>> 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/CAKgdMg-%2Bs99MCNpwJz99QBs0NTke7EV2Tt%3DWPEj5NZBzjkJaHg%40mail.gmail.com
> 
> .
>
> 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/CANMVJzmdKoB9PZfYNcA6tGMyC2pT5Mg13LP9UMMW%2Bt3FAC1qTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Flow DSL: non-blocking build trigger

[Barry Laffoy]

Is it possible to trigger a build of a job from a Build Flow job whose 
execution does not block the execution of the calling job?

If that's not clear, say I have three Jenkins jobs: flow-job, short-job, 
long-job. "flow-job" is used to trigger a build of both "short-job" and 
"long-job". However, as implied by their names, one job normally takes much 
longer than the other. Using the build() function in the build flow DSL, 
flow-job won't exit until both short-job and long-job have completed. 
However, I would like for both the short and long job to be triggered by 
the flow DSL, but for flow-job to only wait for short-job to complete: 
long-job should be allowed continue operation after flow-job has completed.

Is there any functionality in the flow DSL that would allow this? I've put 
together a system by which groovy will execute a curl command to trigger 
the long running job:

def vars = "FOO=BAR=QUX";
def trigger_url = 
"http://localhost:8080/job/long-job/buildWithParameters?${vars};;
def cmd = "curl -o trigger.log ${trigger_url}";
out.println(cmd);
def proc = cmd.execute();
proc.waitFor();

and trigger the short running job normally with build("short-job").

This feels a bit messy to me. Is there any native way within the DSL to 
achieve this?

-- 
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/571e33fe-d41d-4e59-8dc1-4c7e15b915e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build not triggered when change is pushed to bitbucket

[Rohit Sharma]

Hello Slide,

I configured the free style job in jenkins and checked the git option under 
SCM. And under Build Triggers i selected the option which states "Build 
when a change is pushed to BitBucket" there after i taking shell login to 
remote server using Publish Over SSH plugin to pull the latest code from 
bitbucket. Another thing which i did to make it work is added a webhook in 
bitbucket to send push notificaion to jenkins.

Now to test i did test commit on repository and got 500 error when checked 
the logs of push events generated at bitbucket console. 

And to resolve this i tried all the solutions provided at :
https://blog.bitbucket.org/2015/06/24/the-new-bitbucket-webhooks/
http://stackoverflow.com/questions/32430427/bitbucket-webhook-keep-returning-error-500
http://stackoverflow.com/questions/30995662/bitbucket-new-webhook-not-working
https://answers.atlassian.com/questions/18448498/webhook-always-returning-500-error

Apart from this I also whitelisted all the IP's provided at bitbucket on 
server where jenkins was setup. IN order to make jenkins work but still no 
success.

Thanks
Rohit

On Thursday, 21 January 2016 21:37:46 UTC+5:30, slide wrote:
>
> Perhaps it would help if you gave some more information about your 
> configuration, things you have tried, exact error messages, etc. Your 
> request is somewhat lacking in that regard.
>
> On Thu, Jan 21, 2016, 08:44 Rohit Sharma  > wrote:
>
>> Hello Everyone,
>>
>> I am using the jenkins version 1.625.3. And i am facing issues in 
>> integrating jenkins with bitbucket. What all i need to do is to trigger a 
>> job when a change is pushed to bitbucket. But unfortunately its not working 
>> and I am continuously getting the 500 error response code on webhook 
>> configured on bitbucket.
>> Please help me out in this.
>>
>> Thanks
>> Rohit
>>
>> -- 
>> 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/9f9a6a3d-c504-45c4-8239-79d129ee3e6a%40googlegroups.com
>>  
>> 
>> .
>> 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/714916d0-d458-4b7e-bf0a-bac90fd847c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Feed for changelog

[Daniel Beck]

On 22.01.2016, at 10:14, Johannes Wienke  
wrote:

> is there an RSS feed available with the Changelog (for the LTS version)?
> On the Changelog page there is a feed icon but that is just the feed for
> the blog.
> 
> https://jenkins-ci.org/changelog-stable/

No, there is not.

You could subscribe to our Google calendar, which contains the LTS RC and 
release dates:
https://jenkins-ci.org/content/event-calendar/

-- 
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/E95BD666-32B5-4DA2-8488-D204C20E62B1%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Feed for changelog

[Johannes Wienke]

Hi,

is there an RSS feed available with the Changelog (for the LTS version)?
On the Changelog page there is a feed icon but that is just the feed for
the blog.

https://jenkins-ci.org/changelog-stable/

Cheers,
Johannes
-- 
Johannes Wienke, Researcher at CoR-Lab / CITEC, Bielefeld University
Address: Inspiration 1, D-33619 Bielefeld, Germany (Room 1.307)
Phone: +49 521 106-67277

-- 
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/20160122091419.GL11564%40techfak.uni-bielefeld.de.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

conditional builds within promote plugin

[jhavero]

I have the promoted builds plugin. From within it, I would 

  - trigger/call jobA
  - if jobA success then trigger/call jobB
  - else trigger/call jobC

Does anyone know how I can do this?

-- 
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/3220fb12-b800-4d72-8e9e-749d9a6b510d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Feed for changelog

[Johannes Wienke]

Hi,

On 2016-01-22 11:41:07, Daniel Beck wrote:
> On 22.01.2016, at 10:14, Johannes Wienke  
> wrote:
> > is there an RSS feed available with the Changelog (for the LTS version)?
> > On the Changelog page there is a feed icon but that is just the feed for
> > the blog.
> > 
> > https://jenkins-ci.org/changelog-stable/
> 
> No, there is not.
> 
> You could subscribe to our Google calendar, which contains the LTS RC and 
> release dates:
> https://jenkins-ci.org/content/event-calendar/

Thanks. However, I'd be more interested in what actually changed than
the dates. And not having to navigate to the webpage from my news reader
would be much more convenient. Any chance to set up such a feed?

Cheers,
Johannes
-- 
Johannes Wienke, Researcher at CoR-Lab / CITEC, Bielefeld University
Address: Inspiration 1, D-33619 Bielefeld, Germany (Room 1.307)
Phone: +49 521 106-67277

-- 
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/20160122113659.GM11564%40techfak.uni-bielefeld.de.
For more options, visit https://groups.google.com/d/optout.

Re: AWS ECS Plugin

[nicolas de loof]

First look into jenkins logs.
Also check on ECS a task definition has been created for jenkins-slaves.
Also double check ECS nodes can ping your jenkins master URL.

2016-01-21 22:13 GMT+01:00 Brandon Wagner :

> I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin to
> deploy Jenkins Slave Containers for builds. I have an ECS cluster setup,
> and I have it configured in my Jenkins Configuration. Everything appears to
> be good until I try to build a job, restricting to the ecs cloud label I
> setup, and it just comes back with "(pending—
> Jenkins-Container-Cloud-456...164
> is
> offline)" .
>
> Does anyone know how to fix this, or have suggestions on debugging steps?
>
> --
> 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/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com
> 
> .
> 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/CANMVJzks3yceTvUxrFd5cGo8tYwSFh%3D00V%3DzL%2BxJVB2kCmi%3DhQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: High CPU Usage - Stale reports of Build Node Status

[Taylor Brown]

I've increased the heap available to Jenkins from 512m to 1024m, and I have 
restarted all of my build nodes. I restarted the server, and so far, so 
good. I am watching it closely, but I believe it might have been the issue.

On Friday, January 22, 2016 at 5:43:10 PM UTC-6, Taylor Brown wrote:
>
>
> This might not be the appropriate place to ask this, so forgive me if I 
> should be asking this somewhere else. Any advice on what to look for in our 
> thread dump would be very helpful!
>
> In the past couple of weeks, we have started to see our Jenkins server get 
> into the following state:
> 1) It's CPU usage on the server is pegged at about 250%
> 2) The web interface will usually load, although sometimes it is slow.
> 3) The status of the nodes printed in the left-hand column is very out of 
> date. It appears that all of our nodes are busy, but when you click on the 
> jobs that the column reports they are working on, you discover that the job 
> actually finished many minutes ago (sometimes 30+ minutes).
>
> I've just upgraded to the latest version, but shortly after it started, it 
> got into this state again. The CPU usage has been pegged at 250%+ for about 
> an hour, and now the web UI isn't responding (but luckily I was able to 
> navigate to /threadDump before it stopped responding) 
>
>
> You can see it here:
> https://gist.github.com/Taytay/a88fdc72baf745481b86
>
> I am not sure what I should be looking for to be honest. I assume that 
> there is something pretty obvious/abnormal here to explain the high CPU 
> usage, but I don't know what it is.
>
> I should mention that our host node does _very_ little. It can only run a 
> single short-lived job that is responsible for kicking off other downstream 
> jobs on the actual nodes themselves. So, I wouldn't expect the usage to be 
> much more than is necessary to drive the engine and web UI.
>
> Many thanks for any help you can provide.
>
> Taylor
>

-- 
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/ca361187-ed1e-4ddc-8ffa-622ce75869c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build not triggered when change is pushed to bitbucket

[Slide]

You shouldn't need to use Publish Over SSH to get the source code, the git
plugin will clone it for you already.  Did you check if you have something
similar to the setup described here?

https://bitbucket.org/site/master/issues/11514/webhook-fails-when-using-an-alternative

On Fri, Jan 22, 2016 at 2:56 AM Rohit Sharma 
wrote:

> Hello Slide,
>
> I configured the free style job in jenkins and checked the git option
> under SCM. And under Build Triggers i selected the option which states
> "Build when a change is pushed to BitBucket" there after i taking shell
> login to remote server using Publish Over SSH plugin to pull the latest
> code from bitbucket. Another thing which i did to make it work is added a
> webhook in bitbucket to send push notificaion to jenkins.
>
> Now to test i did test commit on repository and got 500 error when checked
> the logs of push events generated at bitbucket console.
>
> And to resolve this i tried all the solutions provided at :
> https://blog.bitbucket.org/2015/06/24/the-new-bitbucket-webhooks/
>
> http://stackoverflow.com/questions/32430427/bitbucket-webhook-keep-returning-error-500
>
> http://stackoverflow.com/questions/30995662/bitbucket-new-webhook-not-working
>
> https://answers.atlassian.com/questions/18448498/webhook-always-returning-500-error
>
> Apart from this I also whitelisted all the IP's provided at bitbucket on
> server where jenkins was setup. IN order to make jenkins work but still no
> success.
>
> Thanks
> Rohit
>
> On Thursday, 21 January 2016 21:37:46 UTC+5:30, slide wrote:
>
>> Perhaps it would help if you gave some more information about your
>> configuration, things you have tried, exact error messages, etc. Your
>> request is somewhat lacking in that regard.
>>
>> On Thu, Jan 21, 2016, 08:44 Rohit Sharma 
>> wrote:
>>
> Hello Everyone,
>>>
>>> I am using the jenkins version 1.625.3. And i am facing issues in
>>> integrating jenkins with bitbucket. What all i need to do is to trigger a
>>> job when a change is pushed to bitbucket. But unfortunately its not working
>>> and I am continuously getting the 500 error response code on webhook
>>> configured on bitbucket.
>>> Please help me out in this.
>>>
>>> Thanks
>>> Rohit
>>>
>>> --
>>> 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/9f9a6a3d-c504-45c4-8239-79d129ee3e6a%40googlegroups.com
>>> 
>>> .
>>> 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/714916d0-d458-4b7e-bf0a-bac90fd847c7%40googlegroups.com
> 
> .
> 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/CAPiUgVfB23Hp8LCghEg1-p%3DBc6GeNgqmSY%2BqV4Z%3D51NhyMPS9Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

crash plug-in warning - java heap space

[iostrym]

Hi,

We did a crash with jenkins, using plug-in warnings with a logfile that is 
70 Mo big :

[WARNINGS] Parsing warnings in console log with parser FPGA_Questa_UVM

ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to 
exception

hudson.util.IOException2 
: 
remote file operation failed: /***/ at 
hudson.remoting.Channel@**:serveur_linux_rdo 


  at hudson.FilePath.act(FilePath.java:861) 


  at hudson.FilePath.act(FilePath.java:838) 


  at 
hudson.plugins.warnings.WarningsPublisher.annotate(WarningsPublisher.java:447) 


  at 
hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:411)
 


  at 
hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:320) 


  at 
hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333)
 


  at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 


  at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814)
 


  at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786)
 


  at hudson.model.Build$BuildExecution.post2(Build.java:183) 


  at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733) 


  at hudson.model.Run.execute(Run.java:1592) 


  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 


  at hudson.model.ResourceController.execute(ResourceController.java:88) 


  at hudson.model.Executor.run(Executor.java:237) 


Caused by: java.io.IOException 
: Remote 
call on serveur_linux_rdo failed

  at hudson.remoting.Channel.call(Channel.java:681) 


  at hudson.FilePath.act(FilePath.java:854) 


  ... 14 more

Caused by: java.lang.OutOfMemoryError 
: 
Java heap space



We tried to re-run our slave with a bigger heap size but it doesn't help. So we 
wonder if the HEAP error is regarding the master or the slave ? Which one is 
executing the plug-in warning and do the parsing : master or slave ?


because of "Remote call on serveur_linux_rdo failed" we thought that the 
parsing was done by the slave but as the upgrade of the heap size of  Java 
Virtual Machine don't change anything and also because I succeed to crash the 
master and shutdown all slaves connected to the master by testing it, I gives 
me the feeling that the master may do something with the parsing.


Any idea ?


Best regards,


Armand

-- 
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/8f34dbbe-ec3f-4877-a17d-de3d8b21e9ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Does Jenkins still hold all job history in RAM?

[Christopher Shanahan]

So, I've been tasked, at work, with creating a Staging platform for our 
automated testing. The reasoning being that because our test platform is so 
closely tied to our build system, we want to avoid, at all costs, a Build 
not making it to Test because a Tester wrote a bad test. 

I created such a system and am now tasked with making sure it can hold 18 
months worth of build history. 
In speaking with our Developer in charge of maintaining Jenkins he informed 
me that build history is held in active memory for Jenkins (atleast last he 
heard, which is claimed to be a year ago). 

In doing some research myself I ran across this forum thread: 
http://jenkins-ci.361315.n4.nabble.com/jenkins-consumes-lot-of-memory-td4662793.html
 
Which seems to indicate the issue was fixed before my Dev knew about it in 
the first place. 

So I'm tossing the question out to you guys (via an email he gave me). 
Does Jenkins still hold every Job history in RAM? Was this issue fixed like 
stated in the above Forum? Did the issue crop back up since then, and if so 
was it fixed, or is it being worked on currently? 
I'm estimating anywhere around 2,000 to 3,000 saved Job histories once 18 
months has been reached, so I want to either know I'm in the clear, or go 
back to my boss with "it's not feasible to accomplish that". 


The Jenkins version we're currently running is 1.580.1 for frame of 
reference. 

-- 
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/96b101da-f46a-4e62-83e6-3e019bc5bf8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Does Jenkins still hold all job history in RAM?

[Daniel Beck]

On 22.01.2016, at 17:44, Christopher Shanahan  
wrote:

> So I'm tossing the question out to you guys (via an email he gave me). 
> Does Jenkins still hold every Job history in RAM? Was this issue fixed like 
> stated in the above Forum? Did the issue crop back up since then, and if so 
> was it fixed, or is it being worked on currently? 
> I'm estimating anywhere around 2,000 to 3,000 saved Job histories once 18 
> months has been reached, so I want to either know I'm in the clear, or go 
> back to my boss with "it's not feasible to accomplish that". 

Jenkins discards loaded job data from memory as needed. Build data is only 
retained to speed things up.

Of course, once you go below a certain threshold, Jenkins will keep loading 
builds from disk then immediately discard them to make space for other builds 
being loaded, so you still need _some_ memory, and having more of it makes use 
of Jenkins faster, but it's not like it will fail hard if you're no longer able 
to store all builds in RAM at the same time.

-- 
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/2093A039-DD6D-4D26-AB96-E4F8950D45EC%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Feed for changelog

[Daniel Beck]

On 22.01.2016, at 12:36, Johannes Wienke  
wrote:

> Thanks. However, I'd be more interested in what actually changed than
> the dates. And not having to navigate to the webpage from my news reader
> would be much more convenient. Any chance to set up such a feed?

Right now the changelog is a plain HTML page (which is probably not the best of 
ideas anyway, for either changelog, no that we have a static site). We'd need 
to move it into some other data structure from which the HTML changelog (and 
RSS/Atom) would be generated.

Could you file an issue in the WEBSITE project on http://issues.jenkins-ci.org?

(I though RSS was dead since Google Reader was shut down? Are you the last 
holdout? :-) )

-- 
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/A934871F-EF31-421A-B3F9-539CB9B1F23A%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

High CPU Usage - Stale reports of Build Node Status

[Taylor Brown]

This might not be the appropriate place to ask this, so forgive me if I 
should be asking this somewhere else. Any advice on what to look for in our 
thread dump would be very helpful!

In the past couple of weeks, we have started to see our Jenkins server get 
into the following state:
1) It's CPU usage on the server is pegged at about 250%
2) The web interface will usually load, although sometimes it is slow.
3) The status of the nodes printed in the left-hand column is very out of 
date. It appears that all of our nodes are busy, but when you click on the 
jobs that the column reports they are working on, you discover that the job 
actually finished many minutes ago (sometimes 30+ minutes).

I've just upgraded to the latest version, but shortly after it started, it 
got into this state again. The CPU usage has been pegged at 250%+ for about 
an hour, and now the web UI isn't responding (but luckily I was able to 
navigate to /threadDump before it stopped responding) 


You can see it here:
https://gist.github.com/Taytay/a88fdc72baf745481b86

I am not sure what I should be looking for to be honest. I assume that 
there is something pretty obvious/abnormal here to explain the high CPU 
usage, but I don't know what it is.

I should mention that our host node does _very_ little. It can only run a 
single short-lived job that is responsible for kicking off other downstream 
jobs on the actual nodes themselves. So, I wouldn't expect the usage to be 
much more than is necessary to drive the engine and web UI.

Many thanks for any help you can provide.

Taylor

-- 
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/89dc5adb-2df0-4074-8e6d-c173d54e802c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.