Is it possible for a log to be generated that lists which Jenkins Plugins were active during a build?
*Is there a Jenkins Plugin that can create a log that lists which Jenkins Plugins were active during a build?* This would make it possible for our team to detect which Jenkins Plugins are not being used, and could therefore be safely deleted. Also, if the Jenkins plugins active during a build done on a Live (i.e. Production) Master Server could be recorded, this would be very helpful in setting up the correct set of Jenkins plugins to be installed and tested in a Test Master Server Creating a list of Jenkins Plugins used in a build would be difficult, since the program would have to be able to detect the dependencies (and recursive dependencies) for each Jenkins Plugins that was active in a build, as your build proceeded from one Jenkins job to another. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4f1a878a-f704-41d8-940d-ce6dd6ce3525%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Having Trouble with Inheritable Parameters in Jenkins, value zero is interpreted as null
I am having trouble with Inheritable Parameters in Jenkins
My build system is still based on Build Flow, I have not converted to
Pipeline yet
My Jenkins version is 2.5
My "Project-Inheritance" plugin version was originally 2.0, I rolled back
to 1.5.3 later, but am having the same problem with inherited parameters
All inherited parameters are passed down normally, except if they have a
value of zero ("0")
The project which inherits parameters gets all of them correct, except that
If the inherited parameter has a value of zero ("0") , the project thinks
its value is null.
Does anyone know why this could be happening?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/c3b71090-3341-428f-830c-bd67f30ee891%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Need location of Jenkins 2.5 msi file
In the Jenkins website there is an article "Windows installers are now available" https://jenkins.io/blog/2011/03/23/windows-installers-are-now-available/ Does anyone know the internet location from which Jenkins msi's can be downloaded? I would especially like to download a Jenkins msi for Jenkins v2.5. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b40ff9e8-51c4-4186-9e24-94a0e2ff536e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?
Anyone is free to answer this question: Is there any scenario in which Jenkins plugins filenames, associated with Jenkins 2.5, might have had their plugin file extensions changed from *.hpi to *.jpi, in the absence of human intervention or human error? ++ On Tuesday, November 8, 2016 at 9:40:24 AM UTC-6, Robert Kruck wrote: > Based on your result, and based on the fact that no one in our group > touched Jenkins Plugins in any way (in our build servers), is it possible > that some sort of internal code in our Jenkins main installation (we are > using Jenkins 2.5, which was installed earlier this year) could have > changed on its own our Jenkins plugin file extensions from *.hpi to *.jpi? > > Or is this impossible and has this change occurred because of some human > error that occurred in the Jenkins\Plugins folders in our build machines? > > On Tuesday, November 8, 2016 at 9:19:26 AM UTC-6, Daniel Beck wrote: > >> >> > On 08.11.2016, at 15:59, Robert Kruck <robert...@gmail.com> wrote: >> > >> > I would expect all the renamed *.jpi Jenkins plugins to have "Date >> Modified" updated to November 2016, but the "Date Modified" for all the >> renamed *.jpi Jenkins plugins is June 15, 2016 or earlier. >> >> I just booted up a Windows 8.1 test VM and tried it: Renaming a file does >> not change the modification date on Windows. >> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5d4188a4-580c-4cf8-bbbd-3b1a1ebf72a4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?
Based on your result, and based on the fact that no one in our group touched Jenkins Plugins in any way (in our build servers), is it possible that some sort of internal code in our Jenkins main installation (we are using Jenkins 2.5, which was installed earlier this year) could have changed on its own our Jenkins plugin file extensions from *.hpi to *.jpi? Or is this impossible and has this change occurred because of some human error that occurred in the Jenkins\Plugins folders in our build machines? On Tuesday, November 8, 2016 at 9:19:26 AM UTC-6, Daniel Beck wrote: > > > On 08.11.2016, at 15:59, Robert Kruck <robert...@gmail.com > > wrote: > > > > I would expect all the renamed *.jpi Jenkins plugins to have "Date > Modified" updated to November 2016, but the "Date Modified" for all the > renamed *.jpi Jenkins plugins is June 15, 2016 or earlier. > > I just booted up a Windows 8.1 test VM and tried it: Renaming a file does > not change the modification date on Windows. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bdef6722-8f31-45b3-87bd-72fa2f265ea9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?
By timestamp I mean date plus time of day (hours, minutes, AM or PM) For all of these renamed (from *.hpi to *.jpi), their "Date Modified" and "Date Created", without exception, are June 15, 2016 or earlier. I would expect all the renamed *.jpi Jenkins plugins to have "Date Modified" updated to November 2016, but the "Date Modified" for all the renamed *.jpi Jenkins plugins is June 15, 2016 or earlier. Example, taken from Windows Explorer in the Jenkins/Plugin folder of one of our build machines (this file only last week was called versionnumber.hpi): NameDate Modified Date Created versionnumber.jpi 6/15/2016 2:10 PM 9/16/2014 11:28 AM + On Tuesday, November 8, 2016 at 8:36:11 AM UTC-6, Daniel Beck wrote: > > > On 08.11.2016, at 15:29, Robert Kruck <robert...@gmail.com > > wrote: > > > > One would think a new filename would lead to a new timestamp for the > renamed file. > > Not sure what you mean by 'timestamp'. mtime or ctime? Only the latter > changes on rename, and e.g. `ls -l` only shows the former. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/91c244ed-8604-47f2-9a70-689562638d1d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?
ALL Jenkins plugins, in all three of our build servers which have Jenkins plugins, were in the past week renamed from *.hpi to *.jpi. The timestamps of the renamed plugins are unchanged, the newest such timestamp is June 15, 2016. I would expect that if some human intervention had occurred in the build machines - deliberately or by accident - the timestamps of these Jenkins plugins, now ending in *.jpi, would now have November 2016 timestamps, but this is not the case, their timestamps remain June 15, 2016 or earlier, which is very confusing. One would think a new filename would lead to a new timestamp for the renamed file. On Tuesday, November 8, 2016 at 8:12:37 AM UTC-6, Daniel Beck wrote: > Which plugins are affected by this? > > Jenkins normalized plugin names to jpi when extracting bundled plugins, > when uploading through the UI, and when downloading from an update site. > But rename of existing files doesn't happen AFAIK. > > > On 08.11.2016, at 14:03, Robert Kruck <robert...@gmail.com > > wrote: > > > > We have Jenkins plugins installed on three Jenkins Master build servers. > > > > Until very recently all Jenkins plugins files in the Jenkins/Plugins > folders of these three build servers had a filename ending in *.hpi. > > > > When I looked into these folders yesterday all the Jenkins plugins files > now have a filename ending in *.jpi. > > > > Timestamps of these *.jpi files are unchanged -- the newest timestamp is > June 15, 2016. > > > > There was no human intervention that could have caused this change in > the Jenkins plugins filenames from *.hpi to *.jpi. > > > > Has anyone else seen this? Does anyone know how this could have > happened? How can a Jenkins installation update its plugin filenames on its > own, from *.hpi to *.jpi, without human intervention? > > > > > > -- > > You received this message because you are subscribed to the Google > Groups "Jenkins Users" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to jenkinsci-use...@googlegroups.com . > > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/d8febd04-6ce4-4506-8d88-324d88fd0f15%40googlegroups.com. > > > > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/36304936-fa5a-4158-bab9-53d23fe9d460%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Why have our Jenkins/Plugins *.hpi files changed to *.jpi files?
We have Jenkins plugins installed on three Jenkins Master build servers. Until very recently all Jenkins plugins files in the Jenkins/Plugins folders of these three build servers had a filename ending in *.hpi. When I looked into these folders yesterday all the Jenkins plugins files now have a filename ending in *.jpi. Timestamps of these *.jpi files are unchanged -- the newest timestamp is June 15, 2016. There was no human intervention that could have caused this change in the Jenkins plugins filenames from *.hpi to *.jpi. Has anyone else seen this? Does anyone know how this could have happened? How can a Jenkins installation update its plugin filenames on its own, from *.hpi to *.jpi, without human intervention? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d8febd04-6ce4-4506-8d88-324d88fd0f15%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
I need to know Bundled Plugins version numbers for Jenkins 2.5
For Jenkins 2.5 I know which are its bundled plugins by examining the *.hpi files associated with Jenkins 2.5, but I don't know the versions of these plugins. I know there are scripts to find out bundled plugins' versions but I am not allowed to download them to my workplace computer. Does anyone know the version numbers, of the Jenkins 2.5 bundled plugins listed below: ModeLastWriteTime Length Name - -- -a--- 6/15/2016 11:09 AM 90421 ant.hpi -a--- 6/15/2016 11:09 AM 112483 antisamy-markup-formatter.hpi -a--- 6/15/2016 11:09 AM 406478 credentials.hpi -a--- 6/15/2016 11:09 AM 929025 cvs.hpi -a--- 6/15/2016 11:09 AM 55546 external-monitor-job.hpi -a--- 6/15/2016 11:09 AM 38073 javadoc.hpi -a--- 6/15/2016 11:09 AM 331127 junit.hpi -a--- 6/15/2016 11:09 AM 101895 ldap.hpi -a--- 6/15/2016 11:09 AM 128645 mailer.hpi -a--- 6/15/2016 11:09 AM 79681 matrix-auth.hpi -a--- 6/15/2016 11:09 AM 238601 matrix-project.hpi -a--- 6/15/2016 11:09 AM 10805330 maven-plugin.hpi -a--- 6/15/2016 11:09 AM1030550 pam-auth.hpi -a--- 6/15/2016 11:09 AM 164546 script-security.hpi -a--- 6/15/2016 11:09 AM 74973 ssh-credentials.hpi -a--- 6/15/2016 11:09 AM 64366 ssh-slaves.hpi -a--- 6/15/2016 11:09 AM4683101 subversion.hpi -a--- 6/15/2016 11:09 AM 50065 translation.hpi -a--- 6/15/2016 11:09 AM 949638 windows-slaves.hpi -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ead9f36b-f730-48c6-b877-b3f46a6d9d9b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Maintaining a unique Build Number across multiple build servers
On Monday, September 19, 2016 at 2:54:15 PM UTC-5, Robert Kruck wrote: > > Is it possible to preserve the integrity of build numbers (NO DUPLICATES > and build numbers in order) while building in multiple Jenkins build > servers? > > If this capability exists in Jenkins, what Jenkins plugins are required, > and what versions of Jenkins itself, and of the required Jenkins plugins, > are needed? > Would the simplest solution to maintain build number integrity across multiple Jenkins servers be to: a) Create a versioned ini file (in our case, a StarTeam file in a *.ini format), containing the latest 5-digit build number. b) The above StarTeam file would be visible to all our build scripts, no matter what Jenkins server they were located in. c) When a build script is under way, it would do an EXCLUSIVE checkout of the StarTeam build number ini file. (Perhaps a wait time could be added to this checkout step, in case the above file was checked-out & locked at the time by another build script). d) The build script increments the build number in the build number ini file using WriteINI, and uses this incremented build number for its build. e) Finally, the build script checks in the StarTeam build number ini file, so it is unlocked / correctly updated / and visible to other build scripts in other Jenkins servers. 1) Obtaining the build number via a versioned *.ini file would seem to have no problems for an interactive, non-Jenkins build. 2) Would obtaining the build number via a versioned *.ini file, rather than a build number generated by Jenkins, be practical in a build done through Jenkins? 3) Is the above "versioned build number *.ini file" concept reasonable, or would use of Jenkins plugin(s) & Windows Environment variables be the best way to reliably increment, then communicate, build numbers across multiple Jenkins servers? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/26118b34-d8e1-4e5b-b3f4-1eb5eb669159%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Can Jenkins builds be launched in a specific order?
Can Jenkins builds be launched in a specific order? We are launching Jenkins builds using a spreadsheet in which the needed parameters for each Jenkins build appear in each row of the spreadsheet. We would prefer that Jenkins builds be done in a priority order, instead all the Jenkins builds whose parameters are specified in the above spreadsheet are done, but are done in a random order that has nothing to do with our build priorities. Does Jenkins have the capability of doing builds in a specified order rather than in random order? If so, which Jenkins plugins would be needed? And which Jenkins version and Jenkins plugins version would be required? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6a471cd9-4d91-4a36-9521-72d7425b97ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Maintaining a unique Build Number across multiple build servers
Is it possible to preserve the integrity of build numbers (NO DUPLICATES and build numbers in order) while building in multiple Jenkins build servers? If this capability exists in Jenkins, what Jenkins plugins are required, and what versions of Jenkins itself, and of the required Jenkins plugins, are needed? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20ee1dbf-587f-4f11-ae55-9ae7d0f195e7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Can the “Throttle Concurrent Builds Plugin" be used to reliably prevent concurrent builds in a multi-server, "build farm" setting?
Can the “Throttle Concurrent Builds Plugin" be used to reliably prevent concurrent builds in a multi-server, "build farm" setting? Example: if the Build Farm consisted of Master Server, Slave Server 1, Slave Server 2, Slave Server 3 - could the master server request three builds, for three versions of the same software, and all these builds (1 per server) would launch concurrently? (Max Concurrent Builds, Max Concurrent Builds Per Node both set to "1"). Also, can the “Throttle Concurrent Builds Plugin" handle load balancing, choosing the "least busy" of the available servers? Or would a build of a given type be launched on the same server where it was most recently launched? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/010e5b7e-7e1a-4d5f-b0a3-9b0857675f88%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Does the Jenkins Manage Plugins page display a warning if a plugin has a missing dependency?
Does the Jenkins "Manage Plugins" page display a warning, if a Jenkins Plugin has a missing dependency? Example: If *Jenkins Plugin "A"* requires *Jenkins Plugin "B"* as a dependency, and I installed Jenkins Plugin "A" * only*, would a warning about the missing *Jenkins Plugin "B"* appear in the Jenkins "Manage Plugins" page? I have researched this issue for some time on the internet - at present it appears that some Jenkins plugins have this sort of automated dependency checking, but others don't. Please advise; I was thinking of making a spreadsheet to show the dependencies of the Jenkins Plugins we currently use - but if Jenkins has automated dependency checking for all its Plugins, such a spreadsheet would obviously be a waste of time. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d8b2f1ad-0cfc-4197-9876-2c534b46807b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How can semaphores be used to avoid race conditions in Jenkins?
On Thursday, May 5, 2016 at 7:44:47 AM UTC-5, Robert Kruck wrote: > > How can semaphores be used to avoid race conditions in Jenkins? > > We have Jenkins projects that apply StarTeam labels to file versions. > > All labeling for each software package must be completed, before going on > to label another software package. > > Is there a Jenkins plugin that can reliably prevent more than one Jenkins > project from executing on the same resources (i.e. build server)? > > Can this also be done if the master+slaves setup is in the form of a build > farm, in which the risk of concurrency is extreme if a semaphore-like model > is not being used? > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/024f9fd0-5d71-4381-9936-08648e7e4798%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
How can semaphores be used to avoid race conditions in Jenkins?
How can semaphores be used to avoid race conditions in Jenkins? We have Jenkins projects that apply StarTeam labels to file versions. All labeling for each software package must be completed, before going on to label another software pages. Is there a Jenkins plugin that can reliably prevent more than one Jenkins project from executing on the same resources (i.e. build server)? Can this also be done if the master+slaves setup is in the form of a build farm, in which the risk of concurrency is extreme if a semaphore-like model is not being used? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9bf6438d-390c-4cc6-9b19-866a2b7013a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
