Re: Mulit-Branch Project Plugin and Post-build action "Publish artifacts in Maven repository (deploy)"

[Thomas Zoratto]

Hello, 

I think you can solve your problem and improve your CI configuration by 
using the Pipeline plugin and more specifically the Pipeline:Multibranch 
plugin 

.

Thomas

Le mardi 24 mai 2016 09:17:04 UTC+2, Sandra Parsick a écrit :
>
> Hello, 
>
> I have following problem and maybe someone has a good idea how I can solve 
> it. 
>
> I have a Git repository with several branches. I'd like to bring all 
> branches under CI control. That means, after every push to the repository, 
> indepentent in which branch, a job should check whether the build is 
> successful. When the build is sucessful, the build artifact should be 
> uploaded to a Maven repository. But the upload step shouldn't be done on 
> every branch. 
>
>
> I have tried the Multi-Branch Project Plugin, but I couldn't find the 
> Post-build action "Publish artifacts in Maven repository (deploy)", that I 
> usually use in normal Maven-project build jobs. Do you have some ideas, how 
> I can solve my problem? 
>
>
> Best regards, 
>
> Sandra 
>

-- 
You received this message because you are 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/9345dbab-587d-4199-b314-bc1a8fcfd751%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Storing artifacts on file server (Mac+Win)

[Thomas Zoratto]

I keep this conversation here to possibly help other people with a similar 
question.

---

It's not the only way but it's the cleanest way in my opinion when you have 
enough artifacts to fill your hard drive.

I think the way you integrate the artifact repository with Jenkins depends 
on your projects. In a Maven project for example, you can configure your 
repository in your pom.xml in order to deploy artifacts on it 
automatically. Then, you can configure Maven to lookout for dependencies in 
your repository (instead of the default one).

Also, there are some plugins (see this one 
) 
that can help to integrate your repo with Jenkins in various ways.

I'm no expert here but I would definitely go for the artifact repository. 
However, if you really don't want it, I think you can find the answer to 
your specific question here 
.

Good luck 

Thomas
 

Le 26 mai 2016 à 17:22,  <> a écrit :

Hi Thomas

I know why we're running out of disk space, it's a virtual machine and our 
vm host is quite limited in space so expanding to the degree needed is not 
possible. However we do have plenty of space on our fileserver, just need 
to get jenkins to actually leverage it.

I must admit I was hoping for something less than an artifact repository. 
All we want is for Jenkins to put it's data on our network drive. But if 
that is the only way I guess we'll have to do that.

How does an artifact repository integrate with Jenkins? Will we be able to 
list our builds and grab the artifacts directly from Jenkins?

Thanks for your reply
Joen

On Thu, May 26, 2016 at 4:54 PM,  <> wrote:

> Hi,
>
> First you should check your build's logs policy (maybe you're running out 
> of space because of that). 
>
> Then, I encourage you to use an artifact repository such as Nexus. You'll 
> be able to store your artifacts easily. 
>
> Thomas
>
> Le 26 mai 2016 à 12:52,  a écrit :
>
> Hi Experts,
>
> I'm having problems with our master jenkins server running out of disk 
> space. I want to offload the builds to our file server. 
>
> I'm trying to get Artifact Deployer to work but I'm unable to provide a 
> path that will work both on mac and windows. 
>
> How can I do that? Any advise is appreciated!
>
> Thanks,
> Joen
>
> -- 
> You received this message because you are 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/872270dd-a80f-4866-8b87-666987c28930%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-users/gSBrn395j3c/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/DF75B476-8B6B-4F79-8767-99FD315AA2CF%40gmail.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/481402f3-ab27-4ca0-b214-83865feed63a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: deployment of multiple git branches

[Thomas Zoratto]

Tomáš was talking about Docker so let’s take it for example. You could build a 
new Docker image for each one of your branches and tag it with the branch name, 
build number or whatever you prefer.

Regarding Nexus or Maven specifically you could use a plugin such as the Maven 
build number plugin for that purpose.

It’s just my opinion based on little experience, there are probably better 
methods (or workflows that don’t raise this question) out there.

But honestly, I think this isn’t directly related to Jenkins.

Good luck !

> Le 31 mai 2016 à 18:59, Philipp Meier  a écrit :
> 
> Hi,
> 
> The interesting question for me is how to handle and identify the different 
> artifacts which are built by the several branches. I. e. in Maven you specify 
> a version 1.0.0-snapshot and this is then used to build the Jar. When you're 
> going to deploy this on a machine or a repository (i. e. Nexus) you won't be 
> able to identify from which branch it was built. How do you handle this?
> 
> Best, Philipp
> 
> On Tuesday, 31 May 2016 18:16:34 UTC+2, Thomas Zoratto wrote:
> Hello,
> 
> You can achieve this with a Jenkinsfile per branch in your repository. Then 
> create a new multibranch pipeline job in Jenkins pointing to your repository 
> and you're done. See 
> https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Plugin 
> <https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Plugin>
> 
> Thomas
> 
> Le 31 mai 2016 à 14:00, Tomáš Bohuněk > a 
> écrit :
> 
>> I would like to deploy and run each jar file for each feature branch. 
>> 
>> Project is written in Java and JavaScript. Jar file is built by maven. I 
>> need to deploy somehow to one machine each of jar built from each feature 
>> branch.
>> 
>> 
>> On Tuesday, May 31, 2016 at 1:55:21 PM UTC+2, Mark Waite wrote:
>> I think you'll need to provide more details about the problem you're trying 
>> to solve, and the languages you're using to solve it.  For example, since 
>> you mentioned that you're deploying to tomcat, are you writing in Java or 
>> some other JRE supported language (like Scala)?
>> 
>> Are you building your jar with maven, gradle, ant, or some other build tool?
>> 
>> Mark Waite
>> 
>> On Tue, May 31, 2016 at 5:46 AM Tomáš Bohuněk > wrote:
>> Sorry for mistake. You are right. I have one single git repository (one 
>> project) with a few feature branches.
>> 
>> 
>> On Tuesday, May 31, 2016 at 1:44:19 PM UTC+2, Mark Waite wrote:
>> Could you explain further what you mean by "multiple git repository (one 
>> project with few feature branches)"?
>> 
>> The phrase "multiple git repository" seems to be in conflict with the phrase 
>> "one project".  I typically place a project in a single git repository with 
>> a few feature branches as necessary.  Can you describe more about why you 
>> need multiple git repositories?
>> 
>> Thanks,
>> Mark Waite
>> 
>> On Tue, May 31, 2016 at 5:04 AM Tomáš Bohuněk > wrote:
>> What do you recommend for deployment of multiple git repository (one project 
>> with few feature branches). Final artifact is JAR with bundled Tomcat 
>> application server. I usually run this JAR in Docker container. What do you 
>> prefer?
>> 
>> -- 
>> You received this message because you are 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/911cbd52-c307-486d-b0bd-339ea40b8200%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/911cbd52-c307-486d-b0bd-339ea40b8200%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <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-use...@googlegroups.com <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/a5cf009f-289a-4945-ac5c-00fb6f52568e%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/a5cf009f-289a-4945-ac5c-00fb6f52568e%40googlegroups.com?utm_medium=email&utm_source=footer>.
>&g

Re: Integrating promoted-builds DSL to a job-dsl-gradle-example project

[Thomas Zoratto]

Hello Frank, 

I guess the promoted builds plugin is not directly compatible with the job DSL 
plugin. I mean you can’t find DSL methods relative to the promoted builds 
plugin in the online API 
https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842
 
.
 

I think the job DSL plugin must use the extension point when in the context of 
a running instance with the promoted builds plugin installed.

Though, I suppose you can test it locally thanks to the last updates of 
sheehan's github repo. See 
https://github.com/sheehan/job-dsl-gradle-example/commit/9d6260b44cefdd832ee3f854f107b24f15881ea7
 
.
 You’ll have to specify the plugins you have in your running instance in order 
to simulate a similar environment for your local tests.

sorry for my poor English !

Thomas

> Le 1 juin 2016 à 16:36, François Genois  a écrit :
> 
> Good morning everyone,
> 
> I'm currently using a project based on 
> https://github.com/sheehan/job-dsl-gradle-example and I am trying to get the 
> promoted-builds plugin to work with this project 
> (https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin).
> 
> Everything works fine on my Jenkins server (with the plugin installed), but I 
> can't figure out a way to make my code work on this local project. I use this 
> project to work locally, to debug and to test; instead of sending it to the 
> server for every single modifications.
> 
> Here is an example project that reproduces my problem :
> https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842
> 
> And here one of the ways I run it locally :
> gradlew debugXml -Dpattern=jobs/example1Jobs.groovy
> 
> I'm not quite sure if this is a limitation/bug/feature_request or if it is 
> simply me having a hard time to make it work.
> 
> Please help me and I wish you a nice day!
> 
> - Frank
> 
> -- 
> You received this message because you are 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/596540e7-63dc-49c2-9532-be154aafd98d%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/821809EB-D924-429F-A8CB-B9923AF63644%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Integrating promoted-builds DSL to a job-dsl-gradle-example project

[Thomas Zoratto]

Right now I can’t see a way to do this but my knowledge on this topic is very 
limited. I also have to work on it soon so I’ll let you know if I find a way 
(and if you still don’t have the answer).

Please share your progress, if any 

Good luck !

Thomas


> Le 1 juin 2016 à 20:35, François Genois  a écrit :
> 
> Hello Thomas,
> 
> Thank you very much for your answer.
> The promoted builds plugin is indeed a extension point.
> 
> I added the following line to my dependencies "testCompile 
> 'org.jenkins-ci.plugins:promoted-builds:2.27@jar'" and my 'gradlew test' 
> command now succeeds.
> 
> I just tried applying the same logic to the 'debugXml' gradle task (I use the 
> XML to verify if I haven't done any regression during refactoring), but I 
> can't figure out how to make this code run in a context running an instance 
> of the promoted-builds plugin.
> 
> Do you have an idea of how I could get the XML generated from the scripts?
> 
> Thank you again and have a nice day!
> 
> - Frank
> 
> 
> On Wednesday, June 1, 2016 at 12:20:01 PM UTC-4, Thomas Zoratto wrote:
> Hello Frank, 
> 
> I guess the promoted builds plugin is not directly compatible with the job 
> DSL plugin. I mean you can’t find DSL methods relative to the promoted builds 
> plugin in the online API 
> https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842
>  
> <https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842>.
>  
> 
> I think the job DSL plugin must use the extension point when in the context 
> of a running instance with the promoted builds plugin installed.
> 
> Though, I suppose you can test it locally thanks to the last updates of 
> sheehan's github repo. See 
> https://github.com/sheehan/job-dsl-gradle-example/commit/9d6260b44cefdd832ee3f854f107b24f15881ea7
>  
> <https://github.com/sheehan/job-dsl-gradle-example/commit/9d6260b44cefdd832ee3f854f107b24f15881ea7>.
>  You’ll have to specify the plugins you have in your running instance in 
> order to simulate a similar environment for your local tests.
> 
> sorry for my poor English !
> 
> Thomas
> 
>> Le 1 juin 2016 à 16:36, François Genois > 
>> a écrit :
>> 
>> Good morning everyone,
>> 
>> I'm currently using a project based on 
>> https://github.com/sheehan/job-dsl-gradle-example 
>> <https://github.com/sheehan/job-dsl-gradle-example> and I am trying to get 
>> the promoted-builds plugin to work with this project 
>> (https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin 
>> <https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin>).
>> 
>> Everything works fine on my Jenkins server (with the plugin installed), but 
>> I can't figure out a way to make my code work on this local project. I use 
>> this project to work locally, to debug and to test; instead of sending it to 
>> the server for every single modifications.
>> 
>> Here is an example project that reproduces my problem :
>> https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842
>>  
>> <https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842>
>> 
>> And here one of the ways I run it locally :
>> gradlew debugXml -Dpattern=jobs/example1Jobs.groovy
>> 
>> I'm not quite sure if this is a limitation/bug/feature_request or if it is 
>> simply me having a hard time to make it work.
>> 
>> Please help me and I wish you a nice day!
>> 
>> - Frank
>> 
>> -- 
>> You received this message because you are 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/596540e7-63dc-49c2-9532-be154aafd98d%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/596540e7-63dc-49c2-9532-be154aafd98d%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <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 
> <mailto:jenkinsci-users+u

Re: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

[Thomas Zoratto]

Hi, 

Did you commit your changes in your repo ? 

> Le 3 juin 2016 à 20:43, Freddy Paxton  a 
> écrit :
> 
> I'm new to Jenkins, Ubuntu and Git so the answer to this is probably 
> something I've missed out!
> 
> What I want to do is set up a Git repository in which 2 Java files are 
> located (HelloWorld.java and HelloWorldErr.java - HelloWorldErr is missing an 
> ; ). This is to test the Jenkins build and test system to see if it can 
> successfully compile the HelloWorld.java file and run it, and also discover 
> the error in HelloWorldErr.java. It's a pretty simple test but I'm having 
> trouble getting it working.
> 
> After finally managing to set up the repository correctly, I now get an error 
> saying:
> ERROR: Couldn't find any revision to build. Verify the repository and branch 
> configuration for this job.
> 
> After scouting the internet for tutorials and/or anyone with similar problems 
> I'm still looking for a solution. Even an explanation of the process would 
> probably help me a lot.
> 
> My repository is located at /var/lib/jenkins/repo/test_repo.git/ and the 2 
> Java files are in there. I left the branch specifier as */master as I do not 
> know what this does.
> 
> In my Execute shell command I have:
> 
> javac HelloWorld.java
> java HelloWorld
> Obviously this means that it is not looking at HelloWorldErr.java but for now 
> I just want the build to run successfully.
> 
> Sorry if I haven't explained myself very well. Once I get this working I am 
> also planning to test running files through GitHub but I do not want to start 
> on that before I can get the local Git working correctly.
> 
> Thanks in advance! Any insight on this is going to really help me with my 
> project.
> 
> If it helps here is the console output with branch set to */master...
> Building in workspace /var/lib/jenkins/jobs/HelloWorld/workspace
> > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
> > git config remote.origin.url file:///var/lib/jenkins/repo/test_repo.git 
> >  # timeout=10
> Fetching upstream changes from file:///var/lib/jenkins/repo/test_repo.git 
> 
> > git --version # timeout=10
> > git -c core.askpass=true fetch --tags --progress 
> > file:///var/lib/jenkins/repo/test_repo.git 
> >  
> > +refs/heads/:refs/remotes/origin/
> > git rev-parse refs/remotes/origin/master^
> 
> {commit} # timeout=10
> > git rev-parse refs/remotes/origin/origin/master^{commit}
> # timeout=10
> > git rev-parse origin/master^
> 
> {commit}
> # timeout=10
> ERROR: Couldn't find any revision to build. Verify the repository and branch 
> configuration for this job.
> Finished: FAILURE
> 
> And here is the output when I leave branch blank...
> Building in workspace /var/lib/jenkins/jobs/HelloWorld/workspace
> > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
> > git config remote.origin.url file:///var/lib/jenkins/repo/test_repo.git 
> >  # timeout=10
> Fetching upstream changes from file:///var/lib/jenkins/repo/test_repo.git 
> 
> > git --version # timeout=10
> > git -c core.askpass=true fetch --tags --progress 
> > file:///var/lib/jenkins/repo/test_repo.git 
> >  
> > +refs/heads/:refs/remotes/origin/
> Seen 0 remote branches
> ERROR: Couldn't find any revision to build. Verify the repository and branch 
> configuration for this job.
> Finished: FAILURE
> 
> 
> -- 
> You received this message because you are 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/911c209e-58d8-4cca-9077-43f00d37402d%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/28731CD0-DB4F-458E-B9BA-F7197E58CD58%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

[Thomas Zoratto]

cd /path/to/your/repo

git add --all
git commit -m "your commit message"

I encourage you to go through a git tutorial to learn the basics.

Thomas

> Le 3 juin 2016 à 22:00, Freddy Paxton  a 
> écrit :
> 
> How do I go about doing this?
> 
> On Friday, June 3, 2016 at 8:23:10 PM UTC+1, Thomas Zoratto wrote:
> Hi, 
> 
> Did you commit your changes in your repo ? 
> 
>> Le 3 juin 2016 à 20:43, Freddy Paxton > > a écrit :
>> 
>> I'm new to Jenkins, Ubuntu and Git so the answer to this is probably 
>> something I've missed out!
>> 
>> What I want to do is set up a Git repository in which 2 Java files are 
>> located (HelloWorld.java and HelloWorldErr.java - HelloWorldErr is missing 
>> an ; ). This is to test the Jenkins build and test system to see if it can 
>> successfully compile the HelloWorld.java file and run it, and also discover 
>> the error in HelloWorldErr.java. It's a pretty simple test but I'm having 
>> trouble getting it working.
>> 
>> After finally managing to set up the repository correctly, I now get an 
>> error saying:
>> ERROR: Couldn't find any revision to build. Verify the repository and branch 
>> configuration for this job.
>> 
>> After scouting the internet for tutorials and/or anyone with similar 
>> problems I'm still looking for a solution. Even an explanation of the 
>> process would probably help me a lot.
>> 
>> My repository is located at /var/lib/jenkins/repo/test_repo.git/ and the 2 
>> Java files are in there. I left the branch specifier as */master as I do not 
>> know what this does.
>> 
>> In my Execute shell command I have:
>> 
>> javac HelloWorld.java
>> java HelloWorld
>> Obviously this means that it is not looking at HelloWorldErr.java but for 
>> now I just want the build to run successfully.
>> 
>> Sorry if I haven't explained myself very well. Once I get this working I am 
>> also planning to test running files through GitHub but I do not want to 
>> start on that before I can get the local Git working correctly.
>> 
>> Thanks in advance! Any insight on this is going to really help me with my 
>> project.
>> 
>> If it helps here is the console output with branch set to */master...
>> Building in workspace /var/lib/jenkins/jobs/HelloWorld/workspace
>> > git rev-parse --is-inside-work-tree # timeout=10
>> Fetching changes from the remote Git repository
>> > git config remote.origin.url file:///var/lib/jenkins/repo/test_repo.git <> 
>> > # timeout=10
>> Fetching upstream changes from file:///var/lib/jenkins/repo/test_repo.git <>
>> > git --version # timeout=10
>> > git -c core.askpass=true fetch --tags --progress 
>> > file:///var/lib/jenkins/repo/test_repo.git <> 
>> > +refs/heads/:refs/remotes/origin/
>> > git rev-parse refs/remotes/origin/master^
>> 
>> {commit} # timeout=10
>> > git rev-parse refs/remotes/origin/origin/master^{commit}
>> # timeout=10
>> > git rev-parse origin/master^
>> 
>> {commit}
>> # timeout=10
>> ERROR: Couldn't find any revision to build. Verify the repository and branch 
>> configuration for this job.
>> Finished: FAILURE
>> 
>> And here is the output when I leave branch blank...
>> Building in workspace /var/lib/jenkins/jobs/HelloWorld/workspace
>> > git rev-parse --is-inside-work-tree # timeout=10
>> Fetching changes from the remote Git repository
>> > git config remote.origin.url file:///var/lib/jenkins/repo/test_repo.git <> 
>> > # timeout=10
>> Fetching upstream changes from file:///var/lib/jenkins/repo/test_repo.git <>
>> > git --version # timeout=10
>> > git -c core.askpass=true fetch --tags --progress 
>> > file:///var/lib/jenkins/repo/test_repo.git <> 
>> > +refs/heads/:refs/remotes/origin/
>> Seen 0 remote branches
>> ERROR: Couldn't find any revision to build. Verify the repository and branch 
>> configuration for this job.
>> Finished: FAILURE
>> 
>> 
>> -- 
>> You received this message because you are 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/911c209e-58d8-4cca-9077-43f00d37402d%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/911c209e-

Re: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

[Thomas Zoratto]

you need to do something like that : 

mkdir my-repo
cd my-repo
git init
cp /path/to/a/file ./
git add --all
git commit -m "your commit message"

then you specify the path to this repo in a Jenkins job et voilà !

> Le 3 juin 2016 à 22:16, Freddy Paxton  a 
> écrit :
> 
> Thank you, I have been trying to use tutorials but because I'm already half 
> way through the process it's hard to see what I have missed or what I have 
> setup incorrectly.
> Just for clarification, do my java files need to be in the 
> /var/lib/jenkins/repo folder or the /var/lib/jenkins/repo/test_repo.git 
> folder? Originally I was trying to use the test_repo.git folder for all of 
> this, I think this is mainly where I have been going wrong.
> 
> On Friday, June 3, 2016 at 9:07:36 PM UTC+1, Thomas Zoratto wrote:
> cd /path/to/your/repo
> 
> git add --all
> git commit -m "your commit message"
> 
> I encourage you to go through a git tutorial to learn the basics.
> 
> Thomas
> 
>> Le 3 juin 2016 à 22:00, Freddy Paxton > > a écrit :
>> 
>> How do I go about doing this?
>> 
>> On Friday, June 3, 2016 at 8:23:10 PM UTC+1, Thomas Zoratto wrote:
>> Hi, 
>> 
>> Did you commit your changes in your repo ? 
>> 
>>> Le 3 juin 2016 à 20:43, Freddy Paxton > a 
>>> écrit :
>>> 
>>> I'm new to Jenkins, Ubuntu and Git so the answer to this is probably 
>>> something I've missed out!
>>> 
>>> What I want to do is set up a Git repository in which 2 Java files are 
>>> located (HelloWorld.java and HelloWorldErr.java - HelloWorldErr is missing 
>>> an ; ). This is to test the Jenkins build and test system to see if it can 
>>> successfully compile the HelloWorld.java file and run it, and also discover 
>>> the error in HelloWorldErr.java. It's a pretty simple test but I'm having 
>>> trouble getting it working.
>>> 
>>> After finally managing to set up the repository correctly, I now get an 
>>> error saying:
>>> ERROR: Couldn't find any revision to build. Verify the repository and 
>>> branch configuration for this job.
>>> 
>>> After scouting the internet for tutorials and/or anyone with similar 
>>> problems I'm still looking for a solution. Even an explanation of the 
>>> process would probably help me a lot.
>>> 
>>> My repository is located at /var/lib/jenkins/repo/test_repo.git/ and the 2 
>>> Java files are in there. I left the branch specifier as */master as I do 
>>> not know what this does.
>>> 
>>> In my Execute shell command I have:
>>> 
>>> javac HelloWorld.java
>>> java HelloWorld
>>> Obviously this means that it is not looking at HelloWorldErr.java but for 
>>> now I just want the build to run successfully.
>>> 
>>> Sorry if I haven't explained myself very well. Once I get this working I am 
>>> also planning to test running files through GitHub but I do not want to 
>>> start on that before I can get the local Git working correctly.
>>> 
>>> Thanks in advance! Any insight on this is going to really help me with my 
>>> project.
>>> 
>>> If it helps here is the console output with branch set to */master...
>>> Building in workspace /var/lib/jenkins/jobs/HelloWorld/workspace
>>> > git rev-parse --is-inside-work-tree # timeout=10
>>> Fetching changes from the remote Git repository
>>> > git config remote.origin.url file:///var/lib/jenkins/repo/test_repo.git 
>>> > <> # timeout=10
>>> Fetching upstream changes from file:///var/lib/jenkins/repo/test_repo.git <>
>>> > git --version # timeout=10
>>> > git -c core.askpass=true fetch --tags --progress 
>>> > file:///var/lib/jenkins/repo/test_repo.git <> 
>>> > +refs/heads/:refs/remotes/origin/
>>> > git rev-parse refs/remotes/origin/master^
>>> 
>>> {commit} # timeout=10
>>> > git rev-parse refs/remotes/origin/origin/master^{commit}
>>> # timeout=10
>>> > git rev-parse origin/master^
>>> 
>>> {commit}
>>> # timeout=10
>>> ERROR: Couldn't find any revision to build. Verify the repository and 
>>> branch configuration for this job.
>>> Finished: FAILURE
>>> 
>>> And here is the output when I leave branch blank...
>>> Building in workspace /var/lib/jenkins/jobs/HelloWorld/workspace
>>> > git rev-parse --is-inside-work-tree # timeout=10
>>> Fetching chang

Re: Integrating promoted-builds DSL to a job-dsl-gradle-example project

[Thomas Zoratto]

Hi, 

thanks for this update. I still don’t have time to try something about it but I 
will…! 


> Le 7 juin 2016 à 17:20, François Genois  a écrit :
> 
> Information for all (and for Thomas) :
> 
> I was able to output the XML files in a not-clean-not-proud way :
> I copied the JenkinsJobManagement file (to remove the 'final' keyword from it 
> that class) and I subclassed it as MemoryJobManagement subclasses 
> MockJobManagement.
> I needed to add logging logic to some of the calls of JenkinsJobManagement 
> (wraping JenkinsJobManagement would have been very unpleasant, but 
> subclassing it is really pretty)
> Anyway, here is an example outputting XML if you run 'gradlew test'.
> https://github.com/franknarf8/job-dsl-gradle-example/tree/03524daa83851a544106cc514591026a99f3ee64
>  
> <https://github.com/franknarf8/job-dsl-gradle-example/tree/03524daa83851a544106cc514591026a99f3ee64>
> 
> Thanks again and have a nice day!
> 
> - Frank
> 
> 
> On Wednesday, June 1, 2016 at 5:04:27 PM UTC-4, François Genois wrote:
> Ok, I'm pretty much in the same situation over here. Alright, I'm looking 
> forward your advancement on this issue; I'll keep you updated if I find 
> anything.
> 
> Thanks again!
> 
> - Frank
> 
> On Wed, Jun 1, 2016 at 3:40 PM Thomas Zoratto  <mailto:thomas.zora...@gmail.com>> wrote:
> Right now I can’t see a way to do this but my knowledge on this topic is very 
> limited. I also have to work on it soon so I’ll let you know if I find a way 
> (and if you still don’t have the answer).
> 
> Please share your progress, if any 
> 
> Good luck !
> 
> Thomas
> 
> 
> 
>> Le 1 juin 2016 à 20:35, François Genois > <mailto:frankgenera...@gmail.com>> a écrit :
>> 
> 
>> Hello Thomas,
>> 
>> Thank you very much for your answer.
>> The promoted builds plugin is indeed a extension point.
>> 
>> I added the following line to my dependencies "testCompile 
>> 'org.jenkins-ci.plugins:promoted-builds:2.27@jar'" and my 'gradlew test' 
>> command now succeeds.
>> 
>> I just tried applying the same logic to the 'debugXml' gradle task (I use 
>> the XML to verify if I haven't done any regression during refactoring), but 
>> I can't figure out how to make this code run in a context running an 
>> instance of the promoted-builds plugin.
>> 
>> Do you have an idea of how I could get the XML generated from the scripts?
>> 
>> Thank you again and have a nice day!
>> 
>> - Frank
>> 
>> 
>> On Wednesday, June 1, 2016 at 12:20:01 PM UTC-4, Thomas Zoratto wrote:
>> Hello Frank, 
>> 
>> I guess the promoted builds plugin is not directly compatible with the job 
>> DSL plugin. I mean you can’t find DSL methods relative to the promoted 
>> builds plugin in the online API 
>> https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842
>>  
>> <https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842>.
>>  
>> 
>> I think the job DSL plugin must use the extension point when in the context 
>> of a running instance with the promoted builds plugin installed.
>> 
>> Though, I suppose you can test it locally thanks to the last updates of 
>> sheehan's github repo. See 
>> https://github.com/sheehan/job-dsl-gradle-example/commit/9d6260b44cefdd832ee3f854f107b24f15881ea7
>>  
>> <https://github.com/sheehan/job-dsl-gradle-example/commit/9d6260b44cefdd832ee3f854f107b24f15881ea7>.
>>  You’ll have to specify the plugins you have in your running instance in 
>> order to simulate a similar environment for your local tests.
>> 
>> sorry for my poor English !
>> 
>> Thomas
>> 
>>> Le 1 juin 2016 à 16:36, François Genois > a écrit :
>>> 
>>> Good morning everyone,
>>> 
>>> I'm currently using a project based on 
>>> https://github.com/sheehan/job-dsl-gradle-example 
>>> <https://github.com/sheehan/job-dsl-gradle-example> and I am trying to get 
>>> the promoted-builds plugin to work with this project 
>>> (https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin 
>>> <https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin>).
>>> 
>>> Everything works fine on my Jenkins server (with the plugin installed), but 
>>> I can't figure out a way to make my code work on this local project. I use 
>>> this project to work locally, to debug and to te

Re: Jenkins 2.0 github organization folder not showing up

[Thomas Zoratto]

Hi, 

Did you restart your Jenkins instance after installing these plugins ?

If you look at others thread in the ML you’ll find same kind of problems and 
the solution was to restart. (a known bug it seems)

Thomas

> Le 10 juin 2016 à 12:35, Tuomas-Matti Soikkeli  a écrit :
> 
> 
> 
> 
> 
> Good day.
> 
> I'm migrating to pipelines and other Jenkins 2.0 goodies. However I stumbled 
> into problems in the first steps. I can't see the organization folder job 
> type in new items view.  Any hints? Most of the getting started tutorials 
> state there should be one. Screenshot included. Tested 2.8, 2.3 and 2.0, last 
> two we're docker releases.
> 
> Screenshot:
> 
>  
> 
> 
> Thanks, Tuomas
> 
> 
> 
> -- 
> You received this message because you are 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/1773b3a6-c45d-4d9b-9064-52d309fb2518%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/BD73C7DC-806F-449D-A34C-D9CF6C909360%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Getting started with Pipeline

[Thomas Zoratto]

Hello, 

I’m not sure to understand correctly but your needs seems quite straightforward.

To achieve that, you want to create a multibranch pipeline job (as you have 
already done I see) which will scan all your project’s branches looking for 
Jenkinsfiles.

In those Jenkinsfiles, you’ll have to describe your pipeline. Basically, you 
have to checkout the project and then execute your step. I suppose you can run 
your build tool with a "shell step" like sh 'build_tool ' if your 
build_tool is in the PATH. 

This way you’ll have a Jenkinsfile per branch.

Then, if you wanna define a real pipeline (tests then deploy to some 
environment and then deploy again somewhere else for example) the 
documentation/tutorials will help you I think


> Le 10 juin 2016 à 17:40, Jerry Steele  a écrit :
> 
> Hello,
> 
> I'm looking into getting Jenkins to build feature branches for our github 
> projects, but I'm not entirely sure where to start. Pipeline looks like it 
> might fit the bill, but I'm having trouble getting my head round the 
> Jenkinsfile. I've found the online docs and the "Groovy" generator but am not 
> really sure how to tie it all together. If anyone has a bit oftime to help 
> me, that would be great :)
> 
> We currently use our own build tool to test code as deployed to github, then 
> build the artifacts into a debian package which is uploaded to Amazon S3 and 
> deployed by hand later.
> 
> We currently have separate jobs for each of the major branches of our project:
> 
> subproject_a-qa
> subproject_a-staging
> subproject_a-production
> 
> subproject_b-qa
> subproject_b-staging
> subproject_b-production
> 
> subproject_c-qa
> subproject_c-staging
> subproject_c-production
> 
> The jobs are very simple - they poll github, looking at a specific branch, 
> then if that has changed, they will execute a shell script which looks like 
> this (generic):
> 
> sudo -Hs build_tool arg1 $GIT_URL  
> 
> 
> So, what I'd need is something that builds the following jobs when a feature 
> branch is pushed to look something like:
> 
> sudo -Hs build_tool arg1 $GIT_URL  
> sudo -Hs build_tool arg1 $GIT_URL  
> sudo -Hs build_tool arg1 $GIT_URL  
> 
> Or else, know how to build those.
> 
> Is this possible with Pipeline? Or am I looking at the wrong tool here? I've 
> started a multibranch test project, but am basically stuck at the Jenkinsfile 
> stage, and most tutorials appear to refer to using mvn, which I'm not 
> familiar with. the build tool is written in Python and is testing building 
> for Ruby on Rails :)
> 
> Any help very much appreciated. Any more info needed, please let me know...
> 
> Thanks
> 
> Jerry
> 
> 
> -- 
> You received this message because you are 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/1414775a-307d-49fe-9119-2f77995385ce%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/9D3FDAAB-1C30-40A0-9D1C-AB85BF424A46%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Run pipeline flyweight executors off of master

[Thomas Zoratto]

Hello, 

I’m not sure one can do what you want.

Out of curiosity, what’s the use case for this ?


> Le 13 juin 2016 à 23:16, Eli White  a écrit :
> 
> My understanding is that Jenkinsfile execution runs as a flyweight node on 
> master, but then uses heavyweight nodes on the given node label to execute.
> 
> Per this file: 
> https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md
> 
> Why are there two executors consumed by one Pipeline build?
> 
> Every Pipeline build itself runs on the master, using a flyweight executor — 
> an uncounted slot that is assumed to not take any significant computational 
> power.
> This executor represents the actual Groovy script, which is almost always 
> idle, waiting for a step to complete.
> Flyweight executors are always available.
> 
> On Monday, June 13, 2016 at 2:11:19 PM UTC-7, Craig Rodrigues wrote:
> In your pipeline, the node parameter can take an argument of which node to 
> run on.
> 
> See this example:
> https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/build-test.groovy#L100
>  
> 
> 
> In my job, I defined BUILD_NODE with the NodeLabel Parameter Plugin ( 
> https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin 
>  ).
> 
> --
> Craig
> 
> 
> 
> On Mon, Jun 13, 2016 at 2:03 PM, Eli White  > wrote:
> We follow the Jenkins configuration best practices and have no executors on 
> our master node and force everything to run on our agents. 
> 
> We are starting to work with pipeline jobs and are worried that bad 
> Jenkinsfiles could cause problems on our master. 
> How can we force the flyweight jobs to run on a designated machine *other* 
> than master? 
> 
> How do other people handle this?
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/d4ee67f4-ab75-4a1e-9883-69453bdd656b%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/a41c28a9-fc93-459f-b990-87cb1210cb64%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/9823286F-055A-4C0B-8DD7-D62B87BCB5B6%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Integrating promoted-builds DSL to a job-dsl-gradle-example project

[Thomas Zoratto]

Hello, 

I came up with a solution that doesn’t involve overwriting class, subclass etc.

You just have to use the JenkinsRule object in your test in order to use the 
API of the running Jenkins instance.

e.g. jenkinsRule.jenkins.getAllItems()…

Then you can retrieve the config.xml generated for each job/view. Tested here 
and it works.

But I have good news for you, JenkinsJobManagement is no longer final thanks to 
a recent commit (see 
https://github.com/jenkinsci/job-dsl-plugin/commit/930aa4818a3ff74494696b14c241a521bc75c0a9
 
<https://github.com/jenkinsci/job-dsl-plugin/commit/930aa4818a3ff74494696b14c241a521bc75c0a9>).
 We have to wait for the next release though.

> Le 7 juin 2016 à 17:20, François Genois  a écrit :
> 
> Information for all (and for Thomas) :
> 
> I was able to output the XML files in a not-clean-not-proud way :
> I copied the JenkinsJobManagement file (to remove the 'final' keyword from it 
> that class) and I subclassed it as MemoryJobManagement subclasses 
> MockJobManagement.
> I needed to add logging logic to some of the calls of JenkinsJobManagement 
> (wraping JenkinsJobManagement would have been very unpleasant, but 
> subclassing it is really pretty)
> Anyway, here is an example outputting XML if you run 'gradlew test'.
> https://github.com/franknarf8/job-dsl-gradle-example/tree/03524daa83851a544106cc514591026a99f3ee64
>  
> <https://github.com/franknarf8/job-dsl-gradle-example/tree/03524daa83851a544106cc514591026a99f3ee64>
> 
> Thanks again and have a nice day!
> 
> - Frank
> 
> 
> On Wednesday, June 1, 2016 at 5:04:27 PM UTC-4, François Genois wrote:
> Ok, I'm pretty much in the same situation over here. Alright, I'm looking 
> forward your advancement on this issue; I'll keep you updated if I find 
> anything.
> 
> Thanks again!
> 
> - Frank
> 
> On Wed, Jun 1, 2016 at 3:40 PM Thomas Zoratto  <mailto:thomas.zora...@gmail.com>> wrote:
> Right now I can’t see a way to do this but my knowledge on this topic is very 
> limited. I also have to work on it soon so I’ll let you know if I find a way 
> (and if you still don’t have the answer).
> 
> Please share your progress, if any 
> 
> Good luck !
> 
> Thomas
> 
> 
> 
>> Le 1 juin 2016 à 20:35, François Genois > <mailto:frankgenera...@gmail.com>> a écrit :
>> 
> 
>> Hello Thomas,
>> 
>> Thank you very much for your answer.
>> The promoted builds plugin is indeed a extension point.
>> 
>> I added the following line to my dependencies "testCompile 
>> 'org.jenkins-ci.plugins:promoted-builds:2.27@jar'" and my 'gradlew test' 
>> command now succeeds.
>> 
>> I just tried applying the same logic to the 'debugXml' gradle task (I use 
>> the XML to verify if I haven't done any regression during refactoring), but 
>> I can't figure out how to make this code run in a context running an 
>> instance of the promoted-builds plugin.
>> 
>> Do you have an idea of how I could get the XML generated from the scripts?
>> 
>> Thank you again and have a nice day!
>> 
>> - Frank
>> 
>> 
>> On Wednesday, June 1, 2016 at 12:20:01 PM UTC-4, Thomas Zoratto wrote:
>> Hello Frank, 
>> 
>> I guess the promoted builds plugin is not directly compatible with the job 
>> DSL plugin. I mean you can’t find DSL methods relative to the promoted 
>> builds plugin in the online API 
>> https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842
>>  
>> <https://github.com/franknarf8/job-dsl-gradle-example/commit/f15b7fbf698d7be29b8527043d8649ab15559842>.
>>  
>> 
>> I think the job DSL plugin must use the extension point when in the context 
>> of a running instance with the promoted builds plugin installed.
>> 
>> Though, I suppose you can test it locally thanks to the last updates of 
>> sheehan's github repo. See 
>> https://github.com/sheehan/job-dsl-gradle-example/commit/9d6260b44cefdd832ee3f854f107b24f15881ea7
>>  
>> <https://github.com/sheehan/job-dsl-gradle-example/commit/9d6260b44cefdd832ee3f854f107b24f15881ea7>.
>>  You’ll have to specify the plugins you have in your running instance in 
>> order to simulate a similar environment for your local tests.
>> 
>> sorry for my poor English !
>> 
>> Thomas
>> 
>>> Le 1 juin 2016 à 16:36, François Genois > a écrit :
>>> 
>>> Good morning everyone,
>>> 
>>> I'm currently using a project based on 
>>> https://github.com/sheehan/job-dsl-gradle-example 
>>&

Re: Error While trying to configure S3 plugin

[Thomas Zoratto]

Hi, 

This commit fixed your problem 
(https://github.com/jenkinsci/s3-plugin/commit/b1fa4818c33c6aca594de492a659767516a3bc50
 
)

You’ll have to wait for the next release.

> Le 26 juin 2016 à 11:04, AboveBeyond  a écrit :
> 
> java.lang.NoClassDefFoundError: 
> org/apache/http/conn/ManagedHttpClientConnection

-- 
You received this message because you are 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/E8AE08F1-8174-4CFA-9A36-9381CBB4FE48%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error While trying to configure S3 plugin

[Thomas Zoratto]

I don’t know, in a few days maybe if I look at the release history

Of course you can patch it on your own and install your custom version on your 
server if you can’t wait

> Le 26 juin 2016 à 11:35, AboveBeyond  a écrit :
> 
> 
> 
> On Sunday, June 26, 2016 at 12:28:33 PM UTC+3, Thomas Zoratto wrote:
> Hi, 
> 
> This commit fixed your problem 
> (https://github.com/jenkinsci/s3-plugin/commit/b1fa4818c33c6aca594de492a659767516a3bc50
>  
> <https://github.com/jenkinsci/s3-plugin/commit/b1fa4818c33c6aca594de492a659767516a3bc50>)
> 
> You’ll have to wait for the next release.
> 
>> Le 26 juin 2016 à 11:04, AboveBeyond > a 
>> écrit :
>> 
>> java.lang.NoClassDefFoundError: 
>> org/apache/http/conn/ManagedHttpClientConnection
> 
> 
> When it will be release ? 
> Can i fix it on my server without waiting? 
> 
> 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 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/2729f2a5-f2eb-4fe4-af8d-c88a45ccd8ba%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/2729f2a5-f2eb-4fe4-af8d-c88a45ccd8ba%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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/4DCBBF12-A73D-44CD-8287-A8F2E0630C2D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Synchronize timestamps in Jenkins output console, between nodes and master

[Thomas Zoratto]

Hello,

I don't know if there is a better solution to do it but maybe you could specify 
the desired time zone during the creation of your AWS instance


> Le 29 juin 2016 à 12:56, steliosP  a écrit :
> 
> I am facing the following problem:
> Jenkins slaves are deployed in AWS, in different regions.The console output 
> of builds contains timestamps, in the timezone where each node/slave belongs.
> Is there a way to have timestamps in the same timezone as Jenkins server?
> -- 
> You received this message because you are 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/0f2e7b81-734a-40eb-a412-6cf6c080fa52%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/2951D1CE-21A1-4775-A88A-8565257AFC5B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Building containers with Docker in Docker and Jenkins

[Thomas Zoratto]

Hi Baptiste, 

Not sure you can easily mount the docker client binary (you could, back in the 
day but now there are some required dependencies).
 

 
> Le 2 juil. 2016 à 22:00, Baptiste Mathus  a écrit :
> 
> Worth a read probably: 
> https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/ 
>  
> from a Docker team member.
> 
> For your case, might be even simpler to also bind mount the docker client 
> binary in your container. That way you can keep your Dockerfile independent 
> of that.
> 
> Also, beware that using bind mounts for data is generally not recommended. 
> Better use a named volume (since data volume containers are somehow now 
> deprecated).
> 
> Cheers
> 
> Just wanted to share some of my experiences with building Docker containers 
> using a dockerized Jenkins setup. For people like me who are running simple 
> Jenkins setup on their home hardware this might be interesting to read: 
> https://renzedevries.wordpress.com/2016/06/30/building-containers-with-docker-in-docker-and-jenkins/
>  
> 
> 
> Look forward to hearing some feedback on this and if other people are having 
> similar setups. There is not a lot of information on this subject, but I do 
> see a huge potential for a mobile Jenkins docker solution, where you can run 
> your CI anywhere, specially given the new Jenkins pipelines this becomes very 
> interesting, just deploy the Jenkins container and go.
> 
> -- 
> You received this message because you are 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/ff8b6639-ff66-46e2-8617-a3d6d02a9511%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/CANWgJS7XYJ4%3DgaVkt3FFV1LLMqckKtXRg0NX1XuHL%3D8Uc1hMrA%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/C9B6B91B-6968-4C16-8BE0-03A68041A0CE%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [pipeline] publishHtml failed with file present

[Thomas Zoratto]

Hi, 

this bug is already reported here : 
https://issues.jenkins-ci.org/browse/JENKINS-29711 


publishHTML is not the only step impacted 

> Le 12 juil. 2016 à 18:15, jer...@bodycad.com a écrit :
> 
> I think I found the solution on that page:
> https://jenkins.io/blog/2016/07/01/html-publisher-plugin/ 
> 
> 
> publishHTML([allowMissing: true, alwaysLinkToLastBuild: false, keepAll: true, 
> reportDir: 'x64\\Release\\FailedTestResult\\', reportFiles: 'index.html', 
> reportName: 'Failed Tests'])
> 
> should be
> 
> publishHTML(target:[allowMissing: true, alwaysLinkToLastBuild: false, 
> keepAll: true, reportDir: 'x64\\Release\\FailedTestResult\\', reportFiles: 
> 'index.html', reportName: 'Failed Tests'])
> 
> notice the extra target:
> I guess the pipeline syntaxe for publishHTML have a typo. I would rather have 
> a web link to the full API outside Jenkins.
> 
> 
> On Tuesday, July 12, 2016 at 12:10:35 PM UTC-4, jer...@bodycad.com 
>  wrote:
> Hi,
> 
> I'm trying this into my piple Jenkinsfile:
> 
> publishHTML([allowMissing: true, alwaysLinkToLastBuild: false, keepAll: true, 
> reportDir: 'x64\\Release\\FailedTestResult\\', reportFiles: 'index.html', 
> reportName: 'Failed Tests']);
> 
> The directory is there and the index.html file exist too at that step. But I 
> get the following error:
> 
> [Pipeline] publishHTML
> [Pipeline] }
> [Pipeline] // timestamps
> [Pipeline] }
> [Pipeline] // node
> [Pipeline] End of Pipeline
> ERROR: Cannot publish the report. Target is not specified
> Finished : FAILURE
> 
> I generate my line with the pipeline syntax tools. My question is what is the 
> target and does it represent? Any place where we can find the API doc for all 
> those pipeline functions? 
> 
> Thanks,
> Jerome
> 
> -- 
> You received this message because you are 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/592333c4-e787-4fb8-842a-a80602ce6ab1%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/1B5D1C01-C0B1-41F1-9E07-7BE0FB828F67%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: workspace not getting cleared before or after build.

[Thomas Zoratto]

Be sure that 
https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin 
 is 
installed

> Le 20 juil. 2016 à 15:34, Ashish Yadav  a écrit :
> 
> I am currently running Jenkins LTS v1.642.3 on CentOS 6. In my job configs, I 
> am NOT seeing any section or task to clean the workspace before build or even 
> as a Post-Build activity to clean workspace after build. Did this feature get 
> removed somehow?
> 
> 
> 
> 
> -- 
> You received this message because you are 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/D3B4E819.21FC2%25ashish.yadav%40firemon.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/7BF1FC63-1EA8-4431-A75B-0DA1D158044A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jobs as a code

[Thomas Zoratto]

Hi, 

I use both Jenkins DSL and pipeline and I’m pretty satisfied with this 
configuration.

Jenkins DSL lets me define views and jobs which are specific tasks like doing 
some clean-up or whatever you want.

On the other side, I use pipeline to set up projects' CI/CD.

This way, every single job or view is "as code" 

> Le 21 juil. 2016 à 02:14, Jakov Sosic  a écrit :
> 
> Hi guys
> 
> I would like to manage jenkins jobs through code if possible. I'm kinda 
> getting tired of everybody in the team clicking around and modifying stuff 
> left and right.
> 
> There seems to be 3 options available as far as I could find:
> 
> - Jenkins DSL
> - jenkins-job-builder (OpenStack)
> - Pipeline (formerly known as Workflow) plugin
> 
> 
> Is there anything else, or is this it, and does anybody have any experience? 
> What would you suggest out of these 3 as the best one?
> 
> 
> Thanks,
> 
> Jakov
> 
> -- 
> You received this message because you are 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/579013CC.6080508%40gmail.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/B0F9280B-31CE-4148-9FAA-38CFAA18A0FE%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.x - Pipeline(DSL) - Build failed but all stages are green

[Thomas Zoratto]

currentBuild.result is writable

try to set it to 'SUCCESS' when before your pipeline reaches the end

> Le 21 juil. 2016 à 11:53, thomas.lehm...@teamaol.com a écrit :
> 
> We are working with Jenkins 2.13 the moment.
> We have a ci/cd pipeline with all stages green but the build itself is red.
> 
> From the log I cannot see anything which gives me a hint.
> Also all deployed stuff is fine and the final slack notification were also 
> fine!
> 
> Every "sh" call is wrapped by the try ... catch ... throw ... so if there 
> would
> be an error the pipeline should stop at the stage where the error appears.
> 
> I wrote manually a jenkinsfile but ... as you can guess ... all fine.
> 
> I didn't found a way to check the build state. When is this set?
> Can I do an echo of current state so I could add some output?
> 
> currentBuild.result prints null, so obviously this is not used.
> Any help, proposes?
> 
> Kind regards,
> Thomas
> 
> -- 
> You received this message because you are 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/13fa2d82-4e53-40df-a9a6-d6d2f020b2b7%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/6A5F78FE-585B-47CC-988B-12D7D2377157%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.x - Pipeline(DSL) - Build failed but all stages are green

[Thomas Zoratto]

You want to do something like :

try {
currentBuild.result = "SUCCESS"
//do your stuff, stages etc.
} catch (err) {
currentBuild.result = "FAILURE"
throw err
}

(Of course you’ll have to adjust this to your needs)

This way the build will be green if all the stages are green and it will be red 
if a stage fails.

Is this what you’re looking for ?


> Le 21 juil. 2016 à 12:17, thomas.lehm...@teamaol.com a écrit :
> 
> When I do this ... currentBuild.result = "FAILURE" for a small test pipeline 
> job then the build fails also the stages are green.
> Exactly the problem I explained. When setting to "SUCCESS" all is fine. So 
> obvious there is anything adjusting the state wrongly.
> 
> Is there a way where I can check the success state after each operation?
> (as mentioned ... echo currentBuild.result prints null)
> 
> On Thursday, July 21, 2016 at 12:07:43 PM UTC+2, thomas@teamaol.com 
> <http://teamaol.com/> wrote:
> Will give it a try ...
> 
> On Thursday, July 21, 2016 at 12:00:15 PM UTC+2, Thomas Zoratto wrote:
> currentBuild.result is writable
> 
> try to set it to 'SUCCESS' when before your pipeline reaches the end
> 
>> Le 21 juil. 2016 à 11:53, thomas@teamaol.com <> a écrit :
>> 
>> We are working with Jenkins 2.13 the moment.
>> We have a ci/cd pipeline with all stages green but the build itself is red.
>> 
>> From the log I cannot see anything which gives me a hint.
>> Also all deployed stuff is fine and the final slack notification were also 
>> fine!
>> 
>> Every "sh" call is wrapped by the try ... catch ... throw ... so if there 
>> would
>> be an error the pipeline should stop at the stage where the error appears.
>> 
>> I wrote manually a jenkinsfile but ... as you can guess ... all fine.
>> 
>> I didn't found a way to check the build state. When is this set?
>> Can I do an echo of current state so I could add some output?
>> 
>> currentBuild.result prints null, so obviously this is not used.
>> Any help, proposes?
>> 
>> Kind regards,
>> Thomas
>> 
>> -- 
>> You received this message because you are 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/13fa2d82-4e53-40df-a9a6-d6d2f020b2b7%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/13fa2d82-4e53-40df-a9a6-d6d2f020b2b7%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <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 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/5393aca6-eee1-4832-9dce-3052781a6010%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/5393aca6-eee1-4832-9dce-3052781a6010%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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/0744AC69-CC6E-4B85-90DE-C4AAF7F29368%40gmail.com.
For more options, visit https://groups.google.com/d/optout.