Re: keep this build forever via rest api?
Hi Bruno, On 02/02/2013 14:43, Bruno Cunha wrote: The /toggleLogKeep URL in the job can do that. For example: http://[url]/job/[JOB-NAME]/20/toggleLogKeep This URL will change the lock status of the build 20. Thanks for this, it's almost what I want. The problem with the above is that I need to check what state the build is in before calling toggle. Is there any way, through the REST api, that I can *ensure* the build is kept forever? cheers, Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk -- 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.
Plugin email-ext: use of tokens in Groovy script
Hello,
I am migrating my email-ext mail template to a Groovy script. My current
email configuration uses a lot of tokens (${BUILD_LOG_EXCERPT},
${CHANGES_SINCE_LAST_SUCCESS}, ${BUILD_LOG_REGEX}, ${WARNINGS_RESULT},
${TASKS_RESULT}, ...). I do not want to implement the same functionality
in Groovy which is already available in the Java code of the email-ext
plugin. Is there any way to reuse the existing implementation? Has
anyone done this (and can provide some examples)?
Regards
Bernhard
--
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: Installing operating systems on slaves via Jenkins
Thanks everyone for the inputs. The test process is not flawed, we actually need capabilities in the automation framework to execute tests on a clean slate (fresh OS). We also need capabilities in the framework to run the same tests without re-installing the OS as well i.e., execute the tests on the currently installed OS. I do have an idea to get this stuff done, will post it once I have something concrete in hand. Regards, Manish On Wednesday, 30 January 2013 12:36:18 UTC+5:30, Manish Singh wrote: Hello All, I have a requirement, where I need to reinstall OS on slave machines before a job is executed. This is needed as we need a clean OS before executing the tests. The test process is not flawed, it is needed such that we test our software on a clean machine. One approach I could think of was to have pre-created images of various machines have available. What are the best ways to do this via Jenkins? -Manish -- 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.
Promotions Plugin: Uploading wrong releases
Hi folks, I have loads of weird stuff going on since I chose to re-key the secret keys due to a security flaw :( Biggest flaw was obviously the re-keying... Since then do our promotions upload wrong releases. I don't know if it is related to the re-keying but it happened after that action. The jobs do either copy artifacts from latest succesful jobs or upstream jobs that triggered the promotion job. Checking the workspace shows that the correct artifacts are copied but uploaded are artifacts from previous build jobs. As far as I can tell are artifacts uploaded from the job that ran directly before the wanted one. I have already checked if there are doubled workspaces for a job like workspace@2. None found. The build log refer to the correct upstream jobs so the copy artifact plugin seems to work as expected. The Promotions plugin is failing. The troubles started with failing file patterns. The pormotions couldn't find the files located in the workspace. Even patterns with a hardcoded file name didn't find anything. I fixed that by changing values to something different, saving and then changing back. The file patterns worked fine from that point on but I don't get it where the old artifacts come from. Especially as the build tells crisp and clear where it picks them from and the correct files are located in the workspace. Workspaces are always deleted before a build starts. Has someone an idea, what is going on? Cheers Jan -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: How to lauch tomcat6 into /etc/init.d
A few questions: 1: Is this Tomcat instance the one you're running Jenkins on? I'm guessing not; if you are, then you're trying to press your own 'off' button. 2: Does the Tomcat instance run on a port beneath 1024? If so, I believe that the instance has to run as root, or hide behind something that is running as root. 3: If you're not running on a low port, does the Tomcat instance need to be running as root? In fact, is it, or is the init.d job sudoing to a non-root user before launching the app. 4: Do you need to start the server from Jenkins, stop it from Jenkins, or both? 5: Do you have read/write access to the init.d launcher? If so, I'd suggest writing your own launcher with all the arguments you need and having the init.d launcher just sudo to a non-root user and run your launcher. That way, you'd be able to run that launcher from Jenkins directly without messing with init.d. There are two basic problems here. One is that you are considering running Jenkins as root. If you can run _anything_ from Jenkins as root, then you can run _everything_ from Jenkins as root. If you really need Jenkins to run a particular thing as root, you may want to look at setuid scripts, which would be a smaller security hole (but it's still probably a security hole). The other is that you want to control start/stop from Jenkins, and the fact that there's an init.d script means that you also want to control it from init. It's probably better to let one or the other control the server, but I can see situations where you would require both. -Original Message- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Sami Tikka Sent: Saturday, February 02, 2013 6:45 PM To: jenkinsci-users@googlegroups.com Subject: Re: How to lauch tomcat6 into /etc/init.d It is not a good idea to run Jenkins as root. Unless you know what you are doing. And even then it is not a good idea. And if you do not know how to do it, you definitely should not be doing it. Maybe instead you could explain what you are trying to do and why do you think you need Jenkins to have root privileges? I'm sure there are better ways to do what you need to do without running Jenkins as root. -- Sami adrien ruffie adriennolar...@hotmail.fr kirjoitti 29.1.2013 kello 18.40: Hello all I have a problem, My tomcat is launch on the server with /etc/init.d/tomcat6 start/stop And only with following script because several properties were set into This script. But Jenkins doesn't have a a root privileges to run this script, how I can do that With a job plz ? -- 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. -- 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. 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. -- 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.
Strict order if there are dependencies among the jobs
Hi everyone! My problem is the following. There are A and B jobs. B depends on A. I trigger A and when A is done, it will trigger B. That's okay. But if I trigger A and I trigger A again with different parameter, when the first A is done, the second A will be building and not the B, which is triggered by the first A. So I would like when the first A is done, the B will be the next in the queue, and after the second A, and the last will be the second B. Is there any option to solved this? I tried to set job priority but it did not works. Thank you! Adam -- 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: jenkins clustering
If you’re willing to pony up some money, you should talk to Cloudbees regarding their Enterprise version (http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-overview.cb). I haven’t tried it (yet), but it comes with several plugins you can’t get otherwise, and one of them is a High Availability plugin. This specifically allows you to fail over to a second Jenkins master on the fly if the master dies. --Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Matteo Sent: Tuesday, January 22, 2013 2:24 PM To: jenkinsci-users@googlegroups.com Subject: jenkins clustering Hello, first i'd like to thank developers for this great project. I'm sorry if already asked but i'm new on this list and searching the web has produced no results. We have a jenkins installation with 1 master and 5 slaves connected through ssh. We are mostly a java shop and jenkins is central to our infrastructure since we build and deploy releases to servers from it. For this reason slave resiliency in the face of master failure is paramount to us. My question: Is there a way, in a master/slave configuration, to have slave builds running to completion even in case of master failure (ideally refetching console logs once the master is back up :))? In our current setup, we get a proxy error on master UI and builds are aborted. Thanks in advance for any hint, -m 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. -- 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: I did not spawn a child process to build my project, why am I getting this: Process leaked file descriptors. See wiki.jenkins-ci.org/display/JENKINS/. for more information ERROR: Failed to clean t
Hi Sami, Thank you for your reply. I have figured it out that for the latest Git version, I need to use Git Installation\cmd\git.exe. I used Git Installation\cmd\gitk.cmd, this will cause a file handler being referenced by Git, hence, a Git thinks the file handler is a spawned child process. I need to update my post. Regards, Hong Lily Ju SoftWare Engineer CARE, IT 781-375-3034 (o) 781-801-9313 (c) hong...@steward.org Steward Heath Care -Original Message- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Sami Tikka Sent: Sunday, February 03, 2013 6:05 PM To: jenkinsci-users@googlegroups.com Subject: Re: I did not spawn a child process to build my project, why am I getting this: Process leaked file descriptors. See wiki.jenkins-ci.org/display/JENKINS/... for more information ERROR: Failed to clean the workspace Well, everything is more difficult on Windows. I do not use Windows but I work in an organization where people have to do battle with the same issues you are fighting with. I think your issues might be caused by the git command not being a .exe but a .bat. -- Sami hong...@steward.org kirjoitti 21.1.2013 kello 22.29: have never configured a system as hard as this combination, Jenkins (1.499), Git (1.8.0.msysgit.0), and Windows 7 32 bit. I have been stumped for three days, did not make any progress. I have been googling crazily and all the answers found here and there seemed to help me a little, ex: no space for Git home. In Jenkins, for Git installation it is C:\Git\cmd\gitk.cmd, notice, there is no space in the path (I reinstalled Git from Program Files\Git to C:\Git to get rid of the space issue). My repository is a private one, so I need to use an SSH protocol. I am able to do this git command in a command line using my Windows account: git clone g...@github.com:mygitproject.git. I have C:/Users/myaccount/.ssh/known_hosts, id_rsa, and id_rsa.pub. Since my Jenksin is a Windows service, it runs under Local System Account, but the known_hosts was generated when I logged in Windows using my Windows account, so I thought I needed to change the Jenkins running user to my Windows account and I did it. However nothing seems working. When I try to build a job from a remote private Github repository, I get this exception: Started by user anonymous Building in workspace C:\Jenkins\workspace\Test Checkout:Test / C:\Jenkins\workspace\Test - hudson.remoting.LocalChannel@6846c Using strategy: Default Cloning the remote Git repository Cloning repository g...@github.com:stewardconnect/CARE.git git --version Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information ERROR: Failed to clean the workspace java.io.IOException: Unable to delete C:\Jenkins\workspace\Test at hudson.Util.deleteFile(Util.java:243) at hudson.Util.deleteRecursive(Util.java:293) at hudson.FilePath$11.invoke(FilePath.java:983) at hudson.FilePath$11.invoke(FilePath.java:981) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:825) at hudson.FilePath.deleteRecursive(FilePath.java:981) at hudson.plugins.git.GitAPI.clone(GitAPI.java:241) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1044) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:825) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:986) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1142) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(Abstra ctBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java :587) at hudson.model.Run.execute(Run.java:1543) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) ERROR: Error cloning remote repo 'origin' : Failed to delete workspace hudson.plugins.git.GitException: Failed to delete workspace at hudson.plugins.git.GitAPI.clone(GitAPI.java:244) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1044) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:986) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:825) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:986) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1142) at hudson.model.AbstractProject.checkout(AbstractProject.java:1325) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(Abstra ctBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java :587) at hudson.model.Run.execute(Run.java:1543)
Getting all Job Information from different Server
Hi, i have a quick question. We are running different Jenkins Server for different departments and jobs and i wanted to know, if there is any way to collect all Job information from all Servers ? It would be only necessary to get the different jobs and the status , not the workspace files. (Just to have an overview about the actual situation) Is there already a existing plugin for this idea ? Otherwise, i would create my own Plugin for this problem -- 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: Plugin email-ext: use of tokens in Groovy script
You should be able to import the content classes, instantiate an instance
of them and call the getContent method.
def BUILD_ID = new BuildIdContent()
def args = [ Arg1 : Foo, Arg2, Foo ]
// currently the publisher is not accessible by the groovy templates, so
some tokens may not work this way (passing null)
// EmailType is not used in any of the content plugins as far as I can
tell, so passing null shouldn't cause an issue here
% BUILD_ID.getContent(build, null, null, args) %
I'll see if I can make the publisher available in the next version of
email-ext.
On Mon, Feb 4, 2013 at 1:58 AM, Bernhard Berbuir bernhard.berb...@web.dewrote:
Hello,
I am migrating my email-ext mail template to a Groovy script. My current
email configuration uses a lot of tokens (${BUILD_LOG_EXCERPT},
${CHANGES_SINCE_LAST_SUCCESS}, ${BUILD_LOG_REGEX}, ${WARNINGS_RESULT},
${TASKS_RESULT}, ...). I do not want to implement the same functionality in
Groovy which is already available in the Java code of the email-ext plugin.
Is there any way to reuse the existing implementation? Has anyone done this
(and can provide some examples)?
Regards
Bernhard
--
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+unsubscribe@**googlegroups.comjenkinsci-users%2bunsubscr...@googlegroups.com
.
For more options, visit
https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.
--
Website: http://earl-of-code.com
--
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.
Antwort: Getting all Job Information from different Server
Hi Clemens, to my knowledge there's no such plugin. But you can use the API to easily pull that information. So if you just need some sort of overview I believe a simple script scraping the data from the instances instead of a plugin will do the trick. To see information available via API browse to http://YOURJENKINSINSTANCE/api/xml There you'll see all jobs coming like that job nameJOBName/name urlhttp://YOURJENKINSINSTANCE/job/JOBName/url colorCOLOR/color /job where COLOR is the interesting stuff for you: it's encoding the build state like blue for all fine!, red for failed, aborted for (well, yeah) aborted and so on. HTH. Kind regards, Andreas Schilling CAE Processes Data Management --- Dipl. Inf. Andreas Schilling Senior Software Architect TWT GmbH Science Innovation Bernhäuser Str. 40 - 42 73765 Neuhausen Tel: +49.7158.17 15.6 73 Mobil: +49.1 72.6 22 88 70 E-Mail: andreas.schill...@twt-gmbh.de www.twt-gmbh.de Geschäftsführung: Dimitrios Vartziotis, Joachim Laicher (Stv.), Frank Beutenmüller (Stv.) Registergericht: Amtsgericht Stuttgart, HRB Nr. 212778 Umsatzsteuer: ID-Nr.: DE147841145 Von:Clemens clemensgoer...@googlemail.com An: jenkinsci-users@googlegroups.com Datum: 04.02.2013 14:31 Betreff:Getting all Job Information from different Server Gesendet von: jenkinsci-users@googlegroups.com Hi, i have a quick question. We are running different Jenkins Server for different departments and jobs and i wanted to know, if there is any way to collect all Job information from all Servers ? It would be only necessary to get the different jobs and the status , not the workspace files. (Just to have an overview about the actual situation) Is there already a existing plugin for this idea ? Otherwise, i would create my own Plugin for this problem -- 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. -- 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: All my added build descriptions and keep build forever annotations gone!
Hello Sami, Jenkins has not been upgraded or downgraded recently. Jenkins has not been restarted recently. There is a lot of information in the log file. When looking for information specific to the affected job, all I see is the normal information, like SCM changes detected ...etc I did not have the config history plugin installed. We are running backups of the jenkins directory. Yes, Jenkins is configured to require login. Thanks for any ideas you may have. Steve K. On Saturday, February 2, 2013 5:51:41 PM UTC-5, sti wrote: Did you upgrade or downgrade Jenkins? Has it restarted? What is in the log file? Did you have job config history plugin installed? And if not, why? Is your Jenkins configured to require login allowing changes? -- Sami Steve K steve.k...@carestream.com javascript: kirjoitti 2.2.2013 kello 0.13: Has anyone else encountered this? I actually spent a fair amount of time adding my own build descriptions and, for a long time, they were visible in my project's build history. I also designated several of the builds as Keep Forever. Now, they are all gone. I know I didn't delete them and no one with the required privileges admits to removing them. There were LOTS of them, so it is unlikely that they were removed by mistake. Could this be a bug or do I have a determined and diabolical saboteur in the ranks? I'm running Jenkins version 1.480.1 I'd appreciate any clues you may be able to provide. Thank you. -- 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 javascript:. 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.
Re: jenkins clustering
Hello Sami, Rob, thanks for your replies. We are currently using redhat cluster to provide failover capabilities to jenkins master. Haven't tried Cloudbees Jenkins Enterprise either but from what' i've read, i assume failover capabilities are restricted to master failover, so functionally equivalent to what we have already achieved. I can't find any reference on slave resiliency in the event of a master failure, but i'll be really glad to be corrected from someone more knowledgeable than me on the enterprise product :) A presto, -m 2013/2/4 Mandeville, Rob rmandevi...@litle.com If you’re willing to pony up some money, you should talk to Cloudbees regarding their Enterprise version ( http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-overview.cb). I haven’t tried it (yet), but it comes with several plugins you can’t get otherwise, and one of them is a High Availability plugin. This specifically allows you to fail over to a second Jenkins master on the fly if the master dies. ** ** --Rob ** ** *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of *Matteo *Sent:* Tuesday, January 22, 2013 2:24 PM *To:* jenkinsci-users@googlegroups.com *Subject:* jenkins clustering ** ** Hello, ** ** first i'd like to thank developers for this great project. ** ** I'm sorry if already asked but i'm new on this list and searching the web has produced no results. ** ** We have a jenkins installation with 1 master and 5 slaves connected through ssh. ** ** We are mostly a java shop and jenkins is central to our infrastructure since we build and deploy releases to servers from it. ** ** For this reason slave resiliency in the face of master failure is paramount to us. ** ** My question: Is there a way, in a master/slave configuration, to have slave builds running to completion even in case of master failure (ideally refetching console logs once the master is back up :))? ** ** In our current setup, we get a proxy error on master UI and builds are aborted. ** ** Thanks in advance for any hint, ** ** -m 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. -- 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. -- 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.
Jenkins + Subversion + SSL client certificates
Hi all, Does there exist a definitive description on how to set Jenkins up to talk to a subversion repository that is protected by SSL client certificates? The native subversion client works perfectly, but the svnkit based client refuses to connect, failing with a handshake error. Does the Jenkins Subversion plugin look at the native subversion configuration at ~/.subversion/servers? Does the plugin look somewhere else? I have trawled the Jenkins UI, and apart from a few boilerplate options in the configure section there is no way to configure svn authentication at all. Is it supposed to be like this or am I doing something wrong? Regards, Graham -- -- 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.
Antwort: Jenkins + Subversion + SSL client certificates
Hi Graham, you know of http://YOURJENKINSINSTANCE/scm/SubversionSCM/enterCredential ? To my current knowledge this URL is still kind of unknown. At least when we set up SVN (like 2 years ago) we stumbled upon this more by accident than by knowing... After switching to hg some time ago I actually don't know alot about what's happening around the SVN integration in Jenkins, but I think this still is the way to pass the credentials. Kind regards, Andreas Schilling CAE Processes Data Management --- Dipl. Inf. Andreas Schilling Senior Software Architect TWT GmbH Science Innovation Bernhäuser Str. 40 - 42 73765 Neuhausen Tel: +49.7158.17 15.6 73 Mobil: +49.1 72.6 22 88 70 E-Mail: andreas.schill...@twt-gmbh.de www.twt-gmbh.de Geschäftsführung: Dimitrios Vartziotis, Joachim Laicher (Stv.), Frank Beutenmüller (Stv.) Registergericht: Amtsgericht Stuttgart, HRB Nr. 212778 Umsatzsteuer: ID-Nr.: DE147841145 Von:Graham Leggett minf...@sharp.fm An: jenkinsci-users@googlegroups.com Datum: 04.02.2013 15:43 Betreff:Jenkins + Subversion + SSL client certificates Gesendet von: jenkinsci-users@googlegroups.com Hi all, Does there exist a definitive description on how to set Jenkins up to talk to a subversion repository that is protected by SSL client certificates? The native subversion client works perfectly, but the svnkit based client refuses to connect, failing with a handshake error. Does the Jenkins Subversion plugin look at the native subversion configuration at ~/.subversion/servers? Does the plugin look somewhere else? I have trawled the Jenkins UI, and apart from a few boilerplate options in the configure section there is no way to configure svn authentication at all. Is it supposed to be like this or am I doing something wrong? Regards, Graham -- -- 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. -- 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: Antwort: Jenkins + Subversion + SSL client certificates
On 04 Feb 2013, at 4:50 PM, Andreas Schilling andreas.schill...@twt-gmbh.de wrote: you know of http://YOURJENKINSINSTANCE/scm/SubversionSCM/enterCredential ? To my current knowledge this URL is still kind of unknown. At least when we set up SVN (like 2 years ago) we stumbled upon this more by accident than by knowing... After switching to hg some time ago I actually don't know alot about what's happening around the SVN integration in Jenkins, but I think this still is the way to pass the credentials. I finally stumbled on a way to put the certificate in on a per project basis (highly non ideal, but I'll take anything that works at this point). Still no joy. The error I get is this: Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake The remote host disconnects because of this: SSL Library Error: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number All of these are deep protocol errors that are just dumped in a logfile, the actual error is discarded or ignored. Is there a way to get rid of svnkit entirely? In our case the native svn client works fine, we don't need this second client, it doesn't seem to work properly with digital certificates and/or SNI and has no error handling at all. Regards, Graham -- smime.p7s Description: S/MIME cryptographic signature
m2release plugin release:rollback
Hi, I came accross the request for release:rollback on failed release[1], however it is still marked as opened. From the wiki of the plugin[2] I can't figure out, if this feature is implemented or not and the RFE is one and half year old. Can someone give me an info? Or is there some other way to perform release:rollback after failed release? My very ugly solution was to set the SCM to None, run Pre-Build step with -B release:rollback goal and then dummy clean Build step, but as you can see this can only work with test jobs, because all config must be cleared :-( TIA [1] https://issues.jenkins-ci.org/browse/JENKINS-8263 [2] https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin -- 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: how to implement an invisible job property plugin
I'm interested in doing something similar. Which jelly file are you referring to? -- 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: m2release plugin release:rollback
Hi, It’s not supported (which is why the RFE is still open) and comments in the wiki are not monitored by the plugin maintainer. Wipe out workspace is probably the best form or release:rollback J maven won’t delete the tag if it created it anyway - so depending on what failed you may well need to do something by hand anyway. Regards, /James On Monday, 4 February 2013 16:58:34 UTC, Ilko wrote: Hi, I came accross the request for release:rollback on failed release[1], however it is still marked as opened. From the wiki of the plugin[2] I can't figure out, if this feature is implemented or not and the RFE is one and half year old. Can someone give me an info? Or is there some other way to perform release:rollback after failed release? My very ugly solution was to set the SCM to None, run Pre-Build step with -B release:rollback goal and then dummy clean Build step, but as you can see this can only work with test jobs, because all config must be cleared :-( TIA [1] https://issues.jenkins-ci.org/browse/JENKINS-8263 [2] https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin -- 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: Ensuring jobs operate on the same Git revision
Hi everyone, The Build Flow Plugin seems like a great way to orchestrate our build pipelines. I would like to ask if there is any best practice on how to ensure that all jobs in one pipeline checkout the same revisions of a Git repository. I believe the Git plugin initially sets the GIT_COMMIT environment variable and this value would have to be injected into the environments for all builds before they are run. I'd greatly appreciate your feedback, thank you! Johannes -- 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: m2release plugin release:rollback
I've seen release:rollback implemented as a Batch Task in a Maven build job. This was at my previous employer so I don't have access to the job anymore to give the details, but I think it is pretty straightforward. This way you can keep the rollback function together with the regular build job with no funny business about the SCM. It's true that if Maven has created tags, they won't be automatically deleted, but you can do that manually if needed. You may want to run maven release -DdryRun=true first to make sure there are no Maven errors before running the real build. DryRun won't commit any changes to source control. Regards, Eric On 2/4/2013 12:28 PM, teilo wrote: Hi, It’s not supported (which is why the RFE is still open) and comments in the wiki are not monitored by the plugin maintainer. Wipe out workspace is probably the best form or release:rollback J maven won’t delete the tag if it created it anyway - so depending on what failed you may well need to do something by hand anyway. Regards, /James On Monday, 4 February 2013 16:58:34 UTC, Ilko wrote: Hi, I came accross the request for release:rollback on failed release[1], however it is still marked as opened. From the wiki of the plugin[2] I can't figure out, if this feature is implemented or not and the RFE is one and half year old. Can someone give me an info? Or is there some other way to perform release:rollback after failed release? My very ugly solution was to set the SCM to None, run Pre-Build step with -B release:rollback goal and then dummy clean Build step, but as you can see this can only work with test jobs, because all config must be cleared :-( TIA [1] https://issues.jenkins-ci.org/browse/JENKINS-8263 https://issues.jenkins-ci.org/browse/JENKINS-8263 [2] https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin -- 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. -- 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.
Not a problem; Re: All my added build descriptions and keep build forever annotations gone!
Solved this issue. This was not a bug. It was pilot error. Doh! -- 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.
$HOSTNAME in email-ext plugins
We would like Jenkins to include the machine name of the slave it used when
it sends an email. On windows slaves, this is solved by using ${ENV,
var=COMPUTERNAME}. This uses the Token Macro expansion plugin to grab the
%COMPUTERNAME% environment variable.
However, this doesn't seem to work with $HOSTNAME (the Unix equivalent).
Strangely, it does work for other Unix variables, like $HOME. Additionally,
when I put 'echo $HOSTNAME' in an 'execute shell' build step, it also
works. Is there some reason that this particular variable doesn't expand?
Is there an alternate method I could use?
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: $HOSTNAME in email-ext plugins
I'd recommend using the NODE_NAME variable instead. It works cross platform.
On Mon, Feb 4, 2013 at 1:00 PM, Foxgang teve...@gmail.com wrote:
We would like Jenkins to include the machine name of the slave it used
when it sends an email. On windows slaves, this is solved by using ${ENV,
var=COMPUTERNAME}. This uses the Token Macro expansion plugin to grab the
%COMPUTERNAME% environment variable.
However, this doesn't seem to work with $HOSTNAME (the Unix equivalent).
Strangely, it does work for other Unix variables, like $HOME. Additionally,
when I put 'echo $HOSTNAME' in an 'execute shell' build step, it also
works. Is there some reason that this particular variable doesn't expand?
Is there an alternate method I could use?
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Website: http://earl-of-code.com
--
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.
arcvhiving takes forever - just me?
Hi all - Super quick question - maybe this is a known issue When archiving a large artifact, jenkins seems to take forever (in some cases, taking a 1 min build up to 30 min). What's weird is when I ssh up to that same slave and scp over that same artifact to the same final location, it takes less than 10 seconds. Suggestions? -- 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.
Jenkins Slave + Maven: How do I pass parameters to maven?
Hi all, In order to run the normal maven command line client, I need to pass various -D parameters to make SSL client certificates work, and this works fine. Maven run via a Jenkins slave maven build however, no joy at all, all I get is a handshake error. As a result, maven is definitely not running with the correct -D parameters when spawned from a Jenkins slave. Is there a definitive process that allows you to pass -D parameters to maven? I have tried to add them to JDK options of the slave, but this makes no difference. I suspect that the JDK environment of the slave is not passed to maven when it is cranked up, but I cannot find anything to definitively prove this, or any documentation that explicitly describes Jenkins' behaviour. Regards, Graham -- -- 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.
Hudson and Jenkins slave?
Before I start, I just want to acknowledge that this is an odd ball question and may or may not be applicable to this group. I am in the process of converting to Jenkins from Hudson, so I currently have two master nodes, one for each version. I also have 26 slaves. Right now they are in use by the Hudson master. These are my production environment and are in use, pretty much every day. I would like to test the Jenkins master against the slave nodes but there can only be one and only one job running on a slave node at any time. My production environment will remain Hudson until I can be assured that Jenkins is up and running correctly. So here's the odd-ball question: is there a way to have the Jenkins master (or Hudson master) respect the one-and-only-one job per slave constraint? For concreteness, here's a test scenario: 1) Hudson master kicks off a job on slave tm22 2) Jenkins master wants to kick off a job on slave tm22 but holds off until the current (Hudson) job on tm22 completes. 3) Jenkins detects the job is complete and triggers a job on tm22 4) and Hudson master does the same thing: it waits till the current job on tm22 finishes and then triggers it's own job. Thanks for your patience and help, John -- 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: jenkins clustering
Oh you really meant you want your slaves to HA! Usually people just have so many slaves it doesn't matter if some go down. -- Sami Matteo Centonza mat...@metatype.it kirjoitti 4.2.2013 kello 16.37: Hello Sami, Rob, thanks for your replies. We are currently using redhat cluster to provide failover capabilities to jenkins master. Haven't tried Cloudbees Jenkins Enterprise either but from what' i've read, i assume failover capabilities are restricted to master failover, so functionally equivalent to what we have already achieved. I can't find any reference on slave resiliency in the event of a master failure, but i'll be really glad to be corrected from someone more knowledgeable than me on the enterprise product :) A presto, -m 2013/2/4 Mandeville, Rob rmandevi...@litle.com If you’re willing to pony up some money, you should talk to Cloudbees regarding their Enterprise version (http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-overview.cb). I haven’t tried it (yet), but it comes with several plugins you can’t get otherwise, and one of them is a High Availability plugin. This specifically allows you to fail over to a second Jenkins master on the fly if the master dies. --Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Matteo Sent: Tuesday, January 22, 2013 2:24 PM To: jenkinsci-users@googlegroups.com Subject: jenkins clustering Hello, first i'd like to thank developers for this great project. I'm sorry if already asked but i'm new on this list and searching the web has produced no results. We have a jenkins installation with 1 master and 5 slaves connected through ssh. We are mostly a java shop and jenkins is central to our infrastructure since we build and deploy releases to servers from it. For this reason slave resiliency in the face of master failure is paramount to us. My question: Is there a way, in a master/slave configuration, to have slave builds running to completion even in case of master failure (ideally refetching console logs once the master is back up :))? In our current setup, we get a proxy error on master UI and builds are aborted. Thanks in advance for any hint, -m 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. -- 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. -- 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. -- 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.
答复: how to implement an invisible job property plugin
I want to use a JobPropertyDescriptor, where add a creator property, it’s saved
when job is created, and cannot be changed later, so we went this property is
visible to user.
public final class JobCreatorProperty extends JobPropertyAbstractProject?,?
{
private String creator;
public String getCreator(){
return creator;
}
public void setCreator(String creator){
this.creator = creator;
}
@Extension
public static final class DescriptorImpl extends JobPropertyDescriptor{
public DescriptorImpl(){
super(JobCreatorProperty.class);
…
}
发件人: Walter Kacynski [mailto:walter.kacyn...@gmail.com]
发送时间: 2013年2月5日 1:10
收件人: jenkinsci-users@googlegroups.com
抄送: Shen,Hui
主题: Re: how to implement an invisible job property plugin
I'm interested in doing something similar. Which jelly file are you referring
to?
--
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: m2release plugin release:rollback
Thanks for the info. Wipe out the workspace will leave the versions as changed during the prepare stage. IMHO this feature will be very helpful to revert to a stable stage w/out too much extra magic. It's true that the tag must be removed manually, if it has been created, but in our case this could be done direct from the IDE. On opposite, the build infrastructure is not in our (developers) full control and it is not so trivial to execute rollback from the shell because of the file permissions. On 04.02.2013, at 18:39, Eric Pyle eric.p...@cd-adapco.com wrote: I've seen release:rollback implemented as a Batch Task in a Maven build job. This was at my previous employer so I don't have access to the job anymore to give the details, but I think it is pretty straightforward. This way you can keep the rollback function together with the regular build job with no funny business about the SCM. It's true that if Maven has created tags, they won't be automatically deleted, but you can do that manually if needed. You may want to run maven release -DdryRun=true first to make sure there are no Maven errors before running the real build. DryRun won't commit any changes to source control. Regards, Eric On 2/4/2013 12:28 PM, teilo wrote: Hi, It’s not supported (which is why the RFE is still open) and comments in the wiki are not monitored by the plugin maintainer. Wipe out workspace is probably the best form or release:rollback J maven won’t delete the tag if it created it anyway - so depending on what failed you may well need to do something by hand anyway. Regards, /James On Monday, 4 February 2013 16:58:34 UTC, Ilko wrote: Hi, I came accross the request for release:rollback on failed release[1], however it is still marked as opened. From the wiki of the plugin[2] I can't figure out, if this feature is implemented or not and the RFE is one and half year old. Can someone give me an info? Or is there some other way to perform release:rollback after failed release? My very ugly solution was to set the SCM to None, run Pre-Build step with -B release:rollback goal and then dummy clean Build step, but as you can see this can only work with test jobs, because all config must be cleared :-( TIA [1] https://issues.jenkins-ci.org/browse/JENKINS-8263 [2] https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin -- 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. -- 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. -- 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.
Unable to find current vision in submodule path 'corelibs''
Hi, I'm having an issue where I can't get Jenkins to checkout a project that has a submodule in it (which contains further submodules), but I am able to do so myself. For instance, if I manually run: git clone [repository-url] [chdir into repository] git submodule update --recursive --init Everything goes fine. Everything also goes fine if I manually do git submodule init and git submodule update as necessary, recursively. However, I seem to run into problems using Jenkins and get the following: FATAL: Command git submodule update returned status code 1: stdout: stderr: fatal: Needed a single revision Unable to find current revision in submodule path 'corelibs' hudson.plugins.git.GitException http://stacktrace.jenkins-ci.org/search?query=hudson.plugins.git.GitException: Command git submodule update returned status code 1: stdout: stderr: fatal: Needed a single revision Unable to find current revision in submodule path 'corelibs' at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:897) Would anyone have any idea how I could go about fixing this? I'm not really too familiar with the inner workings of git, but the repositories seem to be okay since I can do everything by hand. -- 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.
