Re: Multi-Branch Project Plugin: NoClassDefFoundError: Could not initialize class org.eclipse.jgit.transport.Transport

[Emmanuel Vanhoucke]

Exactly, the same problem. I came back in a previous version of Jenkins and 
everithing was ok...

Le vendredi 16 octobre 2015 08:32:26 UTC+2, Timo M a écrit :
>
> i have exactly the same error. Is there a solution?
>
> Am Mittwoch, 14. Oktober 2015 16:46:59 UTC+2 schrieb Alex Miles:
>>
>> Hi all,
>>
>>
>> I'm trying to set up builds for my git project, and I want to have a build 
>> for each branch, and also for pull requests, so I can get some feedback in 
>> version control. I'm trying to use the Multi-Branch Project Plugin 
>> (https://wiki.jenkins-ci.org/display/JENKINS/Multi-Branch+Project+Plugin) as 
>> a starting point but I can't get it to sync the branches.
>>
>>
>> I'm not a Java developer, so I feel pretty out of my depth troubleshooting 
>> this, but I've done my best. It looks to me like a problem to do with JGit, 
>> which I understand is a native Java git implementation, which is used by the 
>> Jenkins Git plugin, which the Multi-Branch Project Plugin is calling via the 
>> SCM API. I found configuration options for Git/JGit in the system 
>> configuration settings, and tried adjusting them, but to no avail.
>>
>>
>> I've also tried installing the libjgit-java package.
>>
>>
>> System details:
>>
>> Ubuntu trusty
>>
>> Jenkins 1.633
>>
>> GIT client plugin 1.19.0
>> GIT plugin 2.4.0
>> Multi-Branch Project Plugin 0.3
>>
>>
>> The repo is on Bitbucket, if that makes any difference, and I'm using an SSH 
>> key to authenticate. Those credentials work fine on a freestyle project not 
>> using the multi-branch plugin, although not when I "force" use of JGit but 
>> removing the configuration setting where I specify a path to a git 
>> executable. Which also seems to point to there being a problem with JGit in 
>> my environment.
>>
>>
>> I'd be grateful for any help.
>>
>>
>> In the "Sync Branches Log" of my project I have the following:
>>
>>
>> Started on Oct 14, 2015 1:41:02 PM
>> Setting origin to g...@bitbucket.org:alex/myproject.git
>> Fetching origin...
>> FATAL: Could not initialize class 
>> org.eclipse.jgit.transport.Transportjava.lang.NoClassDefFoundError 
>> :
>>  Could not initialize class org.eclipse.jgit.transport.Transport
>>  at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:120) 
>> 
>>  at 
>> org.jenkinsci.plugins.gitclient.JGitAPIImpl.fetch(JGitAPIImpl.java:672) 
>> 
>>  at 
>> jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:171)
>>  
>> 
>>  at jenkins.scm.api.SCMSource.fetch(SCMSource.java:141) 
>> 
>>  at jenkins.scm.api.SCMSource.retrieve(SCMSource.java:180) 
>> 
>>  at jenkins.scm.api.SCMSource.fetch(SCMSource.java:167) 
>> 
>>  at 
>> com.github.mjdetullio.jenkins.plugins.multibranch.AbstractMultiBranchProject._syncBranches(AbstractMultiBranchProject.java:981)
>>  
>> 
>>  at 
>> com.github.mjdetullio.jenkins.plugins.multibranch.AbstractMultiBranchProject.syncBranches(AbstractMultiBranchProject.java:948)
>>  
>> 
>>  at 
>> com.github.mjdetullio.jenkins.plugins.multibranch.SyncBranchesTrigger.run(SyncBranchesTrigger.java:102)
>>  
>> 
>>  at 
>> com.github.mjdetullio.jenkins.plugins.multibranch.AbstractMultiBranchProject.doConfigSubmit(AbstractMultiBranchProject.java:904)
>>  
>> 
>>  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.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
>>  at org.kohsuke.stapler.Function.bindAndI

Re: How to make the Job name not updatable

[Emmanuel DEMEY]

Hi everyone,

Any ideas about this issue ? Do you need more informations ?

Thanks

Manu


2014-07-21 14:30 GMT+02:00 Emmanuel DEMEY :

> Hi everyone,
>
> After the creation of a job, how can I make the job name read-only for all
> users ?
>
> I need this, in order to break the link between the job and our database
> that use our jenkins resource.
>
> Thanks a lot.
>
> Manu
>
> --
> Emmanuel DEMEY
> Ingénieur Etude et Développement
> Worldline, an atos company
> +33 (0)6 47 47 42 02
> demey.emman...@gmail.com
>
>
> Twitter : @EmmanuelDemey
>



-- 
Emmanuel DEMEY
Ingénieur Etude et Développement
Worldline, an atos company
+33 (0)6 47 47 42 02
demey.emman...@gmail.com


Twitter : @EmmanuelDemey

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to make the Job name not updatable

[Emmanuel DEMEY]

Hi everyone,

After the creation of a job, how can I make the job name read-only for all
users ?

I need this, in order to break the link between the job and our database
that use our jenkins resource.

Thanks a lot.

Manu

-- 
Emmanuel DEMEY
Ingénieur Etude et Développement
Worldline, an atos company
+33 (0)6 47 47 42 02
demey.emman...@gmail.com


Twitter : @EmmanuelDemey

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Call Perform Maven Release through REST API

[Emmanuel]

Ok thanks ! I guess I will use a classic job instead so that I can use the
REST API.


On Wed, May 28, 2014 at 6:33 PM, James Nord (jnord)  wrote:

>  You can’t automate a release via the m2release plugin via a REST like
> API.
>
> You can do it using HTTP Post and curl – just have a look at the form
> befor you do a release and you should be able to craft a cURL request.
>
>
>
> e.g.
>
> releaseVersion=1.2.3
>
> developmentVersion=1.2.4-SNAPSHOT
>
>
>
> if you’re not sure of the data you need to supply – a wireshark capture of
> a test release is your friend.
>
>
>
> /James
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Emmanuel POT
> *Sent:* 28 May 2014 17:03
> *To:* jenkinsci-users@googlegroups.com
> *Cc:* m...@batmat.net
> *Subject:* Re: Call Perform Maven Release through REST API
>
>
>
> Hello,
>
>
>
> Sorry I will try to be more specific. I want to use the Jenkins plugin Maven
> Release <https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin>.
> It takes care of committing the correct version in the pom.xml before the
> release, with the possibility to tune the commit message...
>
>
>
> I create a new Maven job, and activate the plugin for it. In the UI, it
> adds a new button on the left panel at job level "Perform Maven Release"
> that opens a new form in which I can precise a few things including the
> version. It is not a build parameter of the job that I could pass by
> calling the "classic" REST API. I wonder if this specific plugin can be
> called via the API, and if it is the case, how ?
>
>
>
> Maybe the answer is not to use the Maven job configuration and the plugin
> above, and simply define shell steps with build parameters in a free-style
> project.
>
>
>
> Cheers,
>
> Emmanuel
>
> On Wednesday, 28 May 2014 17:55:45 UTC+2, Baptiste Mathus wrote:
>
> Well, you certainly want too give a wee bit more precision.
>
> Trying to approximately answer your question though, one way to do it
> could be:
> 1) define a Jenkins job, and configure it so that the release works fine
> (define a parameter for that build)
> 2) through either jenkins-cli or the rest api, trigger the release build
> remotely, passing the required parameter you speak about.
>
> Cheers
>
> Le 28 mai 2014 09:31, "Emmanuel POT"  a écrit :
>
> Hello,
>
>
>
> I would like to perform a maven release using the maven release plugin
> remotely. Ideally, I would be able to pass as http parameters the version
> to use.
>
>
>
> I googled for 30min but could not find a way to do that. Has anyone
> managed to do it ?
>
>
>
> Cheers,
>
> emmanuel
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-use...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.
>
>   --
> 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/EskpKpyEv_8/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Call Perform Maven Release through REST API

[Emmanuel POT]

Hello,

Sorry I will try to be more specific. I want to use the Jenkins plugin Maven 
Release <https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin>. It 
takes care of committing the correct version in the pom.xml before the 
release, with the possibility to tune the commit message... 

I create a new Maven job, and activate the plugin for it. In the UI, it 
adds a new button on the left panel at job level "Perform Maven Release" 
that opens a new form in which I can precise a few things including the 
version. It is not a build parameter of the job that I could pass by 
calling the "classic" REST API. I wonder if this specific plugin can be 
called via the API, and if it is the case, how ?

Maybe the answer is not to use the Maven job configuration and the plugin 
above, and simply define shell steps with build parameters in a free-style 
project.

Cheers,
Emmanuel

On Wednesday, 28 May 2014 17:55:45 UTC+2, Baptiste Mathus wrote:
>
> Well, you certainly want too give a wee bit more precision.
>
> Trying to approximately answer your question though, one way to do it 
> could be: 
> 1) define a Jenkins job, and configure it so that the release works fine 
> (define a parameter for that build)
> 2) through either jenkins-cli or the rest api, trigger the release build 
> remotely, passing the required parameter you speak about.
>
> Cheers
> Le 28 mai 2014 09:31, "Emmanuel POT" > 
> a écrit :
>
>> Hello,
>>
>> I would like to perform a maven release using the maven release plugin 
>> remotely. Ideally, I would be able to pass as http parameters the version 
>> to use.
>>
>> I googled for 30min but could not find a way to do that. Has anyone 
>> managed to do it ?
>>
>> Cheers,
>> emmanuel
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Call Perform Maven Release through REST API

[Emmanuel POT]

Hello,

I would like to perform a maven release using the maven release plugin 
remotely. Ideally, I would be able to pass as http parameters the version 
to use.

I googled for 30min but could not find a way to do that. Has anyone managed 
to do it ?

Cheers,
emmanuel

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build Flow Plugin and artifacts management in the DSL

[Emmanuel Boudrant]

Thanks, I will try !
-emmanuel

On Monday, September 16, 2013 6:04:02 AM UTC-7, Emmanuel Boudrant wrote:
>
> Hello,
>
> We've checked the Build Flow Plugin for parallel execution, is is possible 
> to manage the artifact in the plugin.
>
> Example :
>
> parallel (
> // Each job is going to produce one artifact{ build("job1") },
> { build("job2") },
>
> ...
>
> { build("jobN") }
>
> )
>
>
> // deploy need access to all the artifact generated by job1, job2, ..., jobN.
> build("deploy")
>
>
> Our use case is we have plenty of slaves for building the artifacts but only 
> one slave can deploy them.
>
>
> Thanks,
>
> -emmanuel
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Build Flow Plugin and artifacts management in the DSL

[Emmanuel Boudrant]

I am not sure it will work, copy Artifact plugin is going to only copy the 
last successful artifact of a given job ?

When I launch N job in parallel they are actually the same job with 
different parameter. Could it copy the artifacts generated by each job 
build ?


On Monday, September 16, 2013 6:09:06 AM UTC-7, rginga wrote:
>
>  The Copy Artifact Plugin will allow your “deploy” job to copy artifacts 
> from your other jobs and put them in the deploy workspace.
>
>  
>
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Emmanuel 
> Boudrant
> *Sent:* Monday, September 16, 2013 9:04 AM
> *To:* jenkins...@googlegroups.com 
> *Subject:* Build Flow Plugin and artifacts management in the DSL
>
>  
>  
> Hello,
>  
>  
>  
> We've checked the Build Flow Plugin for parallel execution, is is possible 
> to manage the artifact in the plugin.
>  
>  
>  
> Example :
>  
>  
>  
> parallel (
>
> // Each job is going to produce one artifact
>
> { build("job1") },
>
> { build("job2") },
>
> ...
>
> { build("jobN") }
>
>  
>
> )
>
>  
>
> // deploy need access to all the artifact generated by job1, job2, ..., jobN.
> build("deploy")
>
>  
>
> Our use case is we have plenty of slaves for building the artifacts but only 
> one slave can deploy them.
>
>  
>
> Thanks,
>
> -emmanuel
>
>   -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_out.
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Build Flow Plugin and artifacts management in the DSL

[Emmanuel Boudrant]

Hello,

We've checked the Build Flow Plugin for parallel execution, is is possible 
to manage the artifact in the plugin.

Example :

parallel (
// Each job is going to produce one artifact{ build("job1") },
{ build("job2") },

...

{ build("jobN") }

)


// deploy need access to all the artifact generated by job1, job2, ..., jobN.
build("deploy")


Our use case is we have plenty of slaves for building the artifacts but only 
one slave can deploy them.


Thanks,

-emmanuel

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Git plugin: push result of a merge

[Emmanuel Grumbach]

Oh I do have this setup. But the tests I want to run per-commit are much
lighter that when I merge from the community.
My goal is to have Jenkins push --force to a branch (since it can't be ff
as I explained), and trigger a huge regression that I can't control and
that fetches the code from the branch.

But in any case I am happy with what I have now. I just thought it could be
a "nice to have"


Emmanuel Grumbach
egrumb...@gmail.com


On Tue, Feb 14, 2012 at 16:07, Mark Waite  wrote:

> I think (based on other conversations on the mailing list) that the Gerrit
> plugin may provide the type of workflow you're describing.  I haven't yet
> installed and configured Gerrit, so I can't answer from experience, but I
> believe others on the list have stated in the past that a "pre-tested
> commit" workflow is available through the combination of Git and Gerrit and
> Jenkins.
>
> Alex Blewitt published an article in InfoQ
> http://www.infoq.com/articles/Gerrit-jenkins-hudson which gives an
> introduction.  I believe I've also watched a screencast from Alex on the
> same topic.
>
> Mark Waite
>
>*From:* Emmanuel Grumbach 
> *To:* jenkinsci-users@googlegroups.com
> *Sent:* Monday, February 13, 2012 11:35 PM
>
> *Subject:* Re: Git plugin: push result of a merge
>
> First sorry for the late reply, somehow your mail didn't pop up anywhere
> so I just saw it... now.
>
> I guess I need to explain a little the purposes of the branches and it
> will be clearer:
> My project is in sync with the community so that I need to merge code from
> outside quite often. The thing is that I would like to test it before I
> introduce to the main branch so that people don't get mad because "yet
> again someone broke something in the community". So it goes like this:
>
> I have 2 trees A and B. A is the main tree people actually work on. B is a
> mirror of the community.
> Jenkins merges from B to A and pushes to a branch "merge_from_community"
> in A. That way I have the latest internal + merge from the community in a
> separate branch. If tests pass on that code, I can push _manually_ to the
> A's master branch.
> Note that this branch is not fast forward: if someone pushes something to
> A, "merge_from_community" has to be rebased.
>
> This is the flow.
> Frankly, I don't really bother to push manually in my script, I just
> thought that I might not be the only person interested in pushing --force.
> Of course this has to be configurable.
>
> Emmanuel Grumbach
> egrumb...@gmail.com
>
>
> On Sun, Feb 5, 2012 at 22:19, Mark Waite  wrote:
>
> I think adding the force option to the git plugin would be a mistake.  We
> lost submissions when a user used "--force" with their push.  I realize the
> submissions were still somewhere in the object store, but they became
> unreferenced and much more difficult to locate.  Ultimately it was easier
> to recreate the history (and forbid non-fast forward submissions) than to
> locate the unreferenced commits.
>
> Can't you make your submissions a fast forward by performing a merge from
> the remote branch first?  Or are you truly intending to remove repository
> history from your Jenkins job?
>
> Mark Waite
>
>*From:* Emmanuel Grumbach 
> *To:* jenkinsci-users@googlegroups.com
> *Sent:* Sunday, February 5, 2012 12:55 PM
> *Subject:* Re: Git plugin: push result of a merge
>
> Hi,
>
> On Sun, Feb 5, 2012 at 00:32, Sami Tikka  wrote:
> > This should work if you use the git plugin to do it.
> >
> > Configure your job with both X-auto and X-dev repos.
> >
> > Then open the git advanced configuration and check "Merge before build".
> >
> > In Post-build Actions check "Git publisher".
> >
> > I have a somewhat similar setup at work.
> >
> > -- Sami
> >
>
> I did that, the issue is that the git publisher can't add the -f flag
> to the push operation. My push is not fast forward.
>
>
>
>
>
>

Re: Git plugin: push result of a merge

[Emmanuel Grumbach]

First sorry for the late reply, somehow your mail didn't pop up anywhere so
I just saw it... now.

I guess I need to explain a little the purposes of the branches and it will
be clearer:
My project is in sync with the community so that I need to merge code from
outside quite often. The thing is that I would like to test it before I
introduce to the main branch so that people don't get mad because "yet
again someone broke something in the community". So it goes like this:

I have 2 trees A and B. A is the main tree people actually work on. B is a
mirror of the community.
Jenkins merges from B to A and pushes to a branch "merge_from_community" in
A. That way I have the latest internal + merge from the community in a
separate branch. If tests pass on that code, I can push _manually_ to the
A's master branch.
Note that this branch is not fast forward: if someone pushes something to
A, "merge_from_community" has to be rebased.

This is the flow.
Frankly, I don't really bother to push manually in my script, I just
thought that I might not be the only person interested in pushing --force.
Of course this has to be configurable.

Emmanuel Grumbach
egrumb...@gmail.com


On Sun, Feb 5, 2012 at 22:19, Mark Waite  wrote:

> I think adding the force option to the git plugin would be a mistake.  We
> lost submissions when a user used "--force" with their push.  I realize the
> submissions were still somewhere in the object store, but they became
> unreferenced and much more difficult to locate.  Ultimately it was easier
> to recreate the history (and forbid non-fast forward submissions) than to
> locate the unreferenced commits.
>
> Can't you make your submissions a fast forward by performing a merge from
> the remote branch first?  Or are you truly intending to remove repository
> history from your Jenkins job?
>
> Mark Waite
>
>*From:* Emmanuel Grumbach 
> *To:* jenkinsci-users@googlegroups.com
> *Sent:* Sunday, February 5, 2012 12:55 PM
> *Subject:* Re: Git plugin: push result of a merge
>
> Hi,
>
> On Sun, Feb 5, 2012 at 00:32, Sami Tikka  wrote:
> > This should work if you use the git plugin to do it.
> >
> > Configure your job with both X-auto and X-dev repos.
> >
> > Then open the git advanced configuration and check "Merge before build".
> >
> > In Post-build Actions check "Git publisher".
> >
> > I have a somewhat similar setup at work.
> >
> > -- Sami
> >
>
> I did that, the issue is that the git publisher can't add the -f flag
> to the push operation. My push is not fast forward.
>
>
>

Re: Git plugin: push result of a merge

[Emmanuel Grumbach]

Hi,

On Sun, Feb 5, 2012 at 00:32, Sami Tikka  wrote:
> This should work if you use the git plugin to do it.
>
> Configure your job with both X-auto and X-dev repos.
>
> Then open the git advanced configuration and check "Merge before build".
>
> In Post-build Actions check "Git publisher".
>
> I have a somewhat similar setup at work.
>
> -- Sami
>

I did that, the issue is that the git publisher can't add the -f flag
to the push operation. My push is not fast forward.