Re: Jenkins Perforce workspace question

[Martin]

Hi, Iata:

Thanks for your detailed info. But I still have some questions.  To keep it 
simpler, I did the following:

I created a super simple test case. It would be great if you can point out 
where I may be wrong. I just want to have a simple test of using P4 Jenkins 
plugin.  My steps are below:
1) Following the P4 wizard, I created a workspace named "test", which point 
to the root of the directory /home/abigail/p4/test/test1 on my local 
machine. 
Please see the attached "p4-workspace.png"

2) In the P4 depot there are two projects, "test1" & "test2", and test1 
maps to the workspace "test". 
Please see "p4-depot.png"

3) In Jenkins, I typed the workspace name "test" and the view map 
"//depot/test1/... //test/...". 
Please see "P4-jenkins.png"

4) admin@Jenkins:~$ p4 info
User name: admin
Client name: test
Client host: Jenkins
Client root: /home/abigail/p4/test/test1
Current directory: /home/admin
Peer address: ...
Client address: xx.xx.xx.xx
Server address: xx.xx.xx.xx:1666
Server root: /opt/p4d
Server date: 2015/07/22 01:42:32 -0400 EDT
Server uptime: 00:32:40
Server version: P4D/LINUX26X86_64/2015.1/1171507 (2015/06/30)
Server license: none
Case Handling: sensitive

My Jenkins is installed by default /var/lib/jenkins/

Event time the Jenkins build finishes, the root of the workspace "test" 
changes to "/var/lib/jenkins/..." from /home/abigail/p4/test/test1 on my 
local machine. This is not the right behavior, or not the good practice, 
right? I need the root directory "/home/abigail/p4/test/test1"  on my local 
machine because all my project resides in this directory, and I can sync 
with P4, but this root is not known by Jenkins, so it copies all files from 
my local workspace root directory to Jenkin's default installation location 
/var/lib/jenkins... for each build. I guess my setting of workspace root 
isn't quite right? But I just followed the P4 wizard to create the 
workspace, and I can syc with P4 correctly. The problem is when Jenkins 
comes into play.

Please use simple or step-wise language to help me get this configured 
properly. This is a simple typical setup. I want to configure nothing 
Unique or Special. Thank you.

Martin

On Tuesday, July 21, 2015 at 5:41:43 AM UTC-4, lata wrote:
>
> 1) What's the problem here? 
>
> 1. Jenkins Perforce Workspace at /var/lib/jenkins/jobs/...
> - The name of this P4 workspace is whatever you have typed in the 
> 'Workspace' field of your Jenkins project configuration -> Perforce 
> section. I'm guessing you typed in 'jenkins_test'.
> - The P4 root of this P4 Workspace would be relative to your slave's Remot 
> Root or your Jenkins Master (if you are running your project directly on 
> Jenkins Master, and not on a slave).
> - Default behaviour is that Jenkins updates the P4 workspace with the Root 
> and Host values, you can override this by checking the 'Don't update client 
> workspace' option in the Advanced section.
>
> 2. Your Perforce workspace, 'jenkins_test', with root /home/maritn/p4/test
> Jenkins is not aware that you have such a P4 workspace created, and that 
> you want to use it. As mentioned above, it will override Root and Host 
> unless you ask it not to.
>
> Reco: 1. If you really can't go with the Jenkins chosen workspace to sync 
> your p4 code to, don't use the option 'Don't update client workspace', 
> instead use the 'custom workspace' in the Advanced project option, and 
> change the workspace location to /home/martin/, if you need to. 
> Don't manage this Jenkins created P4 workspace outside this environment, 
> let Jenkins manage it. (I'm assuming you can't get a slave machine, and 
> need to run your jobs on the Master itself? Otherwise you can straightway 
> set your Slave's remote root location to the right place that you want)
> 2. If you really need to use your Perforce client created outside for some 
> reason, then use the command line within Jenkins config shell and do a 
> manual sync such as P4 -c $yourclient
>
> 2) Does the user "jenkins" on Jenkins have anything to do with the Linux 
> user who installed Jenkins and P4?
> No
>
>
> On Tuesday, July 21, 2015 at 3:36:32 PM UTC+8, Martin wrote:
>>
>> Hello, it's the first time to setup Jenkins Perforce Plugin. I just 
>> wanted to setup a simple project to test the automatic build feature in 
>> Jenkins. On my local machine, my project is:
>>
>> /home/martin/p4/test
>>
>> I created a workspace named jenkins_test, whose root 
>> is /home/martin/p4/test. I can test syncing with Perforce.
>>
>> However, in Jenkins, whenever a build finishes, it changes my root 
>> directory of my workspace from /home/martin/p4/test to 
>> /var/lib/jenkins/jobs/ on the Jenkins machine. This isn't the expected 
>> behavior, right? Otherwise, I have to change the root of the workspace back 
>> to /home/maritn/p4/test on my local machine after each build. 
>>
>> In Jenkins, I created a user named "jenkins" and use that user name to 
>> login Jenkins to start the bui

Re: Jenkins behind SSL, my case not going through

[Snd Lt]

Nevermind.
SELinux had been blocking the communication. Used "setsebool"

On Tuesday, July 21, 2015 at 6:37:21 AM UTC-7, Snd Lt wrote:
>
> Thanks for your time.
> I'm still learning up on Apache and Jenkins.
>
> I've been struggling for days with this. 
>
> Would you mind briefly narrating which should go to httpd.conf and to 
> ssl.conf?
> Perhaps I'm putting ProxyPass to wrong places.
> Not getting the whole picture.
>
> Corrected the syntax but still doing "Service Unavailable, The server is 
> temporarily unable to service your request due to maintenance downtime or 
> capacity problems. Please try again later."
>
> Thanks again.
>
> On Tuesday, July 21, 2015 at 1:16:37 AM UTC-7, Corneil du Plessis wrote:
>>
>> ProxyPass required a path and a url
>> The path is applied to incoming request and matches are sent to the url.
>>
>> ProxyPass /jenkins http://localhost:8080/jenkins
>>
>> In your case you had
>> ProxyPass http://localhost:8080/
>>
>> The correct syntax is:
>> ProxyPass / http://localhost:8080/
>>
>>
>> On Monday, 20 July 2015 17:17:21 UTC+2, Snd Lt wrote:
>>>
>>> Thanks. How would you define that otherwise?
>>> I thought I already defined it at localhost:8080? Which is where Jenkins 
>>> is accessible at?
>>>
>>> On Monday, July 20, 2015 at 8:15:35 AM UTC-7, Corneil du Plessis wrote:

 The path is missing from your ProxyPass and ProxyPassReverse items.

 On 20 July 2015 at 17:01, Snd Lt  wrote:

> ProxyPass http://localhost:8080/ ProxyPassReverse 
> http://localhost:8080/ ProxyPassReverse http://server.com/


 ProxyPass /  http://localhost:8080/
 ProxyPassReverse  /  http://localhost:8080/
 ProxyPassReverse  /  http://server.com/


  
 [image: --]
 Corneil du Plessis
 [image: https://]about.me/corneil
   
  
>>>

-- 
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/c74a945b-0e0b-497e-93ec-c98641424fe5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins P4 (Perforce) Plugin exposed variables

[BeckyY]

Thank you, Daniel!Yes, it was as simple as that!   P4_CHANGELIST is an 
environment variable containing the latest changelist for the path 
provided. 

On Tuesday, July 21, 2015 at 3:49:38 PM UTC-7, BeckyY wrote:
>
> Question is about the P4 plugin by Perforce, not the Perforce plugin by a 
> third party.
> I didn't see in the documentation any info about exposed variables.   In 
> particular, I need to know the changelist # that the plugin selects to 
> build against.   I created a simple project in Jenkins, configured perforce 
> for it. I see from the build log (console output) that it got the latest 
> changelist.  But within my build scripts I need to use that changelist 
> number as a variable.   Anyone know what variables the P4 plugin provides 
> for build scripts?
>

-- 
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/f5ae945e-edc5-4fc2-ad52-ae9f783e2692%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

JUC East and EU - slides/videos available

[Alyssa Tong]

Hi Everyone,

If you missed JUC East and or JUC Europe - videos and slides from these
conferences are now available HERE
 (JUC East) and HERE
 (JUC EU).

The agenda for JUC West (Sept 2-3, 2015) is also available HERE
. Seats are filling up
fast so sign up
 before
the conference is sold out.  I am looking for community experts to staff
the Ask The Experts booth. Pls shoot me an email if you're interested.

thanks,
alyssa

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

Re: Jenkins P4 (Perforce) Plugin exposed variables

[Daniel Beck]

Probably easiest to find out what environment variables are defined with a 
shell or batch build step that executed 'env' or 'set' respectively.

On 22.07.2015, at 00:49, BeckyY  wrote:

> Question is about the P4 plugin by Perforce, not the Perforce plugin by a 
> third party.
> I didn't see in the documentation any info about exposed variables.   In 
> particular, I need to know the changelist # that the plugin selects to build 
> against.   I created a simple project in Jenkins, configured perforce for it. 
> I see from the build log (console output) that it got the latest changelist.  
> But within my build scripts I need to use that changelist number as a 
> variable.   Anyone know what variables the P4 plugin provides for build 
> scripts?
> 
> -- 
> 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/82072428-0072-4d80-ad7e-5f234a7aa62e%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/AB545FD0-6F43-4D7D-9820-E67D7BF013B4%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Jenkins P4 (Perforce) Plugin exposed variables

[BeckyY]

Question is about the P4 plugin by Perforce, not the Perforce plugin by a 
third party.
I didn't see in the documentation any info about exposed variables.   In 
particular, I need to know the changelist # that the plugin selects to 
build against.   I created a simple project in Jenkins, configured perforce 
for it. I see from the build log (console output) that it got the latest 
changelist.  But within my build scripts I need to use that changelist 
number as a variable.   Anyone know what variables the P4 plugin provides 
for build scripts?

-- 
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/82072428-0072-4d80-ad7e-5f234a7aa62e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Approve workflow script from Job DSL plugin

[David Resnick]

I have a workflow script that I set in the workflow job Groovy CPS DSL 
textbox via Job DSL. The problem is that though security on the server is 
set to "logged in users can do anything", apparently the script is not set 
as "Jenkins administrator".

How can I have the workflow job script updated via Job DSL without having 
to approve the script each time it changes?

This is the general layout of the Job DSL:
def flow = '''
node {
  git url: 'ssh://g...@git.com/repo.git'
}
'''
workflowJob('job1') {
  triggers {
  scm('# triggered by post-commit hook')
  }
  definition {
cps {
  script(flow)
}
  }
}

Jenkins is 1.609.1, workflow 1.8, job dsl 1.35.

Thanks,
David

-- 
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/0a562bd7-e5ef-4b5b-b1c6-998f24cb4770%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

custom global parameterized reporting?

[David Smith]

Hi,

Some backstory/details:

   1. I use Jenkins not for builds, but for automation jobs (robot 
   framework)
   2. I have a separate jenkins job for each test bed, even if they are 
   each capable of running the same tests
   3. Each jenkins job is parameterized; those parameters include which 
   software build will be loaded onto the device to be tested, and which 
   device model is to be tested

I want to be able to create a global report that includes data from 
multiple jobs where:

   1. a chart clearly shows pass/fail statistics for each parameterized 
   software build # and device model (ie, device model vs build pass/fail grid)

Some thoughts

   1. I need to be able to create multiple reports, filtering which jobs 
   provide data to the results (ie regex job name filter)
   2. The simple parameterized reports plugin is very close to what i need, 
   except it only shows data for one job, and the layout is jenkins job# 
   based, where in my case one side of the grid is the sw parameterized build 
   #s and one side is parameterized device type, (xy), and the jenkins job # 
   could be inside the resulting box and the text colored green/red depending 
   on pass/fail


So before I reinvent the wheel, is there anything that might provide this 
data already? (Ability to create an x/y grid report based on global 
parameters) and if not, whats my best direction for a primer on writing my 
own jenkins plugin to do this? (Or add it to someone else's existing 
plugin?)

thanks,
David

-- 
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/e0e41e7a-f2bf-4b82-9708-ba80e186053d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Job spawning a thread that creates an ever-growing log file

[Jeff Dickerson]

After a lot of investigation, I now have a way to reliably reproduce this 
error, and can avoid it. The issue occurs when Jenkins tries to abort the 
job during JBehave testing. It originally occurred when someone manually 
aborted a job, but became consistent when I enabled a Jenkins plugin that 
monitored the build time and aborted the job if it ran too long. Since the 
Dev/QA team had recently added a bunch of new tests, the job was taking 
significantly longer, and so Jenkins was trying to abort the job.

The thing is, the job would successfully abort, but JBehave would spin up a 
thread on the SLAVE that was writing a log file to the /tmp directory on 
the MASTER, with the following stack trace, over and over, in an infinite 
loop until the disk filled up. The class/method referenced in the error 
message is the main JBehave class.

ha:Yx+LCP9b85aBtbiIQSWjNKU4P0+
vJLE4u1gvPjexLDVPzxdEhicW5WXmpfvll6S2fNly5fzGzauYGBgqihikoFqS8/
OK83NS9ZwhNEghAwQwghQWAACwxA+XYg==[WARNING] interrupted while joining 
against thread Thread[com.xxx.xxx.xxx.test.TestOrderCallMain.main(),5,com.
com.xxx.xxx.xxx.test.TestOrderCallMain]
java.lang.InterruptedException
 at java.lang.Object.wait(Native Method)
 at java.lang.Thread.join(Thread.java:1281)
 at org.codehaus.mojo.exec.ExecJavaMojo.joinThread(ExecJavaMojo.java:415)
 at org.codehaus.mojo.exec.ExecJavaMojo.joinNonDaemonThreads(ExecJavaMojo.
java:405)
 at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:317)
 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
DefaultBuildPluginManager.java:101)
 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.
java:209)
 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.
java:153)
 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.
java:145)
 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
LifecycleModuleBuilder.java:84)
 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(
LifecycleModuleBuilder.java:59)
 at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild
(LifecycleStarter.java:183)
 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(
LifecycleStarter.java:161)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
 at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java
:117)
 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 org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(
Launcher.java:329)
 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:
239)
 at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:178)
 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 hudson.maven.Maven3Builder.call(Maven3Builder.java:134)
 at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
 at hudson.remoting.UserRequest.perform(UserRequest.java:121)
 at hudson.remoting.UserRequest.perform(UserRequest.java:49)
 at hudson.remoting.Request$2.run(Request.java:324)
 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)

I've mostly avoided the issue by disabling the Jenkins plugins that 
automatically abort the job run. There is still risk, however, because 
users can manually abort runs.

-- 
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/70f35503-297f-4a64-afc8-d67b4c432d9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Log Parser Plugin

[vijayram]

Hi,

 I installed LogParser Plugin into my Jenkins, I do see it in the installed 
list of plugins; I restarted jenkins instance and tried to see if the 
plugin is loaded in /var/log/jenkins/jenkins.log file... but I don't see it 
loaded 

anything I am missing here... anyone used this plugin..

Thank you,
Vijayram..

-- 
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/dadc701d-84d1-4911-a3a0-77d74506d6f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Forcing another job to run immediately on same node

[Eric Pyle]

One way to do this is using the Priority Sorter Plugin, and give jobB a 
high priority.


On 7/20/2015 10:38 AM, Porter Bassett wrote:
I am trying to break up a job into two smaller jobs, which I'll call 
jobA and jobB.


I want jobB to run *immediately* after jobA, and on the same node, 
just like they did when they were the same job.


I can use use the Parameterized Trigger plugin to make jobA trigger 
jobB on the same node.


However, this triggering of jobB doesn't force it to run immediately. 
 If there are other jobs in the queue, then jobB will just be put on 
the end of the queue.


How can I force jobB to always run immediately after jobA, and on the 
same node?


--
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/a02c83b4-0c1c-412d-83a2-006e8f57384d%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/55AE784F.3080004%40cd-adapco.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re: Re: Build Pipeline plugin and Build Flow plugin

[nicolas de loof]

yes, by intention, as the real world CD scenario I've considered aren't
static and can involve various steps depending on runtime context

start a new pipeline is just about re-trigger the initial step (which I
expect to be a git push)
re-run a build could make sense, but then you can just enable retry plugin
on the adequate jobs
manual steps aren't considered by build flow plugin (but fully supported by
workflow)


2015-07-21 17:02 GMT+02:00 Christoph Kutzinski :

> Am I right when saying the the buildgraphview-plugin is a king of 'after
> the fact' view of a pipeline run?
> *I.e. I can see the results of a pipeline afterwards, but I can not
> actively control a pipeline (lie in the Build Pipeline pluing):*
> *- starting a new pipeline run*
> *- re-running a build*
> *- triggering manul steps*
>
> *Gesendet:* Dienstag, 21. Juli 2015 um 14:45 Uhr
> *Von:* "nicolas de loof" 
> *An:* "jenkinsci-users@googlegroups.com"  >
> *Betreff:* Re: Re: Build Pipeline plugin and Build Flow plugin
>  build graph view do rely on upstreamCause so should handle most
> relations between builds
> and for the others (including build-flow) do offer an extension point to
> discover other relations
>
> 2015-07-21 16:44 GMT+02:00 Christoph Kutzinski :
>>
>>   Thanks!
>> I didn't know about
>> https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin
>>
>> Can I also define manual triggered steps in a setup of the Build-Flow
>> plugin and the build-graphview-plugin like you can do with the build
>> pipeline plugin?
>>
>> *Gesendet:* Dienstag, 21. Juli 2015 um 14:37 Uhr
>> *Von:* "nicolas de loof" 
>> *An:* "jenkinsci-users@googlegroups.com" <
>> jenkinsci-users@googlegroups.com>
>>
>> *Betreff:* Re: Build Pipeline plugin and Build Flow plugin
>>  build flow did introduce buildgraphview-plugin for this exact use case
>>
>>  build pipeline only can rendre static and mostly sequential pipelines
>>
>> 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski :
>>>
>>>  Hi,
>>>
>>> I'm trying to set up a CD pipeline with Jenkins where I can
>>>
>>> I) concisely define the relationship (triggers) between the single
>>> pipeline steps (jobs)
>>> II) have a nice visualisation of the full pipeline
>>>
>>> The Build Flow plugin is a good fit for I, while the Build Pipeline
>>> plugin is a nice fit for II.
>>> However, the Build Pipeline plugin doesn't seem to understand the job
>>> dependencies defined via the Build Flow plugin.
>>>
>>> Does someone have experiences with similar setups? What is your solution
>>> for this?
>>>
>>>
>>> cheers
>>> Christoph
>>>
>>>
>>>
>>> --
>>> 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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
>>> 
>>> .
>>> 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/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41
>> .
>>
>>
>> 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/CANMVJzm6OBmC7pgunTgTjFX8qmdjAjQWxwaw-QHpsNbyoPRX4A%40mail.gmail.com
> 

Aw: Re: Re: Build Pipeline plugin and Build Flow plugin

[Christoph Kutzinski]

Am I right when saying the the buildgraphview-plugin is a king of 'after the fact' view of a pipeline run?

I.e. I can see the results of a pipeline afterwards, but I can not actively control a pipeline (lie in the Build Pipeline pluing):

- starting a new pipeline run

- re-running a build

- triggering manul steps

 

Gesendet: Dienstag, 21. Juli 2015 um 14:45 Uhr
Von: "nicolas de loof" 
An: "jenkinsci-users@googlegroups.com" 
Betreff: Re: Re: Build Pipeline plugin and Build Flow plugin


build graph view do rely on upstreamCause so should handle most relations between builds
and for the others (including build-flow) do offer an extension point to discover other relations


 
2015-07-21 16:44 GMT+02:00 Christoph Kutzinski :





Thanks!

I didn't know about https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin

 

Can I also define manual triggered steps in a setup of the Build-Flow plugin and the build-graphview-plugin like you can do with the build pipeline plugin?

 

Gesendet: Dienstag, 21. Juli 2015 um 14:37 Uhr
Von: "nicolas de loof" 
An: "jenkinsci-users@googlegroups.com" 
Betreff: Re: Build Pipeline plugin and Build Flow plugin


build flow did introduce buildgraphview-plugin for this exact use case 

 
 

build pipeline only can rendre static and mostly sequential pipelines
 

 
2015-07-21 16:19 GMT+02:00 Christoph Kutzinski : 




Hi,

 

I'm trying to set up a CD pipeline with Jenkins where I can

 

I) concisely define the relationship (triggers) between the single pipeline steps (jobs)

II) have a nice visualisation of the full pipeline

 

The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice fit for II.

However, the Build Pipeline plugin doesn't seem to understand the job dependencies defined via the Build Flow plugin.

 

Does someone have experiences with similar setups? What is your solution for this?

 

 

cheers

Christoph

 



 
--
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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41.
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/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.






 
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41.



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






-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-6e98f37c-ab18-4f08-9ac4-6db9b3071625-1437490941266%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

Re: Re: Build Pipeline plugin and Build Flow plugin

[nicolas de loof]

build graph view do rely on upstreamCause so should handle most relations
between builds
and for the others (including build-flow) do offer an extension point to
discover other relations

2015-07-21 16:44 GMT+02:00 Christoph Kutzinski :

> Thanks!
> I didn't know about
> https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin
>
> Can I also define manual triggered steps in a setup of the Build-Flow
> plugin and the build-graphview-plugin like you can do with the build
> pipeline plugin?
>
> *Gesendet:* Dienstag, 21. Juli 2015 um 14:37 Uhr
> *Von:* "nicolas de loof" 
> *An:* "jenkinsci-users@googlegroups.com"  >
> *Betreff:* Re: Build Pipeline plugin and Build Flow plugin
>  build flow did introduce buildgraphview-plugin for this exact use case
>
> build pipeline only can rendre static and mostly sequential pipelines
>
> 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski :
>>
>>  Hi,
>>
>> I'm trying to set up a CD pipeline with Jenkins where I can
>>
>> I) concisely define the relationship (triggers) between the single
>> pipeline steps (jobs)
>> II) have a nice visualisation of the full pipeline
>>
>> The Build Flow plugin is a good fit for I, while the Build Pipeline
>> plugin is a nice fit for II.
>> However, the Build Pipeline plugin doesn't seem to understand the job
>> dependencies defined via the Build Flow plugin.
>>
>> Does someone have experiences with similar setups? What is your solution
>> for this?
>>
>>
>> cheers
>> Christoph
>>
>>
>>
>> --
>> 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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
>> 
>> .
>> 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/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41
> 
> .
>
> 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/CANMVJzm6OBmC7pgunTgTjFX8qmdjAjQWxwaw-QHpsNbyoPRX4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Aw: Re: Build Pipeline plugin and Build Flow plugin

[Christoph Kutzinski]

Thanks!

I didn't know about https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin

 

Can I also define manual triggered steps in a setup of the Build-Flow plugin and the build-graphview-plugin like you can do with the build pipeline plugin?

 

Gesendet: Dienstag, 21. Juli 2015 um 14:37 Uhr
Von: "nicolas de loof" 
An: "jenkinsci-users@googlegroups.com" 
Betreff: Re: Build Pipeline plugin and Build Flow plugin


build flow did introduce buildgraphview-plugin for this exact use case
 

build pipeline only can rendre static and mostly sequential pipelines


 
2015-07-21 16:19 GMT+02:00 Christoph Kutzinski :




Hi,

 

I'm trying to set up a CD pipeline with Jenkins where I can

 

I) concisely define the relationship (triggers) between the single pipeline steps (jobs)

II) have a nice visualisation of the full pipeline

 

The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice fit for II.

However, the Build Pipeline plugin doesn't seem to understand the job dependencies defined via the Build Flow plugin.

 

Does someone have experiences with similar setups? What is your solution for this?

 

 

cheers

Christoph

 



 
--
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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41.
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/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.






-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

Re: Re: Build Pipeline plugin and Build Flow plugin

[nicolas de loof]

oh yes indeed, oss version only has a simplified step vizualisation

2015-07-21 16:42 GMT+02:00 Christoph Kutzinski :

> Yes,
> but it doesn't have any visualisation, either (unless I use Jenkins
> Enterprise), has it?
>
> *Gesendet:* Dienstag, 21. Juli 2015 um 14:37 Uhr
> *Von:* "nicolas de loof" 
> *An:* "jenkinsci-users@googlegroups.com"  >
> *Betreff:* Re: Build Pipeline plugin and Build Flow plugin
>  Did you considered using workflow plugin ?
>
> 2015-07-21 16:37 GMT+02:00 nicolas de loof :
>>
>> build flow did introduce buildgraphview-plugin for this exact use case
>>
>> build pipeline only can rendre static and mostly sequential pipelines
>>
>> 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski :
>>>
>>>  Hi,
>>>
>>> I'm trying to set up a CD pipeline with Jenkins where I can
>>>
>>> I) concisely define the relationship (triggers) between the single
>>> pipeline steps (jobs)
>>> II) have a nice visualisation of the full pipeline
>>>
>>> The Build Flow plugin is a good fit for I, while the Build Pipeline
>>> plugin is a nice fit for II.
>>> However, the Build Pipeline plugin doesn't seem to understand the job
>>> dependencies defined via the Build Flow plugin.
>>>
>>> Does someone have experiences with similar setups? What is your solution
>>> for this?
>>>
>>>
>>> cheers
>>> Christoph
>>>
>>>
>>>
>>> --
>>> 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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
>>> 
>>> .
>>> 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/CANMVJz%3D%3DrnO8MxedwwrWBecgE%3Dz-vJVkAfgy%3DKZ04s8uqCBoAw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/trinity-66b6d313-9f9c-4a6f-a975-d2550388efd6-1437489730953%403capp-gmx-bs41
> 
> .
>
> 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/CANMVJzneprg3%3De2QUPU%2Ba0aZtHU%3DzZQxnZKqU8Rojeig8qGsYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build Pipeline plugin and Build Flow plugin

[nicolas de loof]

build flow did introduce buildgraphview-plugin for this exact use case

build pipeline only can rendre static and mostly sequential pipelines

2015-07-21 16:19 GMT+02:00 Christoph Kutzinski :

> Hi,
>
> I'm trying to set up a CD pipeline with Jenkins where I can
>
> I) concisely define the relationship (triggers) between the single
> pipeline steps (jobs)
> II) have a nice visualisation of the full pipeline
>
> The Build Flow plugin is a good fit for I, while the Build Pipeline plugin
> is a nice fit for II.
> However, the Build Pipeline plugin doesn't seem to understand the job
> dependencies defined via the Build Flow plugin.
>
> Does someone have experiences with similar setups? What is your solution
> for this?
>
>
> cheers
> Christoph
>
>
> --
> 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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
> 
> .
> 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/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Aw: Re: Build Pipeline plugin and Build Flow plugin

[Christoph Kutzinski]

Yes,

but it doesn't have any visualisation, either (unless I use Jenkins Enterprise), has it?

 

Gesendet: Dienstag, 21. Juli 2015 um 14:37 Uhr
Von: "nicolas de loof" 
An: "jenkinsci-users@googlegroups.com" 
Betreff: Re: Build Pipeline plugin and Build Flow plugin


Did you considered using workflow plugin ?

 
2015-07-21 16:37 GMT+02:00 nicolas de loof :


build flow did introduce buildgraphview-plugin for this exact use case
 

build pipeline only can rendre static and mostly sequential pipelines




 
2015-07-21 16:19 GMT+02:00 Christoph Kutzinski :




Hi,

 

I'm trying to set up a CD pipeline with Jenkins where I can

 

I) concisely define the relationship (triggers) between the single pipeline steps (jobs)

II) have a nice visualisation of the full pipeline

 

The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice fit for II.

However, the Build Pipeline plugin doesn't seem to understand the job dependencies defined via the Build Flow plugin.

 

Does someone have experiences with similar setups? What is your solution for this?

 

 

cheers

Christoph

 



 
--
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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41.
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/CANMVJz%3D%3DrnO8MxedwwrWBecgE%3Dz-vJVkAfgy%3DKZ04s8uqCBoAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.






-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-66b6d313-9f9c-4a6f-a975-d2550388efd6-1437489730953%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

Re: Build Pipeline plugin and Build Flow plugin

[nicolas de loof]

Did you considered using workflow plugin ?

2015-07-21 16:37 GMT+02:00 nicolas de loof :

> build flow did introduce buildgraphview-plugin for this exact use case
>
> build pipeline only can rendre static and mostly sequential pipelines
>
> 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski :
>
>> Hi,
>>
>> I'm trying to set up a CD pipeline with Jenkins where I can
>>
>> I) concisely define the relationship (triggers) between the single
>> pipeline steps (jobs)
>> II) have a nice visualisation of the full pipeline
>>
>> The Build Flow plugin is a good fit for I, while the Build Pipeline
>> plugin is a nice fit for II.
>> However, the Build Pipeline plugin doesn't seem to understand the job
>> dependencies defined via the Build Flow plugin.
>>
>> Does someone have experiences with similar setups? What is your solution
>> for this?
>>
>>
>> cheers
>> Christoph
>>
>>
>> --
>> 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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
>> 
>> .
>> 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/CANMVJz%3D%3DrnO8MxedwwrWBecgE%3Dz-vJVkAfgy%3DKZ04s8uqCBoAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Build Pipeline plugin and Build Flow plugin

[Christoph Kutzinski]

Hi,

 

I'm trying to set up a CD pipeline with Jenkins where I can

 

I) concisely define the relationship (triggers) between the single pipeline steps (jobs)

II) have a nice visualisation of the full pipeline

 

The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice fit for II.

However, the Build Pipeline plugin doesn't seem to understand the job dependencies defined via the Build Flow plugin.

 

Does someone have experiences with similar setups? What is your solution for this?

 

 

cheers

Christoph

 



-- 
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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41.
For more options, visit https://groups.google.com/d/optout.

Re: Master slave connection problem (Ubuntu slave)

[Ozcan Ovunc]

Oh. I know Build Executor Status bar but that shows only the jobs that 
nodes are currently building :/

On Tuesday, July 21, 2015 at 4:05:52 PM UTC+3, Mark Waite wrote:
>
> Sorry for using the wrong phrase to describe it.  On my installation, it 
> is the "Build Executor Status" and is immediately above the list of slaves 
> on the left side of the root page.
>
> On Tue, Jul 21, 2015 at 7:00 AM, Ozcan Ovunc  > wrote:
>
>> Where is the "node executors" menu btw?
>>
>> On Tuesday, July 21, 2015 at 3:54:57 PM UTC+3, Mark Waite wrote:
>>>
>>> The user executing that JNLP file on your Ubuntu machine probably does 
>>> not have permission to write to the /home/jenkins directory.  From the 
>>> "node executors" menu you should be able to review the properties of that 
>>> node, including the name of the user it is using.  I suspect it is not the 
>>> jenkins user on that Ubuntu machine, or if it is the jenkins user, then the 
>>> jenkins user does not have permission to write to /home/jenkins/workspace.
>>>
>>> On Tue, Jul 21, 2015 at 6:47 AM, Ozcan Ovunc  wrote:
>>>
 Hi,

 I have a Windows master and Ubuntu 14.04 slave (VirtualBox). I 
 successfully connected them by running 

 /home/jenkins$ java -jar slave.jar -jnlpUrl 
 http://192.168.56.1:8080/computer/Kole/slave-agent.jnlp

 command and the output was:

 Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main createEngine
>
> INFO: Setting up slave: Kole
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener 
>
> INFO: Jenkins agent is running in headless mode.
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Locating server among [http://192.168.56.1:8080/]
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Handshaking
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Connecting to 192.168.56.1:51149
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Trying protocol: JNLP2-connect
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Connected
>
> When I go master and check out for slave log, it confirms that 
 everything is ok:

 JNLP agent connected from /192.168.56.1
 <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.51
 This is a Unix slave
 Slave successfully connected and online

  
 But when I try to build one of my projects, I get this error from 
 console:

 Started by user anonymous 
 Building remotely on Kole  (python27 
 natty) in workspace /home/jenkins/workspace/jenkins-test
 java.io.IOException: Failed to mkdirs: /home/jenkins/workspace/jenkins-test
at hudson.FilePath.mkdirs(FilePath.java:1164)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1275)
at 
 hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
 hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
at hudson.model.Run.execute(Run.java:1744)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:374)
 Finished: FAILURE


 Any help would be really appreciated!


 Regards.

  -- 
 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/07579680-7550-4ce8-bf52-3134ffcf0dce%40googlegroups.com
  
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> -- 
>>> Thanks!
>>> Mark Waite
>>>  
>>  -- 
>> 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/e4cf4d43-f9ff-4ee7-8e0d-bf41abd6d132%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> 

Re: Stuck creating local jenkins update center

[jje]

Last but not least:

Gettin' metadata via browser(JSON Index File) is now working as expected. 
But it is nearly impossible to move jenkins to download plugins. Even 
though either machine and jenkins user has access to local repository 
granted, which actually has been tested by getting plugin files(*.hpi) via 
wget http:/sljdflsjdfj/plugin.hpi out of console.

Having said that bare mind it is guaranteed that trusty chain is working as 
expected, as metadata  file wasn't downloaded otherwise if not. 

My workaround is to put tinyproxy on my jenkins machine and configure 
jenkins properly. That way I'll get the plugins downloaded as expected. 
Hope that helps anyone.
BTW:Anyone a better solution?

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/8fd12045-7484-455b-8424-74d081362bf2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Stuck creating local jenkins update center

[jje]

Pls. note that our local repo containing plugin-files and jenkins master 
reside in same network either.

Am Dienstag, 21. Juli 2015 15:50:11 UTC+2 schrieb jje:
>
> Last but not least:
>
> Gettin' metadata via browser(JSON Index File) is now working as expected. 
> But it is nearly impossible to move jenkins to download plugins. Even 
> though either machine and jenkins user has access to local repository 
> granted, which actually has been tested by getting plugin files(*.hpi) via 
> wget http:/sljdflsjdfj/plugin.hpi out of console.
>
> Having said that bare mind it is guaranteed that trusty chain is working 
> as expected, as metadata  file wasn't downloaded otherwise if not. 
>
> My workaround is to put tinyproxy on my jenkins machine and configure 
> jenkins properly. That way I'll get the plugins downloaded as expected. 
> Hope that helps anyone.
> BTW:Anyone a better solution?
>
> 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/6a1ece3d-cb10-4213-bf43-56fa8211232f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins behind SSL, my case not going through

[Snd Lt]

Thanks for your time.
I'm still learning up on Apache and Jenkins.

I've been struggling for days with this. 

Would you mind briefly narrating which should go to httpd.conf and to 
ssl.conf?
Perhaps I'm putting ProxyPass to wrong places.
Not getting the whole picture.

Corrected the syntax but still doing "Service Unavailable, The server is 
temporarily unable to service your request due to maintenance downtime or 
capacity problems. Please try again later."

Thanks again.

On Tuesday, July 21, 2015 at 1:16:37 AM UTC-7, Corneil du Plessis wrote:
>
> ProxyPass required a path and a url
> The path is applied to incoming request and matches are sent to the url.
>
> ProxyPass /jenkins http://localhost:8080/jenkins
>
> In your case you had
> ProxyPass http://localhost:8080/
>
> The correct syntax is:
> ProxyPass / http://localhost:8080/
>
>
> On Monday, 20 July 2015 17:17:21 UTC+2, Snd Lt wrote:
>>
>> Thanks. How would you define that otherwise?
>> I thought I already defined it at localhost:8080? Which is where Jenkins 
>> is accessible at?
>>
>> On Monday, July 20, 2015 at 8:15:35 AM UTC-7, Corneil du Plessis wrote:
>>>
>>> The path is missing from your ProxyPass and ProxyPassReverse items.
>>>
>>> On 20 July 2015 at 17:01, Snd Lt  wrote:
>>>
 ProxyPass http://localhost:8080/ ProxyPassReverse 
 http://localhost:8080/ ProxyPassReverse http://server.com/
>>>
>>>
>>> ProxyPass /  http://localhost:8080/
>>> ProxyPassReverse  /  http://localhost:8080/
>>> ProxyPassReverse  /  http://server.com/
>>>
>>>
>>>  
>>> [image: --]
>>> Corneil du Plessis
>>> [image: https://]about.me/corneil
>>>   
>>>  
>>

-- 
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/f4a7b6f5-a5a4-4ba6-b789-71fb954494e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Master slave connection problem (Ubuntu slave)

[Mark Waite]

Sorry for using the wrong phrase to describe it.  On my installation, it is
the "Build Executor Status" and is immediately above the list of slaves on
the left side of the root page.

On Tue, Jul 21, 2015 at 7:00 AM, Ozcan Ovunc  wrote:

> Where is the "node executors" menu btw?
>
> On Tuesday, July 21, 2015 at 3:54:57 PM UTC+3, Mark Waite wrote:
>>
>> The user executing that JNLP file on your Ubuntu machine probably does
>> not have permission to write to the /home/jenkins directory.  From the
>> "node executors" menu you should be able to review the properties of that
>> node, including the name of the user it is using.  I suspect it is not the
>> jenkins user on that Ubuntu machine, or if it is the jenkins user, then the
>> jenkins user does not have permission to write to /home/jenkins/workspace.
>>
>> On Tue, Jul 21, 2015 at 6:47 AM, Ozcan Ovunc  wrote:
>>
>>> Hi,
>>>
>>> I have a Windows master and Ubuntu 14.04 slave (VirtualBox). I
>>> successfully connected them by running
>>>
>>> /home/jenkins$ java -jar slave.jar -jnlpUrl
>>> http://192.168.56.1:8080/computer/Kole/slave-agent.jnlp
>>>
>>> command and the output was:
>>>
>>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main createEngine

 INFO: Setting up slave: Kole

 Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener 

 INFO: Jenkins agent is running in headless mode.

 Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status

 INFO: Locating server among [http://192.168.56.1:8080/]

 Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status

 INFO: Handshaking

 Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status

 INFO: Connecting to 192.168.56.1:51149

 Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status

 INFO: Trying protocol: JNLP2-connect

 Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status

 INFO: Connected

 When I go master and check out for slave log, it confirms that
>>> everything is ok:
>>>
>>> JNLP agent connected from /192.168.56.1
>>> <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.51
>>> This is a Unix slave
>>> Slave successfully connected and online
>>>
>>>
>>> But when I try to build one of my projects, I get this error from
>>> console:
>>>
>>> Started by user anonymous 
>>> Building remotely on Kole  (python27 
>>> natty) in workspace /home/jenkins/workspace/jenkins-test
>>> java.io.IOException: Failed to mkdirs: /home/jenkins/workspace/jenkins-test
>>> at hudson.FilePath.mkdirs(FilePath.java:1164)
>>> at hudson.model.AbstractProject.checkout(AbstractProject.java:1275)
>>> at 
>>> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
>>> at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
>>> at 
>>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
>>> at hudson.model.Run.execute(Run.java:1744)
>>> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>>> at hudson.model.ResourceController.execute(ResourceController.java:98)
>>> at hudson.model.Executor.run(Executor.java:374)
>>> Finished: FAILURE
>>>
>>>
>>> Any help would be really appreciated!
>>>
>>>
>>> Regards.
>>>
>>>  --
>>> 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/07579680-7550-4ce8-bf52-3134ffcf0dce%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
>  --
> 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/e4cf4d43-f9ff-4ee7-8e0d-bf41abd6d132%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Thanks!
Mark Waite

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

Re: Master slave connection problem (Ubuntu slave)

[Ozcan Ovunc]

Where is the "node executors" menu btw?

On Tuesday, July 21, 2015 at 3:54:57 PM UTC+3, Mark Waite wrote:
>
> The user executing that JNLP file on your Ubuntu machine probably does not 
> have permission to write to the /home/jenkins directory.  From the "node 
> executors" menu you should be able to review the properties of that node, 
> including the name of the user it is using.  I suspect it is not the 
> jenkins user on that Ubuntu machine, or if it is the jenkins user, then the 
> jenkins user does not have permission to write to /home/jenkins/workspace.
>
> On Tue, Jul 21, 2015 at 6:47 AM, Ozcan Ovunc  > wrote:
>
>> Hi,
>>
>> I have a Windows master and Ubuntu 14.04 slave (VirtualBox). I 
>> successfully connected them by running 
>>
>> /home/jenkins$ java -jar slave.jar -jnlpUrl 
>> http://192.168.56.1:8080/computer/Kole/slave-agent.jnlp
>>
>> command and the output was:
>>
>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main createEngine
>>>
>>> INFO: Setting up slave: Kole
>>>
>>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener 
>>>
>>> INFO: Jenkins agent is running in headless mode.
>>>
>>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>>>
>>> INFO: Locating server among [http://192.168.56.1:8080/]
>>>
>>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>>>
>>> INFO: Handshaking
>>>
>>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>>>
>>> INFO: Connecting to 192.168.56.1:51149
>>>
>>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>>>
>>> INFO: Trying protocol: JNLP2-connect
>>>
>>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>>>
>>> INFO: Connected
>>>
>>> When I go master and check out for slave log, it confirms that 
>> everything is ok:
>>
>> JNLP agent connected from /192.168.56.1
>> <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.51
>> This is a Unix slave
>> Slave successfully connected and online
>>
>>  
>> But when I try to build one of my projects, I get this error from console:
>>
>> Started by user anonymous 
>> Building remotely on Kole  (python27 
>> natty) in workspace /home/jenkins/workspace/jenkins-test
>> java.io.IOException: Failed to mkdirs: /home/jenkins/workspace/jenkins-test
>>  at hudson.FilePath.mkdirs(FilePath.java:1164)
>>  at hudson.model.AbstractProject.checkout(AbstractProject.java:1275)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
>>  at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
>>  at hudson.model.Run.execute(Run.java:1744)
>>  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>>  at hudson.model.ResourceController.execute(ResourceController.java:98)
>>  at hudson.model.Executor.run(Executor.java:374)
>> Finished: FAILURE
>>
>>
>> Any help would be really appreciated!
>>
>>
>> Regards.
>>
>>  -- 
>> 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/07579680-7550-4ce8-bf52-3134ffcf0dce%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Thanks!
> Mark Waite
>  

-- 
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/e4cf4d43-f9ff-4ee7-8e0d-bf41abd6d132%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Master slave connection problem (Ubuntu slave)

[Mark Waite]

The user executing that JNLP file on your Ubuntu machine probably does not
have permission to write to the /home/jenkins directory.  From the "node
executors" menu you should be able to review the properties of that node,
including the name of the user it is using.  I suspect it is not the
jenkins user on that Ubuntu machine, or if it is the jenkins user, then the
jenkins user does not have permission to write to /home/jenkins/workspace.

On Tue, Jul 21, 2015 at 6:47 AM, Ozcan Ovunc  wrote:

> Hi,
>
> I have a Windows master and Ubuntu 14.04 slave (VirtualBox). I
> successfully connected them by running
>
> /home/jenkins$ java -jar slave.jar -jnlpUrl
> http://192.168.56.1:8080/computer/Kole/slave-agent.jnlp
>
> command and the output was:
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main createEngine
>>
>> INFO: Setting up slave: Kole
>>
>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener 
>>
>> INFO: Jenkins agent is running in headless mode.
>>
>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>>
>> INFO: Locating server among [http://192.168.56.1:8080/]
>>
>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>>
>> INFO: Handshaking
>>
>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>>
>> INFO: Connecting to 192.168.56.1:51149
>>
>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>>
>> INFO: Trying protocol: JNLP2-connect
>>
>> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>>
>> INFO: Connected
>>
>> When I go master and check out for slave log, it confirms that everything
> is ok:
>
> JNLP agent connected from /192.168.56.1
> <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.51
> This is a Unix slave
> Slave successfully connected and online
>
>
> But when I try to build one of my projects, I get this error from console:
>
> Started by user anonymous 
> Building remotely on Kole  (python27 
> natty) in workspace /home/jenkins/workspace/jenkins-test
> java.io.IOException: Failed to mkdirs: /home/jenkins/workspace/jenkins-test
>   at hudson.FilePath.mkdirs(FilePath.java:1164)
>   at hudson.model.AbstractProject.checkout(AbstractProject.java:1275)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
>   at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
>   at hudson.model.Run.execute(Run.java:1744)
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>   at hudson.model.ResourceController.execute(ResourceController.java:98)
>   at hudson.model.Executor.run(Executor.java:374)
> Finished: FAILURE
>
>
> Any help would be really appreciated!
>
>
> Regards.
>
>  --
> 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/07579680-7550-4ce8-bf52-3134ffcf0dce%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Thanks!
Mark Waite

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

Master slave connection problem (Ubuntu slave)

[Ozcan Ovunc]

Hi,

I have a Windows master and Ubuntu 14.04 slave (VirtualBox). I successfully 
connected them by running 

/home/jenkins$ java -jar slave.jar -jnlpUrl 
http://192.168.56.1:8080/computer/Kole/slave-agent.jnlp

command and the output was:

Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main createEngine
>
> INFO: Setting up slave: Kole
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener 
>
> INFO: Jenkins agent is running in headless mode.
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Locating server among [http://192.168.56.1:8080/]
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Handshaking
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Connecting to 192.168.56.1:51149
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Trying protocol: JNLP2-connect
>
> Jul 21, 2015 3:22:08 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Connected
>
> When I go master and check out for slave log, it confirms that everything 
is ok:

JNLP agent connected from /192.168.56.1
<===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.51
This is a Unix slave
Slave successfully connected and online

 
But when I try to build one of my projects, I get this error from console:

Started by user anonymous 
Building remotely on Kole  (python27 
natty) in workspace /home/jenkins/workspace/jenkins-test
java.io.IOException: Failed to mkdirs: /home/jenkins/workspace/jenkins-test
at hudson.FilePath.mkdirs(FilePath.java:1164)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1275)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
at hudson.model.Run.execute(Run.java:1744)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:374)
Finished: FAILURE


Any help would be really appreciated!


Regards.

-- 
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/07579680-7550-4ce8-bf52-3134ffcf0dce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Invoking top-level Maven targets on a slave

[Anthony Green]

I''m running a Jenkins Ubuntu Master with an OS X Slave

I can't get a build step "Invoking top-level Maven targets" to run on a 
slave.

I get a 

FATAL: command execution failed

java.io.IOException 
: Cannot run 
program "mvn"

I've tried setting environment variables and that works for a shell script 
build step but not a Maven build step.
I've tried setting Tool Locations on the slave to point at the slave's Maven 
installation and that doesn't work.

How is this supposed to be accomplished? 

-- 
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/92f3f50e-b18e-4f82-a437-219c968d9957%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Perforce workspace question

[lata]

1) What's the problem here? 

1. Jenkins Perforce Workspace at /var/lib/jenkins/jobs/...
- The name of this P4 workspace is whatever you have typed in the 
'Workspace' field of your Jenkins project configuration -> Perforce 
section. I'm guessing you typed in 'jenkins_test'.
- The P4 root of this P4 Workspace would be relative to your slave's Remot 
Root or your Jenkins Master (if you are running your project directly on 
Jenkins Master, and not on a slave).
- Default behaviour is that Jenkins updates the P4 workspace with the Root 
and Host values, you can override this by checking the 'Don't update client 
workspace' option in the Advanced section.

2. Your Perforce workspace, 'jenkins_test', with root /home/maritn/p4/test
Jenkins is not aware that you have such a P4 workspace created, and that 
you want to use it. As mentioned above, it will override Root and Host 
unless you ask it not to.

Reco: 1. If you really can't go with the Jenkins chosen workspace to sync 
your p4 code to, don't use the option 'Don't update client workspace', 
instead use the 'custom workspace' in the Advanced project option, and 
change the workspace location to /home/martin/, if you need to. 
Don't manage this Jenkins created P4 workspace outside this environment, 
let Jenkins manage it. (I'm assuming you can't get a slave machine, and 
need to run your jobs on the Master itself? Otherwise you can straightway 
set your Slave's remote root location to the right place that you want)
2. If you really need to use your Perforce client created outside for some 
reason, then use the command line within Jenkins config shell and do a 
manual sync such as P4 -c $yourclient

2) Does the user "jenkins" on Jenkins have anything to do with the Linux 
user who installed Jenkins and P4?
No


On Tuesday, July 21, 2015 at 3:36:32 PM UTC+8, Martin wrote:
>
> Hello, it's the first time to setup Jenkins Perforce Plugin. I just wanted 
> to setup a simple project to test the automatic build feature in Jenkins. 
> On my local machine, my project is:
>
> /home/martin/p4/test
>
> I created a workspace named jenkins_test, whose root 
> is /home/martin/p4/test. I can test syncing with Perforce.
>
> However, in Jenkins, whenever a build finishes, it changes my root 
> directory of my workspace from /home/martin/p4/test to 
> /var/lib/jenkins/jobs/ on the Jenkins machine. This isn't the expected 
> behavior, right? Otherwise, I have to change the root of the workspace back 
> to /home/maritn/p4/test on my local machine after each build. 
>
> In Jenkins, I created a user named "jenkins" and use that user name to 
> login Jenkins to start the build and do the configure.
>
> I have a few questions here:
> 1) What' the problem here? 
> 2) Does the user "jenkins" on Jenkins have anything to do with the Linux 
> user who installed Jenkins and P4?
>
> Thank you for help.
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/981b3563-13ac-4fb2-b470-f0b2ecac76f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Exclusion-Plugin: Dynamic Name of Resource

[mr]

Is it possible to set the name of the resource to be managed dynamically? 
For example as ${testDatabase}

The aim is to start multiple execution of one job depending on the 
availability of test databases. The job can be executed with different test 
databases, and the parallel execution shall be allowed only with a test 
database which is currently not in 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/cf75d55a-d3d3-495a-b31b-a1d18e5d0a3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't figure out how Jenkins GIT Plugin works

[ozcaaan94]

I totally agree with you. I thought that I was mising something like some 
configuration setting.

Multi Branch Plugin solved my problem tho.

Thank you so much!

On Tuesday, July 21, 2015 at 10:58:01 AM UTC+3, nicolas de loof wrote:
>
> multi-branch support in git-plugin is a poor implementation, and running 
> the job manually will just rebuild the last commit (so only one branch from 
> your 3 ones) not all of them, not even considering build history is 
> irrelevant with branches mixed
>
> If you want actual multi-branch support select a job type which do support 
> scm-api, for sample 
> https://wiki.jenkins-ci.org/display/JENKINS/Multi-Branch+Project+Plugin 
>
> I'd like we deprecate this is git plugin (which would remove 75% of its 
> most unmaintainable code) but this would have HUGE impact on user base
>
>
>
> 2015-07-21 9:15 GMT+02:00 >:
>
>> Hi everyone,
>>
>> I have a project on Github which has 3 branches: master, test2, test3 -> 
>> https://github.com/ozcanovunc/jenkins-test/blob/master/test.py. And I'm 
>> running test.py file in batch command by "python test.py" command.
>>
>>- test2 branch : code with error in test.py
>>- test3 branch : code with error in test.py
>>- master branch : ok code in test.py
>>
>> So when I modify test.py in each branch and build the project I get 3 
>> builds with 1 success and 2 failures which is fine. But afterwards, when I 
>> build the project on Jenkins again (with no modifications on codes), I get 
>> 1 build and that is test3 build with failure.
>>
>> So is that a bug or something? Where are the 2 other builds? Master and 
>> test2?
>>
>>
>> (And one more thing. I think it's the pretty much the same problem. When 
>> I modify only test.py in master, then build the project, I get one build 
>> with success. It doesn't build other branches.)
>>
>> Regards,
>> Ozcan
>>
>> -- 
>> 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/9af1cea7-198a-40dc-98e3-71bc372e945d%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/43ed7486-7a95-44fb-9af4-ecf5cfea236f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins behind SSL, my case not going through

[Corneil du Plessis]

ProxyPass required a path and a url
The path is applied to incoming request and matches are sent to the url.

ProxyPass /jenkins http://localhost:8080/jenkins

In your case you had
ProxyPass http://localhost:8080/

The correct syntax is:
ProxyPass / http://localhost:8080/


On Monday, 20 July 2015 17:17:21 UTC+2, Snd Lt wrote:
>
> Thanks. How would you define that otherwise?
> I thought I already defined it at localhost:8080? Which is where Jenkins 
> is accessible at?
>
> On Monday, July 20, 2015 at 8:15:35 AM UTC-7, Corneil du Plessis wrote:
>>
>> The path is missing from your ProxyPass and ProxyPassReverse items.
>>
>> On 20 July 2015 at 17:01, Snd Lt  wrote:
>>
>>> ProxyPass http://localhost:8080/ ProxyPassReverse http://localhost:8080/ 
>>> ProxyPassReverse http://server.com/
>>
>>
>> ProxyPass /  http://localhost:8080/
>> ProxyPassReverse  /  http://localhost:8080/
>> ProxyPassReverse  /  http://server.com/
>>
>>
>>  
>> [image: --]
>> Corneil du Plessis
>> [image: https://]about.me/corneil
>>   
>>  
>

-- 
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/cf9600fa-0b37-49d1-b32f-a6a99cbe0cf1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Version Issues on Website

[David Aldrich]

Just to mention that it seems that 1.621 is still not available despite being 
advertised.

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Daniel Beck
> Sent: 20 July 2015 13:18
> To: jenkinsci-users@googlegroups.com
> Subject: Re: Version Issues on Website
> 
> Thanks for telling us! I'll look into this.
> 
> On 20.07.2015, at 14:07, Rinaldo DiGiorgio 
> wrote:
> 
> > http://mirrors.jenkins-ci.org/war/latest/jenkins.war when downloaded is
> actually 1.620 and not 1.621 from http://jenkins-ci.org/
> >
> > The changelog page is also broken.
> >
> > http://jenkins-ci.org/changelog
> >
> >
> > --
> > 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/9c0511d7-76e8-47c9-
> b93d-ea8b84c383ac%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/416497F9-C76F-47E1-
> 8BF9-950A7FFF75F2%40beckweb.net.
> For more options, visit https://groups.google.com/d/optout.
> 
> 
>  Click
> https://www.mailcontrol.com/sr/2EJo6sc4OCbGX2PQPOmvUsPk3Ki21lNCY5
> GD8nHjJvBdz9G1rMaWvnm0eELTdPUblxXnKT2vAUANCU1!U1Tbvw==  to
> report this email as spam.

-- 
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/41302A7145AC054FA7A96CFD03835A0A0B9AEF97%40EX10MBX02.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.

Re: Can't figure out how Jenkins GIT Plugin works

[nicolas de loof]

multi-branch support in git-plugin is a poor implementation, and running
the job manually will just rebuild the last commit (so only one branch from
your 3 ones) not all of them, not even considering build history is
irrelevant with branches mixed

If you want actual multi-branch support select a job type which do support
scm-api, for sample
https://wiki.jenkins-ci.org/display/JENKINS/Multi-Branch+Project+Plugin

I'd like we deprecate this is git plugin (which would remove 75% of its
most unmaintainable code) but this would have HUGE impact on user base



2015-07-21 9:15 GMT+02:00 :

> Hi everyone,
>
> I have a project on Github which has 3 branches: master, test2, test3 ->
> https://github.com/ozcanovunc/jenkins-test/blob/master/test.py. And I'm
> running test.py file in batch command by "python test.py" command.
>
>- test2 branch : code with error in test.py
>- test3 branch : code with error in test.py
>- master branch : ok code in test.py
>
> So when I modify test.py in each branch and build the project I get 3
> builds with 1 success and 2 failures which is fine. But afterwards, when I
> build the project on Jenkins again (with no modifications on codes), I get
> 1 build and that is test3 build with failure.
>
> So is that a bug or something? Where are the 2 other builds? Master and
> test2?
>
>
> (And one more thing. I think it's the pretty much the same problem. When I
> modify only test.py in master, then build the project, I get one build with
> success. It doesn't build other branches.)
>
> Regards,
> Ozcan
>
> --
> 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/9af1cea7-198a-40dc-98e3-71bc372e945d%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/CANMVJz%3DegK2ikMdh3HwDV9ibdX86sybvO0ntiQ1e%3DW4NqsGhwA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Perforce workspace question

[Martin]

Also, the Jenkins doc says user can change JENKINS_HOME directory:
https://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins

I don't quite understand this either. How can we change its home directory 
after it is installed? Like Java installation, $JAVA_HOME has to always 
points to the Java's installation directory, not any other directory. Can 
$JENKINS_HOME point to some place different from its installation 
directory? 


On Tuesday, July 21, 2015 at 3:36:32 AM UTC-4, Martin wrote:
>
> Hello, it's the first time to setup Jenkins Perforce Plugin. I just wanted 
> to setup a simple project to test the automatic build feature in Jenkins. 
> On my local machine, my project is:
>
> /home/martin/p4/test
>
> I created a workspace named jenkins_test, whose root 
> is /home/martin/p4/test. I can test syncing with Perforce.
>
> However, in Jenkins, whenever a build finishes, it changes my root 
> directory of my workspace from /home/martin/p4/test to 
> /var/lib/jenkins/jobs/ on the Jenkins machine. This isn't the expected 
> behavior, right? Otherwise, I have to change the root of the workspace back 
> to /home/maritn/p4/test on my local machine after each build. 
>
> In Jenkins, I created a user named "jenkins" and use that user name to 
> login Jenkins to start the build and do the configure.
>
> I have a few questions here:
> 1) What' the problem here? 
> 2) Does the user "jenkins" on Jenkins have anything to do with the Linux 
> user who installed Jenkins and P4?
>
> Thank you for help.
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fae0c000-d81c-4d95-8dae-01db2ebd2935%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Perforce workspace question

[Martin]

Hello, it's the first time to setup Jenkins Perforce Plugin. I just wanted 
to setup a simple project to test the automatic build feature in Jenkins. 
On my local machine, my project is:

/home/martin/p4/test

I created a workspace named jenkins_test, whose root 
is /home/martin/p4/test. I can test syncing with Perforce.

However, in Jenkins, whenever a build finishes, it changes my root 
directory of my workspace from /home/martin/p4/test to 
/var/lib/jenkins/jobs/ on the Jenkins machine. This isn't the expected 
behavior, right? Otherwise, I have to change the root of the workspace back 
to /home/maritn/p4/test on my local machine after each build. 

In Jenkins, I created a user named "jenkins" and use that user name to 
login Jenkins to start the build and do the configure.

I have a few questions here:
1) What' the problem here? 
2) Does the user "jenkins" on Jenkins have anything to do with the Linux 
user who installed Jenkins and P4?

Thank you for help.

 

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

Can't figure out how Jenkins GIT Plugin works

[ozcaaan94]

Hi everyone,

I have a project on Github which has 3 branches: master, test2, test3 -> 
https://github.com/ozcanovunc/jenkins-test/blob/master/test.py. And I'm 
running test.py file in batch command by "python test.py" command.

   - test2 branch : code with error in test.py
   - test3 branch : code with error in test.py
   - master branch : ok code in test.py

So when I modify test.py in each branch and build the project I get 3 
builds with 1 success and 2 failures which is fine. But afterwards, when I 
build the project on Jenkins again (with no modifications on codes), I get 
1 build and that is test3 build with failure.

So is that a bug or something? Where are the 2 other builds? Master and 
test2?


(And one more thing. I think it's the pretty much the same problem. When I 
modify only test.py in master, then build the project, I get one build with 
success. It doesn't build other branches.)

Regards,
Ozcan

-- 
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/9af1cea7-198a-40dc-98e3-71bc372e945d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

email list of all users defined in active directory + role-based auth

[lata]

Hi

We are using Active Directory + Role-Based Strategy for Jenkins 
authentication.
We want to be able to send out notifications on important changes such as 
upgrades to all users on our Jenkins, and also restrict it only to those 
users / groups who are listed in 'User/Group' of 'Assign Roles' section 
(and not all authenticated via AD).
Is there a convenient way to do this, the only way I can think of is to 
programmatically pull out the users from config.xml (sid), if the entry is 
a group, lookup Active Directory for its members, and make a full list.
Is there an easier way from within Jenkins? 

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/83d6ef88-ba2d-4bdd-834e-5aeb73d2044c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.