Jenkins Pipeling ECS deployments plugin

[Kai]

Hi,


It would be great if a plugin is available to support new ECS deployments 
where we just specify the ECS cluster, service name and docker image tag, 
and it just takes the existing task definition the service is mapped to and 
updates the image tag to the new one and updates the ecs service to the new 
ecs task revision. Is there a ECS deployment plugin in the works for 
Jenkins pipeline?


Thanks

-- 
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/a504fd83-fb63-4a7a-974a-334627024328%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Pipeline - build job step, ability to return build job number

[Kai]

wow, thanks so much!

On Saturday, December 23, 2017 at 3:35:42 AM UTC-8, Victor Martinez wrote:
>
> The build job step returns a RunWrapper object, and in your case you can 
> use the getId method 
> 
>
> def buildObj = build job: 'my-test-job', parameters: [string(name: 
> 'environment', value: 'QA')], quietPeriod: 10
> echo buildObj.getId()
>
> Cheers
>

-- 
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/2e99ca17-77a7-4cfa-96e8-cd7e0487ee02%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Pipeline - build job step, ability to return build job number

[Kai]

Hi,

We are using Jenkins Pipeline - build job step and wanted the ability to 
return build job number so that we can use the build job # in the next step.

e.g.
buildJobNumber=build job: 'my-test-job', parameters: [string(name: 
'environment', value: 'QA')], quietPeriod: 10

Then be able to use buildJobNumber in the next stage.

Thanks


-- 
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/6447f75c-8853-4295-bfa7-cb92c2e87812%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to define LabelParameterValue in Jenkinsfile

[Kai Wang]

Hi,

I have two jobs A and B. Job A calls Job B like this

*build job: "B", parameters[[$class: 'LabelParameterValue', name: 'node', 
label: "${env.NODE_NAME}"]]*

I know I am supposed to add a Label parameter in B. But the problem is B is 
a multiple branch pipeline project defined by Jenkinsfile.

So the question is, how do I define a Label parameter in Jenkinsfile? I 
tried 

*parameters {*
*LabelParameterValue(name: 'node', label: '')*
*}*

But I got the error:

*WorkflowScript: 11: Invalid parameter type "Label". Valid parameter types: 
[booleanParam, choice, credentials, file, text, password, run, string] @ 
line 11, column 9.*
*   Label(name: 'node', label: '')*
*   ^*

Thanks for the help.

-- 
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/aeac1bc6-5bac-405b-afca-957eed19d6c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins conditional post-based action in a pipeline stage

[Kai]

It seems like using try/catch complicates the code and then I have to 
remember to still fail the pipeline in the exception block. Using the post 
functionality seems to be for the entire pipeline not for a specific step.

Is there a post-step functionality that can be invoked for both pass and 
fail of a step ?  Thanks

On Wednesday, September 20, 2017 at 1:50:21 PM UTC-7, Kai wrote:
>
> Hi,
>
> I have a pipeline with multiple stages and for my integration test stage, 
> I trigger my integration test. I wanted to setup some post-step based 
> logic where if the test job passes, it does some action and if the test job 
> fails it performs a different action (e.g. send email) .
>
> stage('Run Integration Tests') {
> steps {
> timeout(time: 30, unit: 'MINUTES') {
> retry(1) {
> build job: 'my-integration-test'
> }
> } 
> }
> }
> Enter code here...
>
> Is it possible to accomplish this kind of setup ?
>
> Thanks
>

-- 
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/3fd2026d-1fbc-428b-9d18-6432063207fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins conditional post-based action in a pipeline stage

[Kai]

Hi,

I have a pipeline with multiple stages and for my integration test stage, I 
trigger my integration test. I wanted to setup some post-step based logic 
where if the test job passes, it does some action and if the test job fails 
it performs a different action (e.g. send email) .

stage('Run Integration Tests') {
steps {
timeout(time: 30, unit: 'MINUTES') {
retry(1) {
build job: 'my-integration-test'
}
} 
}
}
Enter code here...

Is it possible to accomplish this kind of setup ?

Thanks

-- 
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/01bf16ec-1115-411e-9038-87a203a8dd0d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Declarative Jenkinsfile for pullrequests.

[Kai Mildner]

I'm using the declarative Format, maybe with scripted parts? I'm not sure. 
Here is a short example how i do the checkout.

pipeline{
agent {label 'master'}
triggers { pollSCM('H 0 1 1 0') }
options{
buildDiscarder(logRotator(numToKeepStr: '3'))
timeout(time: 1, unit: 'HOURS')
skipDefaultCheckout()
retry(3)
}
environment{
INSTALL_DIR='my/install/dir'
}
stages{
stage('Checkout'){
steps{
script{
try{
cleanWs notFailBuild: true   
checkout(
[
$class: 'GitSCM', 
branches: [[name: '${BRANCH_NAME}']], 
doGenerateSubmoduleConfigurations: false, 
extensions:
[
[
$class: 'CloneOption', 
depth: 0, 
noTags: false, 
reference: '', 
shallow: true
], 
[
$class: 'SubmoduleOption', 
disableSubmodules: false, 
parentCredentials: false, 
recursiveSubmodules: true, 
reference: '', 
trackingSubmodules: false
],
[
$class: 'CleanBeforeCheckout'
]
], 
submoduleCfg: [], 
userRemoteConfigs: 
[
[
credentialsId: 
'X', 
url: 'my.git'
]
]
]
)
}catch(e){
String error = e.toString()
echo error
currentBuild.result = 'Failure'
emailext body: '${DEFAULT_CONTENT}', subject: 
'${DEFAULT_SUBJECT}', recipientProviders: [[$class: 
'DevelopersRecipientProvider'], [$class: 
'UpstreamComitterRecipientProvider']]
throw e
}
finally{
cleanWs notFailBuild: true
}
}
}
}
}
}

The Git source Control Provider is a local Bitbucket Server. The plugin i 
used in the multibranch Pipeline Project on Jenkins is Bitbucket to get the 
build results and builds also on the bitbucket overviews.



-- 
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/54ad9e3f-967b-4d94-8a4c-f6e1ce696847%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Declarative Jenkinsfile for pullrequests.

[Kai Mildner]

Hi,


i have a Jenkinsfile in my repository. On Jenkins i setted up a Multibranch 
Pipeline Project for the repository. 

Everything is fine, it builds via Jenkinsfile for everey branch i create 
and triggers also on push etc. 

Now i want to also build at pull requests. So the pull request is 
triggering the build. 

The Problem is now that my checkout is not working for the pull request.


$class: 'GitSCM', branches: [[name: '${BRANCH_NAME}']], 
doGenerateSubmoduleConfigurations: false, extensions: [ [ $class: 
'CloneOption', depth: 0, noTags: false, reference: '', shallow: true ], [ 
$class: 'SubmoduleOption', disableSubmodules: false, parentCredentials: false, 
recursiveSubmodules: true, reference: '', trackingSubmodules: false ], [ 
$class: 'CleanBeforeCheckout' ] ], submoduleCfg: [], userRemoteConfigs: [ [ 
credentialsId: 'xxx', url: 'my.git' ] ]

So now i have the problem that the branch name is "PR-[number]" when i 
create a pull request. So checking out that branch is not possible, because 
it not exists. I also tried it with 


branches: [[name: '**']]


But then nothing builds.

The git server is a local Bitbucket server.


What can i do to get also pullrequests Building?


Regards


Kai

-- 
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/8ef41809-ab53-4939-b1aa-a5aeeb86431d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins pipeline script params not recognized, bad substitution error

[Kai]

thanks so much, that worked!

On Tuesday, July 11, 2017 at 2:26:40 AM UTC-7, Jakub Pawlinski wrote:
>
> try using double quote:
>
> sh "python deploy.py ${params.version}"
>
> I think single quotes do not evaluate strings
>

-- 
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/0b37a833-0789-4aa2-93f9-58a028109f05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Invoking AWS lambda from Jenkins Pipeline Stage

[Kai]

Hi,

Is there a plugin available to invoke AWS lambda from Jenkins Pipeline 
Stage ? 

Thanks

-- 
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/5afe490a-99ff-4480-b79b-65f26e664c6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins pipeline script params not recognized, bad substitution error

[Kai]

I have a similar issue, I have a build job that is parameterized and am Not 
able to successfully use that parameter to pass as an argument to my python 
script in my pipeline stage

On Monday, July 10, 2017 at 2:46:17 PM UTC-7, Justin Khoo wrote:
>
> how can I read in the params from jenkins script shell sh? 
>
> pipeline {
>   stages{
>stage('Deploy') {
> steps {
> sh 'python deploy.py ${params.version}'
> }
> }
>   }
> }
>
> I have tried several ways, but still not able to read in params.
>

-- 
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/52bb8118-5eb1-4e43-88d3-f91fff1f6311%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

possible to have jenkins job pass in parameter to next stage in pipeline

[Kai]

Hi,

We have a stage in Jenkins pipeline where we invoke a Jenkins Job. (e.g. 
 build job: ... )

Is there a way for that Jenkins job that is invoked to pass in a 
value/parameter to the next stage in the pipeline ?

thanks

-- 
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/a3c66f3b-44f6-4542-a1f8-b419afd67bd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Pipeline - CodeBuild stage

[Kai]

Hi,

We are trying to leverage the awsCodeBuild plugin in out Jenkins pipeline

However, the plugin seems limiting as we are not able to pass in override 
env vars to the CodeBuild project during build invocation.

Is there a way to pass in override env vars to the CodeBuild project? Or, 
do we need to request an enhancement?

Thanks

-- 
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/89015cea-07e4-4cb0-9adc-0a724c4419ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to pass parameters to Jenkins Pipeline?

[Kai]

Hi,

We are trying to setup a Jenkins pipeline and have a Deploy step to deploy 
a specific version of the application.

The pipeline job will be invoked programmatically by another system.

Is there a way to pass in parameters programmatically to the pipeline job 
so it knows which version to deploy?

Thanks

-- 
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/c2c2f562-acce-475c-8a5f-eb0544118113%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Invoking jenkins job on separate Jenkins instance in Pipeline

[Kai]

Thanks, I was looking more of a way to do this in Pipeline using the 
declarative syntax. If anyone has an example it would be very much 
appreciated. Thanks



On Thursday, July 6, 2017 at 5:33:34 AM UTC-7, Richard Ginga wrote:
>
> I have not done this but I believe you can trigger another job that 
> resides on another jenkins master via a url.
>
> https://www.nczonline.net/blog/2015/10/triggering-jenkins-builds-by-url/
>
>
>
> On Thu, Jul 6, 2017 at 8:28 AM, Kai <kaite...@gmail.com > 
> wrote:
>
>> Hi,
>>
>> We need to create a pipeline where one of the stages needs to invoke 
>> another job that lives on a separate Jenkins instance.
>>
>> Is this possible? If so, is there an example on how we can accomplish 
>> this?
>>
>> Thanks
>>
>> -- 
>> 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/09f8733e-a8fd-47dc-a6de-b39dfa1402af%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/09f8733e-a8fd-47dc-a6de-b39dfa1402af%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Dick Ginga
> Build Engineer
> rgi...@disruptorbeam.com 
>
>

-- 
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/85f438ed-fdbf-474d-b51b-4899d549569e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Restricting Pipeline Job to run on specific slaves

[Kai]

Thank you both.

Now I see that I can do something like this:

agent { label 'slaves' }

On Thursday, July 6, 2017 at 5:26:49 AM UTC-7, Richard Ginga wrote:
>
> Where a pipeline runs is defined within the pipeline script using "node" 
> blocks. the Jenkins master "runs" the pipeline.
>
> On Thu, Jul 6, 2017 at 8:19 AM, Kai <kaite...@gmail.com > 
> wrote:
>
>> Hi,
>>
>> I have created a pipeline job in Jenkins but I don't see a "Restrict 
>> where this project can be run" option.
>>
>> Is there a way to restrict pipeline jobs to run on specific slaves?
>>
>> Thanks
>>
>> -- 
>> 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/03d44fad-b6fe-4901-bb9a-b204b4c8aebe%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/03d44fad-b6fe-4901-bb9a-b204b4c8aebe%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Dick Ginga
> Build Engineer
> rgi...@disruptorbeam.com 
>
>

-- 
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/7fe18592-c35c-4392-883b-45b8d9f1c2b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Invoking jenkins job on separate Jenkins instance in Pipeline

[Kai]

Hi,

We need to create a pipeline where one of the stages needs to invoke 
another job that lives on a separate Jenkins instance.

Is this possible? If so, is there an example on how we can accomplish this?

Thanks

-- 
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/09f8733e-a8fd-47dc-a6de-b39dfa1402af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Restricting Pipeline Job to run on specific slaves

[Kai]

Hi,

I have created a pipeline job in Jenkins but I don't see a "Restrict where 
this project can be run" option.

Is there a way to restrict pipeline jobs to run on specific slaves?

Thanks

-- 
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/03d44fad-b6fe-4901-bb9a-b204b4c8aebe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Workflow Jobs not appearing in queue

[Kai H]

Appears to have been fixed in the Jenkins core 1.642 version. I do see the 
Builds in the queue now.

On Sunday, December 20, 2015 at 11:31:11 AM UTC+1, Kai H wrote:
>
> Hi,
>
> I tried this "adapted" example from the the TUTORIAL.md:371 ff:
>
> node ('a-specific-node-with-one-executor') {
>   input "Just stall the build for a while"
> }
>
> When I run this twice in parallel, the first build will be running on the 
> executor and waiting for me to click on Proceed. The second job appears as 
> pending in the project, yet when I look at the overall Jenkins build queue 
> there is no trace of it at all. The document claims it would be shown as 
> "part of " in the global Jenkins build queue. What am I missing?
>
> Kai.
>

-- 
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/5cddaef3-7bca-4ba8-afd0-b63b2d382f59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Workflow Jobs not appearing in queue

[Kai H]

Hi,

I tried this "adapted" example from the the TUTORIAL.md:371 ff:

node ('a-specific-node-with-one-executor') {
  input "Just stall the build for a while"
}

When I run this twice in parallel, the first build will be running on the 
executor and waiting for me to click on Proceed. The second job appears as 
pending in the project, yet when I look at the overall Jenkins build queue 
there is no trace of it at all. The document claims it would be shown as 
"part of " in the global Jenkins build queue. What am I missing?

Kai.

-- 
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/1a5dea8b-7f4e-48da-8d57-cb0c0a55fe75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

buildWithParameters API not returning JSON response for Jenkins 1.575

[Kai]

Hi,

I'm invoking a job in Jenkins like 
so: http://jenkins/job/test-job/buildWithParameters?environment=DEVtype=test

with header  Accept:application/json

On Jenkins 1.552, when I invoke this API, I get a JSON response back

I just upgraded to Jenkins 1.575, and whey I invoke the same API call with 
the same header, I don't get any json response back

Did something change in the new version of Jenkins? (I can't find any 
documentation in regards to this that something did change)

Thanks.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: buildWithParameters API not returning JSON response for Jenkins 1.575

[Kai]

Ahhh, thank you! Good find!   :)

Gosh, should've looked in the response header

On Thursday, October 9, 2014 1:50:54 PM UTC-7, Daniel Beck wrote:

  (I can't find any documentation in regards to this that something did 
 change 

 Finding requires searching ;-) 

 http://jenkins-ci.org/changelog#v1.561 

 What's new in 1.561 (2014/04/27) 
 • Return queue item location when triggering buildWithParameters. (issue 
 13546) 

 https://issues.jenkins-ci.org/browse/JENKINS-13546 

 On 09.10.2014, at 22:41, Kai kaite...@gmail.com javascript: wrote: 

  Hi, 
  
  I'm invoking a job in Jenkins like so: 
 http://jenkins/job/test-job/buildWithParameters?environment=DEVtype=test 
  
  with header  Accept:application/json 
  
  On Jenkins 1.552, when I invoke this API, I get a JSON response back 
  
  I just upgraded to Jenkins 1.575, and whey I invoke the same API call 
 with the same header, I don't get any json response back 
  
  Did something change in the new version of Jenkins? (I can't find any 
 documentation in regards to this that something did change) 
  
  Thanks. 
  
  -- 
  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 javascript:. 
  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.
For more options, visit https://groups.google.com/d/optout.

show extra links in executor status by plugin

[Kai-Hsiang Chang]

Hi all,
 
By default, there has project and buildnumber link in executor status and 
it's writen in executors.jelly.
 
Is that possible to show some job-related information links in executor 
status by plugin? 
 
if possible, what's the extension point? 
 
Thanks!
 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: Maven Builds - Slow Build Times on Jenkins Slaves

[Kai]

Thanks for the follow-up Mathus!

I was able to track down the issue. The culprit seems to be the disk-usage 
plugin http://wiki.jenkins-ci.org/display/JENKINS/Disk+Usage+Plugin.
Once I disabled the disk-usage plugin, the builds on the jenkins slave 
started performing as fast as on the master.

I'm not sure why it was churning to calculate the disk usage when running 
on slaves. If anyone has insights into this, I would love to know, thanks!

Here is the stacktrace I saw in the logs:
Mar 28, 2014 11:58:42 AM hudson.plugins.disk_usage.DiskUsageUtil 
calculateWorkspaceDiskUsageForPath
WARNING: Disk usage fails to calculate workspace for file path 
/var/lib/jenkins/workspace/test-project through channel 
hudson.remoting.Channel@7ad8a715:jenkins-slave-3
java.util.concurrent.TimeoutException
at hudson.remoting.Request$1.get(Request.java:275)
at hudson.remoting.Request$1.get(Request.java:210)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)
at 
hudson.plugins.disk_usage.DiskUsageUtil.calculateWorkspaceDiskUsageForPath(DiskUsageUtil.java:294)
at 
hudson.plugins.disk_usage.DiskUsageBuildListener.onCompleted(DiskUsageBuildListener.java:60)
at 
hudson.plugins.disk_usage.DiskUsageBuildListener.onCompleted(DiskUsageBuildListener.java:23)
at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199)
at hudson.maven.MavenBuild$ProxyImpl2.end(MavenBuild.java:574)
at sun.reflect.GeneratedMethodAccessor448.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at hudson.model.Executor$1.call(Executor.java:559)
at hudson.util.InterceptingProxy$1.invoke(InterceptingProxy.java:23)
at $Proxy50.end(Unknown Source)
at sun.reflect.GeneratedMethodAccessor447.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280)
at 
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

On Thursday, March 27, 2014 10:34:14 AM UTC-7, Baptiste Mathus wrote:

 If using the maven type job, try using a freestyle one and see if you got 
 a different result. 

 Apart from that, it would be really helpful if you could generate many 
 stacktraces in a dedicated jira, take them during those apparently idle 
 times to see what it's doing.

 Cheers
 Le 27 mars 2014 17:08, Kai kaite...@gmail.com javascript: a écrit :

 Hi, just wanted to check-in if anyone has insights into this or if anyone 
 else is experiencing similar issues with mvn build jobs running on jenkins 
 slaves?

 Thanks.

 On Saturday, March 22, 2014 11:38:35 AM UTC-7, Kai wrote:

 Sorry for the late reply. Actually, it runs pretty quick when I run my 
 maven command manually on the slave - takes about ~8 mins.

 However, when I run through Jenkins, it takes between ~18-19mins for the 
 job to complete.
 Here are a few snippets from the console logs. Most of the areas where 
 it tends to be slow is when it says deleting .../target directory, then 
 says archiving disabled and stays there for like 2 mins usually, then 
 moves on. And it does this for each maven module that's part of the 
 project, so it adds up.
 Also, takes some time, after archiving steps, then says archiving 
 disabled, usually like up to 2 min delay before moving on.

 *Snippets from Console Log*


 *19:56:10 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
 test-project-parent ---19:56:10 [INFO] Deleting 
 /var/lib/jenkins/workspace/test-project/target19:56:13 [JENKINS] Archiving 
 disabled 19:58:33 [INFO]20:03:32 [JENKINS] Archiving site from 
 /var/lib/jenkins/workspace/test-project-main/test-project/target/site to 
 /var/lib/jenkins/jobs/test-project-main/site/test-project 20:03:32 
 [JENKINS] Archiving disabled20:05:51 [INFO]   *





 On Tuesday, March 18, 2014 11:15:49 PM UTC-7, Baptiste Mathus wrote:

 Outside Jenkins, I mean.
 Le 19 mars 2014 07:15, Baptiste Mathus bma...@batmat.net a écrit :

 Is it also slow if you run the maven build manually on that slave?
 Le 16 mars 2014 22:57, Kai kaite...@gmail.com a écrit :

 Hi,

 We are currently

Re: Maven Builds - Slow Build Times on Jenkins Slaves

[Kai]

Hi, just wanted to check-in if anyone has insights into this or if anyone 
else is experiencing similar issues with mvn build jobs running on jenkins 
slaves?

Thanks.

On Saturday, March 22, 2014 11:38:35 AM UTC-7, Kai wrote:

 Sorry for the late reply. Actually, it runs pretty quick when I run my 
 maven command manually on the slave - takes about ~8 mins.

 However, when I run through Jenkins, it takes between ~18-19mins for the 
 job to complete.
 Here are a few snippets from the console logs. Most of the areas where it 
 tends to be slow is when it says deleting .../target directory, then says 
 archiving disabled and stays there for like 2 mins usually, then moves 
 on. And it does this for each maven module that's part of the project, so 
 it adds up.
 Also, takes some time, after archiving steps, then says archiving 
 disabled, usually like up to 2 min delay before moving on.

 *Snippets from Console Log*


 *19:56:10 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
 test-project-parent ---19:56:10 [INFO] Deleting 
 /var/lib/jenkins/workspace/test-project/target19:56:13 [JENKINS] Archiving 
 disabled19:58:33 [INFO]20:03:32 [JENKINS] Archiving site from 
 /var/lib/jenkins/workspace/test-project-main/test-project/target/site to 
 /var/lib/jenkins/jobs/test-project-main/site/test-project20:03:32 [JENKINS] 
 Archiving disabled20:05:51 [INFO]   *





 On Tuesday, March 18, 2014 11:15:49 PM UTC-7, Baptiste Mathus wrote:

 Outside Jenkins, I mean.
 Le 19 mars 2014 07:15, Baptiste Mathus bma...@batmat.net a écrit :

 Is it also slow if you run the maven build manually on that slave?
 Le 16 mars 2014 22:57, Kai kaite...@gmail.com a écrit :

 Hi,

 We are currently on Jenkins 1.551 and are experiencing significant 
 maven build slowness on our jenkins slaves.

 It seems deleting the target directory takes forever.
 Also, during the site phase, a step: Archiving site from ... comes 
 and takes a while (even though archiving is disabled), then it says 
 archiving disabled and moves on.

 However, when the build runs on the master, I don't experience this 
 slowness and deleting the target directory is really quick.

 Has anyone else experienced this issue or know what could be causing 
 the slowness when building on Jenkin slaves?

 Thank you so much!

 -- 
 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.
 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.
For more options, visit https://groups.google.com/d/optout.

Re: Maven Builds - Slow Build Times on Jenkins Slaves

[Kai]

Sorry for the late reply. Actually, it runs pretty quick when I run my 
maven command manually on the slave - takes about ~8 mins.

However, when I run through Jenkins, it takes between ~18-19mins for the 
job to complete.
Here are a few snippets from the console logs. Most of the areas where it 
tends to be slow is when it says deleting .../target directory, then says 
archiving disabled and stays there for like 2 mins usually, then moves 
on. And it does this for each maven module that's part of the project, so 
it adds up.
Also, takes some time, after archiving steps, then says archiving 
disabled, usually like up to 2 min delay before moving on.

*Snippets from Console Log*


*19:56:10 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
test-project-parent ---19:56:10 [INFO] Deleting 
/var/lib/jenkins/workspace/test-project/target19:56:13 [JENKINS] Archiving 
disabled19:58:33 [INFO]20:03:32 [JENKINS] Archiving site from 
/var/lib/jenkins/workspace/test-project-main/test-project/target/site to 
/var/lib/jenkins/jobs/test-project-main/site/test-project20:03:32 [JENKINS] 
Archiving disabled20:05:51 [INFO]   *





On Tuesday, March 18, 2014 11:15:49 PM UTC-7, Baptiste Mathus wrote:

 Outside Jenkins, I mean.
 Le 19 mars 2014 07:15, Baptiste Mathus bma...@batmat.net javascript: 
 a écrit :

 Is it also slow if you run the maven build manually on that slave?
 Le 16 mars 2014 22:57, Kai kaite...@gmail.com javascript: a écrit :

 Hi,

 We are currently on Jenkins 1.551 and are experiencing significant maven 
 build slowness on our jenkins slaves.

 It seems deleting the target directory takes forever.
 Also, during the site phase, a step: Archiving site from ... comes and 
 takes a while (even though archiving is disabled), then it says archiving 
 disabled and moves on.

 However, when the build runs on the master, I don't experience this 
 slowness and deleting the target directory is really quick.

 Has anyone else experienced this issue or know what could be causing the 
 slowness when building on Jenkin slaves?

 Thank you so much!

 -- 
 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 javascript:.
 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.
For more options, visit https://groups.google.com/d/optout.

Maven Builds - Slow Build Times on Jenkins Slaves

[Kai]

Hi,

We are currently on Jenkins 1.551 and are experiencing significant maven 
build slowness on our jenkins slaves.

It seems deleting the target directory takes forever.
Also, during the site phase, a step: Archiving site from ... comes and 
takes a while (even though archiving is disabled), then it says archiving 
disabled and moves on.

However, when the build runs on the master, I don't experience this 
slowness and deleting the target directory is really quick.

Has anyone else experienced this issue or know what could be causing the 
slowness when building on Jenkin slaves?

Thank you so much!

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: The network name cannot be found

[kai zeng]

Hi Vinod, 

I meet the same issue, have you resolve it?

thanks
luke

On Wednesday, February 15, 2012 10:15:32 PM UTC+8, Vinod wrote:

 Hi All, 
 I am running master on linux machine and slave on Windows machine. 
 While running node job I get this message 
 where xx.xxx.xx.xxx is IP Address for slave jenkins 

 Connecting to xx.xxx.xx.xxx 
 ERROR: The network name cannot be found. 
 jcifs.smb.SmbException: The network name cannot be found. 
 at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:545) 
 at jcifs.smb.SmbTransport.send(SmbTransport.java:646) 
 at jcifs.smb.SmbSession.send(SmbSession.java:244) 
 at jcifs.smb.SmbTree.treeConnect(SmbTree.java:176) 
 at jcifs.smb.SmbFile.doConnect(SmbFile.java:906) 
 at jcifs.smb.SmbFile.connect(SmbFile.java:949) 
 at jcifs.smb.SmbFile.connect0(SmbFile.java:875) 
 at jcifs.smb.SmbFile.queryPath(SmbFile.java:1328) 
 at jcifs.smb.SmbFile.exists(SmbFile.java:1410) 
 at 
 hudson.os.windows.ManagedWindowsServiceLauncher.launch(ManagedWindowsServiceLauncher.java:
  

 235) 
 at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) 
 at 
 java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 
 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 
 at java.util.concurrent.ThreadPoolExecutor 
 $Worker.runTask(ThreadPoolExecutor.java:886) 
 at java.util.concurrent.ThreadPoolExecutor 
 $Worker.run(ThreadPoolExecutor.java:908) 
 at java.lang.Thread.run(Thread.java:619) 

 Please Help and suggest some Solution if some one can Help Me. 

 Thanks In Advance 
 Vinod Kumar