Re: Git plugin: push result of a merge
If you push with the -f or --force option, the entries on the master branch which are on your central repository after the release_job will be lost. I think you will be very frustrated that your Jenkins job pushed a change to the master branch which lost your most recent work. We avoid that problem by having the most recent build of job_master tag the SHA1 which it built. After job_master has tagged the SHA1 which it built, a script in job_master performs a git fetch, a git merge, and a git push. The job_release is configured to always build from that tag which job_master updates, rather than building from the latest on the branch. If job_release needs to push changes back to the central repository, you could have it do something similar by tagging the SHA1 which it built, then perform a git fetch, a git merge, and a git push. That means those jobs are sometimes pushing something to the central repository which they have not built, but at least they can push to the central repository without losing recent work on the central repository. We have this condition because the team wants the version number checked into source control and incremented automatically on every build of job_master. I would have preferred to have a person increment the version number at key milestones, but the team preferred the automation of version number increment in the build because the version number is used widely in the system to version Microsoft.NET assemblies. Mark Waite From: Juliano Picussa juliano.picu...@gmail.com To: jenkinsci-users@googlegroups.com Cc: egrumb...@gmail.com Sent: Thursday, September 27, 2012 4:29 PM Subject: Re: Git plugin: push result of a merge I've got a similar issue: - I have 2 jenkins jobs for two distinct git branches: master and release (1 job_master to 1 branch master / 1 job_release for branch release) - job_master has a post built configuration to push to the release branch. - job_release has a post built configuration to push to the master branch. Before push, in the release_job the version file is increased and committed to GIT. This is working fine. The problem is when I run the release_job but the release branch is behind of the master branch, the push to master does not work (non-ff). Unfortunately, I didn't find the push -f in the jenkins post built section. This way, or I have to push manually (using --force) or configure a post built shell script (to push --force). Have you found a way to use push -f or other solution for allow non-ff push, using git plugin (publisher)? Tks. On Tuesday, 14 February 2012 14:30:34 UTC, Emmanuel Grumbach wrote: 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 egru...@gmail.com On Tue, Feb 14, 2012 at 16:07, Mark Waite mark...@yahoo.com 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 egru...@gmail.com To: jenkins...@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
Jenkins does not understand netbeans j2se-project namespace
Hi all,
I'm creating a build job using the Ant task below;
project xmlns:j2seproject1=http://www.netbeans.org/ns/j2se-project/1;
xmlns:j2seproject3=http://www.netbeans.org/ns/j2se-project/3; name=pcdn-core
default=default basedir=.
descriptionBuilds, tests, and runs the project pcdn-core./description
fail message=Please build using Ant 1.8.0 or higher.
condition
not
antversion atleast=1.8.0/
/not
/condition
/fail
target depends=test,jar,javadoc description=Build and test whole
project. name=default/
target depends=init name=-pre-pre-jar
dirname file=${dist.jar} property=dist.jar.dir/
mkdir dir=${dist.jar.dir}/
/target
target name=-pre-jar
!-- Empty placeholder for easier customization. --
!-- You can override this target in the ../build.xml file. --
/target
target depends=init,compile,-pre-pre-jar,-pre-jar if=do.archive
name=-do-jar-without-manifest unless=manifest.available-mkdist.available
j2seproject1:jar/
/target
target depends=init,compile,-pre-pre-jar,-pre-jar
if=do.archive+manifest.available name=-do-jar-with-manifest
unless=manifest.available+main.class-mkdist.available
j2seproject1:jar manifest=${manifest.file}/
/target
target depends=init,compile,-pre-pre-jar,-pre-jar
if=do.archive+manifest.available+main.class name=-do-jar-with-mainclass
unless=manifest.available+main.class+mkdist.available
j2seproject1:jar manifest=${manifest.file}
j2seproject1:manifest
j2seproject1:attribute name=Main-Class
value=${main.class}/
/j2seproject1:manifest
/j2seproject1:jar
echo level=infoTo run this application from the command line
without Ant, try:/echo
property location=${build.classes.dir}
name=build.classes.dir.resolved/
property location=${dist.jar} name=dist.jar.resolved/
pathconvert property=run.classpath.with.dist.jar
path path=${run.classpath}/
map from=${build.classes.dir.resolved}
to=${dist.jar.resolved}/
/pathconvert
echo level=infojava -cp ${run.classpath.with.dist.jar}
${main.class}/echo
/target
target depends=init if=do.archive
name=-do-jar-with-libraries-create-manifest unless=manifest.available
tempfile deleteonexit=true destdir=${build.dir}
property=tmp.manifest.file/
touch file=${tmp.manifest.file} verbose=false/
/target
target depends=init if=do.archive+manifest.available
name=-do-jar-with-libraries-copy-manifest
tempfile deleteonexit=true destdir=${build.dir}
property=tmp.manifest.file/
copy file=${manifest.file} tofile=${tmp.manifest.file}/
/target
target
depends=init,-do-jar-with-libraries-create-manifest,-do-jar-with-libraries-copy-manifest
if=do.archive+main.class.available name=-do-jar-with-libraries-set-main
manifest file=${tmp.manifest.file} mode=update
attribute name=Main-Class value=${main.class}/
/manifest
/target
target
depends=init,compile,-pre-pre-jar,-pre-jar,-do-jar-with-libraries-create-manifest,-do-jar-with-libraries-copy-manifest,-do-jar-with-libraries-set-main
if=do.mkdist name=-do-jar-with-libraries-pack
j2seproject3:copylibs manifest=${tmp.manifest.file}/
echo level=infoTo run this application from the command line
without Ant, try:/echo
property location=${dist.jar} name=dist.jar.resolved/
echo level=infojava -jar ${dist.jar.resolved}/echo
/target
target depends=-do-jar-with-libraries-pack if=do.archive
name=-do-jar-with-libraries-delete-manifest
delete
fileset file=${tmp.manifest.file}/
/delete
/target
target
depends=init,compile,-pre-pre-jar,-pre-jar,-do-jar-with-libraries-create-manifest,-do-jar-with-libraries-copy-manifest,-do-jar-with-libraries-set-main,-do-jar-with-libraries-pack,-do-jar-with-libraries-delete-manifest
name=-do-jar-with-libraries/
target name=-post-jar
!-- Empty placeholder for easier customization. --
!-- You can override this target in the ../build.xml file. --
/target
target
depends=init,compile,-pre-jar,-do-jar-with-manifest,-do-jar-without-manifest,-do-jar-with-mainclass,-do-jar-with-libraries,-post-jar
description=Build JAR. name=jar/
However, I'm surprised that Jenkins cannot parse j2se-project namespace from
Netbeans.
/var/lib/jenkins/jobs/pcdnmgt core build/workspace/build.xml:257: Problem:
failed to create task or type http://www.netbeans.org/ns/j2se-project/1:jar
Any ideas on this will be greatly appreciated.
Thanks
Re: Jenkins does not understand netbeans j2se-project namespace
Did you put the netbeans ant jars in your jenkins ant lib folder ?
I'm pretty sure those tasks/namespaces are not published by ant but are
extensions developped by netbeans.
Richard
On 2012-09-28, at 07:31, Kayode Odeyemi drey...@gmail.com wrote:
Hi all,
I'm creating a build job using the Ant task below;
project xmlns:j2seproject1=http://www.netbeans.org/ns/j2se-project/1;
xmlns:j2seproject3=http://www.netbeans.org/ns/j2se-project/3;
name=pcdn-core default=default basedir=.
descriptionBuilds, tests, and runs the project pcdn-core./description
fail message=Please build using Ant 1.8.0 or higher.
condition
not
antversion atleast=1.8.0/
/not
/condition
/fail
target depends=test,jar,javadoc description=Build and test whole
project. name=default/
target depends=init name=-pre-pre-jar
dirname file=${dist.jar} property=dist.jar.dir/
mkdir dir=${dist.jar.dir}/
/target
target name=-pre-jar
!-- Empty placeholder for easier customization. --
!-- You can override this target in the ../build.xml file. --
/target
target depends=init,compile,-pre-pre-jar,-pre-jar if=do.archive
name=-do-jar-without-manifest unless=manifest.available-mkdist.available
j2seproject1:jar/
/target
target depends=init,compile,-pre-pre-jar,-pre-jar
if=do.archive+manifest.available name=-do-jar-with-manifest
unless=manifest.available+main.class-mkdist.available
j2seproject1:jar manifest=${manifest.file}/
/target
target depends=init,compile,-pre-pre-jar,-pre-jar
if=do.archive+manifest.available+main.class name=-do-jar-with-mainclass
unless=manifest.available+main.class+mkdist.available
j2seproject1:jar manifest=${manifest.file}
j2seproject1:manifest
j2seproject1:attribute name=Main-Class
value=${main.class}/
/j2seproject1:manifest
/j2seproject1:jar
echo level=infoTo run this application from the command line
without Ant, try:/echo
property location=${build.classes.dir}
name=build.classes.dir.resolved/
property location=${dist.jar} name=dist.jar.resolved/
pathconvert property=run.classpath.with.dist.jar
path path=${run.classpath}/
map from=${build.classes.dir.resolved}
to=${dist.jar.resolved}/
/pathconvert
echo level=infojava -cp ${run.classpath.with.dist.jar}
${main.class}/echo
/target
target depends=init if=do.archive
name=-do-jar-with-libraries-create-manifest unless=manifest.available
tempfile deleteonexit=true destdir=${build.dir}
property=tmp.manifest.file/
touch file=${tmp.manifest.file} verbose=false/
/target
target depends=init if=do.archive+manifest.available
name=-do-jar-with-libraries-copy-manifest
tempfile deleteonexit=true destdir=${build.dir}
property=tmp.manifest.file/
copy file=${manifest.file} tofile=${tmp.manifest.file}/
/target
target
depends=init,-do-jar-with-libraries-create-manifest,-do-jar-with-libraries-copy-manifest
if=do.archive+main.class.available name=-do-jar-with-libraries-set-main
manifest file=${tmp.manifest.file} mode=update
attribute name=Main-Class value=${main.class}/
/manifest
/target
target
depends=init,compile,-pre-pre-jar,-pre-jar,-do-jar-with-libraries-create-manifest,-do-jar-with-libraries-copy-manifest,-do-jar-with-libraries-set-main
if=do.mkdist name=-do-jar-with-libraries-pack
j2seproject3:copylibs manifest=${tmp.manifest.file}/
echo level=infoTo run this application from the command line
without Ant, try:/echo
property location=${dist.jar} name=dist.jar.resolved/
echo level=infojava -jar ${dist.jar.resolved}/echo
/target
target depends=-do-jar-with-libraries-pack if=do.archive
name=-do-jar-with-libraries-delete-manifest
delete
fileset file=${tmp.manifest.file}/
/delete
/target
target
depends=init,compile,-pre-pre-jar,-pre-jar,-do-jar-with-libraries-create-manifest,-do-jar-with-libraries-copy-manifest,-do-jar-with-libraries-set-main,-do-jar-with-libraries-pack,-do-jar-with-libraries-delete-manifest
name=-do-jar-with-libraries/
target name=-post-jar
!-- Empty placeholder for easier customization. --
!-- You can override this target in the ../build.xml file. --
/target
target
depends=init,compile,-pre-jar,-do-jar-with-manifest,-do-jar-without-manifest,-do-jar-with-mainclass,-do-jar-with-libraries,-post-jar
description=Build JAR. name=jar/
However, I'm surprised that Jenkins cannot parse j2se-project namespace from
Netbeans.
/var/lib/jenkins/jobs/pcdnmgt core build/workspace/build.xml:257: Problem:
failed to create task or type http://www.netbeans.org/ns/j2se-project/1:jar
RE: Configuring multiple svn accounts in jenkins
I don't think that Jenkins can really do this, not without major surgery. This goes against the grain of not just Jenkins, but continuous integration and automated builds in general. Part of the idea of having Jenkins is to fully automate your build so that it doesn't matter _who_ built the job, it all comes out the same. I think it might be better if we knew why you needed this. Every build includes a record of how the build was triggered, and if it was triggered by hand (rather than by seeing a change in SVN or on another sort of schedule), it will tell you which Jenkins user triggered the build. In my own build system (with 60+ users), Jenkins checks the code out of the repository as its own user, which has read-only privileges on the repository. I can always find out who launched a build, but it's by asking Jenkins, not my source control. --Rob -Original Message- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kalpana Sent: Friday, September 28, 2012 7:28 AM To: jenkinsci-users@googlegroups.com Subject: Configuring multiple svn accounts in jenkins Hello, I have around 10-12 users using the svn repository (basically my team). I need to configure all their svn credentials in jenkins, such that whenever they try to run a job , jenkins must ask for their account details.Also this svn user/pwd should be synced with jenkins user accounts such that whenever they login with the svn account, the corresponding jenkins user account must be logged in.If the concerned user starts a job, then the job must appear as run from the particular user's login and not as anonymous or some common username. When I was browsing through forums certain sites pointed that only one svn credential can be configured. Please help me in this.. -- View this message in context: http://jenkins.361315.n4.nabble.com/Configuring-multiple-svn-accounts-in-jenkins-tp4641682.html Sent from the Jenkins users mailing list archive at Nabble.com. The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
RE: Moving Jenkins to a new server?
Are you upgrading versions at the same time? Is the new server on the same IP network? I'm just finishing a migration but I installed a newer version and then migrated corresponding build slaves and jobs while over time to ensure that they all still worked. As far as the configuration, yes, it is just a matter of copying the Jenkins directory - if I remember correctly. I ran into problems transitioning from a fairly old version of Jenkins to the latest LTS release because of the transition from the obsolete Setenv plug-in to the Envinject plug-in. The environment variables configured in setenv configuration were lost once I edited the job on the new system, so I had to re-configure those jobs to add the environment variables in the new format. Another issue I had was with firewall rules because the new Jenkins server was not in the same IP network. Was the old server upgraded from Hudson and are you installing Jenkins on the new server and then copying the data? You might want to check for path issues in the configuration file and change /var/lib/hudson to /var/lib/jenkins
Is LTS 1.466.2 releases?
Hi, my Jenkins tells me there is a 1.466.2 release, but there is no changelog on the Jenkins page for this release number. So is / was there an 1.466.2 release? Cheers Rainer
RE: Is LTS 1.466.2 releases?
From earlier thread ‘Re: RE: Jenkins 1.466.2 LTS Changelog’: Hi, I'm not sure how to fix changelog for already release version, but the only change was security bug fix, for details see [1] Vojta [1] https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2012-09-17 From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of RainerW Sent: 28 September 2012 13:33 To: jenkinsci-users@googlegroups.com Subject: Is LTS 1.466.2 releases? Hi, my Jenkins tells me there is a 1.466.2 release, but there is no changelog on the Jenkins page for this release number. So is / was there an 1.466.2 release? Cheers Rainer Click herehttps://www.mailcontrol.com/sr/TyoNbcfMEKnTndxI!oX7Um3TMWn3KSUY3n2OkiyQF4IJQ90gHHORLl!xeRjTdfaB449qNLIrjzq2eN6FcXjHgg== to report this email as spam.
Re: Is LTS 1.466.2 releases?
Thanks, guessed something like that. On Friday, September 28, 2012 2:37:17 PM UTC+2, David Aldrich wrote: From earlier thread ‘Re: RE: Jenkins 1.466.2 LTS Changelog’: Hi, I'm not sure how to fix changelog for already release version, but the only change was security bug fix, for details see [1] Vojta [1] https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2012-09-17 *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *RainerW *Sent:* 28 September 2012 13:33 *To:* jenkins...@googlegroups.com javascript: *Subject:* Is LTS 1.466.2 releases? Hi, my Jenkins tells me there is a 1.466.2 release, but there is no changelog on the Jenkins page for this release number. So is / was there an 1.466.2 release? Cheers Rainer Click herehttps://www.mailcontrol.com/sr/TyoNbcfMEKnTndxI!oX7Um3TMWn3KSUY3n2OkiyQF4IJQ90gHHORLl!xeRjTdfaB449qNLIrjzq2eN6FcXjHgg==to report this email as spam.
Re: Git plugin: push result of a merge
Hi Mark, thanks for the explanation. In my case the push -f will not because it is a controlled environment. However, I might I also use the git commands to resolve my problem. However, I'm trying do this using jenkins git-puglin. In the post build Merge Results (If pre-build merging is configured, push the result back to the origin), but On Friday, 28 September 2012 12:29:49 UTC+1, Mark Waite wrote: If you push with the -f or --force option, the entries on the master branch which are on your central repository after the release_job will be lost. I think you will be very frustrated that your Jenkins job pushed a change to the master branch which lost your most recent work. We avoid that problem by having the most recent build of job_master tag the SHA1 which it built. After job_master has tagged the SHA1 which it built, a script in job_master performs a git fetch, a git merge, and a git push. The job_release is configured to always build from that tag which job_master updates, rather than building from the latest on the branch. If job_release needs to push changes back to the central repository, you could have it do something similar by tagging the SHA1 which it built, then perform a git fetch, a git merge, and a git push. That means those jobs are sometimes pushing something to the central repository which they have not built, but at least they can push to the central repository without losing recent work on the central repository. We have this condition because the team wants the version number checked into source control and incremented automatically on every build of job_master. I would have preferred to have a person increment the version number at key milestones, but the team preferred the automation of version number increment in the build because the version number is used widely in the system to version Microsoft.NET assemblies. Mark Waite -- *From:* Juliano Picussa juliano...@gmail.com javascript: *To:* jenkins...@googlegroups.com javascript: *Cc:* egru...@gmail.com javascript: *Sent:* Thursday, September 27, 2012 4:29 PM *Subject:* Re: Git plugin: push result of a merge I've got a similar issue: - I have 2 jenkins jobs for two distinct git branches: master and release (1 job_master to 1 branch master / 1 job_release for branch release) - job_master has a post built configuration to push to the release branch. - job_release has a post built configuration to push to the master branch. Before push, in the release_job the version file is increased and committed to GIT. This is working fine. The problem is when I run the release_job but the release branch is behind of the master branch, the push to master does not work (non-ff). Unfortunately, I didn't find the push -f in the jenkins post built section. This way, or I have to push manually (using --force) or configure a post built shell script (to push --force). Have you found a way to use push -f or other solution for allow non-ff push, using git plugin (publisher)? Tks. On Tuesday, 14 February 2012 14:30:34 UTC, Emmanuel Grumbach wrote: 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 egru...@gmail.com On Tue, Feb 14, 2012 at 16:07, Mark Waite mark...@yahoo.com 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 egru...@gmail.com *To:* jenkins...@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
Re: Git plugin: push result of a merge
Thanks for the explanation... I could use the git commands to fix my problem, using the Post Steps - Execute Shell jenkins options. However, I'm trying solve my issue using the jenkins Post Build Actions, where it is possible to add the Git Publisher and then choose the branch to push/target remote name. Additionally, in the Git Pusblisher there is an option Merge Results (If pre-build merging is configured, push the result back to the origin) that is checked in my job_release. This way, I was expecting in the job_release post build, a merge of the release branch to my origin/master branch and then a push to the master. However, unfortunately, I can't see the merge... So, my job_release changes only the version file (increasing the version), just it. But, as I said, the push to the master is not allowed if the release branch is behind of the master branch... On Friday, 28 September 2012 12:29:49 UTC+1, Mark Waite wrote: If you push with the -f or --force option, the entries on the master branch which are on your central repository after the release_job will be lost. I think you will be very frustrated that your Jenkins job pushed a change to the master branch which lost your most recent work. We avoid that problem by having the most recent build of job_master tag the SHA1 which it built. After job_master has tagged the SHA1 which it built, a script in job_master performs a git fetch, a git merge, and a git push. The job_release is configured to always build from that tag which job_master updates, rather than building from the latest on the branch. If job_release needs to push changes back to the central repository, you could have it do something similar by tagging the SHA1 which it built, then perform a git fetch, a git merge, and a git push. That means those jobs are sometimes pushing something to the central repository which they have not built, but at least they can push to the central repository without losing recent work on the central repository. We have this condition because the team wants the version number checked into source control and incremented automatically on every build of job_master. I would have preferred to have a person increment the version number at key milestones, but the team preferred the automation of version number increment in the build because the version number is used widely in the system to version Microsoft.NET assemblies. Mark Waite -- *From:* Juliano Picussa juliano...@gmail.com javascript: *To:* jenkins...@googlegroups.com javascript: *Cc:* egru...@gmail.com javascript: *Sent:* Thursday, September 27, 2012 4:29 PM *Subject:* Re: Git plugin: push result of a merge I've got a similar issue: - I have 2 jenkins jobs for two distinct git branches: master and release (1 job_master to 1 branch master / 1 job_release for branch release) - job_master has a post built configuration to push to the release branch. - job_release has a post built configuration to push to the master branch. Before push, in the release_job the version file is increased and committed to GIT. This is working fine. The problem is when I run the release_job but the release branch is behind of the master branch, the push to master does not work (non-ff). Unfortunately, I didn't find the push -f in the jenkins post built section. This way, or I have to push manually (using --force) or configure a post built shell script (to push --force). Have you found a way to use push -f or other solution for allow non-ff push, using git plugin (publisher)? Tks. On Tuesday, 14 February 2012 14:30:34 UTC, Emmanuel Grumbach wrote: 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 egru...@gmail.com On Tue, Feb 14, 2012 at 16:07, Mark Waite mark...@yahoo.com 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 egru...@gmail.com *To:* jenkins...@googlegroups. com *Sent:* Monday, February 13, 2012 11:35 PM *Subject:*
Re: Git plugin: push result of a merge
I don't understand how you can create a controlled environment which won't lose commits. The reason git disallows non fast-forward merges by default is described in the git push man page. It includes the following text with the --force option: This can cause the remote repository to lose commits; use it with care. Can you describe how you have structured that controlled environment so that it does not lose commits when you force a non-fast forward commit onto the remote repository? I don't think there is a way for the Jenkins Git Publisher to perform a merge as part of the post build action. It can push the results of a pre-build merge, but can't perform a post-build merge as far as I can tell. You either need that (which will then place commits in the working copy which have not been evaluated as part of the just completed continuous integration job), or you accept that you'll lose commits with git push --force. Mark Waite From: Juliano Picussa juliano.picu...@gmail.com To: jenkinsci-users@googlegroups.com Cc: Mark Waite markwa...@yahoo.com Sent: Friday, September 28, 2012 8:06 AM Subject: Re: Git plugin: push result of a merge Hi Mark, thanks for the explanation. In my case the push -f will not because it is a controlled environment. However, I might I also use the git commands to resolve my problem. However, I'm trying do this using jenkins git-puglin. In the post build Merge Results (If pre-build merging is configured, push the result back to the origin), but On Friday, 28 September 2012 12:29:49 UTC+1, Mark Waite wrote: If you push with the -f or --force option, the entries on the master branch which are on your central repository after the release_job will be lost. I think you will be very frustrated that your Jenkins job pushed a change to the master branch which lost your most recent work. We avoid that problem by having the most recent build of job_master tag the SHA1 which it built. After job_master has tagged the SHA1 which it built, a script in job_master performs a git fetch, a git merge, and a git push. The job_release is configured to always build from that tag which job_master updates, rather than building from the latest on the branch. If job_release needs to push changes back to the central repository, you could have it do something similar by tagging the SHA1 which it built, then perform a git fetch, a git merge, and a git push. That means those jobs are sometimes pushing something to the central repository which they have not built, but at least they can push to the central repository without losing recent work on the central repository. We have this condition because the team wants the version number checked into source control and incremented automatically on every build of job_master. I would have preferred to have a person increment the version number at key milestones, but the team preferred the automation of version number increment in the build because the version number is used widely in the system to version Microsoft.NET assemblies. Mark Waite From: Juliano Picussa juliano...@gmail.com To: jenkins...@googlegroups. com Cc: egru...@gmail.com Sent: Thursday, September 27, 2012 4:29 PM Subject: Re: Git plugin: push result of a merge I've got a similar issue: - I have 2 jenkins jobs for two distinct git branches: master and release (1 job_master to 1 branch master / 1 job_release for branch release) - job_master has a post built configuration to push to the release branch. - job_release has a post built configuration to push to the master branch. Before push, in the release_job the version file is increased and committed to GIT. This is working fine. The problem is when I run the release_job but the release branch is behind of the master branch, the push to master does not work (non-ff). Unfortunately, I didn't find the push -f in the jenkins post built section. This way, or I have to push manually (using --force) or configure a post built shell script (to push --force). Have you found a way to use push -f or other solution for allow non-ff push, using git plugin (publisher)? Tks. On Tuesday, 14 February 2012 14:30:34 UTC, Emmanuel Grumbach wrote: 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 egru...@gmail.com On Tue, Feb 14, 2012 at 16:07, Mark Waite mark...@yahoo.com 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
How to display Firefox window when running GUI tests?
Hi All, I am new to jenkins. I am trying to run GUI tests which opens a Firefox window in Windows 7. Now it is running headless mode. I run this in master machine not in any slave. I just call the batch script to invoke the selenium webdriver testcases. It runs the cases in headless mode. I searched for it and found these two links via the xvnc plugin http://forgetfulprogrammer.wordpress.com/2011/09/21/netbeans-gui-tests-on-jenkins-windows/ http://wiki.hudson-ci.org/display/HUDSON/Tomcat However, running using war file to doesn't work. It still running the GUI tests headless mode. How do I make the Firefox window to run in head mode. I tried calling java myclass in the execute script option. That too didnt help. Any help is appreciated.
Re: Many jobs at the same slave
I just started a thread (Tests which require an initial reboot?) which has a potential use case for successive jobs on the same slave. I need to test driver builds which require an initial install and reboot, and then functional tests. One possible way to implement this would be to schedule consecutive jobs on the same slave - first an install reboot job, and then the functional test job. One key requirement, in my case, is that other jobs shouldn't be scheduled on the slave between those two. Any advice about this or other approaches would be appreciated. Thanks, -- Jonathan On Wednesday, June 20, 2012 5:01:59 PM UTC-5, sti wrote: Exactly. Copying artifacts to master for archiving and copying them out to the workspace where they are used seems to be the way Jenkins works, at least, currently. You need to install the Copy artifact plugin, or at least it will make your life easier. At work my build artifacts are around 300 MB and I haven't considered the time spent copying them to be a show stopper. I get an archived copy of the artifacts and I do not have worry about something overwriting the artifacts. If your artifacts really are so large they cannot be moved around, I believe you need to create a new plugin to make it safe to pass them from one job to another in one slave. -- Sami Les Mikesell lesmi...@gmail.com javascript: kirjoitti 19.6.2012 kello 23.48: On Tue, Jun 19, 2012 at 2:57 PM, Jeff preda...@gmail.com javascript: wrote: I have a potential use casebut I'm also new to Jenkins so this may be doable today in a way that I have yet to learn. In trying to resolve how to use Maven and Jenkins and create a continuous delivery (CD) pipeline where each step in the pipeline progresses the state such as: build-Unit Test-Deploy-dev-Integration Tests-Deploy-stage-Load Tests-DeployLive (or something like this), we could have the functionality to run each pipeline stage as part of the same source project and configured via various profiles/plugins in the Maven POM. However, it seems that allowing any random slave to execute the various steps in the pipeline would incur a lot of unneeded overhead by either requiring the project and artifacts be archived and/or copied to each slave at each point in the pipeline depending on who gets the job, or the same source would need to be checked out and built for whichever phase is being run. Seems like a lot of unneeded overhead. The overhead of a few file copies is pretty small in the context of builds and probably more than offset but letting you build components in parallel and especially if you can come up with a scheme to only build the changed component(s) and the final result. -- Les Mikesell lesmi...@gmail.com javascript:
using people redirector plugin
Hello. I have installed the people redirector plugin (plugin mgr confirms installation) but it does not seem to work. I have supplied an http link similar to the example and also tried simply checking the disable redirection box. when I click on the People link on the main dashboard it still goes to the internal people DB either way. Can anyone tell me how to make this work? thanks, John. background: We want to use this server to work with external companies and so do not want users to login and follow the dashboard people link and see other user accounts. Since I got no response re: disabling or securing the dashboard people link, I was hoping I could use this people redirector plugin to either disable or redirect some where else.
Re: Moving Jenkins to a new server?
On Sep 28, 2012, at 4:46 AM, Lars Nordin lnor...@internap.com wrote: Are you upgrading versions at the same time? Is the new server on the same IP network? I was not planning on upgrading versions at the same time. The old server is only two revisions behind current, and I didn't see anything in the change log that would make me feel inclined to try to change anything more than absolutely necessary during this move. The new machine is on a different subnet, but otherwise within the same Enterprise network address space. As far as the configuration, yes, it is just a matter of copying the Jenkins directory - if I remember correctly. That's what I was hoping, but I didn't find anything in the wiki regarding moving Jenkins to another machine, and so far things have not worked well in this instance. At this point, it looks like Jenkins is actually starting up, but then you get gibberish when you connect to http://localhost:8080/. Of course, all this is complicated by the fact that I'm running Jenkins on OS X, specifically version 10.7.3. So, there's also the Mac-specific parts that could potentially go wonky. I ran into problems transitioning from a fairly old version of Jenkins to the latest LTS release because of the transition from the obsolete Setenv plug-in to the Envinject plug-in. The environment variables configured in setenv configuration were lost once I edited the job on the new system, so I had to re-configure those jobs to add the environment variables in the new format. The old server is already on the new plugin for this case, so I don't think this should be an issue. Another issue I had was with firewall rules because the new Jenkins server was not in the same IP network. The network firewall rules shouldn't need to change in this case. The host firewall rules are non-specific enough that they shouldn't need to change, either. Was the old server upgraded from Hudson and are you installing Jenkins on the new server and then copying the data? You might want to check for path issues in the configuration file and change /var/lib/hudson to /var/lib/jenkins No, the old version isn't anywhere near that old. -- Brad Knowles b...@shub-internet.org LinkedIn Profile: http://tinyurl.com/y8kpxu
Re: Automatic diagram
Hi, since I am the maintainer and creater of the plugin, I would not say that it is not maintained anymore. I hopefully will find some time soon to restructure the code in a way to make it better extensible. I also was looking for a possibility to layout the graph without resorting to graphviz, but I was not able to find a solution in java or javascript. If you know a good library which provides a similar functionality as graphviz, then please tell me. Regards, Stefan On Wednesday, September 26, 2012 9:16:27 AM UTC-3, kikou wrote: Hello sorry for this late answer I didnt pay attention but indeed it is working Nevertheless i found pity that we need another graphical lib, i am sure that a plugin could be done with java tools only or html object, i really prefer a plugin which not needs external binaries. K. Le mercredi 5 septembre 2012 15:23:40 UTC+2, Mark Waite a écrit : We use that plugin very frequently and it works great for us. Why do you say what a pity that this plugin is not maintained? We've not found any cases where it had bugs or issues that blocked our work, and I don't recall any recent complaints from other users either. Can you describe further why you think it might need an update? Mark Waite *From:* kikou ingenieur...@gmail.com *To:* jenkins...@googlegroups.com *Sent:* Wednesday, September 5, 2012 5:20 AM *Subject:* Re: Automatic diagram Hi Gergo Thank you. The plugin you gave is exaclty what i am looking for. I maybe do a missunderstanding but it is the dependancy indeed i'd like to have in a graph showing the sequence of projects (not build number), in other words seeing upstream and downstream projects in one graph. what a pitty that this plugin is not maintained. Yes maybe i could update it but not now. Thank you a lot Gergo Rgds K. Le mercredi 5 septembre 2012 12:15:51 UTC+2, Gergo a écrit : Hi, You mention job sequence but if you mean build sequence - I don't think it's predictable/static as it depends on dynamic factors (e.g availability of slaves, build duration changes affect allocation). Not exactly sure about your requirements, but I'm using Dependency Graph View: http://wiki.hudson-ci.org/display/HUDSON/Dependency+Graph+View+Plugin , this seems to be how far you can get solely looking at the jobs. hth, Gergo On Wed, Sep 5, 2012 at 8:14 AM, kikou ingenieur...@gmail.com wrote: Hi all Is there any plugin which draw automatically a diagram showing the job sequence ? So that it is more easy to show to some people the i dont like the format of pipeline view and it is more to show the result of last builds than the sequence. Rgds K.
Re: Automatic diagram
Stefan, I actually already starter this on your plugin, here is the branch using http://jsplumb.org - https://github.com/imod/depgraph-view-plugin/tree/jsPlumb Unfortunately I did not finish it yet… the current implementation works so far, but has an issue if there are cyclic dependencies between jobs. If you like it, feel free or/and let me know :)... regards Domi On 28.09.2012, at 19:25, Stefan Wolf glowwo...@gmail.com wrote: Hi, since I am the maintainer and creater of the plugin, I would not say that it is not maintained anymore. I hopefully will find some time soon to restructure the code in a way to make it better extensible. I also was looking for a possibility to layout the graph without resorting to graphviz, but I was not able to find a solution in java or javascript. If you know a good library which provides a similar functionality as graphviz, then please tell me. Regards, Stefan On Wednesday, September 26, 2012 9:16:27 AM UTC-3, kikou wrote: Hello sorry for this late answer I didnt pay attention but indeed it is working Nevertheless i found pity that we need another graphical lib, i am sure that a plugin could be done with java tools only or html object, i really prefer a plugin which not needs external binaries. K. Le mercredi 5 septembre 2012 15:23:40 UTC+2, Mark Waite a écrit : We use that plugin very frequently and it works great for us. Why do you say what a pity that this plugin is not maintained? We've not found any cases where it had bugs or issues that blocked our work, and I don't recall any recent complaints from other users either. Can you describe further why you think it might need an update? Mark Waite From: kikou ingenieur...@gmail.com To: jenkins...@googlegroups.com Sent: Wednesday, September 5, 2012 5:20 AM Subject: Re: Automatic diagram Hi Gergo Thank you. The plugin you gave is exaclty what i am looking for. I maybe do a missunderstanding but it is the dependancy indeed i'd like to have in a graph showing the sequence of projects (not build number), in other words seeing upstream and downstream projects in one graph. what a pitty that this plugin is not maintained. Yes maybe i could update it but not now. Thank you a lot Gergo Rgds K. Le mercredi 5 septembre 2012 12:15:51 UTC+2, Gergo a écrit : Hi, You mention job sequence but if you mean build sequence - I don't think it's predictable/static as it depends on dynamic factors (e.g availability of slaves, build duration changes affect allocation). Not exactly sure about your requirements, but I'm using Dependency Graph View: http://wiki.hudson-ci.org/display/HUDSON/Dependency+Graph+View+Plugin , this seems to be how far you can get solely looking at the jobs. hth, Gergo On Wed, Sep 5, 2012 at 8:14 AM, kikou ingenieur...@gmail.com wrote: Hi all Is there any plugin which draw automatically a diagram showing the job sequence ? So that it is more easy to show to some people the i dont like the format of pipeline view and it is more to show the result of last builds than the sequence. Rgds K.
Re: Automatic diagram
2012/9/5 kikou ingenieur.high.t...@gmail.com: what a pitty that this plugin is not maintained. Yes maybe i could update it but not now. That's because you are looking at Hudson wiki, not Jenkins Wiki. See https://wiki.jenkins-ci.org/display/JENKINS/Dependency+Graph+View+Plugin and you see that the last release was yesterday! (because I've released it!) Thank you a lot Gergo Rgds K. Le mercredi 5 septembre 2012 12:15:51 UTC+2, Gergo a écrit : Hi, You mention job sequence but if you mean build sequence - I don't think it's predictable/static as it depends on dynamic factors (e.g availability of slaves, build duration changes affect allocation). Not exactly sure about your requirements, but I'm using Dependency Graph View: http://wiki.hudson-ci.org/display/HUDSON/Dependency+Graph+View+Plugin , this seems to be how far you can get solely looking at the jobs. hth, Gergo On Wed, Sep 5, 2012 at 8:14 AM, kikou ingenieur...@gmail.com wrote: Hi all Is there any plugin which draw automatically a diagram showing the job sequence ? So that it is more easy to show to some people the i dont like the format of pipeline view and it is more to show the result of last builds than the sequence. Rgds K. -- Kohsuke Kawaguchi
Re: using GIT plugin: cannot clone submodule
THis is exactly what I did to circumvent the problem, I will work without the GIT plugin until the SSH credentials are better integrated. On Tuesday, September 18, 2012 6:50:02 PM UTC+3, Emil Petkov wrote: Hello, I have set up Jenkins and installed the GIT plugin ( https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin). 1. First, I created a depot of my repository by executing: git clone --bare /home/git_repos/admin_pci.git /home/jenkins_bare_repos/admin_pci.git 2. Added the clone as the remote origin for the original so I can push to the clone: cd /home/git_repos/admin_pci.git git remote add origin /home/jenkins_bare_repos/admin_pci.git 3. Then created a job in Jenkins: selected GIT for Source Code Management, Repository URL = /home/jenkins_bare_repos/admin_pci.git, Branches to Build = 'master', etc 4. Ran the job and got the following error: Started by user anonymous http://10.100.25.14:8084/user/null Building in workspace /var/lib/jenkins/jobs/admin_pci specs/workspace Checkout:workspace / /var/lib/jenkins/jobs/admin_pci specs/workspace - hudson.remoting.LocalChannel@4eeaabad Using strategy: Default Last Built Revision: Revision 0654d4080e49815ce1869bea3260ecfa2334f5fd (origin/app_testing) Fetching changes from 1 remote Git repository Fetching upstream changes from /home/jenkins_bare_repos/admin_pci.git Commencing build of Revision fee7f8c3386e79bd27459fb76b0085d679ec5012 (origin/master) Checking out Revision fee7f8c3386e79bd27459fb76b0085d679ec5012 (origin/master) FATAL: Command git submodule update returned status code 1: stdout: Cloning into vendor/plugins/secure_gate... stderr: Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,password). fatal: The remote end hung up unexpectedly Clone of 'ssh://git_deployer@10.100.25.14/home/git_repo/gw_plugin.git' into submodule path 'vendor/plugins/secure_gate' failed hudson.plugins.git.GitException http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException: Command git submodule update returned status code 1: stdout: Cloning into vendor/plugins/secure_gate... stderr: Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,password). fatal: The remote end hung up unexpectedly Clone of 'ssh://git_deployer@10.100.25.14/home/git_repo/gw_plugin.git' into submodule path 'vendor/plugins/secure_gate' failed at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:855) at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:817) at hudson.plugins.git.GitAPI.submoduleUpdate(GitAPI.java:446) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1308) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1269) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1269) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) It seems that the submodule of the project cannot be cloned correctly. Is this a well known issue with GIT submodules? Any ideas how to resolve it? Thanks in advance.
Re: Tests which require an initial reboot? (driver testing)
On possibility that we've used for similar situations: - Create a lock (Lock and Latches or Throttle plugins) for each slave that you're going to test on. - Set the slave up to accept only targeted jobs - that way other jobs won't wander onto your slave. Also, the slave must be setup to automatically start the slave agent on reboot, you cannot have the Jenkins start the slave. - Create a master job. This job will obtain the lock for the slave that will be reboot. - The master jobs spawns - and WAITS - for a pre-reboot job via the Trigger Parameterized Job build step on the node using a Node parameter. - The pre-reboot job runs on the slave, does it's stuff, then initiates a reboot of itself. The job terminates. - The master returns from the wait, then initiates another wait while waiting for the slave to get far enough into the shutdown that the slave agent isn't running. - The master job spanws - and WAITS - for a post-boot job, just like the pre-reboot job. Jenkins will queue the job up until the slave takes it. - Post-boot job runs and does it's stuff. - The master returns from the wait and does anything it needs to. This general approach should work. Jason On Friday, September 28, 2012 8:43:47 AM UTC-7, Jonathan Rice wrote: I'm doing a project which involves building and testing drivers on OS X. Testing would happen on dedicated slave machines, but the snag is that after installing the drivers, the machine must be rebooted before functional testing is started. I can think of two general ways to approach this in Jenkins - I'd be grateful for any advice as to which (or other approaches) might be workable: 1. Design a single Jenkins build job that includes an initial driver install and reboot, and then runs its functional tests after the reboot. I can certainly arrange for daemon code to be run after a reboot on OS X, but I suspect there's no way to make the post-reboot work appear to the master as part of the same job. I presume the master will always think the job ended at the reboot. 2. Make the install reboot be a first build job, and then arrange for the functional tests to be the next build job on that same slave. I suppose this might be done in some way with node labels - a single node per slave, labeled with the machine name, or other distinguishing id. But for this to work, the initial install/reboot job would have to block all other jobs from that slave until the functional test job had been scheduled and completed. Does Jenkins have any way to schedule successive jobs to the same slave like this? If anyone has any advice on these or other methods, please let me know. Thanks! -- Jonathan
How make WebSVN rev, file, diff URLs work with Jenkins WebSVN or WebSVN2 plug-in?
I am using WebSVN 2.3.3. Any advice getting this to integrate with Jenkins is much appreciated: * * *Built-in Jenkins WebSVN Support* * * Built-in WebSVN partially works. I configured Jenkins Job WebSVN URL as: *http://fesnaval.fescorp.com/websvn/wsvn/NTI_Battery_Exerciser/trunk/* The built-in WebSvn works for the revision URL: http://fesnaval.fescorp.com/websvn/wsvn/NTI_Battery_Exerciser/trunk/?rev=305sc=1 But not for a file URL (note double /trunk/trunk/ in URL and missing rev=305 ); http://fesnaval.fescorp.com/websvn/wsvn/NTI_Battery_Exerciser*/trunk/trunk/* Battery_Exerciser_Client/src/mainwindow.cpp and not for a file diff URL: http://fesnaval.fescorp.com/websvn/wsvn/NTI_Battery_Exerciser/trunk/trunk/Battery_Exerciser_Client/src/mainwindow.cpp?op=diffrev=305 *WebSVN2 * * * I can not get anything working with WebSVN2. I configured the Jenkins job's WebSVN2 URL s: http://fesnaval.fescorp.com/websvn/wsvn/listing.php?repname=diagnostics-snmppath=/trunk/. The revision URL WebSVN2 generates is something like: http://fesnaval.fescorp.com/websvn/revision.php?repname=diagnostics-snmprev=1261 It expected the URL to be: http://fesnaval.fescorp.com/websvn/wsvn/diagnostics-snmp/trunk/?rev=1261 I love WebSvn. Has anyone got this working? Can you share the syntax of your Jenkins job;s WebSVN2 URL? Thanks in advance, -Ed Jenkins 1.478 Winstone server on RHEL 5.2 WebSvn 2.3.3 on Apache RHEL 5.2 http://fesnaval.fescorp.com/websvn/wsvn/diagnostics-snmp/trunk/?rev=1261
Hudson to Jenkins migration
Hi, I have an old Ubuntu server running Hudson. I'd like to migrate it to a new hardware running Jenkins on Ubuntu. I have copied /var/lib/hudson/* to the new server, and renamed it to /var/lib/jenkins, but it does not see the jobs created in the old server. I tried changing JENKINS_HOME from /var/lib/jenkins to /var/lib/husdon, but it did not work either. How do I migrate jobs from old server to new server??? Best Regards, Fory Horio
RE: Hudson to Jenkins migration
First, what version of Hudson are you trying to migrate from? The formats for the XML files diverged after a certain point l, which makes it very difficult to migrate. Are you using the deb packaging? Sent from my Windows Phone -- From: Fory Horio Sent: 9/28/2012 5:24 PM To: jenkinsci-users@googlegroups.com Subject: Hudson to Jenkins migration Hi, I have an old Ubuntu server running Hudson. I'd like to migrate it to a new hardware running Jenkins on Ubuntu. I have copied /var/lib/hudson/* to the new server, and renamed it to /var/lib/jenkins, but it does not see the jobs created in the old server. I tried changing JENKINS_HOME from /var/lib/jenkins to /var/lib/husdon, but it did not work either. How do I migrate jobs from old server to new server??? Best Regards, Fory Horio
Re: Hudson to Jenkins migration
We are running Hudson 2.2.1 on Ubuntu 10.10. I just grabbed the latest Jenkins 1.483 installed on Ubuntu 12.04. Yes, I am using deb package. deb http://hudson-ci.org/debian and http://pkg.jenkins-ci.org/debian/ On Friday, September 28, 2012 3:34:02 PM UTC-7, slide wrote: First, what version of Hudson are you trying to migrate from? The formats for the XML files diverged after a certain point l, which makes it very difficult to migrate. Are you using the deb packaging? Sent from my Windows Phone -- From: Fory Horio Sent: 9/28/2012 5:24 PM To: jenkins...@googlegroups.com javascript: Subject: Hudson to Jenkins migration Hi, I have an old Ubuntu server running Hudson. I'd like to migrate it to a new hardware running Jenkins on Ubuntu. I have copied /var/lib/hudson/* to the new server, and renamed it to /var/lib/jenkins, but it does not see the jobs created in the old server. I tried changing JENKINS_HOME from /var/lib/jenkins to /var/lib/husdon, but it did not work either. How do I migrate jobs from old server to new server??? Best Regards, Fory Horio
Re: Hudson to Jenkins migration
Yeah, that version of Hudson has a very different format for storing a lot of the config information in the xml files. Upgrading from Hudson 1.39 is very easy, but the further away from that version you get, the less success you are likely to have. slide On Fri, Sep 28, 2012 at 3:40 PM, Fory Horio f...@trihard.net wrote: We are running Hudson 2.2.1 on Ubuntu 10.10. I just grabbed the latest Jenkins 1.483 installed on Ubuntu 12.04. Yes, I am using deb package. deb http://hudson-ci.org/debian and http://pkg.jenkins-ci.org/debian/ On Friday, September 28, 2012 3:34:02 PM UTC-7, slide wrote: First, what version of Hudson are you trying to migrate from? The formats for the XML files diverged after a certain point l, which makes it very difficult to migrate. Are you using the deb packaging? Sent from my Windows Phone -- From: Fory Horio Sent: 9/28/2012 5:24 PM To: jenkins...@googlegroups.**com Subject: Hudson to Jenkins migration Hi, I have an old Ubuntu server running Hudson. I'd like to migrate it to a new hardware running Jenkins on Ubuntu. I have copied /var/lib/hudson/* to the new server, and renamed it to /var/lib/jenkins, but it does not see the jobs created in the old server. I tried changing JENKINS_HOME from /var/lib/jenkins to /var/lib/husdon, but it did not work either. How do I migrate jobs from old server to new server??? Best Regards, Fory Horio -- Website: http://earl-of-code.com
Re: Hudson to Jenkins migration
So, that's the best option here? Stay with Hudson? How much farther down the road do we have a support (updates) for Hudson? On Fri, Sep 28, 2012 at 3:53 PM, Slide slide.o@gmail.com wrote: Yeah, that version of Hudson has a very different format for storing a lot of the config information in the xml files. Upgrading from Hudson 1.39 is very easy, but the further away from that version you get, the less success you are likely to have. slide On Fri, Sep 28, 2012 at 3:40 PM, Fory Horio f...@trihard.net wrote: We are running Hudson 2.2.1 on Ubuntu 10.10. I just grabbed the latest Jenkins 1.483 installed on Ubuntu 12.04. Yes, I am using deb package. deb http://hudson-ci.org/debian and http://pkg.jenkins-ci.org/debian/ On Friday, September 28, 2012 3:34:02 PM UTC-7, slide wrote: First, what version of Hudson are you trying to migrate from? The formats for the XML files diverged after a certain point l, which makes it very difficult to migrate. Are you using the deb packaging? Sent from my Windows Phone From: Fory Horio Sent: 9/28/2012 5:24 PM To: jenkins...@googlegroups.com Subject: Hudson to Jenkins migration Hi, I have an old Ubuntu server running Hudson. I'd like to migrate it to a new hardware running Jenkins on Ubuntu. I have copied /var/lib/hudson/* to the new server, and renamed it to /var/lib/jenkins, but it does not see the jobs created in the old server. I tried changing JENKINS_HOME from /var/lib/jenkins to /var/lib/husdon, but it did not work either. How do I migrate jobs from old server to new server??? Best Regards, Fory Horio -- Website: http://earl-of-code.com
Re: Hudson to Jenkins migration
If you have a lot of jobs to convert, it may be better to stay with Hudson. In terms of how long Hudson will be around, you'd have to ask on the Hudson mailing lists. slide On Fri, Sep 28, 2012 at 3:58 PM, Fory Horio f...@trihard.net wrote: So, that's the best option here? Stay with Hudson? How much farther down the road do we have a support (updates) for Hudson? On Fri, Sep 28, 2012 at 3:53 PM, Slide slide.o@gmail.com wrote: Yeah, that version of Hudson has a very different format for storing a lot of the config information in the xml files. Upgrading from Hudson 1.39 is very easy, but the further away from that version you get, the less success you are likely to have. slide On Fri, Sep 28, 2012 at 3:40 PM, Fory Horio f...@trihard.net wrote: We are running Hudson 2.2.1 on Ubuntu 10.10. I just grabbed the latest Jenkins 1.483 installed on Ubuntu 12.04. Yes, I am using deb package. deb http://hudson-ci.org/debian and http://pkg.jenkins-ci.org/debian/ On Friday, September 28, 2012 3:34:02 PM UTC-7, slide wrote: First, what version of Hudson are you trying to migrate from? The formats for the XML files diverged after a certain point l, which makes it very difficult to migrate. Are you using the deb packaging? Sent from my Windows Phone From: Fory Horio Sent: 9/28/2012 5:24 PM To: jenkins...@googlegroups.com Subject: Hudson to Jenkins migration Hi, I have an old Ubuntu server running Hudson. I'd like to migrate it to a new hardware running Jenkins on Ubuntu. I have copied /var/lib/hudson/* to the new server, and renamed it to /var/lib/jenkins, but it does not see the jobs created in the old server. I tried changing JENKINS_HOME from /var/lib/jenkins to /var/lib/husdon, but it did not work either. How do I migrate jobs from old server to new server??? Best Regards, Fory Horio -- Website: http://earl-of-code.com -- Website: http://earl-of-code.com
Re: Perforce Plugin and PATH
Sounds like this might potentially be a bug. Can you file a ticket? If you can't set the PATH on the systems correctly before starting the slave agents, then you may need to define your P4 installation in jenkins instead. On Wednesday, 26 September 2012 23:22:07 UTC-6, Erling Andersen wrote: Hi We have had problem with the Perforce plugin on Windows. The issue is related to which PATH is used when the the p4 command is run. We thought that PATH would have the value defined on the node in Jenkins and NOT the PATH value defined on the machine and know by Java. We define PATH on each node inside Jenkins on the configure page on the nodes. Is it not possible to define PATH on each node? And should not that valued by used by running p4? Erling
Re: Jenkins does not understand netbeans j2se-project namespace
On Fri, Sep 28, 2012 at 12:38 PM, Richard Lavoie lavoie.rich...@gmail.comwrote: Did you put the netbeans ant jars in your jenkins ant lib folder ? I'm pretty sure those tasks/namespaces are not published by ant but are extensions developped by netbeans. Thanks for the pointer Richard. This blog post was helpful: http://www.rekk.de/bloggy/2008/adaptation-of-netbeans-ant-build-for-integration-copylibs-issue/
