[Extensions][Development][Test] Why JenkinsRule no longer finds my extension's WEB Endpoints?

['Christian Yeste Vidal' via Jenkins Users]

Hi,

I'm developing an extensión for Jenkins, that consists of a new WEB API 
aimed to provide our ALM tooling with tailored operations on Jenkins. The 
starting point for me was this guide 
, which I 
have reproduced step by step.

After manual tests of a bare minimum API, I concluded that the extension 
was working and ready for further development. 

To speed up development and testing, I have also prepared a canary test in 
JUnit, following the previous guide (linked above) and this other 
 to feed test with 
*@LocalData.*

The firsts times I run the JUnit, it worked. Test passed. So, I was able to 
run *mvn clean packge* and complete the build executing (and passing) all 
tests

Today, I did open the IDE, run the same maven goals to ensure that 
everything was ok (a  routine of mine), but tests failed due to a *404 Not 
Found*

Here the stacktrace









































*Test timeout disabled.=== Starting 
test_ping(net.corp.jenkins.plugins.almapirest.AlmApiTest)   0.152 [id=1]   
 INFOo.jvnet.hudson.test.WarExploder#explode: Picking up existing 
exploded jenkins.war at 
/home/user/Desarrollo/workspace-11/jenkins-plugins/imi-alm-jenkinsplugin-almapirest/target/jenkins-for-test
  
 0.522 [id=1]INFOo.jvnet.hudson.test.JenkinsRule#createWebServer: 
Running on http://localhost:34866/jenkins/   1.057 [id=33]INFO   
 jenkins.InitReactorRunner$1#onAttained: Started initialization   2.433 
[id=38]INFOhudson.PluginManager#considerDetachedPlugin: Loading a 
detached plugin as a dependency: 
/tmp/jenkins11162667569266280008/plugins/bouncycastle-api.jpi   2.545 
[id=38]INFOhudson.PluginManager#considerDetachedPlugin: Loading a 
detached plugin as a dependency: 
/tmp/jenkins11162667569266280008/plugins/command-launcher.jpi   2.554 
[id=38]INFOhudson.PluginManager#considerDetachedPlugin: Loading a 
detached plugin as a dependency: 
/tmp/jenkins11162667569266280008/plugins/jdk-tool.jpi   2.566 [id=38]   
 INFOhudson.PluginManager#considerDetachedPlugin: Loading a detached 
plugin as a dependency: /tmp/jenkins11162667569266280008/plugins/jaxb.jpi  
 2.791 [id=38]INFOjenkins.InitReactorRunner$1#onAttained: Listed 
all pluginsWARNING: An illegal reflective access operation has 
occurredWARNING: Illegal reflective access by 
com.google.inject.internal.cglib.core.$ReflectUtils$2 
(file:/home/user/.m2/repository/com/google/inject/guice/4.0/guice-4.0.jar) 
to method 
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)WARNING:
 
Please consider reporting this to the maintainers of 
com.google.inject.internal.cglib.core.$ReflectUtils$2WARNING: Use 
--illegal-access=warn to enable warnings of further illegal reflective 
access operationsWARNING: All illegal access operations will be denied in a 
future release   6.538 [id=36]INFO   
 jenkins.InitReactorRunner$1#onAttained: Prepared all plugins   6.577 
[id=34]INFOjenkins.InitReactorRunner$1#onAttained: Started all 
plugins   6.590 [id=36]INFOjenkins.InitReactorRunner$1#onAttained: 
Augmented all extensions   7.742 [id=37]INFO   
 jenkins.InitReactorRunner$1#onAttained: System config loaded   7.743 
[id=37]INFOjenkins.InitReactorRunner$1#onAttained: System config 
adapted   7.743 [id=37]INFOjenkins.InitReactorRunner$1#onAttained: 
Loaded all jobs   7.748 [id=31]INFO   
 jenkins.InitReactorRunner$1#onAttained: Configuration for all jobs 
updated   7.858 [id=35]INFOjenkins.InitReactorRunner$1#onAttained: 
Completed initialization  10.414 [id=1]INFO   
 n.o.j.p.almapirest.AlmApiTest#logJenkinsWebResponse: 404 
Not FoundStapler processed this HTTP request as follows, but 
couldn't find the resource to consume the request-> 
evaluate( 
:hudson.model.Hudson,"/alm-api/ping")-> 
evaluate(((StaplerProxy)).getTarget(),"/alm-api/ping")->
 
evaluate(.getDynamic("alm-api",...),"/ping")
  
  hudson.model.Hudson@5d1c17df.getDynamic("alm-api",...)==null. 
Back tracking.-> 
evaluate(((StaplerFallback)).getStaplerFallback(),"/alm-api/ping")->
 
evaluate( 
:hudson.model.AllView,"/alm-api/ping")-> 
evaluate(.getDynamic("alm-api",...),"/ping")
  
  
hudson.model.AllView@2c546831[view/all/].getDynamic("alm-api",...)==null. 
Back tracking.-> No matching rule was found on 
 for 
"/alm-api/ping" 
has the following URL mappings, in the order of preference:If path 
ends without '/' insert it*

When I run *mvn hpi:run* to do manual testing, the extension works and the 
endpoints are accessible. I also check that *work/plugins *con

Re: How to access jenkins using ip address remotely ?

['Christian Brauchmann' via Jenkins Users]

tl;dr
You need to adjust httpListenAddress
See here:
https://stackoverflow.com/questions/64338546/making-jenkins-localhost-publicly-available-within-the-same-network/64339357#64339357

Am Mi., 21. Okt. 2020 um 13:20 Uhr schrieb Daniel Beck :

>
>
> > On 20. Oct 2020, at 07:22, Vaibhav Khachane 
> wrote:
> >
> > I am trying to access jenkins using ip address but it is not working . I
> am using macOS.
> >
> > Following jenkins url working fine
> > http://localhost:8080/
> > http://127.0.0.1:8080/
> > http://0.0.0.0:8080/
> >
> > but while using ip adress of my machine it is not working
> > http://(ip address of my. machine ):8080/
>
> Jenkins installed via Homebrew only listens on the loopback interface, so
> this is expected. Why they do this, I have no idea. Perhaps our former
> (2016 and earlier) lack of having a secure configuration out of the box.
>
>
> https://github.com/Homebrew/homebrew-core/blob/0a483dc47a7f30266b626f1bfcf465c733c880b8/Formula/jenkins.rb#L55
>
> https://github.com/Homebrew/homebrew-core/blob/0a483dc47a7f30266b626f1bfcf465c733c880b8/Formula/jenkins-lts.rb#L46
>
> --
> 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/306846EF-A0BB-49E1-8C6D-13EEB2EB3BFD%40beckweb.net
> .
>


-- 
Von meinem Atari ST520 gesendet

-- 
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/CAOtmfbnUk0Q03Dc57dZ2c%3DDgnaLgng0OymeVdBVSxApoPaNAEw%40mail.gmail.com.

Re: how to use git commands inside a Multi Branch Project?

[Christian Baumann]

Hi all,

I know this topic is rather old, but I´m facing the very same issue and was 
not able to find a proper solution.
Has anything changed since this question has been raised and someone could 
provide an answer?

Many thanks,
Christian

Am Mittwoch, 30. November 2016 12:20:22 UTC+1 schrieb Torsten Reinhard:
>
> Hi all,
>
> I have a Multi Branch Project, using a *.git Repository. All branches are 
> detected and the checkout is working. 
> In my JenkinsFile I need to execute some "git" commands, like:
>
> ...
> sh "git tag -d FOR_INTEGRATION_TESTING" // removes 
> the tag in local env.
> sh "git push origin :refs/tags/FOR_INTEGRATION_TESTING"// removes 
> the tag in remote env.
> sh "git tag -a FOR_INTEGRATION_TESTING"// adds 
> the tag to different commit
> sh "git push origin FOR_INTEGRATION_TESTING"// pushes the 
> change to the remote
> ...
>
> How can I apply the credentials here ? 
> When trying 
>
> withCredentials [$class: 'UsernamePasswordMultiBinding', credentialsId: 
> git_creds, usernameVariable: 'G_USER', passwordVariable: 'G_PASS'] {
>   ...
> }
>
>
> I see this exception:
>
> org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: 
> Credentials 'a378e16a-3d20-4465-aef1-b2bd233f15b6' is of type 'SSH Username 
> with private key' 
> where 
> 'com.cloudbees.plugins.credentials.common.StandardUsernamePasswordCredentials'
>  was expected
>
>
> Is there another class instead of "UsernamePasswordMultiBinding" I have to 
> use? 
>
> Thanx for pointing me in the right direction, 
>
> Torsten
>
>
>

-- 
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/b73419d8-67c4-44d2-bddc-092e591f2a23%40googlegroups.com.

RE: Jobs with a wildcard tag refspec sometimes rebuild tags at same commit

[Beushausen, Christian]

Hi Eric, Mark,

Could you keep the list updated? Or have you created a new issue on Jira for 
this?
We do see this (or a very similar) issue also for at least one job in our 
environment

Thank you and cheers.

Mit freundlichen Gruessen/Best regards,

Christian Beushausen
I S&T PD SW SWF
Interior Systems & Technology

E-Mail: 
christian.beushau...@continental-corporation.com<mailto:christian.beushau...@continental-corporation.com>


From: jenkinsci-users@googlegroups.com  On 
Behalf Of Mark Waite
Sent: Dienstag, 7. Januar 2020 01:21
To: Jenkins Users 
Subject: Re: Jobs with a wildcard tag refspec sometimes rebuild tags at same 
commit

Discard old builds is very likely the problem.  If a tag build is removed from 
the history by "Discard old builds" then future searches for the that tag (or 
the SHA-1 of the commit associated with the tag) will fail and it will build 
again.

On Mon, Jan 6, 2020 at 5:18 PM Eric Pierson 
mailto:pierson...@gmail.com>> wrote:
Thank you for your response, Mark!

I have not tried to run any scripts to prune history as I see described in 
JENKINS-19022.  There are a lot of comments in this one and I am still 
re-reading them to be sure I am not missing something else relevant folks 
discovered along the way.

I do have "Discard old builds" enabled with Strategy "Log Rotation" and "Max # 
of builds to keep" = 10.  Forgive me for omitting the fact that I use Discard 
old builds initially.

Reading more about  "Discard old builds":

  *   Build count: discard the oldest build when a certain number of builds 
already exist
  *   Note that Jenkins does not discard items immediately when this 
configuration is updated, or as soon as any of the configured values are 
exceeded; these rules are evaluated each time a build of this project completes.
I am now focusing on the "Discard old builds" settings and build.xml content, 
and what may be happening to the build history when a build completes.  I have 
one job that has only run a total of 7 times that had the issue on builds #3 
and #4, and the example I initially provided has only run a total of 12 times 
and we see the issue on multiple builds there, too.  So while there are indeed 
many tags in the repo, the build history is not "large" yet.

I have another Jenkins environment I used for a while where I did not have this 
issue.  It had the same settings (including "Discard old builds"), but when I 
was running jobs through this environment on a regular basis, Jenkins and 
plugins would have been at older versions.

To hone in on git plugin versions just in the change they are relevant, I 
compared my build.xml:

New Environment
mailto:git@4.0.0>">
mailto:git-client@3.0.0>">
mailto:git-client@3.0.0>">

Old Environment
mailto:git@3.9.3>">
mailto:git-client@2.7.7>">
mailto:git-client@2.7.7>">

 ---

Given this additional information, please let me know if you have any new 
thoughts or if you feel I should file a bug report (for perhaps the logRotate 
or BuildDiscarder area?) as I continue to research and test.

Thank you again for your help and everything you do for the Jenkins community!

-Eric



On Fri, Jan 3, 2020 at 8:38 PM Mark Waite 
mailto:mark.earl.wa...@gmail.com>> wrote:


On Fri, Jan 3, 2020 at 2:51 PM Eric Pierson 
mailto:pierson...@gmail.com>> wrote:
I am troubleshooting a scenario where jobs with a wildcard tag refspec 
(+refs/tags/*:refs/remotes/origin/tags/*) sometimes detect changes and rebuild 
a successfully built tag referencing the same commit.

When a rerun occurs, prior job runs for the tag are no longer present in the 
Git Build History for the job.


That sounds to me as though you are relying on the JENKINS-19022 memory bloat 
bug to retain history of more jobs in the BuildData than are actually in the 
build history.

If someone executed one of the scripts that is mentioned in JENKINS-19022 to 
clean the excess BuildData from the history, that seems like it might cause the 
SHA-1's referenced by some of the tags to be removed from the history.

If build history were being removed based on a specific number of builds, then 
it also could be that the history entry which included that tag was removed 
from the list, and thus was no longer visible.

Mark Waite

I am seeking help to further investigate and trace polling activity to try to 
determine what changes are being detected that trigger the job to run again, or 
learn if i should submit this as a bug report for assistance instead.

Thanks, everyone!


---
Existing Bugs Found:

This was the most relative bug I could find, yet my situation is different.

https://issues.jenkins-ci.org/browse/JENKINS-17614?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&showAll=true
---


My Environment:

Jenkins 2.176.3 on tradi

Cloud/Docker nodes missing node based security?

['Christian Zagrodnick' via Jenkins Users]

Hi,

I'm missing the "Enable node-based security" for docker cloud nodes 
(/configureClouds that is). Am I missing something here?

Best,

Christian

-- 
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/fe0b9f70-1e2b-4752-95d1-b0051240ecc7%40googlegroups.com.

RE: jenkins pipeline - how to add another parallel to 2 other parallel.

[Beushausen, Christian]

Hi Prashanth,

my understanding:
What you want to achieve is not possible with declarative pipeline.
You should be able to get this done with a scripted pipeline though. Note: Blue 
Ocean is not able to represent it.

Mit freundlichen Gruessen/Best regards,

Christian Beushausen
I S&T PD SW SWF
Interior Systems & Technology

Besucheradresse / Visitor address:
Continental Automotive GmbH
Philipsstrasse 1, 35576 Wetzlar, Germany

Rechnungsadresse / Invoice address:
Continental Automotive GmbH
Philipsstrasse 1, 35576 Wetzlar, Germany

Phone: +49 6441 370-9031
Mobile: +49 151 746 602 27
Fax: +49 6441 37013-9031
E-Mail: 
christian.beushau...@continental-corporation.com<mailto:christian.beushau...@continental-corporation.com>

<$$014!>

From: jenkinsci-users@googlegroups.com  On 
Behalf Of Prashanth Linga
Sent: Dienstag, 10. September 2019 21:25
To: Jenkins Users 
Subject: jenkins pipeline - how to add another parallel to 2 other parallel.

Hello friends / Jenkins Users,
I want stage 9 to be parallel to first and second parallel. stage 9 should 
finish before installer stage. Attached is existing diagram, proposed one to be 
created.
Either declarative or scripted is fine. .

Please share your ideas and thanks for taking time to look into this issue. I 
appreciate your response. Thank you.

pipeline {
agent any
environment {
//TODO - this will apply to steps within this file
}
stages {
stage('Preparation') {
steps {
echo 'First stage'
}//step for stage
}
stage ('parallel-1') {
parallel {
stage ('8') {
steps {
echo "stage-8"
}
}
stage ('7 6 5') {
stages ('stage Libraries'){
stage ('stage 7') {
steps {
echo "stage 7"
}
}
stage ('stage 6'){
steps {
echo "stage 6"
}
}
stage ('stage 5'){
steps {
echo "stage 5"
}
}
}
}
stage ("stage 9") {
steps {
echo 'stage 9'
}

}
}
}
stage ('parallel-2'){
parallel  {
stage ("stage 2") {
steps {
echo 'stage 2'
}
}
stage ("stage 3") {
steps {
echo 'stage 3'
}
}
stage ("stage 4") {
steps {
echo 'stage 4'
}
}
}
}
stage ('installer jackpot'){
steps {
echo 'inside jackpot'
}
}
}
}
--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7e4b02c5-a379-4a2a-a701-ec4108a81bc8%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/7e4b02c5-a379-4a2a-a701-ec4108a81bc8%40googlegroups.com?utm_medium=email&utm_source=footer>.

https://www.continental.com


Continental Automotive GmbH, Vahrenwalder Str. 9, D-30165 Hannover
Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Helmut Matschi
Geschaeftsfuehrer/Managing Director: Georg Sistermanns, Harald Stuhlmann
Sitz der Gesellschaft/Registered Office: Hannover
Registergericht/Registered Court: Amtsgericht Hannover, HRB 59424
USt.-ID-Nr./VAT-ID-No. DE814950663

__

Proprietary and confidential. Distribution only by express authority of 
Continental AG or its subsidiaries.

-- 
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/AM6PR03MB4774409E27AE441B60A2BB13CFB10%40AM6PR03MB4774.eurprd03.prod.outlook.com.

RE: Recommended Plug in for migrating jobs between 2 jenkins instances

[Beushausen, Christian]

Hi Nicolas,

We are sometimes using this plugin:
https://plugins.jenkins.io/job-import-plugin

Or, you could (from what I have heard):

  *   Copy job folders on file system level
  *   Download job config as xml via Jenkins CLI and upload it on the new 
instance.

Mit freundlichen Gruessen/Best regards,

Christian Beushausen
I S&T PD SW SWF
Interior Systems & Technology

Besucheradresse / Visitor address:
Continental Automotive GmbH
Philipsstrasse 1, 35576 Wetzlar, Germany

Rechnungsadresse / Invoice address:
Continental Automotive GmbH
Philipsstrasse 1, 35576 Wetzlar, Germany

Phone: +49 6441 370-9031
Mobile: +49 151 746 602 27
Fax: +49 6441 37013-9031
E-Mail: 
christian.beushau...@continental-corporation.com<mailto:christian.beushau...@continental-corporation.com>

<$$014!>

From: jenkinsci-users@googlegroups.com  On 
Behalf Of Nicolas Grossi
Sent: Donnerstag, 8. November 2018 15:15
To: jenkinsci-users@googlegroups.com
Subject: Fwd: Recommended Plug in for migrating jobs between 2 jenkins instances

Hi team:
  Is there any plug in that can be used to expport/import jobs form 
one jenkins instances to another ?

Thanks in advance!
--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAATVPEhTJeiLvvMc0Auwbcs8%2BN4KchE6LaA%3D4WHjzVdxG0zhag%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CAATVPEhTJeiLvvMc0Auwbcs8%2BN4KchE6LaA%3D4WHjzVdxG0zhag%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

http://www.continental-corporation.com


Continental Automotive GmbH, Vahrenwalder Str. 9, D-30165 Hannover
Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Helmut Matschi
Geschaeftsfuehrer/Managing Director: Georg Sistermanns, Harald Stuhlmann
Sitz der Gesellschaft/Registered Office: Hannover
Registergericht/Registered Court: Amtsgericht Hannover, HRB 59424
USt.-ID-Nr./VAT-ID-No. DE814950663

__

Proprietary and confidential. Distribution only by express authority of 
Continental AG or its subsidiaries.

-- 
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/VI1PR0302MB3421FD721F6DEDC7232776F5CFC60%40VI1PR0302MB3421.eurprd03.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

RE: Jenkins Administration - Role-based Authorization Strategy - Manage & Assign Roles list really big

[Beushausen, Christian]

Hi,

We set up dedicated AD groups for different types of users (developers, users, 
integrators) and only those groups are maintained on Jenkins. Everything else 
is done via the AD groups.

Maybe also not the best approach, but this way we were able to mostly 
centralize all access requests to one single point of entry.

Br,
Christian

From: jenkinsci-users@googlegroups.com  On 
Behalf Of gotviser...@gmail.com
Sent: Mittwoch, 24. Oktober 2018 21:50
To: Jenkins Users 
Subject: Jenkins Administration - Role-based Authorization Strategy - Manage & 
Assign Roles list really big

We use Role-based Authorization Strategy plugin and when we go to Assign Roles, 
the list is really huge and it's becoming hard day by day to add users.  Is 
there a way to address this issue?

1) We are currently handling these manually.  Is there a way to handle this 
manual (like freeze panes in Windows Excel or something of that sort)?
2) Can we automate this using Ansible as we are going to have Ansible setup 
soon?
--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/43505685-e9c9-41ab-8ba7-312859a42f80%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/43505685-e9c9-41ab-8ba7-312859a42f80%40googlegroups.com?utm_medium=email&utm_source=footer>.
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/AM0PR0302MB3410369F9F3E6291B21D4145CFCC0%40AM0PR0302MB3410.eurprd03.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: can I have concurrent steps in a pipeline?

[Beushausen, Christian]

Hi Don,

Why do step 3 and 4 have to run concurrently?
It sounds to me that burpsuite could be started as step 3, listening for 
connections. Then execute step 4 that runs against the running burpsuite 
instance. As a post step you could then let burpsuite finish processing 
whatever it's doing and then shut it down. Notify and archive afterwards as 
needed.
If step 4 fails have your post step handle the error accordingly.


Mit freundlichen Gruessen/Best regards,

Christian Beushausen
I S&T PD SW SWF
Interior Systems & Technology

Besucheradresse / Visitor address:
Continental Automotive GmbH
Philipsstrasse 1, 35576 Wetzlar, Germany

Rechnungsadresse / Invoice address:
Continental Automotive GmbH
Philipsstrasse 1, 35576 Wetzlar, Germany

Phone: +49 6441 370-9031
Mobile: +49 151 746 602 27
Fax: +49 6441 37013-9031
E-Mail: 
christian.beushau...@continental-corporation.com<mailto:christian.beushau...@continental-corporation.com>

<$$014!>


From: Don Raikes 
Sent: Wednesday, October 17, 2018 5:34:33 PM
To: jenkinsci-users@googlegroups.com
Subject: can I have concurrent steps in a pipeline?

Hi,

I am planning my first pipeline job, but I am not sure how to tell jenkins to 
run two of the steps concurrently.

Job outline:

Step 1. Clone from git
Step 2: build code from repository
Step 3: start burpsuite security proxy
Step 4: run tests on built code.

Steps 3 and 4 need to be run concurrently.  Step 3 starting burpsuite needs to 
start first, then once burpsuite is running step 4 needs to run to proxy my 
tests through burpsuite.  The automated tests in step 4 will finish then 
burpsuite will continue processing for some time after the tests have completed.

What is the best way to accomplish this?  I want Jenkins to notify me when the 
burpsuite processing is complete and to archive the burpsuite reports.

Thanks,
Don

--
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<mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2bba8324-25b6-415f-bd9d-6ddefd99fac6%40default<https://groups.google.com/d/msgid/jenkinsci-users/2bba8324-25b6-415f-bd9d-6ddefd99fac6%40default?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

http://www.continental-corporation.com


Continental Automotive GmbH, Vahrenwalder Str. 9, D-30165 Hannover
Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Helmut Matschi
Geschaeftsfuehrer/Managing Director: Georg Sistermanns, Harald Stuhlmann
Sitz der Gesellschaft/Registered Office: Hannover
Registergericht/Registered Court: Amtsgericht Hannover, HRB 59424
USt.-ID-Nr./VAT-ID-No. DE814950663

__

Proprietary and confidential. Distribution only by express authority of 
Continental AG or its subsidiaries.

-- 
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/AM0PR0302MB3410537FF9CD15E992D82A83CFF80%40AM0PR0302MB3410.eurprd03.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

How to use Jenkins pipeline method parameters in Powershell script?

[Daniel Christian Schröter]

I ask this question already 
on 
https://stackoverflow.com/questions/51622150/how-to-use-jenkins-pipeline-method-parameters-in-powershell-script,
 
but maybe here is someone to help me.

I defined the following method in jenkins declarative pipeline, but I am 
not able to use the variables/output from "serverName", 
"archiveDestination" and "wwwrootPath". I tried already different ways but 
is does not work. The output from Write-Output is still "$serverName", 
${archiveDestination} and/or an empty variable.

How can I access the parameters from the serverdeployment-method in the 
Powershell script part?

def serverdeployment(serverName, archiveDestination, wwwrootPath) {
powershell script: '''
$servername = \'"$serverName"'
$archivedestination = \'${archiveDestination}'
$wwwrootpath = ${wwwrootPath}
Write-Output $servername
Write-Output $archivedestination
Write-Output $wwwrootpath
$pass = ConvertTo-SecureString -AsPlainText "X" -Force
$cred = New-Object System.Management.Automation.PSCredential -ArgumentList 
"X",$pass
$sessionOption = New-PSSessionOption -SkipCACheck -SkipCNCheck 
-SkipRevocationCheck
$session = New-PSSession -ComputerName $serverName -UseSSL -Credential 
$cred -SessionOption $sessionOption
Copy-Item $env:WORKSPACE\\* -Destination "$archiveDestination" -Filter 
*TEST* -Recurse -Force -Verbose -ToSession $session
Invoke-Command -Session $session -ScriptBlock {iisreset /STOP}
$filename = $env:JOB_NAME + "_TEST_" + $env:Version + "_" + 
$env:BUILD_NUMBER + "_wwwroot.7z"
Invoke-Command -Session $session -ScriptBlock { & "C:\\Program 
Files\\7-Zip\\7z.exe" x $using:archiveDestination$using:filename -o$wwwrootpath 
-aoa >$null }
Remove-Item "$wwwrootPath\\*\\_Cache\\*" -Recurse -Force
Invoke-Command -Session $session -ScriptBlock {iisreset /START}
Remove-PSSession $session
Exit-PSSession
'''
}


This method will be executed in steps part:

serverdeployment('myservername', 'C:\\data\\install\\', 
'C:\\inetpub\\wwwroot\\')


Thank you!


-- 
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/092fcb64-1fc8-47c1-98f9-9bcf7af3035f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pushing git tags (created inside Jenkins GUI) to remote

[Christian Ciach]

Hi,

For every git build, there is a disk icon on the left bar saying "No tags". 
This icon can be used to create git tags using the web GUI of jenkins. 
(This triggers "GitTagAction.java" of the git-plugin.)

When creating tags this way, they seem to be only created inside the local 
git reposity of the jenkins workspace. Is there a way to automatically push 
the created tags to the remote server, or at least trigger a job that could 
do it?

Best regards,
Christian

-- 
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/39638533-8107-4fad-affc-d612d6dcec91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Antwort: Parallel Build issue

[Christian . Beushausen]

Hi Somshekar,

We had the same issue with our build environment and I saw that we had 2 
possible solutions.
1. 
https://wiki.jenkins.io/display/JENKINS/Features+controlled+by+system+properties
 
amongst others gives you hudson.slaves.WorkspaceList which you can change 
to set a different token. 
2. use a ws(){} block in your pipeline to change to a different workspace. 
(for declarative Pipeline this is the customWorkspace option of the agent 
keyword (see. https://jenkins.io/doc/book/pipeline/syntax/#agent)

Since I don't control the Jenkins master in our project I used the second 
approach. Especially since I am building in parallel on the same node I am 
reusing the original workspace and all checked out sources and build in a 
new subdirectory of the workspace.

Hope this helps.
Christian

jenkinsci-users@googlegroups.com schrieb am 04.05.2018 07:53:42:

> Von: Somshekar C Kadam 
> An: jenkinsci-users@googlegroups.com
> Datum: 04.05.2018 07:54
> Betreff: Parallel Build issue
> Gesendet von: jenkinsci-users@googlegroups.com
> 
> Hi All, 
> 
> I have setup a parallel build using data pipeline. This build 
> machine is on VM. 
> 
> 
> pipeline {
>  
>  stages {
>  
> stage('ParallelBuild') {
> 
>parallel {
> 
>   stage(‘BuildIntel’) {
>   agent {
>..
>;;;
> 
>stage(‘BuildArm’) {
>agent {
> 
> 
> Workspace for Intel 
> 
> [‘BuildIntel’] 
> [CYELP_feature-3WJHZSTZRAESMPGCATYIL555HUF7XSCPTK2GXMGWNX7W5MCBMX4A]
> 
> Workspace for Arm
> [‘BuildARM’] 
> [CYELP_feature-3WJHZSTZRAESMPGCATYIL555HUF7XSCPTK2GXMGWNX7W5MCBMX4A@2
> 
> Build for Arm is failing 
> [‘BuildARM’] Error, you have an invalid character (@) in your 
> COREBASE directory path. Please move the installation to a directory
> which doesn't include any @ characters.
> 
> as it is same workspace dir wit @2 extra
> 
> to make it build I can create a separate dir in workspace and proceed. 
> Is it the right solution or any other fix is better please suggest 
> 
> thanks in advance
> 
> Regards
> Somshekar C Kadam
> 
> -- 
> 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/CALbGK-pAedn1a8aeFaMYq%3DPWsG44JvjRsqaOe_f-
> zUkYLHitWQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

Mit freundlichen Gruessen/Best regards,

Christian Beushausen
I S&T PD SW SWF
Interior Systems & Technology

Besucheradresse / Visitor address: 
Continental Automotive GmbH
Philipsstrasse 1, 35576 Wetzlar, Germany

Rechnungsadresse / Invoice address: 
Continental Automotive GmbH
Philipsstrasse 1, 35576 Wetzlar, Germany

Telefon/Phone: +49 6441 370-9031
Mobile: +49 151 74660227
Telefax: +49 6441 37013-9031
E-Mail: christian.beushau...@continental-corporation.com

http://www.continental-automotive.com


Continental Automotive GmbH, Vahrenwalder Str. 9, D-30165 Hannover 
Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Helmut 
Matschi 
Geschaeftsfuehrer/Managing Director: Georg Sistermanns, Harald Stuhlmann 
Sitz der Gesellschaft/Registered Office: Hannover 
Registergericht/Registered Court: Amtsgericht Hannover, HRB 59424
USt.-ID-Nr./VAT-ID-No. DE814950663 


Proprietary and confidential. Distribution only by express authority of
Continental AG or its subsidiaries.

-- 
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/OF2CDE8E6F.F579456E-ONC1258283.0050379E-C1258283.00514802%40continental-corporation.com.
For more options, visit https://groups.google.com/d/optout.

Question on behaviour of workflow-multibranch-plugin when building pull requests

[Christian . Beushausen]

Hi all,

I stumbled over a behaviour that I do not quite understand.

In our organisation we have a couple of Jenkins master running. Mixed 
between Linux based and Windows based masters.
We have one Java application repository where the responsible team created 
a Jenkins Multibranch Pipeline project on a Linux master. On this 
environment the build of pull requests runs w/o problems. This job was now 
moved to a Windows based Jenkins master and we see the following problems 
with the pull requests:

hudson.plugins.git.GitException: Command "git checkout -f 
a2e753c586b2dbf4ea2a101d49dcaa9cf0710147" returned status code 128:
stdout: 
stderr: error: unable to create file : Filename too long

Builds for existing branches on the other hand can successfully run on 
both instances.
The main difference I saw is that for the pull request build the 
repository is initially checked out on master:
Checking out git  into 
D:\casdev\.jenkins\workspace\vel_sw.tool.cofmk_gen_PR-22-JEYJ4XXNXUAUGONVULFEJEDR366W2SMKOHDDE7J4CPPY7OCPAJSQ@script
 
to read Jenkinsfile

Whereas the master branch build does not perform this checkout on the 
Jenkins master.

Could you let me know if this is the expected behaviour and if you are 
aware of any possible workarounds?


Mit freundlichen Gruessen/Best regards,

Christian Beushausen
I S&T PD SW SWF
Interior Systems & Technology

Besucheradresse / Visitor address: 
Continental Automotive GmbH
Philipsstrasse 1, 35576 Wetzlar, Germany

Rechnungsadresse / Invoice address: 
Continental Automotive GmbH
Philipsstrasse 1, 35576 Wetzlar, Germany

Telefon/Phone: +49 6441 370-9031
Mobile: +49 151 74660227
Telefax: +49 6441 37013-9031
E-Mail: christian.beushau...@continental-corporation.com

http://www.continental-automotive.com


Continental Automotive GmbH, Vahrenwalder Str. 9, D-30165 Hannover 
Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Helmut 
Matschi 
Geschaeftsfuehrer/Managing Director: Georg Sistermanns, Harald Stuhlmann 
Sitz der Gesellschaft/Registered Office: Hannover 
Registergericht/Registered Court: Amtsgericht Hannover, HRB 59424
USt.-ID-Nr./VAT-ID-No. DE814950663 


Proprietary and confidential. Distribution only by express authority of
Continental AG or its subsidiaries.

-- 
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/OF6ADE8291.8637CFC1-ONC1258273.0054B5A2-C1258273.0054ED55%40continental-corporation.com.
For more options, visit https://groups.google.com/d/optout.

AWS EC2/ECS and parallel dockerised stages

[Christian Gagneraud]

Hi there,

>From within a pipeline i would like to generate parallel jobs, and i
want all these jobs to run as ECS tasks using different specialised
docker images.
Can I use this syntax to achieve that?

stages {
  stage ('Parallel builds') {
parallel {
  stage ('Build#1') {
   agent { docker 'image1' }
   ...
  }
  stage ('Build#2') {
   agent { docker 'image2' }
   ...
  }
   }
}
---

>From my experiments, I have the feeling that Jenkins will spawn
dockerised slaves in parallel for each parallel stage (good), but the
docker container will run within the EC2 instance ($DOCKER_HOST), and
thus it won't take advantage of CPU scaling (bad).

Right now, my ECS slave template is configured to use an image which
is just jenkins-jnlp + docker client.

Do I have to create one template per docker image and use "agent {
label '...' }" in place of "agent { docker '...' }"?

This looks weird to me.

Sorry if the question sounds stupid, i'm not that familiar with
Jenkins and Amazon ECS.

Thanks,
Chris

-- 
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/CABxGUTjM%2BE1pw-ZSnR7cu0JSc_TpuBJYGPHFkGMsQ0sG%2BONggw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Windows agent can't delete workspace

[Christian Gagneraud]

On 18 March 2018 at 03:21, Sean Talts  wrote:
> Hey all,
>
> I'm having this sudden crazy problem where my Windows agent can't delete
> some files in its workspace anymore, failing all builds. It's getting a
> java.nio.file.AccessDeniedException on some files that it created. You can
> see the full exceptions at the end of the log here:
> http://d1m1s1b1.stat.columbia.edu:8080/job/Stan/job/develop/80/console also
> copied below.
>
> I've tried so many things, including switching JVMs on master and agent,
> upgrading and switching to LTS, uninstalling and reinstalling a new agent
> service in a new working directory… Any tips or advice would be extremely
> appreciated; been trying to solve this all day and night since it started
> Thursday when the master rebooted during a job on the Windows agent.

We have thins kind of errors on Windows when there are still running
processes that have a file descriptor opened.
You could log on to the machine and check if there are any "zombie" processes.

Chris

>
> Thanks in advance,
> Sean
>
> Full error:
>
> java.nio.file.AccessDeniedException:
> C:\Jenkins2\workspace\Stan_develop-3CVGV42HAM7J3BLI3M44PCR6M52FN6ZQ65IEZ6TOSHJURSBO2PPA\src\test\test-models\bad\read_only
> at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
> at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
> at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown Source)
> at java.nio.file.Files.deleteIfExists(Unknown Source)
> at hudson.Util.tryOnceDeleteFile(Util.java:297)
> at hudson.Util.deleteFile(Util.java:253)
> Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to
> JNLP4-connect connection from
> gelman-group-win.stat.columbia.edu/128.59.76.64:50229
> at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1737)
> at hudson.remoting.UserResponse.retrieve(UserRequest.java:313)
> at hudson.remoting.Channel.call(Channel.java:952)
> at hudson.FilePath.act(FilePath.java:998)
> at hudson.FilePath.act(FilePath.java:987)
> at hudson.FilePath.deleteRecursive(FilePath.java:1192)
> at
> org.jenkinsci.plugins.workflow.steps.DeleteDirStep$Execution.run(DeleteDirStep.java:77)
> at
> org.jenkinsci.plugins.workflow.steps.DeleteDirStep$Execution.run(DeleteDirStep.java:69)
> at
> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49)
> at hudson.security.ACL.impersonate(ACL.java:290)
> at
> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused: java.io.IOException: Unable to delete
> 'C:\Jenkins2\workspace\Stan_develop-3CVGV42HAM7J3BLI3M44PCR6M52FN6ZQ65IEZ6TOSHJURSBO2PPA\src\test\test-models\bad\read_only'.
> Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.
> at hudson.Util.deleteFile(Util.java:258)
> at hudson.FilePath.deleteRecursive(FilePath.java:1225)
> at hudson.FilePath.deleteContentsRecursive(FilePath.java:1234)
> at hudson.FilePath.deleteRecursive(FilePath.java:1216)
> at hudson.FilePath.deleteContentsRecursive(FilePath.java:1234)
> at hudson.FilePath.deleteRecursive(FilePath.java:1216)
> at hudson.FilePath.deleteContentsRecursive(FilePath.java:1234)
> at hudson.FilePath.deleteRecursive(FilePath.java:1216)
> at hudson.FilePath.deleteContentsRecursive(FilePath.java:1234)
> at hudson.FilePath.deleteRecursive(FilePath.java:1216)
> at hudson.FilePath.deleteContentsRecursive(FilePath.java:1234)
> at hudson.FilePath.deleteRecursive(FilePath.java:1216)
> at hudson.FilePath.access$1100(FilePath.java:208)
> at hudson.FilePath$13.invoke(FilePath.java:1195)
> at hudson.FilePath$13.invoke(FilePath.java:1192)
> at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2816)
> at hudson.remoting.UserRequest.perform(UserRequest.java:210)
> at hudson.remoting.UserRequest.perform(UserRequest.java:53)
> at hudson.remoting.Request$2.run(Request.java:364)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at hudson.remoting.Engine$1$1.run(Engine.java:94)
> at java.lang.Thread.run(Unknown Source)
> Also:   java.nio.file.AccessDeniedException:
> C:\Jenkins2\workspace\Stan_develop-3CVGV42HAM7J3BLI3M44PCR6M52FN6ZQ65IEZ6TOSHJURSBO2PPA\src\test\test-models\bad\stanc_helper

Re: Problems with (Declarative) pipeline in AWS ECS

[Christian Gagneraud]

On 17 March 2018 at 21:15, Christian Gagneraud  wrote:
[...]
> It looks to me that the templated jenkins-slave container doesn't
> share /homme/jenkins with it's host, and so side containers
> (python:2.7 in my case) cannot inherit them.
>
> Does anyone know what sort of tweaking are required for such a setup?
> Do i need to customised the EC2 docker host? I'm running the default
> AWS AMI Linux.

I managed to troubleshoot a bit the problem, I don't have a proper
fix, but this should help understand what's going wrong:

I first noticed on the EC2 docker host that /home/jenkins and all
subdirs were owned by root.
So i decided to create a jenkins user/group with id 1 in the EC2
docker host.
I then made sure that my chgans/jenkins-slave-ecs container run the
entry point as user jenkins.
I added the mount point
"/home/jenkins/workspace:/home/jenkins/workspace" in my ECS slave
template.

But his was not enough, /home/jenkins was owned by jenkins.jenkins
(created via adduser command), but the workspace sub-directory was
automatically created and owned by root.

So I manually created /home/jenkins/workspace and made sure it was
owned by jenkins.jenkins.

Now when i run a job, the templated jenkins slave can clone stuff in
it's workspace, with the right ownership with regards to the docker
host.
The declarative pipeline plugin then creates the sister containers
(python:2.7 in my case) from within the jenkins slave, using
'--volumes-from ' and '-u 1:1'.

Which lead me to the following questions:
- do I have to setup my own EC2 and make sure it has a jenkins user?
- Who is creating /home/jenkins/workspace as root, and why?
- Why do I have to share workspace, shouldn't /home/jenkins/agent be
all what is necessary?

Thanks,
Chris

-- 
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/CABxGUTiEuu%3DKgWNVu__pTfi%2BH0hcZBAz%3Dm2Bx2XEj1H%2Bc2kyEQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Problems with (Declarative) pipeline in AWS ECS

[Christian Gagneraud]

Hi there,

Running Jenkins 2.89.4 (BlueOcean), with Amazon EC2 Container Service
plugin v 1.11

I have successfully setup my self-hosted docker host connected to
jenkins using the "docker cloud" plugin, i can get this cloud execute
declarative pipelines that needs docker container such as:
--
pipeline {
agent { docker 'python:2.7'}
stages {
stage('Dummy stage') {
steps {
sh 'python --version'
}
}
}
}
--

I have successfully setup an Amazon ECS connected to jenkins using the
"Amazon EC2 Container Service plugin", i can get this cloud execute
dead-simple job: no git repo, just execute a few shell commands such
as:

echo "Hello world! From Amazon ECS"


The console output says:
-
Started by user admin
Building remotely on ecs-builder-de-35016db04c851 (ecs-de.cloud) in
workspace /home/jenkins/workspace/test-aws
[test-aws] $ /bin/sh -xe /tmp/jenkins8406299037257519290.sh
+ echo Hello world! From Amazon ECS.
Hello world! From Amazon ECS.
Finished: SUCCESS
--

When i try to execute a job from my project that uses the declarative
pipeline, the last step (the "Dummy stage") fails with:
---
sh: 1: cannot create
/home/jenkins/workspace/tion_feature_gfdgfgfdgfdgfd-KZ7OXHZWKOBIKEE7D6XZOM3UNTYU5DGJSLNIET2I5IITHIBHBWPA@tmp/durable-e5c611c5/jenkins-log.txt:
Directory nonexistent
---

To reach this stage i'm using a custom ECS slave templates:
---
Template Name  = jenkins-slave
Label = docker.jenkins.slave
Docker Image = chgans/jenkins-slave-ecs:latest
Filesystem root = /home/jenkins
Soft Memory Reservation = 1024
Hard Memory Reservation = 0
CPU units = 1
DNS Search Domains
Task Role ARN
Override entrypoint
JVM arguments
Privileged
Logging Driver
Logging Configuration
Environments
Extra Hosts
Container Mount Points
  Name = docker_socket
  source Path = /var/run/docker.sock
  Container Path = /var/run/docker.sock
  Read Only
---

The custom docker image deals mainly with user/group issues.

When i execute the pipeline, here is what i get in the console output:
Note: The project name is "application", and the pull request is
"feature/gfdgfgfdgfdgfd"
---
Started by user admin
Obtained Jenkinsfile from 955ff5122ac1ab67ff8b70743d0a2064a63ceb9a
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on ecs-builder-de-352c7774fa56f in
/home/jenkins/workspace/tion_feature_gfdgfgfdgfdgfd-KZ7OXHZWKOBIKEE7D6XZOM3UNTYU5DGJSLNIET2I5IITHIBHBWPA
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
< ... snipped git stuff ...>
 > git checkout -f 955ff5122ac1ab67ff8b70743d0a2064a63ceb9a
Commit message: "Jenkinsfile edited online with Bitbucket"
 > git rev-list --no-walk 955ff5122ac1ab67ff8b70743d0a2064a63ceb9a # timeout=10
[Bitbucket] Notifying commit build result
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Agent Setup)
[Pipeline] sh
[tion_feature_gfdgfgfdgfdgfd-KZ7OXHZWKOBIKEE7D6XZOM3UNTYU5DGJSLNIET2I5IITHIBHBWPA]
Running shell script
+ docker pull python:2.7
2.7: Pulling from library/python
Digest: sha256:83b5b650aadb1c85a9764da0e7f6e4caa8dbb4c387ced0aca6ff510980576f31
Status: Image is up to date for python:2.7
[Pipeline] }
[Pipeline] // stage
[Pipeline] sh
[tion_feature_gfdgfgfdgfdgfd-KZ7OXHZWKOBIKEE7D6XZOM3UNTYU5DGJSLNIET2I5IITHIBHBWPA]
Running shell script
+ docker inspect -f . python:2.7
.
[Pipeline] withDockerContainer
ecs-builder-de-352c7774fa56f seems to be running inside container
52fcf60dcae91c7bab6a1ec17209482018f1dc528264360b2d1706209e681086
but 
/home/jenkins/workspace/tion_feature_gfdgfgfdgfdgfd-KZ7OXHZWKOBIKEE7D6XZOM3UNTYU5DGJSLNIET2I5IITHIBHBWPA
could not be found among [/home/jenkins/.jenkins, /home/jenkins/agent,
/var/run/docker.sock]
but 
/home/jenkins/workspace/tion_feature_gfdgfgfdgfdgfd-KZ7OXHZWKOBIKEE7D6XZOM3UNTYU5DGJSLNIET2I5IITHIBHBWPA@tmp
could not be found among [/home/jenkins/.jenkins, /home/jenkins/agent,
/var/run/docker.sock]
$ docker run -t -d -u 1:1 -w
/home/jenkins/workspace/tion_feature_gfdgfgfdgfdgfd-KZ7OXHZWKOBIKEE7D6XZOM3UNTYU5DGJSLNIET2I5IITHIBHBWPA
-v 
/home/jenkins/workspace/tion_feature_gfdgfgfdgfdgfd-KZ7OXHZWKOBIKEE7D6XZOM3UNTYU5DGJSLNIET2I5IITHIBHBWPA:/home/jenkins/workspace/tion_feature_gfdgfgfdgfdgfd-KZ7OXHZWKOBIKEE7D6XZOM3UNTYU5DGJSLNIET2I5II

Re: Logs inside BlueOcean do not get updated automatically

[Christian Ciach]

This happens for me with Firefox and with Chromium. Also, it doesn't matter 
how long the tab has been open; it happens with freshly opened tabs, too.

As I see, there is already a pull request that supposedly fixes that. 

I really wonder that noone else reported this in the several weeks I've 
experienced this issue, so I was almost sure the issue was on my side. 
That's the reason I didn't create a ticket at the issue tracker. 

I even started over again with a completely fresh installation with only 
the most essential plugins (like Blue Ocean), but the issue remained. I 
tried to debug it using the developer tools of Firefox, but there are no 
obvious javascript errors or .js-files that failed to load.

Thanks for your quick answers and for creating JENKINS-49929 for me!

Best regards

Am Montag, 5. März 2018 23:11:15 UTC+1 schrieb R Tyler Croy:
>
> (replies inline) 
>
> On Mon, 05 Mar 2018, Vivek Pandey wrote: 
>
> > Hi Christian, 
> > 
> > This looks like regression. I have opened 
> > https://issues.jenkins-ci.org/browse/JENKINS-49929, we are going to 
> take a 
> > look at it. Thanks for reporting. 
>
>
>
> Christian, are you using Firefox perhaps? I've noticed that "Karoake mode" 
> seems to stop when I switch away from Blue Ocean tabs for too long of time 
> while a a Pipeline is running. 
>
> Josh speculated in Gitter that this might be somehow related to recent 
> Firefox 
> features which "quiet" the background tabs. 
>
>
>
> > 
> > On Mon, Mar 5, 2018 at 6:08 AM Christian Ciach  > wrote: 
> > 
> > > Hello, 
> > > 
> > > I wish I could describe this issue better, but I have no idea how to 
> debug 
> > > this. 
> > > 
> > > I am using the current version of Jenkins (2.106) with BlueOcean 
> (1.4.2) 
> > > on CentOS. 
> > > 
> > > Usually, I would expect the logs inside BlueOcean to automatically 
> update 
> > > themself when my build logs new stuff, but this is not the case. I 
> think 
> > > the developers call this the "karaoke mode". 
> > > 
> > > Watching the live log works nicely using the classic view at the URL 
> > > "/job/JOBNAME/JOBNUMBER/console". But with BlueOcean, I have to 
> refresh the 
> > > whole page to see the updated log. 
> > > 
> > > How can I even begin to debug this? 
> > > 
> > > Best regards, 
> > > Christian Ciach 
> > > 
> > > -- 
> > > 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/0120b425-2c72-4abd-8af5-89a9fdacdb96%40googlegroups.com
>  
> > > <
> https://groups.google.com/d/msgid/jenkinsci-users/0120b425-2c72-4abd-8af5-89a9fdacdb96%40googlegroups.com?utm_medium=email&utm_source=footer>
>  
>
> > > . 
> > > For more options, visit https://groups.google.com/d/optout. 
> > > 
> > -- 
> > Sent from my iPhone 
> > 
> > -- 
> > 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/CAKT4V18LBW8%2Bfq_mWmn_UBym87TdfnO_e_8PXpkvbArk%3DfYm8A%40mail.gmail.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
> - R. Tyler Croy 
>
> -- 
>  Code: <https://github.com/rtyler> 
>   Chatter: <https://twitter.com/agentdero> 
>  xmpp: rty...@jabber.org  
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F 
> -- 
>

-- 
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/60a481ec-326b-453c-8ba9-d0f37af9a1ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

"Bitbucket Team/Project"

[Christian Gagneraud]

I'm trying the "Bitbucket Team/Project" (which uses the "multibranch Pipeline").
Using "jenkinsci/blueocean:latest" docker image.

When i create a new ""Bitbucket Team/Project"" item, the BB project is
scanned, project is added and repo too. Repo that have a
"/Jenkinsfile" are picked up and built, everything seems to work as
expected.

Now when i go to one of the generated "multibranch pipeline" job, and
click the "View configuration" (no "Configure" accessible), I land on
a page that allows me to edit the job, but I get a Jenkins screenshot
showing "admin is missing Job/Configure permission" in between
"repository name" and "Behaviors" on the
https://jenkins-url/job/job-name/configure page.

When I manually create a custom multi-branch pipeline job with the
same bitbucket branch source, i do not see this message at all, and
there is nothing b/w "repository name" and "Behaviors".

Did I misconfigured something? The admin account is created suing a
pre-configure groovy hook:

-
def instance = Jenkins.getInstance()

def user = "admin"
def pass = "..."
def hudsonRealm = new HudsonPrivateSecurityRealm(false)
hudsonRealm.createAccount(user, pass)
instance.setSecurityRealm(hudsonRealm)

def strategy = new FullControlOnceLoggedInAuthorizationStrategy()
strategy.setAllowAnonymousRead(false)
instance.setAuthorizationStrategy(strategy)
instance.save()
-

Is it the cause of my problem?

Does anyone has example on how to use `RoleBasedAuthorizationStrategy`
from a groovy script?
I was stuck b/c I couldn't call the private `createAdminRole()` method
(and I'm an absolute noob with groovy and jenkins scripting)

Thanks,
Chris

-- 
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/CABxGUTh%2BP6CRWAD0uMrOhgYFMmqv37WeA5PNpkDZLAW9BT61gQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Logs inside BlueOcean do not get updated automatically

[Christian Ciach]

Hello,

I wish I could describe this issue better, but I have no idea how to debug 
this.

I am using the current version of Jenkins (2.106) with BlueOcean (1.4.2) on 
CentOS. 

Usually, I would expect the logs inside BlueOcean to automatically update 
themself when my build logs new stuff, but this is not the case. I think 
the developers call this the "karaoke mode".

Watching the live log works nicely using the classic view at the URL 
"/job/JOBNAME/JOBNUMBER/console". But with BlueOcean, I have to refresh the 
whole page to see the updated log.

How can I even begin to debug this?

Best regards,
Christian Ciach

-- 
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/0120b425-2c72-4abd-8af5-89a9fdacdb96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [solved] Re: Docker cloud plugin and pipeline using docker

[Christian Gagneraud]

On 27 February 2018 at 04:55, nicolas de loof  wrote:
> For a dockerized agent to be able to run docker pipeline, it has to use a
> volume for workspace directory so this one can be shared with other
> containers it creates.
> Your docker agent template should be configured to use "/home/jenkins/agent"
> as agent root directory, as this one is a volume and as such workspace
> sub-folder will be shareable with other containers.

Thanks a lot for the tip, greatly appreciated!

Chris

-- 
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/CABxGUTj7dV1DDcgmBMd6rc7KxO767%3DSZ%2BqZLeE%3DSqHhXWGvBaQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[solved] Re: Docker cloud plugin and pipeline using docker

[Christian Gagneraud]

On 26 February 2018 at 15:29, Christian Gagneraud  wrote:
> On 26 February 2018 at 03:10, nicolas de loof  
> wrote:
>> docker support in declarative pipeline relies on docker-workfow plugin,
>> which require the jenkins slave to have access to a LOCAL docker daemon,
>> which means the docker agent you are provisioning on computer B using docker
>> plugin HAS to be configured with /var/run/docker.sock (so, the one from B)
>> bind mounted. Doing so it can then create some side container to host the
>> build steps.
>
> Hi Nicolas,
>
> Thanks for the tips, i think i'm getting there, but i'm still missing some 
> bits:
> - I have created a docker image based on jenkinsci/jnlp-slave, the
> only customisation is installing docker in it
> - The pipeline now get checkout inside tmy slave (on machine B)
> - The docker image from the Jenkinsfile is pulled and executed.
>
> But i get this weird error (see full log at the end of this email):
> 
> docker-44734997459c on work-leader seems to be running inside
> container e7f7a4381e32c456b806695b9b7334751d88f1a3985867bb964e9fd3d2e8c948
> but 
> /home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q
> could not be found among [/home/jenkins/.jenkins, /home/jenkins/agent]

Google didn't return much with "could not be found among"

https://stackoverflow.com/questions/47559469/jenkins-declarative-pipeline-docker-agent-timeout-run?rq=1
https://tutel.me/c/programming/questions/46530963/run+jenkins+agent+in+docker+container+issue+with+jenkins+pipeline+and+varrundockersocket

Not very useful, but using google's "repeat the search with the
omitted results included.", I got a few extra results, one of them, an
IRD log, that gave me the answer:
https://echelog.com/logs/browse/jenkins/1497304800

I had to add /home/jenkins in the "Volumes" of the "Docker Agent
templates" (as well as "Remoting Filling System Root", but this was
set by default).
I noticed as well that if no "user" is specified in the "Connect
method"/"Attach Docker Container", the Python image script will be run
with id 1000:1000, which does not exists. But this doesn't seem to be
a problem. (user=root is not required, nor is "Run container
privileged").

Thanks!
Chris

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

Re: Docker cloud plugin and pipeline using docker

[Christian Gagneraud]

On 26 February 2018 at 03:10, nicolas de loof  wrote:
> docker support in declarative pipeline relies on docker-workfow plugin,
> which require the jenkins slave to have access to a LOCAL docker daemon,
> which means the docker agent you are provisioning on computer B using docker
> plugin HAS to be configured with /var/run/docker.sock (so, the one from B)
> bind mounted. Doing so it can then create some side container to host the
> build steps.

Hi Nicolas,

Thanks for the tips, i think i'm getting there, but i'm still missing some bits:
- I have created a docker image based on jenkinsci/jnlp-slave, the
only customisation is installing docker in it
- The pipeline now get checkout inside tmy slave (on machine B)
- The docker image from the Jenkinsfile is pulled and executed.

But i get this weird error (see full log at the end of this email):

docker-44734997459c on work-leader seems to be running inside
container e7f7a4381e32c456b806695b9b7334751d88f1a3985867bb964e9fd3d2e8c948
but 
/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q
could not be found among [/home/jenkins/.jenkins, /home/jenkins/agent]
but 
/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q@tmp
could not be found among [/home/jenkins/.jenkins, /home/jenkins/agent]
$ docker run -t -d -u 1:1 -w
/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q
-v 
/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q:/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q:rw,z
-v 
/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q@tmp:/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q@tmp:rw,z
-e  -e  -e  -e  -e  -e
 -e  -e  -e  -e  -e 
-e  -e  -e  -e  -e  -e
 -e  -e  -e  -e  -e 
-e  -e  -e  -e  -e  -e
 python:2.7 cat
$ docker top 20801bdc7f7f4777b89a864c2cd52b03e3906d02ad3c708df4c4cdc5ebe4f45b
-eo pid,comm
[Pipeline] {
[Pipeline] stage
[Pipeline] { (dummy)
[Pipeline] sh

[aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q]
Running shell script
sh: 1: cannot create
/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q@tmp/durable-f19371c8/jenkins-log.txt:
Directory nonexistent
sh: 1: cannot create
/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q@tmp/durable-f19371c8/jenkins-result.txt:
Directory nonexistent

process apparently never started in
/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q@tmp/durable-f19371c8
---

work-leader is machine B, docker-44734997459c is, I believe, an
instance of my custom jnlp-slave, as you can see the slave fails to
run the python container

I wonder if this could be some permissions issues, for now machine B
is a VBox managed using vagrant, on it I can see that:
vagrant@leader:~$ ls -l /home/jenkins/workspace/
total 8
drwxr-xr-x 2 root root 4096 Feb 26 02:02
aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q
drwxr-xr-x 2 root root 4096 Feb 26 02:02
aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q@tmp
vagrant@leader:~$ ls -la /home/jenkins/workspace/*
/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q:
total 8
drwxr-xr-x 2 root root 4096 Feb 26 02:02 .
drwxr-xr-x 4 root root 4096 Feb 26 02:02 ..

/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q@tmp:
total 8
drwxr-xr-x 2 root root 4096 Feb 26 02:02 .
drwxr-xr-x 4 root root 4096 Feb 26 02:02 ..

Any idea?
Chris

Here is my Dockerfile (jenkins-slave-agent):
-
FROM jenkinsci/jnlp-slave
USER root
curl -sfL -o docker.tgz https:// && tar -C /usr/bin -xzf
docker.tgz && rm docker.tgz
USER jenkins
-

And the project's Jenkinsfile:
--
pipeline {
agent { docker 'python:2.7'}
stages { stage('dummy') { steps { sh 'python --version' } } }
}
--

Full build log:
--
Started by user admin
Obtained Jenkinsfile from 0be91558399793412462578e0061fef50a7919c3
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on docker-44734997459c on work-leader in
/home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YKHSBXYJPJLEX7A2AM6K5M6Q
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
Cloning repository https://code.nav

Docker cloud plugin and pipeline using docker

[Christian Gagneraud]

Hi there,

I have a machine A that runs Jenkins and Bitbucket-server in docker containers.
I have a machine B, that just has docker listening over tcp.
I have a project that uses Declarative pipeline with "agent { docker
'foobar:X.Y'}"
I'm using "jenkinsci/blueocean:latest" docker image with
"docker-workflow v1.15" plugin.

Ignoring machine B (for now), my setup is working:
- 1. A dev open a pull-request on bitbucket
- 2. The declarative pipline is executed by jenkins
- 3. The docker container(s) specified in the Jenkinsfile are executed
by machine A
- 4. The pipeline finished
- 5. Jenkins notify Bitbucket.

>From a docker point of view, for the above to work, I simply need to
run the Jenkins container with --volume
/var/run/docker.sock:/var/run/docker.sock

Now, I would like to achieve 3 things:
- Leave machine A runs non-build services only
- Use machine B to spawn containers as directed by declarative pipelines.
- Eventually make machine B a docker swarm manager, and let other
docker swarm workers join in if/when needed.

The first modification I did to the jenkins container is to remove the
"/var/run/docker.sock" volume. This is to make sure jenkins can only
talk to the remote docker I configure.

I have then tried 3 plugins:
- "docker plugin" https://plugins.jenkins.io/docker-plugin
- "docker swarm" https://plugins.jenkins.io/docker-swarm
- "Yet another docker plugin"
https://plugins.jenkins.io/yet-another-docker-plugin

All of them add a type of "cloud providers", but I never managed to
get my pipeline executed using one.

The "docker plugin" is the only one that gave me the feeling I was almost there:
The job was handled by a docker container spawn on machine B, which i
had to specify the image name (From examples and tutorials, i settled
down on "jenkinsci/jnlp-slave" in "Launch attached" mode).
But at that stage, I got an error "docker: command not found" emitted
from the jnlp-slave container.
The reason being that Jenkins master contacted docker on machine B to
execute a "jenkinsci/jnlp-slave", and then ask this
"jenkinsci/jnlp-slave" to execute the pipeline, which is an operation
that requires to instantiate the docker containers specified in the
project's pipeline...

So I would like to know if the "docker-plugin" is the right tool for
my job or should I head in another direction.
In case "docker-plugin" is the way to go, then how do I tell my
customised jnlp-slave to connect to the right docker daemon? Is there
an off-the-shelf docker image to play that role? I couldn't find
documentation on how to create it, and the specificites of having
docker inside it.

As a side note:
I found a bit inefficient to have to instantiate Jenkins slave
container whose sole purpose is to read the pipeline and spawn
containers as directed by the pipeline.
Ideally I would like the pipeline to be parsed by Machine A (jenkins
master) and the required containers to be executed on machine B, I do
not know if volumes (jenkins workspace) can be shared across 2 docker
daemons thought...

Any opinion or advice are very welcome, point-out of any sort would be
greatly appreciated too.

Thanks,
Chris

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

Re: Is there a way to name shell scripts for BlueOcean?

[Christian]

I like the second approach. Thank you.

Am Dienstag, 12. Dezember 2017 20:35:44 UTC+1 schrieb Victor Martinez:
>
> IIRC, you cannot label them but you can use the suggested approach as 
> explained here 
> 
>  
>
> and the view will be something like the example shown in this thread 
>  
>
> 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/4d013ac0-4682-45ef-93b4-c92dc52f05d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Is there a way to name shell scripts for BlueOcean?

[Christian]

Hello,

I use a lot of shell scrips in my Jenkinsfile and I am not satisfied with 
the labels in the BlueOcean step overview.
According to https://issues.jenkins-ci.org/browse/JENKINS-36933 it is 
resolved but I have not found a way to label them.

Is there any way to set custom names to them?

Regards,
Christian

-- 
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/08577e5e-e61f-4a49-80c8-18c32c2213ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins build unstable while loading artifact from repo.maven.org instead of internal Nexus.

[Christian]

Hello,

one of my build gets "UNSTABLE" while downloading two artifact from the 
Arquillian deployment dependencies. For some reason it does not load the 
dependency from the internal Nexus repository which does contain the 
required artifacts. This is the message in the logs:

Nov 15, 2017 10:17:19 AM 
org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener 
transferFailed
WARNUNG: Failed downloading 
com/fasterxml/jackson/datatype/jackson-datatype-jsr310/2.7.4/jackson-datatype-jsr310-2.7.4.pom
 from https://repo.maven.apache.org/maven2/. 
 Reason: 
org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer 
artifact com.fasterxml.jackson.datatype:jackson-datatype-jsr310:pom:2.7.4 
from/to central (https://repo.maven.apache.org/maven2): Error transferring 
file: repo.maven.apache.org
Nov 15, 2017 10:17:19 AM 
org.jboss.shrinkwrap.resolver.impl.maven.logging.LogTransferListener 
transferFailed
WARNUNG: Failed downloading 
com/fasterxml/jackson/datatype/jackson-datatype-jsr310/2.7.4/jackson-datatype-jsr310-2.7.4.pom
 from http://repo1.maven.org/maven2/.  Reason: 
org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer 
artifact com.fasterxml.jackson.datatype:jackson-datatype-jsr310:pom:2.7.4 
from/to central (http://repo1.maven.org/maven2): Error transferring file: 
repo1.maven.org


I have scanned the project; nowhere is the repo.maven.org repo set. All 
other dependencies declared in the pom gets downloaded from the internal 
Nexus.

I use the Config File Provider Plugin to set some options:

   - POM is set to "pom.xml"
   - Goals and options: clean verify
   - use private maven repository
  - strategy: Default (~/.m2/repository)
   - settings file: provided settings
  - I selected the settings file I created in the managed config files.
   
I have some pre-build steps set to build two of the sub projects first. 
They don't fail, only one of the following sub projects. 

Do you have any ideas what I am doing wrong here?

Thanks in advance.

-- 
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/92beec18-768a-46f7-9e78-ef4585bae3ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Select checkout branch dependent on a build parameter

[Christian]

Hello,

I have a question. I need to select the branch to checkout dependent on a 
build parameter. And the branch name does *not* equal the parameters. If 
the parameter equals foo1 I need to checkout branch origin/bar1 and for 
foo2 origin/bar2. Is that possible? 

I could only get that far that I can checkout different branches when using 
the build parameter directly (origin/{$build_param}). I thought about 
setting a variable with the EnvInject Plugin, but it seems that the 
checkout step cannot access these variables, or am i missing something 
there?

It is a maven build, no pipeline

thank you and best regards,
Christian

-- 
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/5d6ab08f-68a2-412b-b599-1cb285b94103%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Can't create freeStyleJobs, getting "IllegalArgumentException: Expected named arguments"

[Christian]

Hello,

I am trying to use the nexus-artifact-uploader-plugin to upload the 
packaged war files to my nexus 3 repository. The nexus-artifact-uploader 
provides an example which I modified, but for some reason it already fails 
when it gets to the name.

This is my code:

def uploadToNexus(module) {
  def groupId = "com.example"
  def moduleVersions = [
  "client-module": "1.0.0-SNAPSHOT",
  "server-module": "1.0.0-SNAPSHOT",
  ]

  def moduleVersion = moduleVersions.get(module)
  def jobName = "${fixModuleName(module)}NexusArtifactUploaderJob"

  echo "will run freeStyleJob ${jobName} now..."
  freeStyleJob(jobName) {
steps {
  nexusArtifactUploader {
nexusVersion('nexus3')
protocol('http')
nexusUrl('nexus:8081')
groupId(groupId)
version(moduleVersion)
repository('maven2_central')
credentialsId('nexus_admin')
artifact {
  artifactId('${module}')
  type('war')
  classifier('debug')
  file('${module}.war')
}
  }
}
  }}


When I run this on Jenkins I get the following error:

java.lang.IllegalArgumentException: Expected named arguments but got 
[clientmoduleNexusArtifactUploaderJob, 
org.jenkinsci.plugins.workflow.cps.CpsClosure2@63d801fc]
  at org.jenkinsci.plugins.workflow.cps.DSL.parseArgs(DSL.java:511)
  at org.jenkinsci.plugins.workflow.cps.DSL.invokeDescribable(DSL.java:291)
  at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153)
  at 
org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108)
  at sun.reflect.GeneratedMethodAccessor463.invoke(Unknown Source)
  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:498)
  ...



I checked many sites and tried to find my error but it just won't work. I 
also tried to pass a static string instead of a variable but it doesn't 
work either.

What can I do now?

-- 
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/f2a6b0b7-3c39-40a4-b9bf-3fd3d03af2cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean: Is it possible to populate the column "message" from a pipeline script?

[Christian Kerth]

Posted on wrong list before but already 
answered: https://groups.google.com/d/msg/jenkinsci-dev/Odm2GnXNI40/YvIUZL9HBAAJ

On Monday, April 3, 2017 at 3:20:41 PM UTC+2, Christian Kerth wrote:
>
> Is it possible to manually populate the message column in the run overview 
> page for a pipeline? 
>
> I don't use the commit feature and want to display different information 
> there. Classic UI had e.g. manager.addShortText.
>
>
> <https://lh3.googleusercontent.com/-TAKUaUdCmEA/WOJL5PheexI/FJg/D9M3apUpW9I6Lnbikghz3IHlreZMMYoRQCLcB/s1600/blue.PNG>
>
>

-- 
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/c2ac3aa3-cf90-4b69-838d-2a2524b481b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Blue Ocean: Is it possible to populate the column "message" from a pipeline script?

[Christian Kerth]

Is it possible to manually populate the message column in the run overview 
page for a pipeline? 

I don't use the commit feature and want to display different information 
there. Classic UI had e.g. manager.addShortText.



-- 
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/67f2e6b4-2828-4320-a282-f6388d7f2519%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[christian polzer]

Thanks again... 

it is hurting, thou:)

On Wednesday, February 15, 2017 at 2:24:56 PM UTC+1, Daniel Beck wrote:
>
>
> > On 15.02.2017, at 14:21, christian polzer  > wrote: 
> > 
> > Should i report that with lts version and version of all plugins?? 
>
> You're overriding PATH in an unsupported way. See JENKINS-41339 for 
> solutions. 
>
>

-- 
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/f54a26e9-42d3-41f0-9541-ef1025a47462%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[christian polzer]

Ok.

updating the plugins did enable the new declarative poipeline, but disabled 
usage of everything path related.. shell "sh"  steps:

Running shell script
nohup: failed to run command ‘sh’: No such file or directory


Should i report that with lts version and version of all plugins??



On Tuesday, February 14, 2017 at 1:14:26 PM UTC+1, Daniel Beck wrote:
>
>
> > On 14.02.2017, at 11:59, christian polzer  > wrote: 
> > 
> > Would it be possible to somehow track the version the documentation is 
> written for? :) 
>
> You can assume latest LTS or newer, with plugins up to date, as these are 
> the only releases we consider to be supported. (I think rtyler has plans to 
> improve this, but I doubt that'll be available soon.) 
>
> Running anything older is frequently a terrible idea anyway, see 
> https://jenkins.io/security/advisories/ 
>
>

-- 
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/628b08a6-708f-44b6-b83b-4136970941d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[christian polzer]

Ok, we have Jenkins LTS ver. 2.19.4 <http://jenkins-ci.org/>
installed with plugins updated just now.

And voila - it is working. 

Then now to another issue: Would it be possible to somehow track the 
version the documentation is written for? :)


On Tuesday, February 14, 2017 at 11:11:20 AM UTC+1, Daniel Beck wrote:
>
>
> > On 14.02.2017, at 10:22, christian polzer  > wrote: 
> > 
> > I just wondered if the pipeline example is pseudo code and if so - if it 
> has to? 
> > 
>
> You don't have the correct plugin installed: 
> https://plugins.jenkins.io/pipeline-model-definition 
>
> It should be automatically installed if you update plugins now, assuming 
> you have the default set from 2.0 onward installed. 
>
>

-- 
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/928af447-26af-4208-a776-fd2cc94758ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[christian polzer]

Hi there, 

just a comment on your second question:

2) secondly, why Jenkins creates another  directory @tmp when I would like 
to execute a command from my workspace.

-> you are able to configure the executing jvm to use another tmp dir. 
Example : java -Djava.io.tmpdir=/path/to/tmpdir
(Especially handy if you are using RHEL7 or other oses which do not allow 
to execute stuff in /tmp)

On Tuesday, February 14, 2017 at 3:34:12 AM UTC+1, Sharan Basappa wrote:
>
> Tyler,
>
> I have a few questions for which I could not find answers after going 
> through the documentation.
> Unfortunately, understanding of these are necessary for anyone to create a 
> decent build jobs.
>
> 1) Jenkins seems to be executing from a directory named @tmp (and some 
> other names). The files I am referring are not available in @tmp directory 
> and hence
> the pipeline stage is exiting
> 2) secondly, why Jenkins creates another  directory @tmp when I would like 
> to execute a command from my workspace.
> All the references made by the script are available here.
> 3) I have also seen that sometimes the files from git are available but 
> .git itself is missing
>
> Can you comment?
>
> On Monday, 13 February 2017 19:31:37 UTC+5:30, R Tyler Croy wrote:
>
>> (replies inline) 
>>
>> On Mon, 13 Feb 2017, christian polzer wrote: 
>>
>> > Hello, 
>> > 
>> > I am currently trying to spread pipeline usage for a jenkins 
>> environment 
>> > within my fellow coworkers. 
>> > Of course, th jenkins pipeline is greatly embrased :) 
>> > 
>> > But what is the documentation in the jenkins book about? Fellow 
>> CoCoders 
>> > stumble over the jenkinsfile chapter as the examples are not working: 
>> > https://jenkins.io/doc/book/pipeline/ 
>> > 
>> > What documentation do you guys use? 
>>
>>
>> What examples are not working for you? I wrote almost all of them and I'm 
>> pretty sure every single one works, perhaps I made a typo. 
>>
>> Could you share the error you're seeing and the corresponding Jenkinsfile 
>> example? 
>>
>>
>> Cheers 
>> - R. Tyler Croy 
>>
>> -- 
>>  Code: <https://github.com/rtyler> 
>>   Chatter: <https://twitter.com/agentdero> 
>>  xmpp: rty...@jabber.org 
>>
>>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F 
>> -- 
>>
>

-- 
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/8de9e3e9-af40-42d6-9a45-0e335f99c374%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline documentation jenkins-book vs realty?

[christian polzer]

Hi, 
and thanks for the quick reply.
To be precice, I am getting questions about the "Jenkinsfile (Declarative 
Pipeline)" example. 

*For example : *

1.) No such DSL method 'pipeline'

*2.) "*agent any" is not working , and as far as I learned from other 
coverage, agents (= nodes? ) are addressed with this syntax:  

"node('[slave|node|agent] name here'){
}"   
**

When introducing jenkins pipelines,  I had setup loads of pipeline examples 
on our Jenkins. But as the common developer is behaving, 
they never get bored of digging into stuff, in a struggle to make things 
easier and try out different angles :-)

When they finally stumble upon the jenkins book section, this is the 
question I get from most of my colleagues:
"How is this example meant to be used, or is it referring to a version of 
pipeline which is either outdated or we dont have installed yet?"
-> It also is unclear to me, if that syntax would be working, since I never 
saw this in any other example when digging into pipeline. 

This results in parts of the team drawing conclusions how pipeline is not 
so precise at all and syntax save and blablablah, and oh well - the 
documentation...
and then they skip multibranch pipelines and setup 60 identically build 
jobs by hand (which I have to maintain and backup) :-/

Please excuse my partly bad english - and please understand that no harm is 
intended here. I am really amazed by the jenkins project and the 
documentation and all.
 
I just wondered if the pipeline example is pseudo code and if so - if it 
has to?

Thanks for the good work and kind regards,

chris












On Monday, February 13, 2017 at 3:01:37 PM UTC+1, R Tyler Croy wrote:
>
> (replies inline) 
>
> On Mon, 13 Feb 2017, christian polzer wrote: 
>
> > Hello, 
> > 
> > I am currently trying to spread pipeline usage for a jenkins environment 
> > within my fellow coworkers. 
> > Of course, th jenkins pipeline is greatly embrased :) 
> > 
> > But what is the documentation in the jenkins book about? Fellow CoCoders 
> > stumble over the jenkinsfile chapter as the examples are not working: 
> > https://jenkins.io/doc/book/pipeline/ 
> > 
> > What documentation do you guys use? 
>
>
> What examples are not working for you? I wrote almost all of them and I'm 
> pretty sure every single one works, perhaps I made a typo. 
>
> Could you share the error you're seeing and the corresponding Jenkinsfile 
> example? 
>
>
> Cheers 
> - R. Tyler Croy 
>
> -- 
>  Code: <https://github.com/rtyler> 
>   Chatter: <https://twitter.com/agentdero> 
>  xmpp: rty...@jabber.org  
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F 
> -- 
>

-- 
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/995a3fef-c3b0-4b90-93d5-55ffd6058f78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline documentation jenkins-book vs realty?

[christian polzer]

Hello,

I am currently trying to spread pipeline usage for a jenkins environment 
within my fellow coworkers. 
Of course, th jenkins pipeline is greatly embrased :)

But what is the documentation in the jenkins book about? Fellow CoCoders 
stumble over the jenkinsfile chapter as the examples are not working:
https://jenkins.io/doc/book/pipeline/

What documentation do you guys use?





-- 
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/85bef299-294a-43c2-9e4a-f629e51fac88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins2 pipeline - Global methods in shared-library fails when invoked

[Tor Christian Solevågseide]

I was finally able to solve this myself. The problem was how I referenced 
the shared library. Apparently, I need to add the underscore character to 
the end if my @Library annotation like this:
@Library('customized-portal-lib') _

Also, I must make sure to not import my global *acme *variable.

This is documented 
in https://jenkins.io/doc/book/pipeline/shared-libraries/ for those who 
take their time to fine read it (which I didn't at first):

> For Shared Libraries which only define Global Variables (vars/), or a 
> Jenkinsfile which only needs a Global Variable, the annotation 
> <http://groovy-lang.org/objectorientation.html#_annotation> pattern 
> @Library('my-shared-library') 
> _ may be useful for keeping code concise. In essence, instead of 
> annotating an unnecessary import statement, the symbol _ is annotated.
>
 

> It is not recommended to import a global variable/function, since this 
> will force the compiler to interpret fields and methods as static even if 
> they were intended to be instance. The Groovy compiler in this case can 
> produce confusing error messages.


/TC


fredag 20. januar 2017 12.24.21 UTC+1 skrev Tor Christian Solevågseide 
følgende:
>
> As documented in https://jenkins.io/doc/book/pipeline/shared-libraries/, 
> I've created the file vars/acme.groovy in a library project checked into 
> our SVN.
>
>
> def setName(value) {
> this.name = value;
> }
> def getName() {
> return this.name;
> }
> def caution(message) {
> echo "Hello, ${this.name}! CAUTION: ${message}"
> }
>
>
>
>
> My pipeline script in a Jenkins2 pipeline project:
> acme.name = 'Alice'
> echo acme.name 
>
> acme.caution 'The queen is angry!'
>
>
>
>
> The two first lines, setting and getting the name works fine.
> But when I include the last line, calling the "caution" function the 
> script fails with
>
>
> hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No 
> signature of method: static Alice.caution() is applicable for argument 
> types: (java.lang.String) values: [The queen is angry!]
> Possible solutions: caution(java.lang.Object), wait(), 
> main([Ljava.lang.String;)
> at 
> groovy.lang.MetaClassImpl.invokeStaticMissingMethod(MetaClassImpl.java:1503)
> at groovy.lang.MetaClassImpl.invokeStaticMethod(MetaClassImpl.java:1489)
> at 
> org.codehaus.groovy.runtime.callsite.StaticMetaClassSite.call(StaticMetaClassSite.java:53)
> at 
> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
> at 
> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
> at 
> com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:18)
> at WorkflowScript.run(WorkflowScript:8)
>
>
>
> If I remove the first 2 lines of the pipeline script, leaving only the 
> "acme.caution" call, the error detail is changed to
>
> hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No 
> signature of method: static acme.caution() is applicable for argument types: 
> (java.lang.String) values: [The queen is angry!]
>
>
>
> Jenkins version 2.41
> Pipeline plugin 2.4
>
>
> Any idea what's going on here?  Feels like a bug, or at least wrong doc...?
>
> regards
> Tor Christian Solevågseide
>

-- 
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/c5863b80-60eb-465f-9b5c-ae7636d88c5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Docker Hub Notification plugin

[Christian Del Pino]

Hello,

Anyone have experience with the Cloudbees Docker Hub plugin:

https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Hub+Notification

I have been trying to get this to work in my environment with no luck. I 
keep getting errors on the Docker Hub side, but with no explanation as to 
what the issue is.

Am I correct in thinking that this plugin allows Docker Hub to trigger a 
Jenkins job when a new image is pushed to a monitored Docker Hub repo?

Thanks,
Chris

-- 
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/ebc44a43-644e-4707-b072-71bff0601f5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins2 pipeline - Global methods in shared-library fails when invoked

[Tor Christian Solevågseide]

As documented in https://jenkins.io/doc/book/pipeline/shared-libraries/, 
I've created the file vars/acme.groovy in a library project checked into 
our SVN.


def setName(value) {
this.name = value;
}
def getName() {
return this.name;
}
def caution(message) {
echo "Hello, ${this.name}! CAUTION: ${message}"
}




My pipeline script in a Jenkins2 pipeline project:
acme.name = 'Alice'
echo acme.name 

acme.caution 'The queen is angry!'




The two first lines, setting and getting the name works fine.
But when I include the last line, calling the "caution" function the script 
fails with


hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No 
signature of method: static Alice.caution() is applicable for argument 
types: (java.lang.String) values: [The queen is angry!]
Possible solutions: caution(java.lang.Object), wait(), 
main([Ljava.lang.String;)
at 
groovy.lang.MetaClassImpl.invokeStaticMissingMethod(MetaClassImpl.java:1503)
at groovy.lang.MetaClassImpl.invokeStaticMethod(MetaClassImpl.java:1489)
at 
org.codehaus.groovy.runtime.callsite.StaticMetaClassSite.call(StaticMetaClassSite.java:53)
at 
org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at 
org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at 
com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:18)
at WorkflowScript.run(WorkflowScript:8)



If I remove the first 2 lines of the pipeline script, leaving only the 
"acme.caution" call, the error detail is changed to

hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No 
signature of method: static acme.caution() is applicable for argument types: 
(java.lang.String) values: [The queen is angry!]



Jenkins version 2.41
Pipeline plugin 2.4


Any idea what's going on here?  Feels like a bug, or at least wrong doc...?

regards
Tor Christian Solevågseide

-- 
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/4ea660e5-672e-404d-b0d3-d8733878221d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Doing rollbacks with Jenkins pipeline

[Christian Posta]

Looking for thoughts on how to add rollback steps to a Jenkinsfile / 
pipeline when something fails.. for example, i may want to do a rollback of 
DB changes if a pipeline fails in a particular stage, etc. Any pointers 
would be appreciated!

-- 
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/6b47d4a2-5648-4be4-8882-5bd2a904dc5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How exactly does stash / unstash work AND how to use the same node in different stages

[Christian Ditscher]

Hi, 

@Baptiste: Your suggestion sound more me like my last suggestion. Checking 
out, stashing and then unstashing again. (This could be a solution if it 
were clear how exactly the stash/unstash works. --> What is transferred? 
Where are stashed files located/saved?) In general I would like to reduce 
the a mount of data that has to be transferred over network connections to 
a minimum. Therefore I would prefer to only transfer the needed files only 
once and then use them again. (Something like Björn suggested). 


@ Björn: the External Workspace Manager plugin sounds really interesting. 
This would be a great thing to reduce data transfer. Sadly it is not a 
"proven" plugin. Using it in my application is therefore not possible at 
this moment.  I will have to wait some time until it is stable.


Am Freitag, 1. Juli 2016 10:05:35 UTC+2 schrieb Björn Pedersen:
>
> Hi,
>
> Maybe 
> https://groups.google.com/d/msg/jenkinsci-dev/nAZD0-upB68/YwYjqmKgAwAJ 
> can be of help for you?
>
> Björn
>
> Am Donnerstag, 30. Juni 2016 18:03:19 UTC+2 schrieb Christian Ditscher:
>>
>> Hello, 
>>
>> I was wondering how exactly the stash unstash commands work.  When are 
>> the files transferred? 
>>
>>- stash transfers selected files to master and unstash loads them 
>>from master to a slave?
>>- stash attaches a label to the files which are transferred between 
>>the nodes when unstashed?
>>- something else?
>>
>>
>> Also I am asking myself how I can minimize the be transferred data during 
>> the build.
>>
>> One Idea I have is the following (example): I have 10 nodes which should 
>> be used to build and run tests and some other nodes to do something else. 
>> To minimize the number of files to be transferred I'd like to check out the 
>> sources only once. 
>>
>>- checkout and build on one of the 10 nodes. 
>>- do something with the build result on another node (stash -> 
>>unstash). 
>>- do something with the sources already on the node from before 
>>(without checking out again)
>>
>> If another build is started during the first is still running any of the 
>> remaining nodes is used for the next build. 
>>
>> How could I achieve that? Is this procedure useful?
>>
>> If I don't use the procedure described above I think have to stash all 
>> the sources and then unstash when I need them again. If checked out from 
>> source control again the sources already might already have changed.  --> 
>> Is this correct?
>>
>>
>> Thanks!
>> Chris 
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>

-- 
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/48395472-6a7c-4fea-8860-8197e47643e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How exactly does stash / unstash work AND how to use the same node in different stages

[Christian Ditscher]

Hello, 

I was wondering how exactly the stash unstash commands work.  When are the 
files transferred? 

   - stash transfers selected files to master and unstash loads them from 
   master to a slave?
   - stash attaches a label to the files which are transferred between the 
   nodes when unstashed?
   - something else?
   

Also I am asking myself how I can minimize the be transferred data during 
the build.

One Idea I have is the following (example): I have 10 nodes which should be 
used to build and run tests and some other nodes to do something else. To 
minimize the number of files to be transferred I'd like to check out the 
sources only once. 

   - checkout and build on one of the 10 nodes. 
   - do something with the build result on another node (stash -> unstash). 
   - do something with the sources already on the node from before (without 
   checking out again)
   
If another build is started during the first is still running any of the 
remaining nodes is used for the next build. 

How could I achieve that? Is this procedure useful?

If I don't use the procedure described above I think have to stash all the 
sources and then unstash when I need them again. If checked out from source 
control again the sources already might already have changed.  --> Is this 
correct?


Thanks!
Chris 
















-- 
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/0cbb89ee-8e95-47e7-8eac-58a424527b59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Split Pipeline script into multiple files -- run it without unnecessary nodes

[Christian Ditscher]

Hi,  

thanks .. this seems to look like this will solve my problem...
Will report back if it doesn't

Am Mittwoch, 15. Juni 2016 15:00:36 UTC+2 schrieb Sverre Moe:
>
> Take a look at Pipeline Global Library 
> https://github.com/jenkinsci/workflow-cps-global-lib-plugin
> I started with the same problem as you now have and solved it by using 
> global pipeline scripts.
> These global script are stored in Jenkins git repository workflowLibs.git 
> and can be accessed within all pipeline scripts.
>
> onsdag 15. juni 2016 12.46.26 UTC+2 skrev Christian Ditscher følgende:
>>
>> Hello, 
>>
>> I use a seperate reopsitory for my pipeline script. Multiple Jenkins Jobs 
>> use this pipeline script to built different Projects. For better 
>> maintainability 
>> the pipeline itself consists of a main script and multiple other sript 
>> files in which I implemented the different stages.
>> The pipelines are started by the built in function of Jenkins to checkout 
>> a Pipelinescript from SCM. Here I have configured the main pipeline script 
>> to be run. This main script then uses "load" to start the different stages.
>>
>> The thing that annoys me is that the "load" command needs to be contained 
>> inside a node {..} block.  This means I have to checkout the script files 
>> again on a node to "load" it. The scripts are already checked out on the 
>> master after "loading the script from SCM". I simply want to use the 
>> Flyweight executor to run the content of the stage script).  A bad solution 
>> would be to have the whole pipeline in one big script file. This would work 
>> but is really confusing.
>>
>> Is there a way to tell the main script (which runs on the master) to 
>> "insert" another groovy file (already present on master)?
>>
>> Any Ideas? 
>>
>> Thanks 
>> Chris
>>
>>
>>
>> *Note:*
>> In the Pipeline documentation I found the following but this still needs 
>> to checkout the scripts to a new node every time I want to load something. 
>>
>>
>>
>> *node {
>> git '…'
>> load 'pipeline.groovy'
>> }()*
>>
>> Ok, I could dedicate a single node like node('pipelineControl') so the 
>> scripts have to be be checked out only once but this solution still doesn't 
>> convince me.
>>
>>

-- 
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/f6cd4fc8-31cf-435d-9fd9-ac038a7a97fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Split Pipeline script into multiple files -- run it without unnecessary nodes

[Christian Ditscher]

Hello, 

I use a seperate reopsitory for my pipeline script. Multiple Jenkins Jobs 
use this pipeline script to built different Projects. For better 
maintainability 
the pipeline itself consists of a main script and multiple other sript 
files in which I implemented the different stages.
The pipelines are started by the built in function of Jenkins to checkout a 
Pipelinescript from SCM. Here I have configured the main pipeline script to 
be run. This main script then uses "load" to start the different stages.

The thing that annoys me is that the "load" command needs to be contained 
inside a node {..} block.  This means I have to checkout the script files 
again on a node to "load" it. The scripts are already checked out on the 
master after "loading the script from SCM". I simply want to use the 
Flyweight executor to run the content of the stage script).  A bad solution 
would be to have the whole pipeline in one big script file. This would work 
but is really confusing.

Is there a way to tell the main script (which runs on the master) to 
"insert" another groovy file (already present on master)?

Any Ideas? 

Thanks 
Chris



*Note:*
In the Pipeline documentation I found the following but this still needs to 
checkout the scripts to a new node every time I want to load something. 



*node {
git '…'
load 'pipeline.groovy'
}()*

Ok, I could dedicate a single node like node('pipelineControl') so the scripts 
have to be be checked out only once but this solution still doesn't convince me.

-- 
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/509c2f95-8d19-4ddf-8719-2e744718644b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

jenkinsci/jenkins docker image ssl issues

[christian polzer]

Hello,

I am currently trying to evaluate an update to Jenkins 2.x here at work 
with the actual docker image of jenkinsci/jenkins.

For this I need to git pull my git repo from a selfhosted Bitbucket/Stash 
Server via https.

Of course, the docker image's JVM has no clue of that cert.

So I wanted to give the plugin "skip-certificate-check" a try, which isn't 
helping in this case.

After several hours of trying and searching my way through the interwebz, I 
am turning to this group, with the hope that anyone here has solved that 
problem before?

Kind regards,

Chris


   

-- 
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/8c0b64a6-564b-4f61-aa06-e2dba5da3084%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Email-Ext and Pipeline - How to add Culprits and Developers as recipients?

[Christian Ditscher]

Hi, 

when using the email-ext plugin in a free-style Job I can select that mails 
are sent to Culprits and Developers. 
When using the plug-in in a pipeline script I don't know how to do this 
(the snippet generator doesn't offer to check this options.)

--> How can I send mails also to Culprits and Developers using email-ext?

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/5d599cc0-8cb8-4da9-a50c-ef7ad78f3606%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How can I set up a job schedule which triggers new jobs when a specific set of prerequisite jobs terminate?

[Christian Goetze]

Essentially, 
this: 
http://stackoverflow.com/questions/32704360/how-can-i-trigger-a-jenkins-job-upon-completion-of-a-set-of-other-jobs#

I know about the multijob plugin and I know about the workflow plugin. Both 
are useless, as they only allow me to schedule static "phases", which turn 
out to be reliably worst case in large scenarios. See the stackoverflow 
question for an example.

I ended up writing a groovy system script to poll and launch jobs, but for 
some reason my script runs Jenkins out of memory pretty quickly when used 
on a large scale.

https://gist.github.com/cg-soft/0ac60a9720662a417cfa

Any pointers on how to code this correctly are greatly appreciated.

-- 
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/8cd9fc0b-8f36-4e47-91c6-67c39c618ebf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maven artifact consistency when using multiple slaves

[Christian Flamm]

bump? :-(

-- 
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/f43d2de1-562a-43e6-97aa-1a5a277c5614%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build-Monitor/Wall Display including Maven Reactor Modules

[Christian Flamm]

*bump*

-- 
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/fa705f35-2af9-458e-a73f-eefa9298509d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Build-Monitor/Wall Display including Maven Reactor Modules

[Christian Flamm]

Hi,
does anyone know a Jenkins Build-Monitor / Wall Display that is able to 
display the status of (selected) module builds of a Maven reactor build?
I'm having problems doing this with the build-monitor-plugin.

Regards,
Thx in advance,
Christian

-- 
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/9c90683e-058d-4a8b-a7bf-31e5e36e38b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Email Notifications

[Christian Flamm]

Hey slide - after seeing some postings of yours I'm under the impressionism 
you might have something to do with email-ext...? :-)

Having a look at my initial posting - how would you configure emai-ext to 
achieve the desired behavior?

Regards + thanks in advance,
Christian

-- 
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/385a5ad8-4d33-46d8-a01b-06564d5429f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Email Notifications

[Christian Flamm]

Hi, thx, did that already. 

What I liked was how easy it is to send an email to the person responsible 
for the first build break in an row. That works great.

What I didn't like was how well it worked to send a "back to stable" email 
to that person again. It seemed to have trouble determining the "suspects" 
it had sent the "you broke the build" email in the first place.

I guess I'll switch to email-ext anyway. But I found it really confusing 
why the standard mailing has two check boxes that seem to be exactly what I 
believe I need. But they don't seem to have any effect.

Would be great if someone spots my lack of understanding those check boxes 
:-)

-- 
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/b4c2b385-49a3-4d5a-8ed9-6fb65b24d73b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Email Notifications

[Christian Flamm]

Hi Jacek,

I absolutely agree with the two points you brought up. Having Jenkins 
notification behavior like this is IMHO a very reasonable standard setting 
for many situations. I just wonder why I can't seem to configure the 
behavior to whatsoever I believe is necessary. I mean.. there are check 
boxes to check/uncheck.. what are they for?

My use case: We have many, many branches and corresponding CI jobs 
(on-push) for each of them. On some of these branches only 1 or 2 people 
work. The main reason I believe it's necessary to implement my desired 
behavior for some branches is: *Jenkins must never spam*!

   1. *Don't spam the right people*: On relatively "unimportant" branches, 
   the person who broke the build first is exactly the right person to notify. 
   Don't tell him over and over again - he knows and he's working on it 
   according to his work priorities. 
   2. *Don't spam the wrong people*: After a branch build breaks the team 
   working on it might integrate the master branch progress (via git merge). 
   All the authors that committed stuff on the master branch are now authors 
   of that branch, too. Don't send them mails, it's not their fault, they 
   don't know, mostly they don't care.
   
After three years of experience with Jenkins using the standard 
notification setting

   1. people often receive redundant notifications which they find 
   unnerving (=spam)
   2. people often receive confusing notifications about branches they 
   don't even know about and about which they don't care (=spam)
   
If I want people to take such notifications seriously I must send as little 
of them as possible. Else people will perceive them as noise. That's the 
last thing I want.

Regards, Christian

-- 
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/83fd1216-241b-4c95-ac14-c1c1c4d50561%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Email Notifications

[Christian Flamm]

Hi,
I have a problem understanding Jenkins' email notification configuration. 
There are three things I can set

   1. List of additional Recipients
   2. Yes/No - Send e-mail for every unstable build
   3. Yes/No - Send separate e-mails to individuals who broke the build

I just cannot seem to configure: *Only send an email to the committer(s) of 
the first failing build. No emails should be sent to any committers for any 
consecutively failing build after this one.*


My naive assumption was to enable this by setting 2. = No and 3. = Yes. But 
weirdly his will (a) send emails for every failing build and (b) to every 
committer since the build failed for the first time.


Anyone?

Thanks in advance,

Christian

-- 
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/c140aa48-8e9d-473c-9d1c-ae451e7f5cdd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Maven artifact consistency when using multiple slaves

[Christian Flamm]

Hi,

we're using a couple of slaves to build our many branches "on-push". There 
is no fix assignment between slave node and branch-building job, so it will 
happen regularly that a build job is run on a different node then the build 
job before.

Each job stores its Maven artifacts in a job-specific Maven repository - 
which is not only job-specific but unfortunately also slave-node-specific.

Scenario: 

   - Maven reactor build job *n *of branch *B *runs on slave *x*. Created 
   artifacts are stored in the job-specific Maven repository for branch *B* 
   on node *x*.
   - Maven reactor build job *n+1 *starts on slave node *y*. It determines 
   which modules to build - and more importantly - which not, since those 
   modules' artifacts have been built during job *n*. Unfortunately those 
   built artifacts have been stored on node *x*. Node *y* may have 
   artifacts older than build *n*, but those from build *n* are missing
   - Jenkins job does an inconsistent reactor build of mixed version 
   modules.

Question: Is there a possible solution other than having a fixed assignment 
between branch job and slave node?


Thanks ind advance, 

Christian

-- 
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/935b8052-9805-4705-9b88-44a12a9c3721%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Let running Jenkins job fail/succeed "from outside"?

[Christian Flamm]

*bump*

-- 
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/80f6a665-8e78-4818-ab62-34aaf88c11ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Let running Jenkins job fail/succeed "from outside"?

[Christian Flamm]

>
> Is there a way to make a job immediately stop do what he's doing after 
> setting the builld result?
>

Ideas anyone? 

-- 
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/4cd92d76-0dc2-4d88-9ab7-3b69d111979a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Let running Jenkins job fail/succeed "from outside"?

[Christian Flamm]

I was wrong! I can set the jobs build result from outside. I wrongly 
thought the job would then immediately be stopped after the result is 
clear, but it will go on doing everything and just use my set build result 
afterwards.

Is there a way to make a job immediately stop do what he's doing after 
setting the builld result?

Thx!

Am Mittwoch, 13. Mai 2015 10:01:49 UTC+2 schrieb Christian Flamm:
>
> To be a bit more precise: I can now run the command, without any complains 
> about ... that it has to be run from within a build ... but it has no 
> effect. 
>
> Am Mittwoch, 13. Mai 2015 09:53:10 UTC+2 schrieb Christian Flamm:
>>
>> Doing this by setting shell environment variables doesn't seem to work - 
>> what am I doing woring? Thx!
>>
>

-- 
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/5049357e-9741-458d-9c64-85008cd3f2da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Let running Jenkins job fail/succeed "from outside"?

[Christian Flamm]

To be a bit more precise: I can now run the command, without any complains 
about ... that it has to be run from within a build ... but it has no 
effect. 

Am Mittwoch, 13. Mai 2015 09:53:10 UTC+2 schrieb Christian Flamm:
>
> Doing this by setting shell environment variables doesn't seem to work - 
> what am I doing woring? Thx!
>

-- 
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/ab0af2d1-d5e6-4359-96ff-4ea06848ce2d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Let running Jenkins job fail/succeed "from outside"?

[Christian Flamm]

Doing this by setting shell environment variables doesn't seem to work - 
what am I doing woring? Thx!

-- 
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/291ec517-3180-41f3-a111-99e90b8bf670%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Let running Jenkins job fail/succeed "from outside"?

[Christian Flamm]

Sounds good! Will try that!
Am 12.05.2015 20:53 schrieb "Daniel Beck" :

> You should be able to use the Jenkins CLI for this (set-build-result
> command). It's intended to be used from a shell started by the build, so
> you'll need to recreate that environment (JOB_NAME and BUILD_NUMBER).
>
> On 08.05.2015, at 11:13, Christian Flamm 
> wrote:
>
> > Hi,
> >
> > is there a way to tell a running Jenkins job it has either
> failed/succeeded from outside? Something like a REST-like access to be able
> to finish running Jobs either way.
> >
> > Thanks in advance,
> > Christian
> >
> > --
> > 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/9d46da37-e258-485f-bba2-0f847b40f29d%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/aeUm6LbSxS0/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/9D141E33-7EC8-4F47-ACFB-2FE9A9A96E9C%40beckweb.net
> .
> 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/CANzp%2BZNHhGY_7BCH3wmKpyHf%2BA%3DD-NA0kWxm4G7z4Jdw6b856g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Let running Jenkins job fail/succeed "from outside"?

[Christian Flamm]

Hi,

is there a way to tell a running Jenkins job it has either failed/succeeded 
from outside? Something like a REST-like access to be able to finish 
running Jobs either way.

Thanks in advance,
Christian

-- 
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/9d46da37-e258-485f-bba2-0f847b40f29d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins freezes for ~10 sec at "first" connect

[Christian Flamm]

"fully loaded" means that the Jenkins Webapp is fully up and running.

-- 
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/192f0efd-e33c-4e8d-ac00-424cf4b36ecf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins freezes for ~10 sec at "first" connect

[Christian Flamm]

 

Whenever Jenkins is "fully loaded" and somebody attempts a connect via 
browser it takes about 10 seconds until Jenkins' main page appears. Every 
subsequent attempt is answered immediately. This state remains for a couple 
of minutes. So there's an amount of time that needs to pass until a "first" 
connection attempt takes 10 sec again, and so on...

Any idea what could cause this? (Bug vs. misconfiguration). No interesting 
log output appears.
 

-- 
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/1a6b9613-6d95-4bb8-b98c-16e0f47e9ad3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Embeddable Build Status Plugin - URLs without view name?

[Christian Galsterer]

Hi, 

I'm planning to implement an enhancement for the Embeddable Build Status 
plugin and wanted to get feedback from the community which way is preferred.

Currently the links for the build status badge contain always the full path 
for the selected job, i.e. when a job is listed as part of a view the link 
contains the view name. Nonetheless there are use cases where the view name 
is changed (i.e reorganization of view) but the job name stays. In order 
not to have broken links in your Wikis, etc. it would be good to have the 
URL pointing always to the job name without the view name in the URL even 
if the job is currently listed in a view. This is of course already 
possible today when you directly view the job (not in a view) but as a 
convenience method it would be good to have an option to have the links 
available without the view name. 

I see two options here:

   - Option 1: Change the URL of the current implementation so that URL is 
   always using only the job name (without the view name). This is changing 
   the current behaviour.
   - Option 2: Add additional fields in the badge containing the direct URL 
   without the view name.


What are your preferences?
Thanks for your feedback in advance.

-- 
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/255b56ee-b434-4195-a1b6-2704d3436020%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Implement custom NodeProvisioner strategy

[Christian Lipphardt]

Hi,

I am also interested in this topic, because we use the docker cloud plugin 
too and there is no load balancing. It just tries to fill up the first 
cloud before it moves on to provision slaves on the second configured cloud.

Cheers,
Christian

-- 
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/b3b4f514-27fb-4df3-95b8-496dc70ed447%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Simple way to temporary exclude job from running on a node in a label group

[Christian]

Hi!

I wan't to be able to temporary exclude a specific job from running on a
node in a label group.

jobA, jobB, jobC are tied to run on label general
nodeA,nodeB,nodeC have the label general on them.

Let's say that jobA starts to fail consistently on nodeA.
Is there some easy way to configure that jobA should temporarily only run
on nodeB and node C and that jobB/C should still run on all nodes in label
general?

The only solutions that I see today are taking nodeA offline for all jobs
or reconfigure many jobs or nodes which is pretty time consuming.

An ideal situation would be to have a configuration on the node:
Exclude job with name: jobA

Thanks,
Christian

-- 
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/CAHcVhVkp4-bvfy2Ri6foTfuNpKATczVZxt6FFhT%2B-5SeBr%2BUeQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

How to use Skip Certificate Check plugin?

[Christian Baumann]

Hi all,

I´ve installed the Skip Certificate Check plugin on our Jenkins server, 
re-downloaded slave.jar & jnlp to the agent, but when I start them, I still 
get the message about the untrusted SSL certificate.

Any advice?

Thanks in advance,
Christian

-- 
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.

Escape Quotes

[Christian Würtz]

Hi, 
I'm testing my project with sbt and to do so I have the following command 
in the "Actions" textfield:

clean update "env development" "set (testOptions in Test) += 
Tests.Argument(TestFrameworks.Specs2, \"exclude\", \"badTest\")" test dist

But the escape of the quotes fails and Jenkins just ignores them, which 
leads to an error. Is there any way to escape double quotes?!

-- 
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: How can I make a label change be effective?

[Christian Goetze]

Thanks, that seems to work... 

-- 
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: How can I make a label change be effective?

[Christian Goetze]

Sadly, the trimLabels() method is private. Is there a public method to 
achieve this, or do I really need to call setNodes(getNodes())

On Friday, May 9, 2014 12:48:41 PM UTC-7, Daniel Beck wrote:
>
> I commented on the issue with an explanation and how to solve your 
> problem. 
>
> On 09.05.2014, at 21:40, Christian Goetze 
> > 
> wrote: 
>
> > I just filed https://issues.jenkins-ci.org/browse/JENKINS-22954 
> > 
> > It appears that if I change the node label string via groovy, that 
> change is not immediately effective, even if I save the model. 
> > 
> > If I launch a subtask from the task that make the label change, that 
> subtask will run on a node where it should not run. 
> > 
> > Is there some call I am missing to make a label change to the nodes be 
> effective? 
> > 
> > -- 
> > 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.

How can I make a label change be effective?

[Christian Goetze]

I just filed https://issues.jenkins-ci.org/browse/JENKINS-22954

It appears that if I change the node label string via groovy, that change
is not immediately effective, even if I save the model.

If I launch a subtask from the task that make the label change, that
subtask will run on a node where it should not run.

Is there some call I am missing to make a label change to the nodes be
effective?

-- 
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: Anyone know.of/use an dashboardable/tablular/trendable arbitrary number plugin?

[Christian Willman]

What language are you interested in? Sounds like SonarQube is right up your 
alley.
 

> Anything like that in existence that anyone knows about? 
>

-- 
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: How do I persist changes to the model made via a Groovy script to disk?

[Christian Goetze]

What is the best way to discover all these nice things one could do...? Do
I really need to fire up an IDE and explore the source?


On Sun, Mar 16, 2014 at 1:41 PM, Christian Goetze <
christian.goe...@appdynamics.com> wrote:

> Thank you - that appears to work.
>
>
> On Sun, Mar 16, 2014 at 1:37 PM, Richard Lavoie 
> wrote:
>
>> Have you tried hudson.model.Hudson.instance.save() ?
>>
>>
>> On Sun, Mar 16, 2014 at 4:07 PM, Christian Goetze <
>> christian.goe...@appdynamics.com> wrote:
>>
>>> I recently learned that I can use the script console to run groovy
>>> scripts to modify items in the model.
>>>
>>> Specifically, I would like to add, change and remove slave node labels
>>> via a script.
>>>
>>> I can make a script like this for example:
>>>
>>> hudson.model.Hudson.instance.slaves.each { slave ->
>>>   out.print("Slave  $slave.nodeName : Labels: $slave.labelString")
>>>   slave.setLabelString(slave.labelString + " " + "operational")
>>>   out.println("   --> New labels: $slave.labelString")}
>>>
>>> Now how do I persist this change to disk?
>>>
>>>  --
>>> 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.
>>>
>>
>>
>>
>> --
>> Richard Lavoie
>> IT consultant / consultant en informatique
>>
>> --
>> 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/epL30VXvXC4/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-users+unsubscr...@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: How do I persist changes to the model made via a Groovy script to disk?

[Christian Goetze]

Thank you - that appears to work.


On Sun, Mar 16, 2014 at 1:37 PM, Richard Lavoie wrote:

> Have you tried hudson.model.Hudson.instance.save() ?
>
>
> On Sun, Mar 16, 2014 at 4:07 PM, Christian Goetze <
> christian.goe...@appdynamics.com> wrote:
>
>> I recently learned that I can use the script console to run groovy
>> scripts to modify items in the model.
>>
>> Specifically, I would like to add, change and remove slave node labels
>> via a script.
>>
>> I can make a script like this for example:
>>
>> hudson.model.Hudson.instance.slaves.each { slave ->
>>   out.print("Slave  $slave.nodeName : Labels: $slave.labelString")
>>   slave.setLabelString(slave.labelString + " " + "operational")
>>   out.println("   --> New labels: $slave.labelString")}
>>
>> Now how do I persist this change to disk?
>>
>>  --
>> 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.
>>
>
>
>
> --
> Richard Lavoie
> IT consultant / consultant en informatique
>
> --
> 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/epL30VXvXC4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@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.

How do I persist changes to the model made via a Groovy script to disk?

[Christian Goetze]

I recently learned that I can use the script console to run groovy scripts 
to modify items in the model.

Specifically, I would like to add, change and remove slave node labels via 
a script.

I can make a script like this for example:

hudson.model.Hudson.instance.slaves.each { slave -> 
  out.print("Slave  $slave.nodeName : Labels: $slave.labelString")
  slave.setLabelString(slave.labelString + " " + "operational")
  out.println("   --> New labels: $slave.labelString")}

Now how do I persist this change to disk?

-- 
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: Is it possible to have non editable execute shell for users?

[Christian Willman]

Stephen,

I'm really interested in the Literate plugin! Like I mentioned to you and 
Jesse before (through Cloudbees support vis-a-vis my work), it's futile for 
us unless we can keep devs from creating FreestyleBuilds. IIRC the project 
types perform a permission check against Item.BUILD, so it seems like we'd 
need to either:

- Override the project types to also check for a more specialized 
permission (e.g. FreestyleBuild.BUILD) OR the existing Item.BUILD, for 
backwards compatibility
- Write a custom ACL and override checkPermission to deny permission to the 
verboten types

The first option is a lot more work but reusable. The second option is a 
good internal hack but has very limited reuse.

What do you think? Maybe there's a much better option? ☺ 

Cheers,
Christian

On Monday, March 10, 2014 6:44:41 PM UTC-4, Stephen Connolly wrote:
>
> I think you need to see where I am going and play with it... you'll be 
> pleasantly surprised... whereas arguing here will not help you see my full 
> vision 
>

-- 
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: how to modify the jenkins ${BUILD_URL} ?

[Christian Willman]

Might want to switch over to a hostname to prevent this problem.

On Monday, March 10, 2014 3:15:26 AM UTC-4, tzxs...@gmail.com wrote:
>
> hi all,
>   my ip is xxx.xxx.xxx.10 ,after some time, I modify the ip to 
>  xxx.xxx.xxx.11, then I get the value of ${BUILD_URL} ,but the value is 10 
> not 11, why? 
>
> how can I get the right value?
>

-- 
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: Is it possible to have non editable execute shell for users?

[Christian Willman]

Stephen,

No biggie for us. We use the Maven enforcer plugin to ban antrun and exec. 
:-)

Cheers,
Christian

On Monday, March 10, 2014 7:56:49 AM UTC-4, Stephen Connolly wrote:
>
> Like that's going to stop them...
>
>   
> org.codehaus.mojo
> exec-maven-plugin
> 1.2.1
> 
>   
> 
>   exec
> 
> 
>   /bin/rm
>   /
>   
> -rf
> /
>   
> 
>   
> 
>   
>
>
>
> On 10 March 2014 00:39, Christian Willman  >wrote:
>
>> Unfortunately it is not possible. A common suggestion is to template out 
>> your specific job type, but even then, there is no authorization strategy 
>> to prevent users from simply creating a new FreestyleBuild with a console 
>> build step.
>>
>> Our organization has the same requirements -- we cannot allow untrusted 
>> developers to run arbitrary shell commands. We've solved this by switching 
>> to an external templating system (which I wrote in-house). Now developers 
>> cannot create or modify *any* jobs directly through the Jenkins UI. This 
>> works for us because 99% of our Java projects can be built with a simple 
>> "mvn clean deploy". The oddball jobs are isolated to a heavily-audited 
>> Jenkins instance.
>>
>> Another potential solution is to implement your own job types and then 
>> write a custom authorization strategy which revokes access to the built-in 
>> job types. But this is not maintainable and will probably require a 
>> dedicated admin to babysit the implementation for the foreseeable future.
>>
>> I've searched through the source and couldn't figure out any other 
>> implementations which don't require modifications to the Jenkins core. 
>> Unfortunately nobody (including Cloudbees) seems interested in this use 
>> case right now.
>>
>> Cheers,
>> Christian
>>
>> -- 
>> 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: Getting rid of multiple workspaces for a job

[Christian Willman]

Small correction, it means ABC was running in parallel, so Jenkins created 
separate workspaces to isolate each parallel execution. Jenkins will use a 
job's singular workspace across serial builds, even if each build occurred 
on a different executor.

On Thursday, March 6, 2014 10:06:35 PM UTC-5, Marc MacIntyre wrote:
>
> Those are from having multiple executors on each slave, the number is the 
> executor number
>

-- 
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: Is it possible to have non editable execute shell for users?

[Christian Willman]

Unfortunately it is not possible. A common suggestion is to template out 
your specific job type, but even then, there is no authorization strategy 
to prevent users from simply creating a new FreestyleBuild with a console 
build step.

Our organization has the same requirements -- we cannot allow untrusted 
developers to run arbitrary shell commands. We've solved this by switching 
to an external templating system (which I wrote in-house). Now developers 
cannot create or modify *any* jobs directly through the Jenkins UI. This 
works for us because 99% of our Java projects can be built with a simple 
"mvn clean deploy". The oddball jobs are isolated to a heavily-audited 
Jenkins instance.

Another potential solution is to implement your own job types and then 
write a custom authorization strategy which revokes access to the built-in 
job types. But this is not maintainable and will probably require a 
dedicated admin to babysit the implementation for the foreseeable future.

I've searched through the source and couldn't figure out any other 
implementations which don't require modifications to the Jenkins core. 
Unfortunately nobody (including Cloudbees) seems interested in this use 
case right now.

Cheers,
Christian

-- 
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: Running a job while slave is offline

[Christian Willman]

Hi EK,

What's the purpose of this exercise? It's very strange indeed.

I guess you could add two System Groovy scripts to the particular job. The 
first script is the first builder in the job's builders list, and it grabs 
a reference to the slave via 
jenkins.model.Jenkins.getInstance()#getComputer(...) and mark it as offline 
with setTemporarilyOffline(...). The next builder will perform whatever 
tasks you want, and a final System Groovy script will mark the slave as 
online.

If you can more thoroughly describe your goals then we can likely suggest a 
better means.

Cheers,
Christian

On Saturday, March 8, 2014 7:08:07 AM UTC-5, EK wrote:
>
> Hi ...
>
> I need to run a job which might cause slave to disconnect from Jenkins 
> server for a while- currently if slave is disconnected job is immediately 
> marked as failed or aborted, is there a way to do this, I was thinking 
> about something like the follow:
> 1. send job to slave
> 2. go offline
> 3. run job
> 4. go online
> 5. report results ...
>
> Best Regards
> EK
>

-- 
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: Is a central/shared local Maven Repo still Not safe for Jenkins master and many slaves?

[Christian Willman]

Definitely coming up, Stephen. We've got one of the largest Jenkins 
environments I've seen, which has forced me to solve a lot of problems 
around high-volume Maven builds. I'll try to write something this weekend.

On Thursday, March 6, 2014 4:34:38 AM UTC-5, Stephen Connolly wrote:
>
> You should write up a blog post of your setup... sounds like you have a 
> local minima set of best practices... they may not be the best practices 
> for everyone, but there are probably quite a lot of people who could share 
> your local minima
>
>
> On 6 March 2014 09:21, Christian Willman  >wrote:
>
>> No, not quite.
>>
>> Your internal Nexus will act as a caching layer. You won't make repeated 
>> calls to Maven central, or other external repos. But Maven will always 
>> still use a local repository to cache artifacts right on the machine 
>> performing the Maven command. And as Baptiste mentioned, this is not safe 
>> to share.
>>
>> If you are using the MavenBuild type then Jenkins can create one local 
>> repo per executor. If you are using mostly FreestyleBuild type jobs, then 
>> you can actually add a flag like this to every Maven command:
>>
>> -Dmaven.repo.local=${JENKINS_HOME}/${EXECUTOR_NUMBER}
>>
>> to get mostly the same effect. It's a good compromise between a global 
>> local repo (impossible) and separate local repos for every job. You'll 
>> probably find that many projects share a lot of common dependencies (and 
>> transitive dependencies) so you'll have lots of cache hits once a local 
>> repo is sufficiently populated.
>>
>> As far as cleanup goes, we purge the local repos every morning. Since the 
>> local repos have predictable paths, it's very easy to write a System Groovy 
>> script which iterates over jenkins.model.Jenkins#getComputers() and removes 
>> all local repos.
>>
>> This mechanism allows us to waste almost no disk space and provides very 
>> good performance. We get about one ticket per quarter WRT corrupt artifacts 
>> in the local repo, which is very good.
>>
>> On Monday, February 24, 2014 1:40:54 PM UTC-5, Seena Kasmai wrote:
>>>
>>> We use Nexus as our snapshot and release repositories; If we instruct 
>>> all of our maven installations (on each slave) to download everything from 
>>> nexus (i.e. like 
>>> this<https://support.sonatype.com/entries/20943003-Configure-Maven-to-Download-from-Nexus>),
>>>  
>>> would Jenkins+Maven-plugin effectively now use nexus as its local maven 
>>> repo (cache), or local m2. checks will always happen before going to remote 
>>> nexus?
>>>
>>> appreciate the feedback.
>>>
>>> --Seena
>>>
>>>
>>>
>>>
>>> On Saturday, February 22, 2014 9:59:45 AM UTC-5, Baptiste Mathus wrote:
>>>>
>>>> This is actually unsafe. You take the risk to corrupt the "maven local 
>>>> repository" (badly named, think more about it like a cache). And there's 
>>>> also potential issues of having a stale dependency installed in the local 
>>>> cache/repository (and if it's not a snapshot, it will never be downloaded 
>>>> again unless you delete it).
>>>>
>>>> In your case, as you're likely to have many executors per slave (which 
>>>> btw i wouldn't recommend) the probability to corrupt the cache is even 
>>>> bigger.
>>>> Then, on top of that, using NFS increases the risk even more, since 
>>>> (your executors count) processes will access the cache concurrently.
>>>>
>>>> Having a 'private' repository and cleaning it up on a regular basis is 
>>>> in fact simple and quite straightforward. The only downside is the disk 
>>>> space, but as having more disks is certainly cheaper than spending time to 
>>>> debug corrupted  repository issues.
>>>>
>>>> Hth
>>>> Le 21 févr. 2014 17:08, "Seena Kasmai"  a écrit :
>>>>
>>>>> Greetings - 
>>>>>
>>>>> It seems there is an outstanding maven issue "Concurrent-safe access 
>>>>> to local Maven repository <http://jira.codehaus.org/browse/MNG-2802>" 
>>>>> which would advise against setting up all Jenkins servers to use a shared 
>>>>> (e.g NFS mount) maven local repo - Can anyone confirm or share experience 
>>>>> on how unsafe this would be?
>>>>>
>>>>> The issue with having d

Re: best approach to automate/manage jenkins jobs?

[Christian Willman]

Great and valid question. Indeed the instances are split by work group. In 
the "old days" before I assumed the role of build master, developers could 
only modify jobs on their respective Jenkins instances. But since we've 
locked down and automated Jenkins, we allow every authenticated user to 
delete jobs, enable/disable jobs, run builds, whatever. Everything but 
creating/editing jobs is fair game, because never do we rely on Jenkins as 
a source of truth for job configuration.

It means we don't have to worry about the problems which will occur when 
one scales Jenkins vertically, by adding more and more slaves to a single 
master (a simple example is slower instance startup times due to the 
increased need to deserialize job configs to memory). Here is a link to 
Kohsuke's presentation <http://www.youtube.com/watch?v=rygTGn-rqVU> on 
elastic build environments which briefly mentions horizontal vs vertical 
scaling. A lot of the Cloudbees marketing material also mentions this well.

Cheers, Christian.

On Thursday, March 6, 2014 9:02:44 AM UTC-5, LesMikesell wrote:
>
> On Thu, Mar 6, 2014 at 3:46 AM, Christian Willman 
> > 
> wrote: 
> > 
> > But now we have too many Jenkins master instances and many active 
> branches 
> > of very similar code, so manually creating jobs via a web UI is too 
> > inefficient. 
>
> Just curious - what is it that drives the decision to use different 
> jenkins masters?   Would you overload a single master, or are they 
> split by location, phase of development, work group, or what? 
>
> -- 
>   Les Mikesell 
>  lesmi...@gmail.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.
For more options, visit https://groups.google.com/d/optout.

Re: best approach to automate/manage jenkins jobs?

[Christian Willman]

I don't like any of the open source templating plugins. I think they're 
rather inflexible and inelegant. I like the Cloudbees templating plugin but 
it's not necessarily cheap and you need to be familiar (or become familiar) 
with jelly.

We're in the same boat -- 99% of jobs share 99% of the same configuration. 
We create different code branches for different release dates, and 
sometimes we do parallel development, meaning we handle a *lot* of 
eerily-similar jobs. Additionally, we have many, many developers and we do 
not want them to directly touch the Jenkins job configuration UI. Reason 
being is partly because a global support team is responsible when a 
developer unknowingly hoses his/her job but still needs to cut a release by 
midnight.

I solved this by externalizing the templating system. At first we wrote a 
Rails app which simply accepts some input fields (job name, SCM URL, etc), 
clones and populates a template config.xml, and POSTs that over to Jenkins. 

But now we have too many Jenkins master instances and many active branches 
of very similar code, so manually creating jobs via a web UI is too 
inefficient. So I wrote a standalone application which contains a series of 
template job config.xml types and a means to parse Maven POMs as input to 
those templates. For instance, the job name is automatically determined via 
the Maven GAV. 

I've also baked-in support for arbitrary plugins; basically, anything that 
can contribute extra XML passages to a main template can be added to the 
tool in about five minutes. Everything supports variable interpolation, 
too. So a tech lead sets up Project X, June release with the following POM 
property:

project-y-$version,project-z-$version

When the job is created, $version resolves to "june-release" and then the 
downstreamJobs section is translated into a valid XML snippet and spliced 
into the template config.xml. The great thing is, in August, a 
fresh-out-of-college dev can create a brand new Project X, October release 
without any knowledge of the internals.

The final great thing is that this standalone application maps a SVN URL to 
an appropriate Jenkins master instance (in our case, the mappings are by 
business unit, which is fairly logical and standard). The app lives in an 
app server with a queue in front of it, and our SVN installation contains a 
post-commit hook which adds a SVN URL to that queue when the commit 
contains a special message ("+makeJob", inspired by Crucible smart 
commits). 

Now novice developers with very little knowledge about the CI system can 
create new jobs without ever entering in any technical details, and they'll 
receive an email containing a link to the new job as soon as it's created. 
Our goal is to allow developers to go from local commits -> artifact 
repository without ever worrying about the build system in between. It was 
a lot cheaper for us to engineer a good job templating system once (or 
twice, really) than to eternally field support requests.

This might be overkill for you; but then again, if you're tasked with 
managing thousands of jobs across a developer base with varying degrees of 
Jenkins competency, it might just be up your alley. If anything, realize 
that externalizing your templating system is a valid option.

PS -- I'd love to open source our templating system if anyone finds it 
interesting. My day job is not keen on releasing software so I would need 
some strong words of encouragement.


On Friday, February 21, 2014 10:14:47 AM UTC-5, phil swenson wrote:
>
> Hi, we have a large number of jenkins jobs and would like to automate and 
> version control their configuration.
>
> From what I can tell, most people just manually config their jobs via the 
> UI.  Unless there are only a few very simple jobs, this leads to an 
> unmanageable mess.
>
> I think the jobs should be coded in a DRY fashion, version controlled, and 
> deployed via a scripted system.
>
> Here are the approaches I am aware of:
>
> 1) scripting via command line (jenkins cli)
> 2) scripting via the rest web services
> 3) chef cookbook http://community.opscode.com/cookbooks/jenkins
>
> What are most people doing?
> Any recommendations?
>
> thanks
> phil
>

-- 
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/groups/opt_out.

Re: Is a central/shared local Maven Repo still Not safe for Jenkins master and many slaves?

[Christian Willman]

No, not quite.

Your internal Nexus will act as a caching layer. You won't make repeated 
calls to Maven central, or other external repos. But Maven will always 
still use a local repository to cache artifacts right on the machine 
performing the Maven command. And as Baptiste mentioned, this is not safe 
to share.

If you are using the MavenBuild type then Jenkins can create one local repo 
per executor. If you are using mostly FreestyleBuild type jobs, then you 
can actually add a flag like this to every Maven command:

-Dmaven.repo.local=${JENKINS_HOME}/${EXECUTOR_NUMBER}

to get mostly the same effect. It's a good compromise between a global 
local repo (impossible) and separate local repos for every job. You'll 
probably find that many projects share a lot of common dependencies (and 
transitive dependencies) so you'll have lots of cache hits once a local 
repo is sufficiently populated.

As far as cleanup goes, we purge the local repos every morning. Since the 
local repos have predictable paths, it's very easy to write a System Groovy 
script which iterates over jenkins.model.Jenkins#getComputers() and removes 
all local repos.

This mechanism allows us to waste almost no disk space and provides very 
good performance. We get about one ticket per quarter WRT corrupt artifacts 
in the local repo, which is very good.

On Monday, February 24, 2014 1:40:54 PM UTC-5, Seena Kasmai wrote:
>
> We use Nexus as our snapshot and release repositories; If we instruct all 
> of our maven installations (on each slave) to download everything from 
> nexus (i.e. like 
> this),
>  
> would Jenkins+Maven-plugin effectively now use nexus as its local maven 
> repo (cache), or local m2. checks will always happen before going to remote 
> nexus?
>
> appreciate the feedback.
>
> --Seena
>
>
>
>
> On Saturday, February 22, 2014 9:59:45 AM UTC-5, Baptiste Mathus wrote:
>>
>> This is actually unsafe. You take the risk to corrupt the "maven local 
>> repository" (badly named, think more about it like a cache). And there's 
>> also potential issues of having a stale dependency installed in the local 
>> cache/repository (and if it's not a snapshot, it will never be downloaded 
>> again unless you delete it).
>>
>> In your case, as you're likely to have many executors per slave (which 
>> btw i wouldn't recommend) the probability to corrupt the cache is even 
>> bigger.
>> Then, on top of that, using NFS increases the risk even more, since (your 
>> executors count) processes will access the cache concurrently.
>>
>> Having a 'private' repository and cleaning it up on a regular basis is in 
>> fact simple and quite straightforward. The only downside is the disk space, 
>> but as having more disks is certainly cheaper than spending time to debug 
>> corrupted  repository issues.
>>
>> Hth
>> Le 21 févr. 2014 17:08, "Seena Kasmai"  a écrit :
>>
>>> Greetings - 
>>>
>>> It seems there is an outstanding maven issue "Concurrent-safe access to 
>>> local Maven repository " 
>>> which would advise against setting up all Jenkins servers to use a shared 
>>> (e.g NFS mount) maven local repo - Can anyone confirm or share experience 
>>> on how unsafe this would be?
>>>
>>> The issue with having different repo is managing the cleaning up for 
>>> each and also not optimized when running same job in different slaves, all 
>>> maven artifacts have to be republished etc...(this is for a setup of 1000s 
>>> of jobs across 10 slaves)
>>>
>>> Any suggestions/advise would be helpful.
>>>
>>> Thanks,
>>> --Seena 
>>>
>>>  -- 
>>> 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/groups/opt_out.
>>>
>>

-- 
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/groups/opt_out.

Re: Best practice to copy Jenkins jobs from old instance to new one - Different networks - No root access to server - Manual Copying preferred

[Christian Willman]

Do you still have the administer authorization in the old Jenkins instance? 
You can write a script like this (psuedocode):

- read a list of job URLs, one URL/line
- for each line:
  - curl http://old-jenkins/job/myjob/config.xml (with basic authorization)
  - curl --data "@config.xml" http://new-jenkins/job/myjob (with basic 
authorization)

It's a crummy way of doing it, but it's fool-proof, and I'm not sure it's 
even with the engineering cost for just 20 jobs.

On Friday, February 28, 2014 2:29:12 PM UTC-5, SamiSam wrote:
>
>
> Any ideas on how to perform the copy manually then? I guess i'll have to 
> do this job by job at this point.. I only have about 20 jobs to move :)
>
>>
>>

-- 
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/groups/opt_out.

Re: Scheduled Safe Restart

[Christian Willman]

Precisely what we do. Every morning we run a scheduled job to grab and 
install our master list of Jenkins plugins and then trigger a safeRestart 
via a System Groovy build step. Works like a charm and hasn't failed us in 
over six months.

One thing to watch out for: if your developers have a rogue job, perhaps 
one with a broken, never-ending test, then you might come in Monday morning 
to a Jenkins instance still stuck in quiet mode with a full build queue. 
The queue will persist a restart but it's not good, especially if other 
teams are relying on Jenkins to deploy to regions or perform critical tests 
over the weekend. If a team is guilty of preventing a restart then we move 
their job(s) to a purgatory until they fix the problem. You could also use 
the build timeout plugin I guess.

On Thursday, February 27, 2014 5:39:45 AM UTC-5, Daniel Beck wrote:
>
> If you use the Groovy plugin, you could create a job that performs 
> safeRestart in a System Groovy build step with 
> 'jenkins.model.Jenkins.instance.safeRestart()'. Schedule as you would any 
> other job. 
>
>

-- 
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/groups/opt_out.

Re: Strategies to disk-risk a Jenkins upgrade

[Christian Willman]

To start, our jobs are 99% sameness. Most of our codebase can be built 
using one standard job, running a well-defined list of Maven commands. 
Realistically only the job name, SCM URL, and maybe timer or downstream job 
list are variable. So the first step in mitigating risk is to group like 
build processes onto separate Jenkins masters. Then you can better test how 
a change will affect the instance as a whole.

As far as what to test, over time I've found a list of 5-10 very stubborn 
projects which require significantly more babysitting than the other 
thousands of jobs I manage. Identifying some similar jobs and cloning them 
to a test region is a good next step. Don't forget to pin the projects to a 
known good SCM revision to create a valid test environment.

I would highly recommend taking nightly backups of the main config.xml, and 
probably every other config file in the Jenkins home directory. It doesn't 
matter how you do it. VM snapshots are great, as Mike points out. If you're 
a Cloudbees customer, their backup plugin is great. The Backup and 
thinBackup plugins are fine, but make sure you're archiving them to a share 
drive. You don't want to rely on the server's filesystem as your recovery 
source. Personally, I use a Jenkins job to tar up the Jenkins home 
directory (with zero depth) and automatically deploy it into Nexus every 
night. It's free and works fine.

We have 14 Jenkins master installations (probably 10K jobs) -- it's pretty 
big. Of course not all masters are created equal. Again, if you can split 
up your jobs into logically distinct Jenkins masters, then you can always 
roll out your changes first to low-volume, low-risk instances and finally 
to the high-volume, high-importance instances.

Finally, we don't use a package manager. We simply have a task to grab a 
specified Jenkins war from the WWW, deploy it to all 14 Jenkins master 
installations, and symlink the actual war name back to a version-agnostic 
name. A basic init.d handles the rest. The cool thing is that -- assuming 
an instance is idle -- we can back out a bad Jenkins upgrade in about two 
minutes -- and that's measuring from the time we receive an emergency page 
to the time we've restarted Jenkins using the old war. It's worth thinking 
about.

Please let me know if this helps, or if it spawns more questions. I love 
discussing this topic.


On Tuesday, March 4, 2014 11:53:59 PM UTC-5, JOHNSTON, Rob wrote:
>
>  Hi list
>
>  
>
> My group run a large Jenkins instance that many other teams in our 
> organisation depend on. We want to automate the Jenkins upgrade process 
> which will include a measure of verification that the upgrade hasn’t broken 
> anything.
>
>  
>
> I’m thinking of only using LTS releases, backing up the main config.xml 
> and the configs for each job, and running test jobs that use the plugins 
> we’re supporting.
>
>  
>
> My question is, what else are you doing to verify a Jenkins upgrade has 
> been successful? What checks do you perform before letting an upgrade go 
> into production?
>
>  
>
> Thanks
>
>  
>
> Rob Johnston
>  
> --
>
> This e-mail is sent by Suncorp Group Limited ABN 66 145 290 124 or one of 
> its related entities "Suncorp".
> Suncorp may be contacted at Level 18, 36 Wickham Terrace, Brisbane or on 
> 13 11 55 or at suncorp.com.au.
> The content of this e-mail is the view of the sender or stated author and 
> does not necessarily reflect the view of Suncorp. The content, including 
> attachments, is a confidential communication between Suncorp and the 
> intended recipient. If you are not the intended recipient, any use, 
> interference with, disclosure or copying of this e-mail, including 
> attachments, is unauthorised and expressly prohibited. If you have received 
> this e-mail in error please contact the sender immediately and delete the 
> e-mail and any attachments from your system.
>  

-- 
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/groups/opt_out.

Re: How to tell Jenkins to provide settings.xml to Maven?

[Christian Willman]

Depends. Are you using a MavenBuild or a FreestyleBuild? The Config File 
Provider plugin will hook into a MavenBuild, but for a FreestyleBuild 
(using the "Invoke Maven Top-Level Targets" build step), you will need to 
enable the "Provide configuration files" Build Environment task and then 
modify the Maven command to include '-s ${SETTINGS_PATH}'.

If you are using this as a mechanism to push out settings.xml changes then 
it might be worthwhile to just provision out VMs using Puppet or Chef using 
your desired Maven configuration.

On Wednesday, March 5, 2014 10:21:18 AM UTC-5, ka...@quipsy.de wrote:
>
> I have configured the Config File plugin to provide a custom settings.xml.
> But it seems the Jenkins slave is not using it.
> How to tell Jenkins that the Maven installation it automatically pushes on 
> the slave shall use that custom settings.xml file?
> I thought Config File plugin would automatically do that "under the hood" 
> (as it knows it is a Maven config file) but in fact it seems it does not.
> Any help appreciated! :-)
> -Markus
>

-- 
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/groups/opt_out.

Re: How can I see all builds in a job via api/json ?

[Christian Goetze]

Hacky solution:

curl -d 'script=println Jenkins.instance.getItem(jobName).builds.each{ 
println "${it.number}:${it.startTimeInMillis}:${it.duration}:${it.result}" 
};' http://localhost:8080/scriptText

On Thursday, February 20, 2014 5:35:19 PM UTC-8, Christian Goetze wrote:
>
> WHen I run /job//api/json?tree=builds[url], then I get a 
> list of some builds, but not all the builds I can retrieve via the UI? 
> What's the magic to get all builds?
>

-- 
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/groups/opt_out.

How can I see all builds in a job via api/json ?

[Christian Goetze]

WHen I run /job//api/json?tree=builds[url], then I get a list 
of some builds, but not all the builds I can retrieve via the UI? What's 
the magic to get all builds?

-- 
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/groups/opt_out.

Strange error when using git reference repos.

[Christian Goetze]

http://stackoverflow.com/questions/21267270/jenkins-git-plugin-and-reference-repos

I have a bare repo on the same host as the agent, and I get errors like 
these:

Error: object directory /.git/objects does not 
exist; check .git/objects/info/alternates

the funny thing is that that .git/objects/info/alternates points to the 
correct path to the reference repo's object dir. Somehow the git plugin is 
simply assuming that the reference repo is a non-bare repo.

-- 
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/groups/opt_out.

How to turn off looking up the previous build?

[Christian Goetze]

I have a Jenkins job which can get triggered in a variety of ways, either 
via SCM polling or via a Gerrit trigger. The order in which the jobs are 
run has no real relationship to the ordering of the commits being built, so 
comparing the current build with the previous build is not very useful.

In addition, attempting to retrieve the commit hash of a previous build may 
fail, as the current workspace may not actually contain the ref of the 
previous build.

I would like to turn off that feature. How can I do that?

Using Jenkins 1.542 and the git plugin 2.0.

-- 
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/groups/opt_out.

Jenkins Maven NPE

[Christian Beikov]

It seems that jenkins is not able to parse my pom.xml or maybe it is 
something different?

Please Help!

My System:

OS: Darwin 9.8.0
JVM: Oracle Zero VM 21.0-b17
AS: JBoss EAP 6.1
Jenkins: 1.535
Maven: 3.1.1
Maven-Plugin: 2.0

Console Output:

Parsing POMs

[Booking] $ java -cp 
/Users/jboss/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.4.jar:/Users/jboss/.jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1/boot/plexus-classworlds-2.5.1.jar:/Users/jboss/.jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1/conf/logging
 jenkins.maven3.agent.Maven31Main 
/Users/jboss/.jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.1.1 
/Library/JBossAS/current/standalone/tmp/vfs/tempad4550f3c74303/jenkins.war-9212d6c4d4b41483/WEB-INF/lib/remoting-2.32.jar
 
/Users/jboss/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.4.jar
 
/Users/jboss/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar
 49293

<===[JENKINS REMOTING CAPACITY]===>channel started

ERROR: Processing failed due to a bug in the code. Please report this to 
jenkinsci-users@googlegroups.com
java.lang.NullPointerException
 <http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException>   
athudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:261)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.AbstractMavenProcessFactory.newProcess&entity=method>
athudson.maven.ProcessCache.get(ProcessCache.java:235)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.ProcessCache.get&entity=method>

athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:739)
  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun&entity=method>
athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.run&entity=method>
athudson.model.Run.execute(Run.java:1665)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute&entity=method>
athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.run&entity=method>
athudson.model.ResourceController.execute(ResourceController.java:88)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute&entity=method>
athudson.model.Executor.run(Executor.java:246)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run&entity=method>
project=hudson.maven.MavenModuleSet@156ffe7[Booking]
project.getModules()=[hudson.maven.MavenModule@1c92bb[Booking/at.ac.tuwien.sse:sse-agile-1][Booking/at.ac.tuwien.sse:sse-agile-1][relativePath:]]
project.getRootModule()=hudson.maven.MavenModule@1c92bb[Booking/at.ac.tuwien.sse:sse-agile-1][Booking/at.ac.tuwien.sse:sse-agile-1][relativePath:]
FATAL: null
java.lang.NullPointerException
 <http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException>   
athudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:261)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.AbstractMavenProcessFactory.newProcess&entity=method>
athudson.maven.ProcessCache.get(ProcessCache.java:235)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.ProcessCache.get&entity=method>

athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:739)
  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun&entity=method>
athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.run&entity=method>
athudson.model.Run.execute(Run.java:1665)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute&entity=method>
athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.run&entity=method>
athudson.model.ResourceController.execute(ResourceController.java:88)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute&entity=method>
athudson.model.Executor.run(Executor.java:246)  
<http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run&entity=method>


--

Mit freundlichen Grüßen,

*Christian Beikov*

--
You received this message be

Re: SSH-Agent git problem

[Christian Beikov]

(StandardWrapperValve.java:230)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:389)
at 
org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
at 
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.IllegalStateException: Can't overwrite cause
at java.lang.Throwable.initCause(Throwable.java:456)
at com.kenai.jffi.Type$Builtin.lookupTypeInfo(Type.java:252)
at com.kenai.jffi.Type$Builtin.getTypeInfo(Type.java:237)
at com.kenai.jffi.Type.resolveSize(Type.java:155)
at com.kenai.jffi.Type.size(Type.java:138)
at 
jnr.ffi.provider.jffi.NativeRuntime$TypeDelegate.size(NativeRuntime.java:178)
at jnr.ffi.provider.AbstractRuntime.(AbstractRuntime.java:48)
at jnr.ffi.provider.jffi.NativeRuntime.(NativeRuntime.java:57)
at jnr.ffi.provider.jffi.NativeRuntime.(NativeRuntime.java:41)
at 
jnr.ffi.provider.jffi.NativeRuntime$SingletonHolder.(NativeRuntime.java:53)
... 97 more



Mit freundlichen Grüßen,
----
*Christian Beikov*
Am 23.10.2013 20:13, schrieb Stephen Connolly:
You probably want to switch to Git 2.0 and it's native support for 
credentials (i.e. should not need ssh-agent configured explicitly)



On 23 October 2013 18:08, Christian Beikov <mailto:christian.bei...@gmail.com>> wrote:


Hello,

I have a problem with jenkins git plugin and ssh-agent checking
out from a bitbucket git repository. The credentials defined for
the ssh-agent are the right ones.

I have no clue what this error is about. Please help me.

My system:

OS: Darwin 9.8.0
JVM: Oracle Zero VM 21.0-b17
AS: JBoss EAP 6.1
Jenkins: 1.535
Git Plugin: 1.5.0
Git Client: 1.4.3
SSH-Agent: 1.4
SSH-Credentials: 1.5.1

The stacktrace:

[ssh-agent] Using credentials jboss (sse-jenkins bitbucket account)
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent]   Java/JNR ssh-agent
[ssh-agent] FATAL: Could not find a suitable ssh-agent provider
[ssh-agent] Diagnostic report
[ssh-agent] * Java/JNR ssh-agent
[ssh-agent] java.lang.UnsatisfiedLinkError: could not load FFI provider 
jnr.ffi.provider.jffi.Provider
[ssh-agent] at 
jnr.ffi.provider.InvalidRuntime.newLoadError(InvalidRuntime.java:83)
[ssh-agent] at 
jnr.ffi.provider.InvalidRuntime.findType(InvalidRuntime.java:24)
[ssh-agent] at jnr.ffi.Struct$NumberField.(Struct.java:649)
[ssh-agent] at jnr.ffi.Struct$Unsigned8.(Struct.java:880)
[ssh-agent] at 
jnr.unixsocket.SockAddrUnix$BSDSockAddrUnix.(SockAddrUnix.java:112)
[ssh-agent] at 
jnr.unixsocket.SockAddrUnix.create(SockAddrUnix.java:99)
[ssh-agent] at 
jnr.unixsocket.UnixSocketAddress.(UnixSocketAddress.java:32)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.jna.AgentServer.start(AgentServer.java:66)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.(JNRRemoteAgent.java:64)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:54)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:35)
[ssh-agent] at 
hudson.remoting.LocalChannel.call(LocalChannel.java:45)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentFactory.start(JNRRemoteAgentFactory.java:61)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.(SSHAgentBuildWrapper.java:211)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:123)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:93)
[ssh-agent] at 
jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:78)
[ssh-agent] at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(Abs

SSH-Agent git problem

[Christian Beikov]

Hello,

I have a problem with jenkins git plugin and ssh-agent checking out from a 
bitbucket git repository. The credentials defined for the ssh-agent are the 
right ones.

I have no clue what this error is about. Please help me.

My system:

OS: Darwin 9.8.0
JVM: Oracle Zero VM 21.0-b17
AS: JBoss EAP 6.1
Jenkins: 1.535
Git Plugin: 1.5.0
Git Client: 1.4.3
SSH-Agent: 1.4
SSH-Credentials: 1.5.1

The stacktrace:

[ssh-agent] Using credentials jboss (sse-jenkins bitbucket account)
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent]   Java/JNR ssh-agent
[ssh-agent] FATAL: Could not find a suitable ssh-agent provider
[ssh-agent] Diagnostic report
[ssh-agent] * Java/JNR ssh-agent
[ssh-agent] java.lang.UnsatisfiedLinkError: could not load FFI provider 
jnr.ffi.provider.jffi.Provider
[ssh-agent] at 
jnr.ffi.provider.InvalidRuntime.newLoadError(InvalidRuntime.java:83)
[ssh-agent] at 
jnr.ffi.provider.InvalidRuntime.findType(InvalidRuntime.java:24)
[ssh-agent] at jnr.ffi.Struct$NumberField.(Struct.java:649)
[ssh-agent] at jnr.ffi.Struct$Unsigned8.(Struct.java:880)
[ssh-agent] at 
jnr.unixsocket.SockAddrUnix$BSDSockAddrUnix.(SockAddrUnix.java:112)
[ssh-agent] at 
jnr.unixsocket.SockAddrUnix.create(SockAddrUnix.java:99)
[ssh-agent] at 
jnr.unixsocket.UnixSocketAddress.(UnixSocketAddress.java:32)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.jna.AgentServer.start(AgentServer.java:66)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.(JNRRemoteAgent.java:64)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:54)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:35)
[ssh-agent] at 
hudson.remoting.LocalChannel.call(LocalChannel.java:45)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentFactory.start(JNRRemoteAgentFactory.java:61)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.(SSHAgentBuildWrapper.java:211)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:123)
[ssh-agent] at 
com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:93)
[ssh-agent] at 
jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:78)
[ssh-agent] at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:556)
[ssh-agent] at hudson.model.Run.execute(Run.java:1665)
[ssh-agent] at 
hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:507)
[ssh-agent] at 
hudson.model.ResourceController.execute(ResourceController.java:88)
[ssh-agent] at hudson.model.Executor.run(Executor.java:246)
[ssh-agent] Caused by: java.lang.ExceptionInInitializerError
[ssh-agent] at 
jnr.ffi.provider.jffi.NativeRuntime.getInstance(NativeRuntime.java:49)
[ssh-agent] at 
jnr.ffi.provider.jffi.Provider.(Provider.java:29)
[ssh-agent] at 
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[ssh-agent] at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
[ssh-agent] at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
[ssh-agent] at 
java.lang.reflect.Constructor.newInstance(Constructor.java:525)
[ssh-agent] at java.lang.Class.newInstance0(Class.java:372)
[ssh-agent] at java.lang.Class.newInstance(Class.java:325)
[ssh-agent] at 
jnr.ffi.provider.FFIProvider$SystemProviderSingletonHolder.getInstance(FFIProvider.java:60)
[ssh-agent] at 
jnr.ffi.provider.FFIProvider$SystemProviderSingletonHolder.(FFIProvider.java:49)
[ssh-agent] at 
jnr.ffi.provider.FFIProvider.getSystemProvider(FFIProvider.java:35)
[ssh-agent] at 
jnr.ffi.Runtime$SingletonHolder.(Runtime.java:85)
[ssh-agent] at jnr.ffi.Runtime.getSystemRuntime(Runtime.java:70)
[ssh-agent] at 
jnr.unixsocket.SockAddrUnix.(SockAddrUnix.java:34)
[ssh-agent] at 
jnr.unixsocket.SockAddrUnix$BSDSockAddrUnix.(SockAddrUnix.java:110)
[ssh-agent] ... 17 more
[ssh-agent] Caused by: java.lang.IllegalStateException: Can't overwrite 
cause
[ssh-agent] at java.lang.Throwable.initCause(Throwable.java:456)
[ssh-agent] at 
com.kenai.jffi.Type$Builtin.lookupTypeInfo(Type.java:252)
[ssh-agent] at 
com.kenai.jffi.Type$Builtin.getTypeInfo(Type.java:237)
[ssh-agent] at com.kenai.jffi.Type.resolveSize(Type.java:155)
[ssh-agent] at com

Subversion Plugin - when release of 1.51?

[Christian Ehrlicher]

Hello,

is there a plan when to release a new subversion plugin? 1.50 does not 
work with subversion 1.8 server but afaics the fix (using svnkit 1.7.10) 
is already commited.
I tried to compile the plugin by my own but got stuck during 
installation. Jenkins somehow does not recognize that my version is 
newer and refuses to use it (and the name is still subversion.hpi but 
shouldn't it be subversion.jpi?). And even when I force it to load (by 
stopping the server and deleting subversion subdir  and subversion.jpi) 
it somehow does not work :(


Thx,
Christian Ehrlicher

--
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/groups/opt_out.

Re: Right procedure to send for Security Advisories

[Christian Catalano]

Ok I am doing it...
is this the right procedure to obtain a CVE too?

Can you help me?
Christian


On Thu, Aug 29, 2013 at 12:47 PM, teilo  wrote:

> Hi Christian,
>
> You should create an issue in the Jenkins bug tracker under the "Security
> Issues" project.
>
> This project has restricted access so only the select few will be able to
> see your report.
>
> See https://wiki.jenkins-ci.org/display/JENKINS/Security+Advisories for
> more info.
>
> /James
>
>
> On Thursday, 29 August 2013 11:36:04 UTC+1, Christian Catalano wrote:
>>
>> Hi everyone,
>>
>> I am executing a PT for my company... in my targets there is a server
>> with a Jenkins application.
>>
>> I think I have found a severe security vulnerability so I would like to
>> know the right procedure to:
>>
>> - advise the jenkins team
>> - send the documentation to explait the vulnerability and to prove it
>> - how I can obtain a CVE Identifier
>>
>>
>> Best regards
>> Christian
>>
>>  --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.