Re: Pipeline: How to cache downloaded (gradle) dependencies using Docker SSH Slave

[Craig Rodrigues]

In 2011, this discussion thread talked about this topic:
https://discuss.gradle.org/t/cache-dependencies-into-local-maven-repository-from-gradle/7525
and it didn't seem possible.

However, I advise you to post your question to https://discuss.gradle.org/
, because there may be new information that can make this possible.

--
Craig


On Wed, Jun 22, 2016 at 4:48 AM, Marco Pas  wrote:

> Now that we have a first successful build using a Jenkinsfile Pipeline we
> are looking on how to cache downloaded dependencies.
> Currently when we build our Gradle applications the dependencies are
> downloaded each time the Docker Slave is executed on a remote host. Is
> there a way to cache the downloaded dependencies for later reuse so we can
> speedup the build process?
>
>

-- 
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/CAG%3DrPVePU3jEwO_AUH8X-i2NEtT6%3DX5Y4dF2x02s4aQKVrS%3DpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Permission denied

[33]

Hi all,
Setting up an ubuntu server to build android roms using jenkins.
Whenever i run a job from jenkins, it shows Permission denied
Chmod and chown is not helping me coz the newly created folders have 
permission issues,
i've tried with chown the entire directory to jenkins and creating a user 
group and adding jenkins and users to it also not helping,
future folders and files is not using the permission from group, So jenkins 
is not able to make changes,
Any help 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/7f070b1d-6ab9-4eef-9b32-d51396298bf8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins is hanging with no errors during startup

[Dustin Nielsen]

So, when I setup Jenkins the instructions I was following made no note that 
there is a difference between running Jenkins on its own server and running 
Jenkins on a web server that was also running Apache.

After figuring out that there is indeed a difference I went a slightly 
different route with my jenkins configuration.

I added --prefix=/jenkins to JENKINS_ARGS in the jenkins configuration 
file. I also changed what port jenkins was listening on to 8081, and 
changed what IP address jenkins was listening on from 0.0.0.0 to 127.0.0.1

I then added:

ProxyPass /jenkins  http://localhost:8081/jenkins nocanon
ProxyPassReverse  /jenkins  http://localhost:8081/jenkins
ProxyRequests Off
AllowEncodedSlashes NoDecode

http://localhost:8081/jenkins*>
  Order deny,allow
  Allow from all


To my Apache configuration file. This fixed my issue and allowed me to 
access Jenkins.

On Wednesday, June 22, 2016 at 8:25:43 PM UTC-6, Dustin Nielsen wrote:
>
> So, I've tried doing my research on this issue but it's gotten to the 
> point where I'm no longer understanding what I'm reading.
>
>
> I've installed Jenkins and Java on my server, running CentOS 6.8 and 
> Apache 2.4. I had a few problems initially with just starting the service 
> but have since ironed those out. Now stopping the service and starting it 
> just gives me a nice green OK message stating that all is well with the 
> world. When I run service jenkins status I get jenkins (pid 32178) is 
> running But when I try to access my server with my server's IP 
> address and the Port number (which I changed to ), it just hangs and 
> then says the site took too long to respond.
>
>
> So I looked at my jenkins logs and everything looked fine, even get this 
> message INFO: Jenkins is fully up and running, but then just below that I 
> get:
>
>
> WARNING: Prober().run() exception
> java.io.IOException: Operation not permitted
> at java.net.PlainDatagramSocketImpl.send(Native Method)
> at java.net.DatagramSocket.send(DatagramSocket.java:693)
> at javax.jmdns.impl.JmDNSImpl.send(JmDNSImpl.java:1537)
> at javax.jmdns.impl.tasks.state.DNSStateTask.run(DNSStateTask.java:131)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
>
> Jun 22, 2016 12:08:59 AM javax.jmdns.impl.JmDNSImpl __recover
> WARNING: RECOVERING
> Jun 22, 2016 12:08:59 AM javax.jmdns.impl.tasks.state.DNSStateTask run
> WARNING: Canceler().run() exception
> java.io.IOException: Operation not permitted
> at java.net.PlainDatagramSocketImpl.send(Native Method)
> at java.net.DatagramSocket.send(DatagramSocket.java:693)
> at javax.jmdns.impl.JmDNSImpl.send(JmDNSImpl.java:1537)
> at javax.jmdns.impl.tasks.state.DNSStateTask.run(DNSStateTask.java:131)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
>
>
> So I looked around for a solution to this and found a few options, first 
> was to make sure that my server is listening on the port that I selected 
> (). So I ran netstat -tuplen and saw ::: with a state of LISTEN and 
> java as the program name. This leads me to believe the system is listening 
> for that port, perhaps I'm wrong though. I also found a mailing list that 
> was long and I didn't understand 75% of it, but it came down to seeing if 
> multicast was enabled on the server, so I ran ifconfig eth0and got UP 
> BROADCAST RUNNING MULTICAST in a big block of text, which leads me to 
> believe multicast is enabled.
>
>
> Also, my java version if openjdk 1.8.0_91, as I'm aware Jenkins doesn't 
> like the normal java that seems to be installed on CentOS machines.
>
>
> Just wondering what else could be the problem for Jenkins not running and 
> giving that error, and what I could do to fix this. I'm for the most part a 
> newbie with this kind of stuff, so more detailed info would be helpful.
>

-- 
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/bcba9973-00d9-4950-958d-aaa9993da9f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins is hanging with no errors during startup

[Dustin Nielsen]

So, I've tried doing my research on this issue but it's gotten to the point 
where I'm no longer understanding what I'm reading.


I've installed Jenkins and Java on my server, running CentOS 6.8 and Apache 
2.4. I had a few problems initially with just starting the service but have 
since ironed those out. Now stopping the service and starting it just gives 
me a nice green OK message stating that all is well with the world. When I 
run service jenkins status I get jenkins (pid 32178) is running But 
when I try to access my server with my server's IP address and the Port 
number (which I changed to ), it just hangs and then says the site took 
too long to respond.


So I looked at my jenkins logs and everything looked fine, even get this 
message INFO: Jenkins is fully up and running, but then just below that I 
get:


WARNING: Prober().run() exception
java.io.IOException: Operation not permitted
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.DatagramSocket.send(DatagramSocket.java:693)
at javax.jmdns.impl.JmDNSImpl.send(JmDNSImpl.java:1537)
at javax.jmdns.impl.tasks.state.DNSStateTask.run(DNSStateTask.java:131)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)

Jun 22, 2016 12:08:59 AM javax.jmdns.impl.JmDNSImpl __recover
WARNING: RECOVERING
Jun 22, 2016 12:08:59 AM javax.jmdns.impl.tasks.state.DNSStateTask run
WARNING: Canceler().run() exception
java.io.IOException: Operation not permitted
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.DatagramSocket.send(DatagramSocket.java:693)
at javax.jmdns.impl.JmDNSImpl.send(JmDNSImpl.java:1537)
at javax.jmdns.impl.tasks.state.DNSStateTask.run(DNSStateTask.java:131)
at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)


So I looked around for a solution to this and found a few options, first 
was to make sure that my server is listening on the port that I selected 
(). So I ran netstat -tuplen and saw ::: with a state of LISTEN and 
java as the program name. This leads me to believe the system is listening 
for that port, perhaps I'm wrong though. I also found a mailing list that 
was long and I didn't understand 75% of it, but it came down to seeing if 
multicast was enabled on the server, so I ran ifconfig eth0and got UP 
BROADCAST RUNNING MULTICAST in a big block of text, which leads me to 
believe multicast is enabled.


Also, my java version if openjdk 1.8.0_91, as I'm aware Jenkins doesn't 
like the normal java that seems to be installed on CentOS machines.


Just wondering what else could be the problem for Jenkins not running and 
giving that error, and what I could do to fix this. I'm for the most part a 
newbie with this kind of stuff, so more detailed info would be helpful.

-- 
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/d019726f-371b-441a-8205-7ab28a2c2e47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Need help on usage of Jenkins console data

[AJITH K.R]

Any more help in this please.

On Tuesday, June 14, 2016 at 4:04:47 PM UTC+5:30, AJITH K.R wrote:
>
> Hi All,
>
> How can I get the console output information of Jenkins build under the 
> workspace. I need to use it as an input for reporting purpose. 
>
> Thanks,
> Ajith
>

-- 
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/5fc3f25c-3e1d-4d80-960d-a4661d683de0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Does Role-based Authorization Strategy has users limit?

[Raj Meghraj]

Hi All, 

I am using Role-based Authorization Strategy 
 in my 
organization for managing and assigning roles to users. In my Manage and 
Assign Roles -> Assign roles tab, I have 160 users for Global Roles and 160 
users for Project Roles. When I tried to add 161th user to the Project 
Roles, it threw a "FormContentSize" error. But I was able to add when I 
removed an existing inactive user. So my question here is does this plugin 
has the limitation of users to 160/320, if yes how can we bump the number 
of users. 

Regards, 
Raj

-- 
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/d46468ad-85dd-4e7b-bf85-441342aa8835%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to automate software using AWS codepipeline with jenkins

[Iftikhar Hossain]

I am novice at Jenkins. My demo project built in github and with AWS 
codedeploy I can run my project succesfully. If I use AWS codepipeline 
without Jenkins, whatever changed in github its automatically integrated 
and run the project. So I want to use Jenkins, if codes have successfully 
built then it should run. So when I add jenkins in AWS codepipeline and 
integrated with my jenkins server this process has not run and it just 
processing in build section. What is the error or it's not integrated with 
jenkins? So what should I do? Kindly help 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/0332ef54-7a26-419f-888a-2af2c20c8267%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Installing Pulseway across multiple windows vm

[aaron . trujillo]

I have search the internet over and am also in contact with a pulseway rep 
(but it is taking long periods of time for him to respond, yes i realize he 
is probably busy).  I would appreciate some help form the group on a matter 
i am having.  
When I install Pulseway on the local (windows) machine from the cmd line 
with the following:

"\\GP1-LAB-FSVR01\Software\Pulseway Agent\Windows\pulseway_x64.msi" 
ALLUSERS=1 /qn username=UUU password=UUU group=Default server=UUU 

it installs just fine.

Then when I run this same command through a Jenkins Deployment in a Windows 
Batch Command, it installs... BUT, there is no desktop icon nor does it 
show up in the programs and features (uninstall) options...

This was the latest response from Pulseway...

It is installing it for the current user (default setting for the Pulseway 
> agent) so the icons and the registration in the programs and features is 
> done for the administrator (or the user that Jenkins uses to run the 
> command).
>
>  
>
> You can install it for all users by adding this property to the command 
> line:
>
> ALLUSERS=1
>

Any help would be appreciated.

Thanks,

Aaron 

-- 
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/5d9d57f6-cf4b-4e9b-9d10-9abc1bf98f68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What are the rules for Jenkins Pipeline to allocate workspaces, are ephemeral workspaces possible?

[Baptiste Mathus]

Also, it would be very easy to define a function like cleanNode that would
be a node calling by default deleteDir before running the passed closure.

Possibly this could even be done as a PR on the node step itself, adding a
boolean param to ask for that (?).
Le 22 juin 2016 4:17 PM, "'Björn Pedersen' via Jenkins Users" <
jenkinsci-users@googlegroups.com> a écrit :

> Hi,
>
> the pipeline tutorial explains workspace quite well:
> https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md#allocating-workspaces
> The default workspace created by 'node' is 'locked'  to a single run of
> the appropriate node part. It is not cleared by default.
> If you need more than one  workspace on a node 'ws' and/or 'dir' may be
> handy.
>
> Björn
>
>
> Am Mittwoch, 22. Juni 2016 15:13:10 UTC+2 schrieb James Read:
>>
>> Hi Antonio,
>>
>> So what I think you're saying, is that every workspace assigned is
>> allowed to contain anything - from other jobs, and always deleteDir()
>> should be used if a clean environment is needed?
>>
>> Is there a way to request a empty workspace, that is also deleted after
>> the node{} block completes when using the Pipeline plugin?
>>
>> - James
>>
>> On Tuesday, 21 June 2016 16:30:22 UTC+1, Antonio Muñiz wrote:
>>>
>>>
>>> On Tue, Jun 21, 2016 at 3:20 PM, James Read  wrote:
>>>
 It seems that actually the Pipeline makes the whole Jenkinsfile 1x
 logical job, and the node{} blocks just allow different node selections
 during that job.
>>>
>>>
>>> Not. Every `node` call has its workspace (and it can be erased at any
>>> time by Jenkins core, so you never know if the workspace contains what you
>>> think). Which means that the Jenkinsfile has to be idempotent and don't
>>> rely on workspace contents from previous builds. Actually every node block
>>> should remove/put whatever it needs (you can move things from one node to
>>> another by using `stash`).
>>>
>>> If you request for two nodes in the same Jenkinsfile using different
>>> labels, you would be using two nodes with two separated workspaces (even in
>>> different physical machines!).
>>>
>>>
>>> --
>>> Antonio Muñiz
>>> Software Engineer
>>> CloudBees, Inc.
>>>
>> --
> 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/54f41f3e-98e7-418b-af94-44f1ef29b6ca%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS4e1Kw%2B6ELNcCHhmS1Zc3s93ASC%2BLJe-KSVojiOq2XtvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multi branch pipeline: How to read global environment variables?

[shan]

There is a typo:
env.DATABASE = props.DATABASE

-- 
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/35df3bee-bea1-4116-9915-7e2bd44c3aeb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Multi branch pipeline: How to read global environment variables?

[shan]

What is a proper way to read environment variables for multi branch 
pipeline?

Right now, I am reading an env.properties file kept in jenkins workspace, 
and then populating my global env.

def readEnvVars(envFile) {
def props = new Properties()
def fis = new FileInputStream(envFile)
props.load(fis)
return props
}
node {
// write into global env variables
def props = readEnvVars('env.properties')
env.DATABASE = props.DATABSE
// and more global env variable
}



I am not that happy with this approach. Still, I can live with it. But this 
throws error in case of multi branch, but works for single branch pipeline.

Error stack trace:

groovy.lang.MissingPropertyException: No such property: props for class: 
groovy.lang.Binding
at groovy.lang.Binding.getVariable(Binding.java:63)
at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224)
at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241)
at 
org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238)
at 
org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:221)
at 
com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:23)
at 
com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:17)
at WorkflowScript.run(WorkflowScript:75)
at ___cps.transform___(Native Method)
at 
com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:62)
at 
com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
at 
com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at 
com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
at com.cloudbees.groovy.cps.Next.step(Next.java:58)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:32)
at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:29)
at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
at 
org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:29)
at 
org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:276)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:78)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:185)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:183)
at 
org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)


I am not able to figure out what's going wrong.

-- 
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/78b10946-cfbb-493e-bf6d-7741621e90ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What are the rules for Jenkins Pipeline to allocate workspaces, are ephemeral workspaces possible?

['Björn Pedersen' via Jenkins Users]

Hi,

the pipeline tutorial explains workspace quite well: 
https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md#allocating-workspaces
The default workspace created by 'node' is 'locked'  to a single run of the 
appropriate node part. It is not cleared by default.
If you need more than one  workspace on a node 'ws' and/or 'dir' may be 
handy.

Björn


Am Mittwoch, 22. Juni 2016 15:13:10 UTC+2 schrieb James Read:
>
> Hi Antonio, 
>
> So what I think you're saying, is that every workspace assigned is allowed 
> to contain anything - from other jobs, and always deleteDir() should be 
> used if a clean environment is needed?
>
> Is there a way to request a empty workspace, that is also deleted after 
> the node{} block completes when using the Pipeline plugin? 
>
> - James 
>
> On Tuesday, 21 June 2016 16:30:22 UTC+1, Antonio Muñiz wrote:
>>
>>
>> On Tue, Jun 21, 2016 at 3:20 PM, James Read  wrote:
>>
>>> It seems that actually the Pipeline makes the whole Jenkinsfile 1x 
>>> logical job, and the node{} blocks just allow different node selections 
>>> during that job.
>>
>>
>> Not. Every `node` call has its workspace (and it can be erased at any 
>> time by Jenkins core, so you never know if the workspace contains what you 
>> think). Which means that the Jenkinsfile has to be idempotent and don't 
>> rely on workspace contents from previous builds. Actually every node block 
>> should remove/put whatever it needs (you can move things from one node to 
>> another by using `stash`).
>>
>> If you request for two nodes in the same Jenkinsfile using different 
>> labels, you would be using two nodes with two separated workspaces (even in 
>> different physical machines!).
>>
>>
>> -- 
>> Antonio Muñiz
>> Software Engineer
>> CloudBees, Inc.
>>
>

-- 
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/54f41f3e-98e7-418b-af94-44f1ef29b6ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: artifactory plugin maven job : Unable to determine Maven version

[Matthieu Simonin]

Hi, 

Jenkins 2.9 
Artifactory Plugin: 2.4.6

is better for me.

Can we conclude that this issue is more related to the artifactory plugin ?

Best,

Matt 

Le mercredi 22 juin 2016 11:10:53 UTC+2, Stephan Leicht Vogt a écrit :
>
> Hi again
>
> Following combination works for me:
>
> Jenkins: 2.10
> Artifactory Plugin: 2.4.6
>
> Greetings
> Stephan
>
> On Wednesday, June 22, 2016 at 11:05:47 AM UTC+2, Stephan Leicht Vogt 
> wrote:
>>
>> Hi
>>
>> I have the same issue even after downgrading artifactory plugin to 2.4.7.
>>
>> Any solution/workaround would be most appreciated.
>>
>> Greetings
>> Stephan
>>
>> On Tuesday, June 21, 2016 at 10:02:51 PM UTC+2, Matthieu Simonin wrote:
>>>
>>> Hello,
>>>
>>> In a maven job : 
>>> When enabling artifactory plugin to deploy artifacts to artifactory
>>> I got the following error (see stacktrace below).
>>>
>>> The build succeeds if I don't "deploy artifacts to artifactory".
>>>
>>> This behaviour has been observed fot 
>>> Jenkins version : 
>>>  - 1.651.2
>>>  - 1.651.3
>>>  - 1.658
>>>  - 2.9
>>>
>>> and artifactory plugin 2.5.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e0ce8211-28cb-48b0-8c45-292c4ee9ca4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What are the rules for Jenkins Pipeline to allocate workspaces, are ephemeral workspaces possible?

[Antonio Muñiz]

> every workspace assigned is allowed to contain anything - from other jobs

No, only for the same job.

> Is there a way to request a empty workspace

No, you have to use deleteDir() to be sure.

> that is also deleted after the node{} block completes

No, again, use deleteDir() as the last step in `node` or `ws` (however,
having deleteDir() as first step you don't need this one).

If you don't want to delete the entire workspace, you can use `dir` step to
create a directory inside the workspace (and clean it up by
`dir('dir_name') { deleteDir() }`

BTW, all this information is in the snippet generator help tips (navigate
to http://[JENKINS]/job/[job_name]/pipeline-syntax/).

On Wed, Jun 22, 2016 at 3:13 PM, James Read  wrote:

> Hi Antonio,
>
> So what I think you're saying, is that every workspace assigned is allowed
> to contain anything - from other jobs, and always deleteDir() should be
> used if a clean environment is needed?
>
> Is there a way to request a empty workspace, that is also deleted after
> the node{} block completes when using the Pipeline plugin?
>
> - James
>
> On Tuesday, 21 June 2016 16:30:22 UTC+1, Antonio Muñiz wrote:
>>
>>
>> On Tue, Jun 21, 2016 at 3:20 PM, James Read  wrote:
>>
>>> It seems that actually the Pipeline makes the whole Jenkinsfile 1x
>>> logical job, and the node{} blocks just allow different node selections
>>> during that job.
>>
>>
>> Not. Every `node` call has its workspace (and it can be erased at any
>> time by Jenkins core, so you never know if the workspace contains what you
>> think). Which means that the Jenkinsfile has to be idempotent and don't
>> rely on workspace contents from previous builds. Actually every node block
>> should remove/put whatever it needs (you can move things from one node to
>> another by using `stash`).
>>
>> If you request for two nodes in the same Jenkinsfile using different
>> labels, you would be using two nodes with two separated workspaces (even in
>> different physical machines!).
>>
>>
>> --
>> Antonio Muñiz
>> Software Engineer
>> CloudBees, Inc.
>>
> --
> 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/77432682-e150-469f-bef9-fc28297ddbb1%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Antonio Muñiz
Software Engineer
CloudBees, Inc.

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

Re: What are the rules for Jenkins Pipeline to allocate workspaces, are ephemeral workspaces possible?

[James Read]

Hi Antonio, 

So what I think you're saying, is that every workspace assigned is allowed 
to contain anything - from other jobs, and always deleteDir() should be 
used if a clean environment is needed?

Is there a way to request a empty workspace, that is also deleted after the 
node{} block completes when using the Pipeline plugin? 

- James 

On Tuesday, 21 June 2016 16:30:22 UTC+1, Antonio Muñiz wrote:
>
>
> On Tue, Jun 21, 2016 at 3:20 PM, James Read  > wrote:
>
>> It seems that actually the Pipeline makes the whole Jenkinsfile 1x 
>> logical job, and the node{} blocks just allow different node selections 
>> during that job.
>
>
> Not. Every `node` call has its workspace (and it can be erased at any time 
> by Jenkins core, so you never know if the workspace contains what you 
> think). Which means that the Jenkinsfile has to be idempotent and don't 
> rely on workspace contents from previous builds. Actually every node block 
> should remove/put whatever it needs (you can move things from one node to 
> another by using `stash`).
>
> If you request for two nodes in the same Jenkinsfile using different 
> labels, you would be using two nodes with two separated workspaces (even in 
> different physical machines!).
>
>
> -- 
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.
>

-- 
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/77432682-e150-469f-bef9-fc28297ddbb1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline: How to cache downloaded (gradle) dependencies using Docker SSH Slave

[Marco Pas]

Now that we have a first successful build using a Jenkinsfile Pipeline we 
are looking on how to cache downloaded dependencies.
Currently when we build our Gradle applications the dependencies are 
downloaded each time the Docker Slave is executed on a remote host. Is 
there a way to cache the downloaded dependencies for later reuse so we can 
speedup the build process?

- Marco

-- 
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/b552e554-93fa-41f7-864c-0d25cb62feb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: Defined parameters are not available in the build

[Sverre Moe]

Yes it is in the job configuration for the multibranch pipeline job

Running the following in the script (Jenkinsfile) should add the parameter 
to the branch projects configuration.
properties([[$class: 'ParametersDefinitionProperty', parameterDefinitions: 
[[$class: 'BooleanParameterDefinition',defaultValue: false, description: 
'Description', name: 'PROP_VERIFY')
The next time building "Build with parameter" you can check this parameter, 
but it is not available in the build.

After SECURITY-170 all parameters not defined in the project was no longer 
available. Triggering a downstream build with a parameter not defined was 
not propagated to the downstream build. After adding the parameter it gets 
propagated.


onsdag 22. juni 2016 13.31.01 UTC+2 skrev Björn Pedersen følgende:
>
> Is '../projectA/master' configured to accept parameter PROP_VERIFY (In 
> the job definition, not in the Jenkinsfile)? Else I guess due to SEC-170 
> fixes, the parameter is not propagetd to the environment. Actually that 
> would be a chicken-and-egg type problem. You need to get and execute the 
> current jenkinsfile to see, if the param is allowed, but the param should 
> already be set. See https://jenkins.io/blog/2016/05/11/security-update/ 
> 
>  
> for details.
>
> The linked issue seem to be a slightly different problem.
>
> Björn
>
> Am Mittwoch, 22. Juni 2016 13:13:48 UTC+2 schrieb Sverre Moe:
>>
>> Have defined parameter for my pipeline projects in the main pipeline 
>> script:
>> properties([[$class: 'ParametersDefinitionProperty', parameterDefinitions
>> : [[$class: 'BooleanParameterDefinition', defaultValue: false, 
>> description: 'Description', name: 'PROP_VERIFY')
>>
>> After building the first time with this I get the option "Build with 
>> Parameters".
>>
>> Doesn't matter how I start a new build. Either manually or in the script:
>> build job: '../projectA/master', parameters: [[$class: 
>> 'BooleanParameterValue', name: 'PROP_VERIFY', value: true]]
>> The environment variable env.PROP_VERIFY is not available. It it always 
>> null.
>>
>> After building I am checking the following URL and can se that the 
>> parameter is set:
>> http://server.company.com:8080/job/projectA/job/master/70/parameters/
>>
>

-- 
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/327d3829-c6e5-4753-8469-bdbda7d1262d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: Defined parameters are not available in the build

['Björn Pedersen' via Jenkins Users]

Is '../projectA/master' configured to accept parameter PROP_VERIFY (In the 
job definition, not in the Jenkinsfile)? Else I guess due to SEC-170 fixes, 
the parameter is not propagetd to the environment. Actually that would be a 
chicken-and-egg type problem. You need to get and execute the current 
jenkinsfile to see, if the param is allowed, but the param should already 
be set. See https://jenkins.io/blog/2016/05/11/security-update/ for details.

The linked issue seem to be a slightly different problem.

Björn

Am Mittwoch, 22. Juni 2016 13:13:48 UTC+2 schrieb Sverre Moe:
>
> Have defined parameter for my pipeline projects in the main pipeline 
> script:
> properties([[$class: 'ParametersDefinitionProperty', parameterDefinitions: 
> [[$class: 'BooleanParameterDefinition', defaultValue: false, description: 
> 'Description', name: 'PROP_VERIFY')
>
> After building the first time with this I get the option "Build with 
> Parameters".
>
> Doesn't matter how I start a new build. Either manually or in the script:
> build job: '../projectA/master', parameters: [[$class: 
> 'BooleanParameterValue', name: 'PROP_VERIFY', value: true]]
> The environment variable env.PROP_VERIFY is not available. It it always 
> null.
>
> After building I am checking the following URL and can se that the 
> parameter is set:
> http://server.company.com:8080/job/projectA/job/master/70/parameters/
>

-- 
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/c117a5ac-ab9b-4622-b825-8848c28bed62%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: Defined parameters are not available in the build

[Sverre Moe]

Seems there is an issue for this
https://issues.jenkins-ci.org/browse/JENKINS-30206

I hope for a fix soon. I am stuck without this.

onsdag 22. juni 2016 13.13.48 UTC+2 skrev Sverre Moe følgende:
>
> Have defined parameter for my pipeline projects in the main pipeline 
> script:
> properties([[$class: 'ParametersDefinitionProperty', parameterDefinitions: 
> [[$class: 'BooleanParameterDefinition', defaultValue: false, description: 
> 'Description', name: 'PROP_VERIFY')
>
> After building the first time with this I get the option "Build with 
> Parameters".
>
> Doesn't matter how I start a new build. Either manually or in the script:
> build job: '../projectA/master', parameters: [[$class: 
> 'BooleanParameterValue', name: 'PROP_VERIFY', value: true]]
> The environment variable env.PROP_VERIFY is not available. It it always 
> null.
>
> After building I am checking the following URL and can se that the 
> parameter is set:
> http://server.company.com:8080/job/projectA/job/master/70/parameters/
>

-- 
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/369cb692-c88f-4bfd-ad3a-0128196e8590%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline: Defined parameters are not available in the build

[Sverre Moe]

Have defined parameter for my pipeline projects in the main pipeline script:
properties([[$class: 'ParametersDefinitionProperty', parameterDefinitions: 
[[$class: 'BooleanParameterDefinition', defaultValue: false, description: 
'Description', name: 'PROP_VERIFY')

After building the first time with this I get the option "Build with 
Parameters".

Doesn't matter how I start a new build. Either manually or in the script:
build job: '../projectA/master', parameters: [[$class: 
'BooleanParameterValue', name: 'PROP_VERIFY', value: true]]
The environment variable env.PROP_VERIFY is not available. It it always 
null.

After building I am checking the following URL and can se that the 
parameter is set:
http://server.company.com:8080/job/projectA/job/master/70/parameters/

-- 
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/85e293f2-1758-4c7f-a9f8-97daf7a02bf1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins fails to deliver e-mails

[S. S.]

Some more things i have tried:

Different users (service users, normal users, etc) - all failed
newer version of mailer plugin - no change


Am Montag, 20. Juni 2016 09:24:51 UTC+2 schrieb S. S.:
>
> This might be a tough thing to figure out but i have to give it a try.
>
> With no changes i am aware of, my jenkins just stopped sending out e-mail 
> notifications. I use jenkins 1.609 and email extension plugin 2.40.5. 
> Jenkins runs as a service using a service-user who also has the rights on 
> the server to send e-mails. Ports to our smtp-server are unlocked. Used 
> telnet for testing that everything works as expected. SMTP-server works 
> fine, so it has something to do with jenkins and i cant figure out what is 
> going wrong.  When i use the test-feature that jenkins offers i get: 
> javax.mail.AuthenticationFailedException: 
> 535 5.7.3 Authentication unsuccessful which tells me that either user or 
> pw is incorrect, but i've checked many times, it's setup correctly. Can 
> anyone help out with this?
>   
> After decrypting the password i can safely say that jenkins does save the 
> password correct. 
>
>  
>
> Pw is set to not expire, because of reasons like this. Checked anyway, but 
> its working as intended.
>
> I also installed the Powershell-Plugin to test if Jenkins would send a 
> mail using the script.  I created a job that sends a mail using the 
> powershell script and another mail right after using the mailer plugin. 
> Script works fine, mailer plugin fails.
>
> I asked the same question on Stack Overflow, it did not solve my problem 
> sadly.
>
> Any help is 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/34e7ea02-e84b-44ea-bc3b-f1323907bed6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: artifactory plugin maven job : Unable to determine Maven version

[Stephan Leicht Vogt]

Hi again

Following combination works for me:

Jenkins: 2.10
Artifactory Plugin: 2.4.6

Greetings
Stephan

On Wednesday, June 22, 2016 at 11:05:47 AM UTC+2, Stephan Leicht Vogt wrote:
>
> Hi
>
> I have the same issue even after downgrading artifactory plugin to 2.4.7.
>
> Any solution/workaround would be most appreciated.
>
> Greetings
> Stephan
>
> On Tuesday, June 21, 2016 at 10:02:51 PM UTC+2, Matthieu Simonin wrote:
>>
>> Hello,
>>
>> In a maven job : 
>> When enabling artifactory plugin to deploy artifacts to artifactory
>> I got the following error (see stacktrace below).
>>
>> The build succeeds if I don't "deploy artifacts to artifactory".
>>
>> This behaviour has been observed fot 
>> Jenkins version : 
>>  - 1.651.2
>>  - 1.651.3
>>  - 1.658
>>  - 2.9
>>
>> and artifactory plugin 2.5.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/36ed5667-5634-4bdb-804b-8da34088598b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: artifactory plugin maven job : Unable to determine Maven version

[Stephan Leicht Vogt]

Hi

I have the same issue even after downgrading artifactory plugin to 2.4.7.

Any solution/workaround would be most appreciated.

Greetings
Stephan

On Tuesday, June 21, 2016 at 10:02:51 PM UTC+2, Matthieu Simonin wrote:
>
> Hello,
>
> In a maven job : 
> When enabling artifactory plugin to deploy artifacts to artifactory
> I got the following error (see stacktrace below).
>
> The build succeeds if I don't "deploy artifacts to artifactory".
>
> This behaviour has been observed fot 
> Jenkins version : 
>  - 1.651.2
>  - 1.651.3
>  - 1.658
>  - 2.9
>
> and artifactory plugin 2.5.0
>
> Am I missing something in the configuration, or someone experienced the 
> same issue ? 
>
> Best,
>
> Matthieu
>
> ERROR: Processing failed due to a bug in the code. Please report this to 
> jenkins...@googlegroups.com 
> java.lang.RuntimeException: Unable to determine Maven version
> at 
> org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.isMavenVersionValid(MavenExtractorEnvironment.java:167)
> at 
> org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.buildEnvVars(MavenExtractorEnvironment.java:100)
> at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:931)
> at 
> hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:56)
> at 
> hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:166)
> at 
> hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:622)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
> at hudson.model.Run.execute(Run.java:1720)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
> at hudson.model.ResourceController.execute(ResourceController.java:98)
> at hudson.model.Executor.run(Executor.java:410)
> Caused by: java.io.IOException: Remote call on [[mycomp]] failed
> at hudson.remoting.Channel.call(Channel.java:789)
> at hudson.FilePath.act(FilePath.java:1102)
> at 
> org.jfrog.hudson.util.MavenVersionHelper.isAtLeast(MavenVersionHelper.java:109)
> at 
> org.jfrog.hudson.util.MavenVersionHelper.isAtLeastVersion(MavenVersionHelper.java:81)
> at 
> org.jfrog.hudson.util.MavenVersionHelper.isAtLeastResolutionCapableVersion(MavenVersionHelper.java:72)
> at 
> org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.isMavenVersionValid(MavenExtractorEnvironment.java:165)
> ... 10 more
> Caused by: java.lang.NoClassDefFoundError: 
> org/codehaus/plexus/classworlds/realm/ClassRealm
> at 
> org.jfrog.hudson.maven3.MavenVersionCallable.call(MavenVersionCallable.java:45)
> at 
> org.jfrog.hudson.maven3.MavenVersionCallable.call(MavenVersionCallable.java:33)
> at hudson.remoting.UserRequest.perform(UserRequest.java:153)
> at hudson.remoting.UserRequest.perform(UserRequest.java:50)
> at hudson.remoting.Request$2.run(Request.java:332)
> at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> at ..remote call to [[mycomp]] (Native Method)
> at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
> at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
> at hudson.remoting.Channel.call(Channel.java:781)
> ... 15 more
> Caused by: java.lang.ClassNotFoundException: 
> org.codehaus.plexus.classworlds.realm.ClassRealm
> at 
> jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1376)
> at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326)
> at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at 
> hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:761)
> at 
> hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:803)
> at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at 
> hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:884)
> at hudson.remoting.Request$2.run(Request.java:332)
> at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
> at org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:18)
> at 
> hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21)
> at 
> jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:6

Re: Multibranch Pipeline: How to parameterize?

[Sverre Moe]

It seems there is no point with Envinject-plugin with Pipeline
There is an issue for removing it in the configuration screen.
https://issues.jenkins-ci.org/browse/JENKINS-26569

Then this is no longer an issue for me. Using the properties context in the 
script I was able to add parameters to my multibranch pipeline.

onsdag 22. juni 2016 08.45.18 UTC+2 skrev Sverre Moe følgende:
>
> Found some clue in https://issues.jenkins-ci.org/browse/JENKINS-32780
> Using the Snippet code generator I was able to generate a build parameter
> properties [[$class: 'ParametersDefinitionProperty', parameterDefinitions: 
> [[$class: 'BooleanParameterDefinition', defaultValue: false, description: 
> 'Force publish RPM artifacts to repository', name: 'FORCE_PUBLISH'
>
> If I want all branches to have this property, could I put it in my global 
> script? I am trying to keep my Jenkinsfiles as DRY as possible.
>
> Using the Snippet generator to "Prepare an environment for the run"
> This is needed because of SECURITY-170, otherwised properties are not 
> propagated to downstream builds.
> It does not generate anything useful. Previously the result was empty 
> whatever I put within "Properties Content". Now I only get
> properties [ EnvInjectJobProperty>]
> This is what the snippet generator gives me for any of the choices, 
> script, file or content.
>
>
>
> onsdag 22. juni 2016 08.27.13 UTC+2 skrev Sverre Moe følgende:
>>
>> Each branch pipeline has their own config.xml. A standard pipeline job 
>> does have support for parameterization. I think I read somewhere in Jenkins 
>> JIRA that such properties should be defined in the Jenkinsfile and set for 
>> the branch pipeline project on the first run. I am a bit unsure how to set 
>> them. Cannot find a single example of this.
>>
>> https://issues.jenkins-ci.org/browse/JENKINS-30519
>>
>> I know how to set them programatically in the Script console for 
>> "regular" projects.
>> StringBuilder builder = new StringBuilder()
>> builder.append("PROP1=true")
>> builder.append("\n")
>> builder.append("PROP2=true")
>> final def propertiesContent = builder.toString()
>>
>> def info = new EnvInjectJobPropertyInfo(null, propertiesContent, 
>> null, null, null, false)
>> def property = new EnvInjectJobProperty()
>> property.setOn(true)
>> property.setKeepJenkinsSystemVariables(true)
>> property.setKeepBuildVariables(true)
>> property.setInfo(info)
>>
>> project.addProperty(property)
>> project.save()
>>
>>
>> mandag 13. juni 2016 10.20.55 UTC+2 skrev Sverre Moe følgende:
>>>
>>> Either I am doing it wrong, or Multibranch pipeline has no way of 
>>> sending parameters to downstream builds.
>>> Considering that each branch within a multibranch pipeline seems to be a 
>>> single Pipeline project and standard such Pipeline projects can be 
>>> parameterized.
>>>
>>> onsdag 8. juni 2016 12.42.01 UTC+2 skrev Sverre Moe følgende:

 Jenkins Pipeline can be parameterized, but not multibranch pipelines. 
 There is no option for "This build is parameterized" in the configuration 
 of a multibranch pipeline. Why is that?

 I have a multibranch project for each repository with multiple branches.

 ProjectA
 master
 develop
 releaseX
 ProjectB
 master
 develop
 releaseX

 In this case ProjectB has a dependency on ProjectA on the same branch.

 The Jenkinsfile is sparse, while the common main build logic is stored 
 in workflowLibs.git

 When a upstream project builds a dependent downstream project I need to 
 provide them with build parameters.
 def BUILD_PROJECT = "projectB"+"/"+env.BUILD_BRANCH
 build job: BUILD_PROJECT, parameters: [[$class: 'BooleanParameterValue'
 , name: 'UPSTREAM_TRIGGERED', value: true]]
 I have some logic in the main build script for when the build is 
 triggered by an upstream dependency.

 Not sure how I can do this since multibranch pipeline cannot be 
 parameterized.

 I have even tried withEnv, but it did not work
 withEnv(["UPSTREAM_TRIGGERED=true"]) {
 def BUILD_PROJECT = "projectB"+"/"+env.BUILD_BRANCH
 build BUILD_PROJECT
 }

>>>

-- 
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/922fe089-6cb2-49e7-9dc9-77c119035eba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Free Monitoring & Alerting tool for Jenkins

[Mike Bayliss]

And less than a day after watching the video I get a LinkedIn contact
request from somebody I don't know at ALMtoolbox.

Mike

On Tue, Jun 21, 2016 at 1:48 PM, David Cohen  wrote:

> Hello to all Jenkins folks,
>
> I'd like to inform you that for the first time, we now provide a Free
> Community Edition of our performance monitoring & alerting tool for Jenkins.
>
> You can quickly get email alerts on slow Jenkins jobs, malfunctioning
> JVMs, slow [or overloaded] Jenkins slaves; unavailable hosts; along with
> daily uptime charts; a graphic dashboard and many other great features.
>
>
> See its dashboard:
>
>
>
>
> To learn more about the tool and download it, follow this link:
> http://www.almtoolbox.com/jenkins.php.
>
>
> You can monitor an unlimited number of Jenkins hosts, and it takes only 1
> hour to start enjoying it :)
>
>
> See a quick demo: https://www.youtube.com/watch?v=263Nxy1Qb9c
>
>
> and if you like it, please share with your colleagues - it's a free tool
> and I'm pretty sure they will thank you.
>
> David-Or Cohen
> Product Manager
> *ALMtoolbox - Productivity ALM Solutions*
> *www.almtoolbox.com *
> Tel - +972 54 778 7266
>
>
> --
> 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/8952d24b-2285-49d9-82a0-93bb0061da11%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAC-P8utzYBiTqhjqFGo%2BJyRdhBzG5G0BaiFyvrQXW71rF39Lvw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Debian origin has changed since 2.9

[Pieter-Jan Busschaert]

Just FYI,


I had unattended-upgrades updating my Jenkins install on Debian 
automatically from pkg.jenkins-ci.org. This had been running fine for a 
long time, however I noticed the upgrades were stuck on version 2.8 and 
didn't continue. Apparently the "origin" parameter of the package has 
changed from "jenkins-ci.org" to "jenkins.io". So, when you are using 
allowed-origins to automatically update jenkins, you might have to edit / 
add that value for the Jenkins repository.


Kind regards,

Pieter-Jan

-- 
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/3a5f0a16-7ca4-4247-9f89-292c321985a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.